Here's a straw man proposal for Explorer and the main page.
Requirements:
- support current uses of nav-explore.lzx (both Explorer and Laszlo
in 10 Minutes)
- allow nav-explore.lzx and dependent content to run in either DHTML
or SWF
- support a simple, easy-to-access, low-tech directory of SDK
resources (e.g. the main page) that doesn't require running any
OpenLaszlo apps
Current system:
Quick overview: both quick-index.html and Laszlo Explorer / Laszlo in
10 Minutes are driven from nav.xml. The app nav-explore.lzx consumes
nav.xml, and quick-index.xslt transforms nav.xml into quick-
index.html. (The build tools copy quick-index.html to index.html, so
it becomes the home page in production builds.) All of this is
currently single-runtime, except where individual demo wrapper pages
have been modified to be multi-runtime.
Proposal:
Extend nav-explore schema to have separate links for DHTML and SWF.
So instead of
<item title="Calendar" name="Calendar" popup="/demos/calendar/
calendar.lzx"
src="/laszlo-explorer/coverpages/calendar_cover.html"
text="A desktop experience for an enterprise web application"
target="LzPopUp" params="lzt=html" >
<subitem title="Source Code Explorer" text="See the legend
at the bottom of the page"
src="/demos/calendar/calendar.lzx"
name="Source" action="source" />
</item>
you would have
<item title="Calendar" name="Calendar" popup="/demos/calendar/
calendar.lzx"
text="A desktop experience for an enterprise web
applcication"
target="LzPopUp" params="lzt=html" >
<src type="dhtml" href="laszlo-explorer/coverpages/
calendar_cover.html?lzr=dhtml" />
<src type="swf7" href="laszlo-explorer/coverpages/
calendar_cover.html?lzr=swf7" />
<subitem title="Source Code Explorer" text="See the legend
at the bottom of the page"
src="/demos/calendar/calendar.lzx"
name="Source" action="source" />
</item>
We'd modify nav-explore.lzx so that it parses this new schema and has
two radio buttons at the bottom of the navbar, "swf" and "dhtml".
Clicking on the unselected one would reload the navbar and dependent
content in that runtime.
(We'd also need to back out my change to some of the wrappers to
remove the "Show in DHTML" / "Show in SWF" buttons. And update the
LZPIX wrapper page to not have separate DHTML/SWF buttons.)
We could also build the nicely-designed browser detect into the
wrapper page for Laszlo Explorer and do something more primitive for
(most of) the dependent pages. (Demos that are linked directly from
openlaszlo.org would also need their own nice browser detect.)
Finally, we'd modify quick-index.xslt to generate entries that had
separate links for DHTML and for SWF. So instead of
<li>
<a href="./laszlo-explorer/coverpages/calendar_cover.html">Calendar</
a> A desktop experience for an enterprise web applcication<ul>
<li>
<a href="./lps/utils/viewer/viewer.jsp?file=/demos/calendar/
calendar.lzx">Source</a> See the legend at the bottom of the page</li>
</ul>
</li>
we'd generate something like
<li>
Calendar&emdash;A desktop experience for an enterprise web
application (<a href="./laszlo-explorer/coverpages/
calendar_cover.html?lzr=swf7">SWF</a>) (<a href="./laszlo-explorer/
coverpages/calendar_cover.html?lzr=dhtml">DHTML</a>)<ul>
<li>
<a href="./lps/utils/viewer/viewer.jsp?file=/demos/calendar/
calendar.lzx">Source</a> See the legend at the bottom of the page</li>
</ul>
</li>
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
