FanOfHue wrote: ↑04 Mar 2020, 08:53
- Stop working on code cleanup/restrucure for now because it's still a lot of work with risks of new instabilities
Well this is really needed to get the code size down as you may have seen in the last few days.
It is a lot of work and it is done in small steps at a time, so it is controllable with true focus on stability.
Also a lot of the movement into .h/.cpp files is meant to make things more stable.
What was happening is that some code was compiled and linked such that there were multiple instances of global variables with the same name.
Not only does that take extra resources, but also it lead to hard to reproduce bugs.
FanOfHue wrote: ↑04 Mar 2020, 08:53
- Stop working on the new UI for now. ESP Easy has a perfect GUI already IMHO
Grovkillen is mainly working on the UI and only every now and then I add a new JSON entry for him to get access to functionality for the GUI.
The release of ESPEasy will not wait for the new UI, that will be a separate release.
The reason why we want it though, is to make it possible to split UI and core functionality.
This will make the binaries much smaller (100 - 150k) and also it does allow to work on them separately.
For future plans it also allows to handle multiple nodes in one UI, but that's future planning.
FanOfHue wrote: ↑04 Mar 2020, 08:53
- Try to focus ONLY on stability, check the real showstoppers from the issue list and declare a CHANGE FREEZE for a few months
See first part of the reply.
The focus is mainly on working towards a release.
If you look at the last few months of commits, there have been only a few new features added and some of those were needed for paid projects I work on.
As you may know, my job is to make rapid prototypes for sensor applications and for that I do use ESPEasy as my toolbox.
So every project I get, will result in improvements and some additions to the ESPEasy code.
As far as I can see now, the main issues are:
- Strange issues with DNS lookups => lead to crashes => probably core lib issue.
- In some circumstances the ESP may take minutes before the first network activity is successful.
- Switch plugin is still acting strange and way too complicated
- Dallas plugin is acting strange in some specific setups.
- Some issues with MQTT controllers. Domoticz MQTT is working very stable, so may have to setup OpenHAB here to see what may be happening.
- Include 1MB modules again.
If those issues are either fixed or made perfectly clear what is causing them (so we can list it as a known issue), then I would call it a release.
FanOfHue wrote: ↑04 Mar 2020, 08:53
- When the stable release candidate is out and being verified by end users:
---- focus on real issues only during a few months
---- focus on your documentation backlog
- Publish the new stable and then move forward with the project for the next cycle.
In the next cycle:
- Cleanup the issue list, prioritize
- Work on the new GUI
- Keep up the good work
Agree.