Quick Devlog

I got no time, but I finished fixing the whole code.

Final Ever Devlog

Well, this is the finale. I have pretty much finished my hackpad. I managed to solder all of the components and took like 2 hours to do but it was all worth it in the end I guess. Overall this was an amazing project and I would definitely do it again.

Devlog #1: Building scrapbook

This is the first devlog into building this blog which is dedicated to the photos I have taken throughout the years. This is not like the Blog mission but rather a personal blog which I am developing. I am trying to use Prisma and Neon for the database and Next.js for the project right now, but obviously things are to change. It’s also going to feature like a custom Admin CMS which allows me to post along with full authentication services and even an image database to store the photos. Right now i’ve worked on:

• Front page
• Adding Database
• Setting up files/folders
• Developing the overall plan of the blog site

Right now the front page looks really basic and there’s barely any style, but that is to change very soon. Stay tuned in the next few devlogs to look at the future improvements to my blog site

Devlog 2: Building Railboard

So I basically fixed the map since it was pixelated, as Leaflet.js is very basic but doesn’t have as good and crisp as Stadia Maps. I also had a problem with the timings as I didn’t realise that there were more than one code for the train station (like GWY for Glen Waverley, but there is also GWV). After I did some train research and figured out that Transport Victoria (State Department of Transportation in Victoria, Australia), had hidden codes for trains and the API was using those, so after adding them into the code, they actually started appearing fine. Next, I also configured categories, like a Metro and V/Line tab respectively, and one tab with all mixed. I originally intended to get platform data, but I quickly realised that Transport Victoria wouldn’t simply give out platform data, so I removed that column.

Additionally, I noticed how the dots (the live train positions) were actually going all over the place and not on their respective roads, so I found a better API run by the same Transport Victoria that gathered all the train positions, so that was resolved, and I also added this cool fly-in feature that when you select from one of the trains that is running (not the ones on time), the map will fly from whatever position it is in to a smooth transition to the station.

Overall I am proud of this result so far for the map.

Devlog 1: Building RailBoard

So I am currently working on RailBoard, which will be this cool app which allows people to see the trains currently in my state (Victoria, Australia). There are currently limitations with data and stuff, which is why I am only focusing on my state’s train data. Best of all, it’s completely open-source! Here’s a summary of what I’ve done:

• Created this snazzy train board that looks as if you’re in a vintage train station
• A dynamic map that actually shows the positions of trains LIVE
• Most importantly, a board which is complete with all the times (you can even click on one and it will fly you in the map to the train’s position!)
• Categories for Metro (More Metropolitan and closer to Melbourne, capital of Victoria), and V/Line (Rural towns and cities in Victoria that are outside Melbourne)

Right now i’m working on

• Fixing the map since I want it to not look very dark but bright, colourful, and also be crisp and load instantly
• Other stuff
• Shipping

I’ve got yet to work more :D

Another Devlog: Building WaveLens

So I’ve decided to work on the site a little bit more, but this time it is more of the style, and adding more features. I’ve even added a cool wave logo I made in Canva! One major thing I have added is buttons in the frequency feed is the Update button which updates the frequencies to the latest version (by second), the clear button to erase, then repopulate the nodes, then CSV, which allows you to export the frequencies into a cool CSV file. I also wanted to reflect on the topography, and make it look much more minimalistic, so I wanted to put in this much smoother look. I like the nodes, and now when there is more receivers from a sender, their node grows bigger, showing like different levels in the map, and I worked on the navbar. I intended on putting a welcome page with a hero section, but I thought it was too chunky and decided to just do the map since it was already as amazing as it is already.

Quick Devlog

I had to rewrite the code again and I decided to add some flair and make the design like my personal website so it looks minimalistic and clean. This devlog is just an update and I have pretty much revamped everything and I am really proud of this result right now.

Devlog #4: Rewriting Everything

I think this was one of the most painful parts of the project, and that apparently my project mostly used AI, so despite that I had to rewrite most of my code and stuff, and I am proud to say that it looks really clean and much better now and now that I have done the README, the code, and the styling, it looks good and the nodes are working. This took some time to make, but I think it was worth it in the end, and I am really proud of this result.

Devlog #3 - Fixing my README

So a reason my project got returned was because my README was not fully informative and was a bit short, so I decided to tidy things up and introduce sections such as instructions as to how to install and run your own instance using a WSGI Gunicorn server, or using the Flask development server from the ground up, and I just added slightly more background to the already existing sections like the features, and blurb. So far the readme is looking much more presentable, and I think my project should be ready now to ship :D

Devlog #2 - Building WaveLens

So as a quick update before I ship my project, it has taken me meticulous hours to bridge connectivity of Wavelens to the web. It was gruelling for the API which kept failing very frequently, leading me to choose one which didn’t require as much calls and was actually free, and I had to keep changing server providers, like Render, then Ngrok, and then finally Cloudflared, which allowed me to use my own subdomain (wavelens.vihaanvinoth.com), and now it is running peacefully, whereas previously you had to take the measures to download the whole project from GitHub, then find a suitable server to host, or locally, then you could run it.

