Hi, Gavin!
It would also be great if there will be integration with T5 Component
References:
http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/
There's a JavaDoc view in Eclipse, may be its possible to show related
reference page in there when you're in tml editor?
Also it would be nice to use the Help view, to show some Wiki links, and/or
TapestryTools own recommendations on the T5/plug-in usage.
Btw, I like the idea of lightweight T5 support with autocomplete and
navigation. I think they have more impact on productivity than
the Component palette and drag&drop, although these are nice features also.
Personally I don't use drag&drop in web development at all, but I like the
idea of component palette as a catalog of all available components.
For me I would better prefer having separate view with component list
(grouped by some categories) integrated with component references, and also
I'd like to see all available T5 services in there with (probably grouped
somehow) with the ability to click on them so that the plugin generated a
piece of code in AppModule with contribute/override logic -- but that just
my thoughts.
I'd also like to see more Navigation features. I.e., in page class:
@Inject
private Application application;
I'd like to CMD+Hover the field and see navigation tip "Open build method"
(like here
http://www.ibm.com/developerworks/opensource/library/os-eclipse-galnav/index.html
).
I'd also liked if TapestryTools moved to GitHub, I think there you can have
more feedback/contributions from open source.
P.S.
Thanks for doing all this :)
2012/2/7 Gavin Lei <gavingui2...@gmail.com>
> Hi All,
>
> After discussion with my GSoC mentor Igor Drobiazko, we think there
> are two ways for TapestryTools to go:
> 1. build TapestryTools on WTP, and keep improving it
> 2. build a brand new simple tool which supplies some special Tapestry5
> features, and it can run without WTP
>
> Solution 1 will make TapestryTools more powerful, but meanwhile, it
> will make it more complex and hard to improve, hard to install and we
> should keep synchronous with Eclipse WTP's release version. Not
> unfavorable for this tool's long term development.
>
> If we build TapestryTools without Eclipse WTP in solution 2, maybe we
> will lost some brilliant features, such as palette drag and drop
> things, but it will make TapestryTools lightweight (just a normal
> Eclipse plug-in, does not need many special dependencies),more focus,
> easy to install, easy to use. And also, we can supply practical
> features:
>
> 1) very easy installation in different Eclipse version
> 2) Tapestry page/component creation wizard
> 3) command to switch between tml and java
> 4) Autocompletion features, includes two aspects:
> * Autocomplete of properties from the .java page when editing the .tml
> file
> * Tapestry built in and custom components autocompletion function in tml
>
> And optional features:
> 1) import Tapestry jar of special version to project
> 2) validation function in Tapestry .tml file source view
> Supplies semantic validation of the Tapestry standard tag
> libraries for both EL and non-EL attribute values in *.tml file
> 3) hyperlink function in Tapestry .tml file source view
> Hyperlink to the Java editor from property and method referenced
> in the Expression Language(EL) of a tag-attribute, click (CTRL +
> property or method ), it will jump to the corresponding Java Class
> file.
>
> And now, we are still in ideas collection period, any feature demands
> from open source community is welcome. Or if you have any advises,
> please let me know, thank you.
>
> ---------------------------------
> 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
>
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
