Replies: 2 comments 1 reply
-
This topic moves to the Discussions. @beres It's not easy to add flexibility to the layout of AutoConnect's embedded pages, but there may be an opportunity to do so. Hope to continue in the Discussions. |
Beta Was this translation helpful? Give feedback.
-
@beres Sorry for the late reply. I have spent less time thinking about your suggestions because I have been prioritizing work on revising HTML generation for AutoConnectElement for the past few days. The following is a simplified block diagram of the AutoConnect structure. It may help us in making your suggestion more concrete. According to PlatformIO's static diagnostics, the largest build size is the AutoConnectElements classes of the AutoConnectAux handler, which is an instantiation of the AutoConnectElements template. The next largest are the AutoConnect core and AutoConnectAux handler, followed by AutoConnectPage.cpp. For use cases that do not require AutoConnectElements, it is indeed a wasteful structure; AutoConnectElemetJsonImpl is reduced by using the AUTOCONNECT_NOUSE_JSON macro definition, but still not a reduction. As you pointed out, AutoConnectPage.cpp is still the big one. Among them, the LUXBAR has a CSS size of 2.7KB. It may be possible to completely isolate AutoConnectAux by templating the AutoConnect class and instantiating it so that it does not contain an API for custom web pages. I will look at a few more ideas on how to disconnect AutoConnectPage. |
Beta Was this translation helpful? Give feedback.
-
Hi @Hieromon,
Thank you for this library, I would like to change the layout of some pages.
Initially I wanted to change the colors of the _PAGE_CONFIG buttons which are not skinnable, by inserting a new label and sending a patch.
Then I thought it would be nice to be able to customize the layout of the pages, what could be the correct approach in your opinion?
You might be interested?
Beta Was this translation helpful? Give feedback.
All reactions