We have to tell people how to deploy their apps. The wrapper pages we generate are one way. There is the ?lzt=deployment 'wrapper' that tries to explain the various ways. This sorely needs to be updated for legals. And there is some other open project 'flash embed' or something that many people ask how to use with our stuff. We need to doc that.
You are asking about a meta step, should we doc how we generate our wapper pages. I think we need to address all of the above first. On 2006-04-20, at 17:42 EDT, John Sundman wrote: > Would this be considered a user-visible feature? Should I mention > this > in the Developer's Guide (or the nearly defunct Deployer's Guide)? > > It seems that it might be useful in some cases, but it does require > touching the "sources" in a way, so it's not strictly user stuff? In > other words, I write the Developer's Guide from the point of view > of OL > as a "black box". Going down into WEB-INF violates that. > > Comments? > > jrs > > On Apr 3, 2006, at 5:17 PM, Henry Minsky wrote: > >> There is a two-part protocol - the server generates some XML >> containing >> relevant info from the compilation, and then that is passed to an >> XSLT >> template - you can even write your own template by naming it >> foo-response.xslt in the WEB-INF/lps/templates dir, and then >> asking for >> foo.lzx?lzt=foo > > _______________________________________________ > Laszlo-user mailing list > [email protected] > http://www.openlaszlo.org/mailman/listinfo/laszlo-user _______________________________________________ Laszlo-user mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-user
