The improved local Wappler server in version 3.3.1 is really a very strong improvement for mobile development. Previously, the work was really difficult: when all pages except the main page look like a mess of tags and symbols in the visual representation of Wappler. And all the work was done only through the code. Anyone who has worked with this before will understand.
Now I see this image in the Wappler visual representation of my app’s include pages:
Anyone who thinks they look bad is wrong. They look much better than when there was no local Wappler server. But they still don’t look like they would if I opened them in a browser:
Nevertheless, this is a very strong progress. Work on the application is significantly accelerated thanks to the local server.
@George it would be absolutely great if Wappler could learn how to do the following:
When it encounters this entry in the file <!-- Wappler include framework7_4= "local" is= "dmx-app" id= ""appConnect=" local "framework7_icons=" local "cordova=" local " -- >
it would make all the connections that are in the main file (index.html), along with all meta tags and server connections. So that in the end, the page in the editor window looks exactly the same as in the browser (including displaying dynamic data).
How realistic is this?
This would speed up work on mobile apps very, very much.