DESIGN PHASE #7
The case came!!!! :yayya
Had to choose black color for the top because they didn’t have blue :(
Nothing much…….
I’m currently waiting for the hackpad kit and pcb to come and start building

Also I had some short cirsuits in the gerbers.zip so i just updated them and sent it back to robu
Let’s see when the pcb arrives

DESIGN PHASE #7
The case came!!!! :yayya
Had to choose black color for the top because they didn’t have blue :(
Nothing much…….
I’m currently waiting for the hackpad kit and pcb to come and start building

Also I had some short cirsuits in the gerbers.zip so i just updated them and sent it back to robu
Let’s see when the pcb arrives

Update #1

There isnt much we have fixed some issues that were being cause because of the way we fetch data from git

DESIGN PHASE #6

As adviced by a fellow hackclubber @Tensor
I have removed the overhang from the macropad
Also,
|I had forgot to add the knob file in Production so added that too!!

DESIGN PHASE #6

As adviced by a fellow hackclubber @Tensor
I have removed the overhang from the macropad
Also,
|I had forgot to add the knob file in Production so added that too!!

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