It should be possible to define a list of packages to look for components

[GoogleCodeExporter]

Right now the list of components used for autocompletion is statically defined 
in your source code. A better approach would to read the component classes from 
several packages, which can be configured. 

By default only two packages are in the list:

- org.apache.tapestry5.corelib.components
- app-package.components, whereby app-package is the applications root package 
defined in the web.xml

Reading components from a list of packages, would allow you to provide 
autocompletion for custom components from different libraries. So we need a 
dialog in which a developer enters a mappin:

x: org.example.components
y: org.acme.lib.components

In this mapping, a library prefix is mapped to a component package. So, every 
component from org.example.components package would have x prefix. For example:

<span t:type="x/MyComponent"></span>

<span t:type="y/Foo"></span>

Please also note that also component parameters should be read dynamically from 
component class.

Original issue reported on code.google.com by igor.dro...@gmail.com on 27 Jun 2012 at 3:25

[GoogleCodeExporter]

Forgot to mention that also in case of invisible instrumentation the parameters 
should be read dynamically

Original comment by igor.dro...@gmail.com on 27 Jun 2012 at 3:27

[GoogleCodeExporter]

I have fix this issue, you can find the design details here 
http://code.google.com/p/tapestrytools/wiki/Install_Guide_Lightweight_TapestryTo
ols

Original comment by gavingui...@gmail.com on 5 Aug 2012 at 6:39

• Changed state: Fixed