Closed GoogleCodeExporter closed 9 years ago
If somebody types <input t:id=" the plugin should suggest a list of all the
component ids, that are defined in the corresponding Java class using
@Component annotation.
Original comment by igor.dro...@gmail.com
on 21 May 2012 at 9:12
Original comment by gavingui...@gmail.com
on 22 May 2012 at 1:55
Same feature with issue 28
http://code.google.com/p/tapestrytools/issues/detail?id=28,
right?
Original comment by gavingui...@gmail.com
on 22 May 2012 at 1:56
No, these are different features.
t:type="ActionLink" is used to define a component in a template. This is used
in combination with component's parameters. Fior example:
<a t:type="ActionLink" context="123">Click me</a>
t:id is used to attach a component, that was defined in page's Java class, to a
html tag. In other words, this is just a reference to a component defined in
Java class. Here is an example:
<a t:id="myLink">Click me</a>
Whereby myLink is a field in page's class of type ActionLink:
@Component( parameters={"context=123"} )
private ActionLink myLink;
See the difference?
Original comment by igor.dro...@gmail.com
on 22 May 2012 at 6:31
Thanks for the explanation, i am clear now
Original comment by gavingui...@gmail.com
on 22 May 2012 at 7:28
Finished, i will update TapestryTools update center soon
Original comment by gavingui...@gmail.com
on 31 May 2012 at 1:11
If no id is specified using @Component annotation, autocompletion still doesn't
work. For example,
@Component(id="myLink")
private EventLink myLink;
@Component(parameters="context=123")
private ActionLink anotherLink;
In this case only myLink is suggested, as shown in attached screenshot.
Note that the field name is the component's id, if no id is specified
explicitly using @Component annotation.
Original comment by igor.dro...@gmail.com
on 27 Jun 2012 at 2:41
Attachments:
Found out the reason, and fix it in the code already, will update the update
site soon
Original comment by gavingui...@gmail.com
on 27 Jun 2012 at 3:42
Original comment by gavingui...@gmail.com
on 27 Jun 2012 at 3:43
Fix already in version 201207011447
Original comment by gavingui...@gmail.com
on 1 Jul 2012 at 12:36
Original issue reported on code.google.com by
igor.dro...@gmail.com
on 21 May 2012 at 9:11