Added application state functionality, to determine what state is currently loaded, and thus allowing for multiple scenes and transitions, etc
Added application state functionality, to determine what state is currently loaded, and thus allowing for multiple scenes and transitions, etc
Added back the graphic output and framebuffer functionality. This should finish the boilerplate I needed to do before working on the actual content
Worked on a small file wrapper, since we don’t have a standard library and some mechanics I need to do are a bit quirky
Added some vendor code for reading PNGs. Hard part was adjusting it to not use the C standard library and instead use some custom implementations for memory allocations and such
Started work on a new uEFI project, this time on a Shoot ’em up kind of thing. The flapyp bird I previously did was not very high quality, considering I had to work with bitmaps, but I might try to make a bit better engine to work this on.
Project Update! Started to assign footprints to the numerous components that are used in the PCB. The process kinda takes a while but seeing everything assigned is rather rewarding. Searching LCSC for part numbers and schematics and the whole import process is a pain however
Woah, another update? Took a small break but I am back from vacation, more ready than I’ll ever be to do this project. With this timelapse session I am starting to introduce the RF impedance matching network according to the documentation to minimize EMI noise
Project Update! Following the reference designs and the schematics I have been in the processing of choosing the most optimal passive values for the EU868 band.
Wired the MCU - nRF52840 - to the regulator and added all of the capacitors that it needs. Moreover started looking into the LoRa module documentation, I am not looking forward with all the shenanigans I need to do…
First devlog of this project, and it is quite an important one. Added the 3.3V power regulator and powermux to switch between battery power and USB power as that is quite important.
Just completed the first iteration of a UEFI Flappy Bird. While working in the project it didn’t cross my mind to create seperate devlogs as I didn’t think it would take me that much time, but here we are
Working on the v2 version of the API, it will have OpenData support and syncing capabilities. Now all of the data will be internal to a database and allow users to custom insert their own routes/trips/schedules. That way it allows for easier access. Unfortunately with this comes the deprecation of the older API specifications but the newer one seems cleaner.
Woah, more changes since the last devlog, and many helpful ones. In my attempt to provide a more developer friendly library, I switched from using the API to using saved data. The tldr is that after a bit of research, I was able to find an official GTFS (General Transit Feed Specification) from the transit entity under my gov’s opendata platform. As such, I am beginning the process of an automated migration of those data to an internal library database. Furthermore, i fundamentally reworked the library to use multiplatform compose - and as such support to many platforms.
Finished iteration v1.0 of the bus tracking api with a tracker using kotlin coroutines and channels
oh my god this notion library is going to be the bane of my existence.