Hi, You mean we should supply a muti-page editor, which open *.tml and corresponding *.java file in the same window, right ? This is a good idea, i will consider this solution.
You said "The tabs could include tml, java, properties, event handlers, services etc", in fact, i am not very clear about the "properties, event handlers, services", i do not think each Tapestry page have these modules, if we added all these tabs in a mutli-page editor, isn't it some kind of place waste ? More important, too many tabs will also affect editor performance, make it more slowly and heavier. your opinion? 2012/2/8 trsvax <trs...@gmail.com>: > I'd vote for a lightweight one also. In fact if I could click on a java or > tml file and end up with a window something like the Maven Pom editor I'd be > happy. The tabs could include tml, java, properties, event handlers, > services etc. Auto complete in the tml file might be nice but I'd say just > having the tml/java tabs would would be a huge win. If I could also go to a > service implementation without going thru the interface I'd be pretty happy. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Need-feedback-for-Eclipse-WTP-based-Tapestry-5-visual-editor-tp5453019p5463843.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- --------------------------------- Best Regards Gavin Lei (雷银) Email: gavingui2...@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
