On Thursday, Oct 10, 2002, at 18:07 Europe/Zurich, Adam Greene wrote:
> In regards to Tapestry RAD being able to load *.html and wrap it with a > generic specification. What about adding a : All this sounds "interesting", but would most likely turn into an exercise in futility. If you want to provide true RAD functionality in Tapestry it has nothing to do with the underlying framework. Instead, the only obvious choice would be to provide something akin to NeXT's InterfaceBuilder for the web: wysiwyg "drawing" of the UI. And don't even waste your time mentioning WOBuilder: it's a utter failure, not even remotely close to IB. Also, something like IB implies two things: a set of useful, generic components to get started. And a plug-in API ala IBPalette to allow third party to provide their pre-build components. With such a tool there is no need to handle any html template or description files: the tool takes care of them. Your only "worry" is to provide an (optional) implementation. Such a tool, coupled with a "rapid turn around mode", would go a long way to provide RAD capacities: draw & run. Nothing much to it. Cheers, PA. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
