With regard to Panel usage, I don't think we should use
<wicket:panel/> and come up with a new tag for every single possible
Wicket componet. What I was simply trying to say is that for Panels,
which are normal Wicket components, you should refering to the wicket
component ID (which might or might not be a panel) in your index.html
and Wicket will bind it like normal. We should not have any sort of
"special keyword" called Panel.
On the topic of <wicket:remove/> I meant to say this is a
different case because we either:
1) Treat "remove" as a component and users would have to specify a
component name and bind to it from the Java side like any other
component, or...
2) Treat "remove" as a special tag and use <wicket:remove> some body
</wicket:remove> to denote that it should be removed without an
associated Wicket component.
Gili
On Thu, 6 Jan 2005 10:11:42 -0800 (PST), Jonathan Locke wrote:
>idea with wicket:region was to reduce the namespace explosion so we
>don't reserve too many wicket:* names. if people don't like this, we
>could go with wicket:panel, wicket:remove, etc. i had half a mind to
>suggest that, so i'm good with either.
>
>don't forget that a panel can't be defined as <wicket:region name =
>"panel"/> because the panel is a region in the html file rather than the
>whole html file.
>
>On Thu, 6 Jan 2005, Gili wrote:
>
>> Hi,
>>
>> I think you made a typo in your RFE, otherwise I disagree with
>> your example. It reads:
>>
>> <div id="header"/><wicket:region name="panel"> ...
>>
>> I think it should read:
>>
>> <div id="header"><wicket:region name="panel"></div>
>>
>> Or, why do we need the surrounding <div> at all?
>>
>> Furthermore, for previewability I am debating with Juergen on
>> whether to use:
>>
>> <wicket:region name="panel"/><wicket:region
>> name="remove">username:<br>password:<br></wicket:region>
>>
>> or
>>
>> <wicket:region name="panel"><wicket:region
>> name="remove">username:<br>password:<br></wicket:region></wicket:region>
>>
>>
>> That is, can you embed a body within a Panel as long as it is
>> removed at runtime? I personally refer the second method of embeding a
>> removable body within the Panel.
>>
>> Another point: I don't like the fact that a region by the name
>> of "remove" or "panel" is some magical region name. My original goal
>> (as I stated in our autolink discussion) is that these names/parameters
>> should be just a normal string and should *not* automatically bind to a
>> special component type. Are you saying that there is a Wicket component
>> called "remove" on the Java end? If not, I dislike this approach. I
>> don't want to have any reserved/special names or parameters that
>> magically create components -- this sort of thing belongs within its
>> own tag such as <wicket:remove> blah </wicket:remove>
>>
>> What do you think?
>>
>> Gili
>>
>> On Thu, 06 Jan 2005 01:50:42 -0800, SourceForge.net wrote:
>>
>> >Bugs item #1097047, was opened at 2005-01-06 10:50
>> >Message generated for change (Tracker Item Submitted) made by Item Submitter
>> >You can respond by visiting:
>> >https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1097047&group_id=119783
>> >
>> >Category: core
>> >Group: None
>> >Status: Open
>> >Resolution: None
>> >Priority: 7
>> >Submitted By: Eelco Hillenius (eelco12)
>> >Assigned to: Nobody/Anonymous (nobody)
>> >Summary: Id's of panels do not have wicket- removed
>> >
>> >Initial Comment:
>> >While the id's of components like labels have the
>> >wicket prefix removed (e.g. <span
>> >id="wicket-myLabel">blah</span> renders <span
>> >id="myLabel">blah</span).
>> >
>> >This is not the case for panels.
>> >
>> >E.g. <div id="wicket-header"/> will render to:
>> >
>> ><div id="wicket-header"/><wicket:region name="panel"> ...
>> >
>> >while it should be:
>> >
>> ><div id="header"/><wicket:region name="panel"> ...
>> >
>> >----------------------------------------------------------------------
>> >
>> >You can respond by visiting:
>> >https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1097047&group_id=119783
>> >
>> >
>> >-------------------------------------------------------
>> >The SF.Net email is sponsored by: Beat the post-holiday blues
>> >Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>> >It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>> >_______________________________________________
>> >Wicket-develop mailing list
>> >[email protected]
>> >https://lists.sourceforge.net/lists/listinfo/wicket-develop
>> >
>>
>>
>>
>>
>> -------------------------------------------------------
>> The SF.Net email is sponsored by: Beat the post-holiday blues
>> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>> _______________________________________________
>> Wicket-develop mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>>
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Wicket-develop mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
