Skip to content
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

ui_bundle Lite #469

Open
awilliam opened this issue Jan 3, 2018 · 2 comments
Open

ui_bundle Lite #469

awilliam opened this issue Jan 3, 2018 · 2 comments
Assignees
Milestone

Comments

@awilliam
Copy link

awilliam commented Jan 3, 2018

Feature request: A smaller ui_bundle, maybe drop the png image, no font encoding

Rationale: Trying to embed homie-esp8266 in devices that may only have 1M flash, I'm unable to get the UI to work with less than 128K SPIFFS. A simple smart-plug with power monitoring sketch based on homie-esp8266 is coming in at ~45% of the remaining space and I understand that I need to stay under 50% to enable OTA, so as pretty as the UI is, I expect to rarely use it and would really prefer if I could make use of a 64K SPIFFS layout.

Thanks, great project!

@timpur
Copy link
Contributor

timpur commented Jan 3, 2018

Yes ill be playing around with the size of the ui bundle in my changed for v2.1, but this might also be good to have a basic build with aesthetics removed to save space.

My goal is also to fix the ui + config in 64kb or less also :)

Also will look into how to reduce the build size of homie (would be nice).

@timpur timpur self-assigned this Jan 3, 2018
@timpur timpur added this to the v2.1.0 milestone Jan 3, 2018
@timpur timpur mentioned this issue Jan 3, 2018
17 tasks
@BTopbas
Copy link

BTopbas commented Oct 16, 2018

Here is some examples. My programming skills not too much. But i think if you read and look this examples maybe convert homie website to this system.

Note Previous versions of project used the SPIFFS partition to store the static contents for the web interface (HTML, scripts, style sheets, images). Since 1.7.0 all these resources are encoded into a header file (a file with the .h extension) and copied to program memory (PROGMEM) during the build process. This means they are included in the firmware image and only one flash step is required. The overall size of the image is (of course) bigger than just the code but way smaller than the firmware plus the filesystem size. In particular this means that 512Kb devices can now have the full featured web interface.

Here you can read a couple of posts about this procedure:

I read this in other esp8266 project. Here is the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants