[
https://issues.apache.org/jira/browse/WICKET-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032534#comment-13032534
]
Ondra Žižka commented on WICKET-3335:
-------------------------------------
..which leads me to another idea - jQuery-like components selectors:
getComponents("Form#form1 WebMarkupContainer.holder input"); // CSS-like
syntax
That would traverse this component's tree and return a collection of matching
components.
Components could have CSS-like classes for this purpose.
Or with a collection proxy able to change the component...
getComponents("Form#form1 WebMarkupContainer.holder input").setVisible(false)
Was something like that proposed?
Maybe this could bring some fresh air to solutions for things like group of
checkboxes etc.
> 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-core
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
