Open thiswillbeyourgithub opened 12 months ago
Hi, yes, I know about waspos and have looked at in some detail. The main constraint that waspos addresses is the small RAM size - 64K - of the RF52832. Thus the frozen code etc.
The design of tempos - short for temporal operating system - was influenced more by my experience with Espruino and it’s Bangle watches. So Tempos has a JavaScript like event model.
I have previously implemented a desktop like icon driven launcher for Bangle so I wanted to experiment with an architecture that selected apps directly by swiping as my experience is that launchers can be a bit fiddly for small devices.
I really like the simplicity of tempos where everything is an app with no special treatment of settings or launching.
Saying that, I think the best approach to running waspos apps would be a compatibility lib which mapped waspos to tempos primitives rather than changing the tempos primitives.
Saying that, I think the best approach to running waspos apps would be a compatibility lib which mapped waspos to tempos primitives rather than changing the tempos primitives.
Noted. I'll do that eventually then. Thanks
Hi!
As I said earlier, I'm quite familiar with wasp-os on the Pinetime from Pine64. It's arguably the most successful micropython os on a hackable watch (albeit not that successful, it's quite niche :) ) so I think harmonizing some parts of the code to reduce the cost to port apps between them is not a bad idea.
Wasp-OS has some great features like :
You can give it a go right away on your computer by cloning their repo then running
make sim
in the root. This will launch the simulator.Before porting my own apps here's what I explored so far:
Here's where I'm at now. I think harmonizing the "API" is what yields the most without hurting the authenticity of this repo and allowing to port apps more easily. By that I mean for example renaming the "g" module to "display", renaming the "setInterval" to waspos's alternative etc.
Here would be the tentative roadmap:
What do you think @jeffmer ? I think it would bring more apps to your OS, increase the visibility to your OS as well as to the twatch (which is incredible but not enough loved!) and be a good thing overall : 2 projects with a common API increase chances of more future watches aligning with this instead of having 3 standards :).
The goal is not to do a major overhaul of the code of course, but just to make it share the same language as waspos.
Can't wait to have your take on this :)
ps : wasp-os is also available on a few other watches, see their great doc