Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for 
change notification.

The following page has been changed by ErikVullings:
http://wiki.apache.org/tapestry/WishList

------------------------------------------------------------------------------
  Debug to IDE support:
   *Have been doing some experimentation with generating exception pages that 
link back to Spindle in Eclipse. The approach is generic and not tied to 
Eclipse. Success has been had with linking stack trace entries to java editors. 
The Wish is: Rework the exception page with two (overridable) components. One 
that renders stack traces and one that renders ILocations. That way a debug 
friendly Exception page can be created that will render the info above as links.
  
+ 
+ John Hyland--
+ 
+ I wrote on the old wiki TapestryAsRAD page and was told to contribute 
something here so I chose this wishlist:
+ 
+ Tapestry (with other framework components) as a UI framework component I 
think is furthest along towards making a RAD. Even a web based wizard RAD tool 
given that Tapestry has such standard widgets. An XML application definition 
file is a good idea. You *could* also use a special schema in the database as a 
"application definition dictionary". This would afford some niceties as well. I 
think a basic "CRUD" database editing, intuitive application creating RAD is a 
good first step towards possibly some more "applicationesque" additions like 
menus, role-privilege access and "flows". Perhaps a scheduler service and a way 
to interact with it in the RAD later on would be really nice.
+ 
+ Basically, my wish is for Tapestry to have a kind of RAD war application so 
that simple database editing applications can be created very quickly. (getting 
rid of excessive specifications like the page specification is a good 
simplification that can be used.)
+ 
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to