Devlog #8
Did more of the PCB. I realised that I didn’t put the correct footprint library for the LED thats why it didn’t appear so I corrected it and fixed it up in the schematic. I made my shape rounded in the corner and did some wiring. I think doing the wiring is like solving a puzzle cause I have to make it connect but sometimes my other wires block the way. In the next session, I’ll have to continue wiring. I stopped because I was strugglying to find the area I can connect them. Should probably redraw some wires next time too.

Devlog #7
I did the layout of my pcb! I’m not entirely sure of the exact mm measurements for the oled so I just did a rough rectangle. This follows my plan that I drew earlier

Devlog #6
I finished the schematic for my hackpad! I think I figured out how the labeling works. You still use wires but instead of all the wires going to one place you need, the labels kind of mean the same thing as that place and you can connect the label and the location you want with the wires, making it less messy. I did a couple of mistakes where I thought I could just just all the wires to one label but when I searched it up, it turns out it kind of messes things up so new thing learnt. I also did a bit of pcb thing and I thought I worked all the correct measurements but for some reason the rotary switch didn’t align with my SW5 which made me utterly confused. Funny, I spent like 20 mins trying to work out how to make it accurate but idk if I even did it correctly cause I was unsure on how to use the measurement tool. Next session I’m gonna continue my pcb board and hopefully can get all the measurement!

Devlog #5
So I thought I found a very easy way to connect things as it gets really messy and hard to read with a lot of wires but it turns out I did not understand how to do it at all lol. As you can tell, I used both labels and wires to do as I thought the labels just are there as naming but oops turns out I was completely wrong. I think I might just stick to plain wires for the future.

Devlog #4
So honestly I didn’t do it for a day because I got lost on what to do when the tutorial ended. In this session I spent like half an hour doing research in which I made a small design plan with the components I want to add and a drawing of my expected outcome for the hackpad. I also added all the new components in the schematic. I just need to wire them now. I learnt a trick where wiring starts to get really confusing and messy when there is a lot so we can use labels to make things neater. In the next session I plan to finish up the schematic and move on to the pcb!

Devlog #3
This was really confusing. So I made the usb port slot and the lid where the keys will be and then the tutorial just ended. The dxf I imported in wouldn’t connect with the other part of the top case when using boolean so I had to slightly increase the size in which I hope doesn’t affect. I know I’m suppose to make it my own now but I am really lost on what to do. Like I genuiely have no idea had the stuff connects or works as I am a complete beginner. I think next session I’ll idk try to watch some tutorials and understand this more. I really hope the hackpad tutorial would go into more further detail though becuase I thought this was beginner friendly 😭

Devlog #2
This was a real pain to do. In the tutorial, it said to use to Fusion360 which I decided to try out for the first time but it was really confusing and hard to understand. The tutorials I searched up were also very limited for the parts I couldn’t get. Like for example, I needed the exact measurement but the dimensions wouldn’t appear for me to change. I only found out how to do it after searching in the comments which was to press D. So well… I kind of gave up and went back to Onshape. I created a bit of the case and the holes. I think in the next session, I might learn how to transfer the Onshape case to Fusion360 as it seems I need to put in some data from the tutorial. I’ll try my best to learn how to use FUsion360!

Devlog #1
Following the Hackpad guide, I made my schematic and some of the PCB parts in Kicad. This was my first time using Kicad.

I figure out the reason why it didn’t work was because I did maze_generation(level, level) but I made level = 1 and I forgot it only increase by +1 in next_level so I just put 4 + level instead so now its a functional maze. In this session I also realise it was very annoying having to spam the letter w or the up arrow to go up so I decide to change it so users could hold it. Instead of turtle.onkey for each key, I did a turtle.onkeypress and turtle.onkeyrelease where when the key is down, it will add the key movement and when it is lifted, it will discard it. To make it more noticeable that there are levels, I added like a title of what level it is. Additionally, I feel like its kind of boring so I might add some timer or coins you can collect in order to go to the next level in the next session. The colours are also horrible lol.

So… I learnt a very important lesson this session. It is to always keep running your program to see if it works. As I was coding this, I was just visualising and going like it will probably turn out like this if I do that but it turned out to be completely different. If you see in the image below, it’s just a red and blue square! Where is even the maze, let alone does it function? So during this time, I was programming the next_level function to make it become like infinite and I’m not too sure if it will work since the maze doesn’t work so I’ll have to fix draw maze_generation and draw_map first. Thats what I plan to do next session!

Added a third section cause i didnt realise we needed 3

I made a personal site for the mission. It has an about me and a table of projects. I learnt how to make a table using html!

Initially, the start of the project was made using a HackClub workshop of the dungeon crawler. However, I wanted to turn it into an infinite maze game using that concept, which is what I did in this time. I had to work out some math and it was pretty hard to visualise everything. I think the hardest part was trying to work out how everything connected to make this maze game infinite and randomised. I just did some functions and next time I’ll make it actually kinda work.

I coded the javascript which made my website functional. There are floating bubbles in the background, which make the screen feel less still. You can add, delete, and edit tasks. I also wanted the website to look prettier, so I made it a pixel theme, all drawn by me!

While coding this, I realised a lot of the functions were only known to be so I had to put some changing-colour hover animation over it to make it noticeable. The bubble animation was probably the hardest part here, as that was a whole step away from the guide I used. It involved a bit of math lol, and I realised I accidentally wrote .png instead of .PNG, which completely stopped the bubbles from appearing.

However, as you can see in the image below, I wanted to make the to-do list my own, so I incorporated pixel elements. I chose to do a star as the checkbox instead to make it feel more like an achievement. Not to mention that the white box was really annoying to make, as I had to make it look pixelated, which was very hard. It took a long time of trial and error to get those pixel corners, but I managed in the end! :D

So I started my project and decided to do the HTML and CSS first (well, of course). I finished the basics of my HTML and CSS, so it looks like an average checklist. I would have included it in the picture below, but only one was allowed. Below, you can see my HTML code. What I learnt in this session was all the HTML shortcuts. I had no idea; honestly, I could just write div and enter and it would make all the <> for me. It saved so much time when I was coding.

Currently, the website is a static website, but soon I’ll code the JavaScript, making it interactive! I am really excited to see my to-do list come to life. I hope to make some sort of animation in the background as the checklist is looking pretty plain