Hi Martijn,
ok, if it so wrong then how to better solve this situation:
Goal: Generic Suckerfish drop Down with Multiple levels, usable for
Bookmarkable,Page + AjaxLinks etc.;
My Solution: 1 Panel holding outer Markup, inheriting a TreePanel;
Links are injected using a List<LinkListItem>;
while LinkListItem has:
public LinkListItem(String label, AbstractLink link, List<LinkListItem>
sublist)
I thought of about a dozen tings, but I couldnt find a way to supply a
LinkListItem where not to send a Link through, as links either want a
class (Bookmarkable + Page) or a onClick (usual Link) and the Ajax
target onClick(target);
How would you then solve this not sending the components?
Best,
Korbinian
Martijn Dashorst schrieb:
you should not re use a component instance in your component
hierarchy. That is *so* wrong. e.g. creating a panel outside a
listview's onpopulate and adding it to the listitem?
Martijn
On 4/12/08, Korbinian Bachl - privat <[EMAIL PROTECTED]> wrote:
Thanks for clear answer; In case i I add a feature request: would it even be
possible to change the Id at a later time?
I catch me regularly to add Components like Links, Panels etc. to a
List<Component> and have them rendered later on to different Markups in
different ListViews - and that means I need to hold them in sync regarding
their id;
And another feature request idea: would it be OK to add a synonym for
wicket:id="" e.g.: w:id="" or even only :id="" ? Would be some less typing
:)
Best,
Korbinian
Matej Knopp schrieb:
short question: Why isn't it possible to have a setId(String id) on the
components?
short anwer:
- Is it really necessary that they know their id at creation-time?
yes
-Matej
Regards,
Korbinian
