DESIGN PHASE #5
Lol :)
I changed the design one more time

Progress

• I tried changing the design of the top case to look like a wave from the side and ig it resembles it a little
• Also I added much needed curves to the design

I’ll provide the screenshots but also checkout the guithub page!! :)

DESIGN PHASE #5
Lol :)
I changed the design one more time

Progress

• I tried changing the design of the top case to look like a wave from the side and ig it resembles it a little
• Also I added much needed curves to the design

I’ll provide the screenshots but also checkout the guithub page!! :)

DESIGN PHASE #4

Yess!!!
I’m done with the firmware finally and I also wrote a README

The firmware has functionsREADME has it:-

• Media controls
• volume controls with mute switch on the rotatory encoder
• Fullscreen

Also wrote the list of components used for the project

DESIGN PHASE # 3

Finaalyy im done with the design and we are into the final steps of the designing phase

Things Done

• Switched between 3 different designs and finally I’m moving with this one
• Rerouted the PCB properly
• Completed the CAD

Things left

• The firmware is left I'm thinking of using circuit python to write that :)
• Write the README.md file for the repo and we’ll be done ig

DESIGN PHASE #2

The LED errors man
Anyways,

Progress

• Added an OLED screen
• Added 2 LEDs to the pcb but they were causing errors
• Redesigned the pcb thinking the error was caused by something that I may have done wrong but that wasn’t the case

Next??

• Add hackclub logos to make the pcb look cooler
• Wait for someone to help me fix the LED problem
• Design the case for the pcb

Learnt

• Learnt more about how kicad pcb editor works (footprints and symbols)

What we currently have?

• 2x LEDs
• 1x OLED screen
• 4x keys
• 1x Volume knob/rotatory encoder switch

DEVLOG 1

Hey all,
I’m new to hardware stuff and decided to begin with this hackpad mission.

What have I done?

I started with the awsome tutorial for hackpad then tried to customize it.
I have addded

• 4 keys
• A volume knob

Next??

I’ll be adding a oled screen first which will be displaying a cute companion typa thing (still didnt figure out the name).

Where did I spend most of the time??

• The most time went into schematics as im new I had made soo many mistakes that I realised I had made by watching some yt videos
• The most fun part was to tinker in PCB editor and watch what the pcb looks like in the 3-d viewer

DESIGN PHASE #4

Yess!!!
I’m done with the firmware finally and I also wrote a README

The firmware has functionsREADME has it:-

• Media controls
• volume controls with mute switch on the rotatory encoder
• Fullscreen

Also wrote the list of components used for the project

DESIGN PHASE # 3

Finaalyy im done with the design and we are into the final steps of the designing phase

Things Done

• Switched between 3 different designs and finally I’m moving with this one
• Rerouted the PCB properly
• Completed the CAD

Things left

• The firmware is left I'm thinking of using circuit python to write that :)
• Write the README.md file for the repo and we’ll be done ig

DESIGN PHASE #2

The LED errors man
Anyways,

Progress

• Added an OLED screen
• Added 2 LEDs to the pcb but they were causing errors
• Redesigned the pcb thinking the error was caused by something that I may have done wrong but that wasn’t the case

Next??

• Add hackclub logos to make the pcb look cooler
• Wait for someone to help me fix the LED problem
• Design the case for the pcb

Learnt

• Learnt more about how kicad pcb editor works (footprints and symbols)

What we currently have?

• 2x LEDs
• 1x OLED screen
• 4x keys
• 1x Volume knob/rotatory encoder switch

DEVLOG 1

Hey all,
I’m new to hardware stuff and decided to begin with this hackpad mission.

What have I done?

I started with the awsome tutorial for hackpad then tried to customize it.
I have addded

• 4 keys
• A volume knob

Next??

I’ll be adding a oled screen first which will be displaying a cute companion typa thing (still didnt figure out the name).

Where did I spend most of the time??

• The most time went into schematics as im new I had made soo many mistakes that I realised I had made by watching some yt videos
• The most fun part was to tinker in PCB editor and watch what the pcb looks like in the 3-d viewer

