> 2. Tapestry page/component creation wizard > It will help us to create the .tml file and .java file together (in Tapestry > 4, this will create the corresponding .page file too) > for a Tapestry page/component. >
I think Loom already does this although I don't use this feature. > 4. Add convenient way for the Web Page Editor to change-over between a > Tapestry page's .tml file and .java file Loom does this well so you might look at how it works: http://code.google.com/p/loom-t5/ > > 5. Add Tapestry built in and custom components autocomplete function for WTP > Web Page Editor's source view > > 6.Autocomplete of properties from the .java page when editing the .tml file > In the Source Page of the Web Page Editor, add the Tapestry tag, (for > example ${prop:index}). 5 and 6 are the features I'd recommend starting with and would probably give the biggest productivity boost for most users. You can actually do 5 now by creating an XML definition document from your components, importing it into Eclipse and using the XML editor. There are instructions for doing this on the wiki. (I'd find the link, but Apache is down right now.) In fact you might be able to do 5 simply by looking at what you can do manually and creating an eclipse plugin to automate it. The autocomplete of properties from the .java page would be wonderful as this is something that there isn't anyway to do right now using Eclipse. IDEA does have the capability. Best of luck. I'm excited to see what you come up with. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
