-
I don't see there's a big problem with 'taking over' the Bangle. I think as a normal app you should have pretty much free reign over what happens - I guess maybe some boot code could interfere but I think on the whole we can just limit what other boot code apps we allow people to install.
nice, if this does not sound like a bad idea, then it works fine as far as I have tested, I will make it working good. Taking over I meant like using my scripts to read the touch controler instead of bangle functions, I am using is my init (.bootrst) file as a bangle clock.
One of the problems I was planning to solve, was the loaders. There are 39 apps in mine, a lot more files that this, lets say I manage to find a way so that there are no conflicts on variable names or file names, do you have a hint as how it could be done so that my loader ignores all the official bangle apps, and the official loader ignores my apps? It looks bad having all those question marks when changing loaders :)
You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
enaon
@Gordon
That looks really cool, thanks!
I had a quick glance at your code, and it looks great to me! At the end of the day it's not about how it looks anyway, it's whether it works and is reliable, and I get the impression yours does just that.
I don't see there's a big problem with 'taking over' the Bangle. I think as a normal app you should have pretty much free reign over what happens - I guess maybe some boot code could interfere but I think on the whole we can just limit what other boot code apps we allow people to install.
If there are firmware mods needed we can look at that - things like the packet length and max connections were useful to everyone when they went in.
Unfortunately I don't have an EUC to test with here, but I guess anyone can check the UI is working ok...