husky wrote: ↑Sun Sep 20, 2020 5:27 pm
Thanks for the feedback. I really have to do documentation of how to configure the wifi and how to make applications that need internet and background tasks.
Regarding the use of the ST7789 driver, I have used the wasp-os driver for application compatibility. But I think I can make a proxy to use the official ST7789
But every time I do things in this fork I find it more difficult to maintain compatibility with the original wasp-os project. I have already separated a lot from the Core, to the way of managing the apps and the battery management. At first I was going to do a PR on the main project. But now I think it is better to keep this project independent.
opinions?
Next things I want to do:
I would like the battery to last 72 hours.
I am working on a weather app.
Hi Husky,
First of all, many thanks for your port and the efforts you put in it.
Much appreciated and very, very helpful!
As for the fork options, please allow me to give some personal opinion:
One of the strength of wasp-os is its architecture and doc, plus the fact that it evolves.
For an app dev, you have all tooling and can mostly abstract the hardware, all being documented.
To me, it would make sense to be as close to the original as possible, mostly for that reason.
Anything you change (like changing case for core variables, was that really mandatory?) means you make it harder for an app to be ported between archs, plus you then need to write and update doc instead of pointing to the original one.
Did you sync with Daniel to see how your fork could be merged, how he would deal with the significant hardware changes?
I really think a unified core - and doc - would be a huge step toward adoption and usage.
As a dev myself, I do understand the pulsion to make things like you like them and tweak the core to your liking instead of Daniel's guidelines and arch, but I feel you're isolating yourself doing that.
(This is not a critic and I could have done the exact same or worse)
Also, merging goes both ways. Daniel already committed several things since your fork, this is lost to you or will require more work.
Now for a debug question:
I tried your wasp os port, "develop" branch, on a TWatch2020.
I used the following micropython, tailored for TWatch2020 with all drivers (plus lvgl)
https://github.com/OPHoperHPO/lilygo-tt ... icropython
I built it from source.
Once your wasp-os fork is installed, the watch does run, no error in console, but it does only displays the time.
(wifi ok, time auto set ok but 2 hours offset)
However, I can't swipe to anything.
Touch events are detected and DEBUG:Touch printed, but this triggers nothing, watch sticks to the time screen.
Any idea what could be wrong?