You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (Commented) (JIRA)" <ji...@apache.org> on 2012/03/23 16:35:28 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=13236681#comment-13236681 ]
Igor Vaynberg commented on WICKET-3335:
---------------------------------------
this is a much more complex problem that i thought initially, mainly because it has to work with auto resolved tags which "pollute" nesting information in markup.
some unfinished attempts at this are in the origin/sandbox/component-queueing and origin/sandbox/hierarchy-completion branches.
> 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
> Assignee: Igor Vaynberg
> Attachments: 0001-component-queuing.patch, wicket-3335.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira