-
I didn't realise you had a whole app loader full of apps! I guess it's gone far enough now that it wouldn't be possible to integrate the apps as normal Bangle.js apps?
Not really apps, some 20 of them are the modules for different models /makers support , some 10 are system apps, and some true apps like the calc, alarm, HiD music, TPMS, Led stripes, things like that.
It is just that using two loaders means I can have the same version for p8/rock/bangle.js2 on most files, and slowly integrating to bangle.js apps could be easier for me if I was really using the bangle.js2, as a motivation I mean. For anyone I think, someone else may do it if he likes it, the code would be inside the watch already.
you could modify your app loader to use .euci or something for the file extension of the info files
very nice, thank you.
You are reading a single comment by @enaon and its replies.
Click here to read the full conversation.
enaon
Yes, I think you're right there @fanoush - it's a shame but it seems to be the way things are, with it being almost impossible to know what hardware you're getting. Even devboards like the CYD appear to have changes that are hard to keep track of.
@enaon wow - I didn't realise you had a whole app loader full of apps! I guess it's gone far enough now that it wouldn't be possible to integrate the apps as normal Bangle.js apps?
The app loader uses
*.infofiles to determine what's installed, and effectively ignores any other file. So if you there wasn't another way you could modify your app loader to use.eucior something for the file extension of the info files, and then they would be separate.