[ 
https://issues.apache.org/jira/browse/WICKET-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095961#comment-13095961
 ] 

Martin Grigorov commented on WICKET-4007:
-----------------------------------------

Bruno,

I respect you for doing these contributions and spending time to implement and 
test them.
But unfortunately not every idea out there can be included in the distro. You 
asked for feedback on the idea in the mailing lists and you see that both users 
and devs are not excited. 
>From user point of view it indeed looks like a step back. It looks like "how 
>the action based frameworks do it". 
My developer point of view: I try to avoid using <wicket:xyz> in my code as 
much as possible because these are the most hard features to debug and support. 
Every now and then a ticket pops up with a problem related to auto-components.
Additionally I don't like that you put that TreeMap in MarkupContainer. This 
will increase the Component size and respectively the Page size and we try to 
keep it as small as possible.
I hope you can still use this feature in your application without changes in 
Wicket core. Ignore us, it is your baby - enjoy it ;-)

> New tag wicket:var
> ------------------
>
>                 Key: WICKET-4007
>                 URL: https://issues.apache.org/jira/browse/WICKET-4007
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>            Reporter: Bruno Borges
>              Labels: tag,, variable, wicket,
>         Attachments: wicket-var-feature.diff
>
>
> This will facilitate users to reference models in several places of the 
> markup.
> One can do: 
> class Page extends WebPage {
>   public Page() {
>     putVariable("username", "Peter Johnson");
>   }
> }
> <html>
> <body>
>   <div class="header">
>     <wicket:var name="name" />
>   </div>
>   <div class="container">
>     <wicket:var name="name" />
>   </div>
>   <div class="footer">
>     <wicket:var name="name" />
>   </div>
> </body>
> </html>
> It will be possible too to do such a thing:
>   Java:  putVariable("css", "blue-header");
>   HTML:   <div wicket:var="class:css">
> And render: <div class="blue-header">
> These variables can be rendered multiple times and my also be accessed from 
> child objects (but not the opposite), like:
>   add(new WebMarkupContainer("header"));
> <div wicket:id="header">
>   <span wicket:var="class:css">Header</span>
> </div>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to