New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's Going On with M5ez? #109
Comments
Hello, Thank you for the update, I am really looking forward to seeing M5ez on the M5core2. Do you have an expected release date yet? Thanks |
There is something that is more of a very early alpha. And it's turned into more of a lightweight Qt than the original M5ez. Which is a good thing when you have a touch screen. If you can deal in not having documentation and just a bunch of examples, check out https://github.com/M5ez/Core2ez . Expect things to change... |
@ropg when you get to the point of wanting testing feedback, I'm happy to help. I've been working extensively with M5ez on an M5Stack Fire over just the last few weeks but getting pretty deep in and loving it. My Core2 is on the way and I'll give the Core2ez library a spin once it comes in. Thanks for all you're doing for the community! |
Any plans to support arduino-esp v2.x? With the latest PlatformIO (arduino v2.0.7), I'm getting
|
Yes, I would be nice if someone smarter than me could bring this project forward to support WiFi and various other patches that have been provided like the animated charging indicator. |
Right now Rop is working hard on adding some much needed Touch functionality to the M5Core2 library.
I'm doing reviews and developing test apps.
This is critical right now, because the 0.0.1 release of M5Core2 was far from compatible with M5ez, and the Touch UI was incomplete.
Once this work is done ("Real Soon Now") work will resume on M5ez and will focus on making the library available on the Core2, the M5Stick and M5Stick PLUS as well.
Work hasn't paused, it's just focused elsewhere for now.
If you've been playing with the M5Core2, do you see yourself using some form of M5ez there in the future?
Are there any new features you like to see to make the experience better on the Core2?
The text was updated successfully, but these errors were encountered: