This seems like the right way to go -- allowing many apps to use html and a local server without excess overhead, without overloading a canonical 'web' activity, and without double-navigation (perhaps an option to keep the default browser UI).
<br><br>SJ<br><br><div><span class="gmail_quote">On 4/14/07, <b class="gmail_sendername">Ian Bicking</b> <<a href="mailto:ianb@colorstudy.com">ianb@colorstudy.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I was talking to someone about the library activity, and he had done<br>some work a product using Gecko without any extra UI, and it seemed kind<br>of interesting. In that case, he implemented all the back buttons and<br>
other navigational UI in HTML. All of which is basically how the<br>current library prototype is written, except there's an additional layer<br>of normal browser UI. Which I actually like in a general sense, but<br>
creates a perhaps-unnecessary second layer of UI in the library; and<br>that's fine when you don't really trust the content (as with most<br>websites), but if we have a consistent design process for content we can
<br>make the UI consistent in HTML.<br><br>This would also be great for other Activities that might want to use<br>HTML and a local web server, but aren't really "web pages". If the<br>activity doesn't add their own navigation then this won't work at all,
<br>so it should require at least some specific assertion (maybe in CSS or<br>the page itself). And probably this should only be allowed for local<br>activities; I wouldn't want normal internet pages to be able to just
<br>completely turn off the UI.<br><br>How these should be launched, I don't know; ideally they'd share memory<br>with the web activities and each other, like when you start multiple web<br>activities (I believe). But that doesn't mean they can't have their own
<br>identity in the form of an icon or whatever else Activities come to<br>represent. A locally hosted web application Activity actually needs the<br>whole thing -- it needs to start up a server, then start a browser, so
<br>it has to be its own Activity.<br><br><br>--<br>Ian Bicking | <a href="mailto:ianb@colorstudy.com">ianb@colorstudy.com</a> | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br> | Write code, do good |
<a href="http://topp.openplans.org/careers">http://topp.openplans.org/careers</a><br>_______________________________________________<br>Library mailing list<br><a href="mailto:Library@laptop.org">Library@laptop.org</a><br>
<a href="http://mailman.laptop.org/mailman/listinfo/library">http://mailman.laptop.org/mailman/listinfo/library</a><br></blockquote></div><br>