Feel free to check out the site at wavelens.vihaanvinoth.com - it’s really cool!

Devlog #2

UPDATE

I forgot to include that I also have to put this all to a GitHub repo!

So I somehow lost my files again, but luckily I had a recover file as a reference, and the DRC doesn’t even work so I had to manually review each wire and other details. However, it was easy to copy over the icons, footprints, etc. I actually think this could be the final product, as I don’t really have much to say. This was a fun project.

This is what i’ve done so far today:

• Find recovery file
• Rewire
• Copy all the stuff

Hopefully this is the final devlog and I hope to ship this probably before the end of today. I love this hack card.

Devlog on making my Hacker Card

So this was a pretty easy project to build with the schematics and PCB since it was just building a business card with NFC compatibility, and I didn’t need to do so much devlogs, so this is a compilation of what i’ve done. I’m proud of the progress so far, and I will be shipping this really soon. I only have to work on the DRC and probably add more features, but overall this is looking epic.

So far this is what I have done:

• Created schematics + PCB in EasyEDA
• Wired components
• Created QR Code
• Added text for website, Github, etc.
• Added flair for my project
• Made the text, QR code, and NFC components a shiny texture.

I used EasyEDA for the project, since most of the footprints I couldn’t find from KiCad libraries, and it was simply easier. Somehow at some point I thought I almost lost all of my files, but luckily it does online backup, so i’m okay for now.

Devlog #1 - Building Lumio

Ok, so I am trying to build an AI smart whiteboard that I can hang up in my room to make a physical display of my ideas to bring them into life. One day I saw some video of a class that used the technology, and I thought - why not make it myself? So, this will be the very first devlog in the creation of this. I’ve created this infinite zoom that should be handy later in the project for pivoting around the workspace.This is what I will have to work on:- Developing the Boxes, Drawing- Compatibility with spreadsheets, Word docs, etc.- Making the boxes + drawing functioning in the brain storm- Develop an account system and database- Create a database for the user’s projects and spaces- Most importantly, develop the AI brain for creating shapes, images, graphs, etc.- Create the Schematics and PCB for the display- CAD the design- Scavenge the parts/fund the projectIt will be a long way to complete this smart whiteboard, but I think it is worth developing this project.

Additional Devlog +1: Building verty-web

This is a small devlog just noting how I worked on my readme and final publishing for GitHub. I am really proud of the work that I have done so far and I hope to work on more stuff soon. Before I shipped I have to add this final few minutes before I ship. :D

Final Devlog: Building verty-web

Ok, now that I have managed to port this custom tab extension to Chrome, it is now up and running on both the site (https://vihaanvinoth.github.io/verty-web) and the extension, and after fixing several bugs with the manifest.json and the API I was able to cleanly create this cool and sleek home tab. I am pretty proud of this and it look really cool on my home tab.

SO, here’s what i’ve done pretty much:

• HTML
• CSS
• JS
• Chrome Extension
• manifest.json
• Published to Github/Github Pages
• Readme
• Yay

So, I guess that’s pretty much it. This was an easy task as I’ve already done stuff like this before (visit https://vihaanvinoth.com; my personal site!) and yeah :D

Now all I got to do is ship this project and I will be able to work on other project ig now!!!!!!!!1!!!

Devlog #1 + Final - Building WaveLens

TL:DR
As I haven’t yet put both devlogs into here, this is it.

Devlog #1:
Alright, so this is the first devlog so far of building WaveLens, which is basically a web dashboard which can extract WSPR/FT8 telemetry feeds, and plots them onto a large node map mapping out the callsigns. So far i’ve run them using Flask, Gunicorn, and Render, however i’m waiting for approval from the admins to approve my Nest Linux server so that I can run the Python app onto the server and run my site. So far it is turning out great, and there might be more stuff to work on soon. The image attached is from my gunicorn application that is running it temporarily, but I will soon transition to a Linux Server interface. This is also my first time building a Radio-related application, and I think it has been really fun to make so far.

Final Devlog:
All right, so this is the final post that I am creating for WaveLens. It has been a very valuable project for me to create, and I hope to create more like this in the future. I was able to use my background of HTML, CSS, and JS, as well as some flask to build this web application.

Devlog #1: Building verty-web

Alright, so I’ve had experience in HTML and CSS, and so I decided to begin building this web tab just for the convenience of my desktop and so I can use it in chrome. So far i’ve worked on the HTML, CSS, and JS, components of the project, and I am pivoting towards pushing this to a chrome extension which will allow me to set this as a chrome home tab. Its going really well and I hope to see how it will go pretty soon. This is a pretty rushed devlog because I forgot to make one in the start, so this is just a compilation of the work i’ve done so far.

Here’s some of the stuff i’ve implemented (some from the instructions):

• NASA APOD api for the background
• Clock
• Google Query Search Bar
• Links group
• Timely affirmations