DAGIT DEVLOG 5

yoo once again!

I’ve worked on the features I’ve been delaying and let’s see the progress

Progress Overview

• I first worked on the idea i got yesterday A status panel to see staged/modified files

• Then I tried to work on scrollbars in the git log and the visualizer but I failed to do so I just scrapped it completely and reset the repo to the after status panel state

• After scrapping that, I worked on the tick rate selection Intervals of time at which we update the data displayed in the TUI

DETAIL

• The status panel idea had come when I was surfing git hub and was just looking at lazygit (A far better project than dagit btw). I saw the same panel there and thought of adding it here because it would make more sense, although dagit is different from lazygit (dagit is only trying to visualze git not become a workflow)

• The scrollbars were out of my league I already knew that but still gave a try. I dont think I would be giving up on the idea. I’ll just watch some tutorials on bubbletea and scrollbars specifically before working on it again

• At first, I thought I would make the tick rate selector a separate panel where we would just scroll through different intervals of time, but as I consider myself lazy I just thought of adding it in such a way that instead of scrolling we change the tick rate with the press of buttons. Although the max tickrate is already small(10sec) I recommend using 1sec on small projects

DAGIT DEVLOG 4

Yoo!
I’ve made soo many updates and the resizing /clipping issues are still eating my brain like bugs

Progress overview

• Decreased the sizes of reference being displayed also truncated lines in the gitlog so that the vertical clipping stops

• I completely styled the UI using lipgloss and it looks soo much better now

• Added highlighting to the head of the repo that pops a little more

• Refactored the old way of refreshing the data

• Refactored the code to increase readability

Explain

• The git logs were looking odd because when the commit messages were long , the log that should only take the space of one line was now also taking space in the second line. So we fixed it using truncateMessages() function

• As we are pushig to multiple tags . The reference also gets long and causes a clipping issue again. So we again simply dosent let the refs be that long[But the current implementation can cause the line to break suddenly that may not look good all the time]-

// Stop 'refs' being too long
if lipgloss.Width(refs) > 30 {
	refs = refs[:27] + "..."
}

• And as dagit is a live visualizer, I removed the old way of refreshing the data[clicking [r] to refresh]. Now what we do is use tea.Tick and the time library to refresh the data every 1 second.

Issues that can be caused

• We are currently refreshing data every second that can put a lot more load on the system when used inside a big repository, So in infuture I’m gonna work to give the user a way to choose the tick Rate

What im gonna work on now

• Scrollbar for gitlog and also visualizer
• A tick rate selector
• File status panel that can be toggled with the visualizer
• A way to search for different repo’s in the user’s computer and jumping between them(something like the nvim feature of finding files) –im not really sure of this

DAGIT DEVLOG 3

Yay!
we have got the release workflow up and running

What we are doing

• what we do is make new binaries name dagit-linux-amd64.tar.gz and dagit-darwin-arm64.tar.gz
  and push them to our releases page with the tag given while pushing to the repo

• We also push to the AUR!! . So all the I use arch btw people can download it easily

Installation

• AUR

yay -S dagit-bin

• Run in a github repo ,ie paste->dagit

• Github releases

• go to the releases page and download the binaries zip, extract it and run in a github repo

DAGIT DEVLOG 2

We’ve improved the TUI soo much!!

What I’ve done

• Got gitlog working with hash, commit message and the contibuter
• Made a somewhat good looking git visualizer and fixed the horizontal and vertical border issue caused by big lines (reference mainly)
• Styled the git visualizer with charm’s lipgloss
• Fixed border issues in the footer and git log too
• Also made dagit resize when the user makes the terminal window larger but idk why it doesnt work when the terminal window is shortened
• I also added a resize keybindr to reload the data in the TUI so that the user does not need to stop it and run again for it to update to latest info

Issues faced

I haven’t faced any big issue in particular but figuring out resizing is the only thing that eats my brain

Where I spent the most time

I have spent the most time making the visualizer, lemme explain a little of it’s woking !!

