You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Makundi (JIRA)" <ji...@apache.org> on 2011/01/18 10:48:45 UTC
[jira] Commented: (WICKET-3335) Component Queuing (extract
hierarchy information from markup)
[ https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983098#action_12983098 ]
Martin Makundi commented on WICKET-3335:
----------------------------------------
I vote
+1 for adding it to 1.4.x
because this feature does not compromise anything, it is just an alternate way of adding components.
> Component Queuing (extract hierarchy information from markup)
> -------------------------------------------------------------
>
> Key: WICKET-3335
> URL: https://issues.apache.org/jira/browse/WICKET-3335
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Giannis Koutsoubos
> Attachments: 0001-component-queuing.patch
>
>
> Doubly defined hierarhices are redundant.
> Server-side hierarchy can be automatically deduced from markup hierarchy.
> Use queue method in MarkupContainer to add components and extract hierarchy information from markup.
> Discussed here: http://apache-wicket.1842946.n4.nabble.com/Free-wicket-from-component-hierarchy-hell-td3027705.html
> Implementation of queue method on branch 1.4.x : https://github.com/koutsoub/wicket/tree/component-queuing
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.