Hi, I've been reviewing the widget requirements with regard to implementation on low memory devices. Within our proposed implementation we would like to have widgets with one or more views - essentially a minimized view for the "widget dashboard" with an option for a widget to maximize to full screen.
This is possible within the framework you have proposed, however for a single "index.html" it still requires that all views are loaded by the browser or widget engine. My question is whether the ideal implementation of multiple views should be: - Separate html files within the widget - essentially requiring that each view can save state to pass to the other. - Individual div sections in the index.html with style.display = "none" for views that should be removed from memory. - ..something else? Would it be possible for the group to suggest a recommended method of supporting multiple views and include this in their documentation? This would help both widget runtime developers and widget authors. Many thanks, Alex. -- Alex Linde +44 7966 204 616