• First we fetch the git log graph from git and then we spread the graph by using SpreadGraph function in graph.go to make it look a little better
• Then we get 15 of the graph lines into out TUI and then render it using lipgloss [Man charm’s tool are soo cool and make CLI/TUI look soo good]. Although we don’t see all the 15 lines as we dont have a scroll feature for now

What we are going to do

• Style it
• Fetch number of commits done to the repo and display it
• Add scrollbar to git visualizer
  _ Also add scrollbar to git log -Not sure

What I currently feel

When I was planning to make dagit, I felt it’ll be different and will attract people towards it but it’s not upto my expectation.
I thinking to adding some feature that will make more people use it

DAGIT DEVLOG 1

(BTW WHOEVER ADDED EMOJIS OPTION SHOULD BE PROMOTED )
Hii,
I’m making a TUI application that beautifully visualizes your GitHub repo inside your terminal!!

Note -> This devlog is a compilation of 2 days of work that I’ll explain

What I have done

DAY 1:

I started working on dagit with first:

• Checking if the current directory is a git repo or not
• If yes, we first fetch the repo name along with
• owner of the repo
• the remote url of current repo
• current branch
  Lmao, this was all I did on day 1

DAY 2

Today the fun began

• I started working on the TUI section
• I started with a simple bubble tea list TUI to remember the simple things that I had forgot in these many days
• Then I used bubbletea to render the left panel containing the the data we fetched from day one but I realised that this is messed up cuz I wont be able to make different sections for the visualizer and the git log history
• When I searched for a fix I saw lipgloss and then integrated it with our current setup
• I used lip gloss to make diffferent sections for our TUI. The sections that I currently want in the TUI left panel/middle(visualizer)/ bottom(git log) along with the footer like nvim
• But I forgot about the resizing problem and idk anything about how I’m going to fix it like other TUI’s do so I’m donna leave it like tat for now

What I’m gonna do

• Make it look prettier
• Get the git log because it’s gonna be easier than the visualizer
• Make my shit code look a little better

GOS DEVLOG 13

On the last devlog I had gos making .gos folder in the homedirectory of the user where it stores custom templates made by the user

What I have got new

I have added two new features:

• gosadd
• gosget

-[gosadd]

• We use the this command to add any folder as a template that we can later use with a different command

• We have got a -a flag to add to folder. Although we wont be using this flags because I have got a way to make it easier and faster to type in the terminal and have given the solution in README.md in [After installation]

-[goget]

• We use this command to fetch the copied folder from .gos/usr_Templates to the current directory we are on

• “gosget” uses two flags:
  – -p –> We use this to give in the new name of the template folder that will be saved in the current directory
  – -e –> We use this to get the correct template that we have stored

• Both -p and -e default values are an empty string so passing a value in necessary for it to work

GOS DEVLOG 12

I’ve made it so that when you run the newest version 0.9.1 which I havent released yet. It automatically creates a .gos folder in the user’s home directory and it’ll be the place where is store custom templates made by the user

I still dont know

I’ve to figure out how do we walk through the current directory and store in the usr_Templates and somehow copy paste it when the user requests that specific template

Other

I still haven’t worked on the project properly due to my school. I currently have 9 hrs to figure out how we are going to move forward = )

GOS DEVLOG 11

I’ve read the reviews by you guys and have found out that:

• Gos needs to have a way so that the user is able add their own templates

• Few ppl also said that initializing a git repo when making a project will be very helpful

• One review was about some bugs that he face in the tool I dont know what he had faced because the version that I had shipped was 0.6.5 and I’m currently working on 0.9.0. If anyone did face them too can you please tell me?

• One guy asked me why did I name Gos as gos so for you:
  The name Gos can be broken down like this : D

Gos
"Go" --> The language 'Golang'
"s" --> from 'Structure'

The first name that I had thought for was Gostruc. But it felt too big to type in the terminal when compared to mkdir and tree

• I’m also thinking about adding a tree like command in this project. Can you guys tell if I should do that ?

I really appretiate your reviews guys and I’ll be working on improving this project. Hoping that it stays a little relevant :(

– Bye