-
Notifications
You must be signed in to change notification settings - Fork 9
Q&A
InkWatchy solves an important problem with all watchy firmwares. All other firmwares are hard to maintain because images, fonts etc. are stored as binary data and most often with no source to them. I generate everything dynamically, editing a font is as easy as replacing a .ttf file, modifying an image is just editing an .png file. Secondly, I put those resources into LittleFS which means they are seperated from the program. This improves upload speeds as you are not uploading the same resources all the time. I could go on and on on why this is all needed (the filesystem mainly) but I have already written down the features of this software in the readme, If you say all of that is not needed for a watch then inkwatchy is not for you, this software makes your watchy more then just a watch.
If you don't want to use vscode / docker you are basically on your own, you can ask me for directions, or make pull request for supporting this way of life... Some notes for you if you plan to don't use either one of them:
- If you are ok with docker but not with vscode, just look at devcontainer and adjust your docker run command (use the same dockerfile) then install platformio cli in the container
- Because of platformio being stupid, purge your
~/.platformio
folder before opening the repo - Look at the dockerfile at what you need to install (Also, at what version of those packages you need), at devcontainer.json what to emulate yourself
- Look also at packages.sh script of what he does with esp idf, he installs it to your home directory
- I won't support your 32404498 distros and then match all the packages version, Previous inkwatchy versions did that and it was pain, I have better things to do. You can add support for it as I mentioned, but I won't do it
- If you say that the requirements are a lot and bloat or smth and it should minimal, go use your default watchy software, I already explained this point above somewhere