For the first item – changes being erased, you can create your own custom-routes.js file which will take precedence. Just include with routes.js:
<!-- All routes used for navigation -->
<script src="js/routes.js"></script>
<script src="js/custom_routes.js"></script>
and in custom.js use routes.push() to append into array of items:
// JavaScript Document
routes.push(
{
"path": "/report/:feed/",
"url": "report.html",
"on": {"pageInit": function() {
dmx.parse("apiGetIP.load()");
...
}}
},
{
"path": "/profile/:feed/",
"url": "profile.html",
"on": {"pageInit": function() {
dmx.parse("apiGetIP.load()");
...
}}
}
);
For the second piece – calling a server connect, you don’t have to do that in routes if you don’t want/need. I put all the server connects on the head page (eg. index.html) and can call them from throughout the app, whether it be content pages, apps.js, or whatever.
Here’s the basic structure I use (with dozens of Content Page Include’s removed for this example). Every page is an include, except for the main login (index).
I’m just using sections to organize, and contain the app connect components.
And for your third item – more features visually. That is a big gap right now…I hope at some point the team can prioritize the mobile development side of things and support the features of fw7, not just the overall framework.
