You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Craig Tataryn (JIRA)" <ji...@apache.org> on 2011/02/07 23:56:57 UTC
[jira] Created: (WICKET-3434) Allow Component Resolution by CSS
Selector
Allow Component Resolution by CSS Selector
------------------------------------------
Key: WICKET-3434
URL: https://issues.apache.org/jira/browse/WICKET-3434
Project: Wicket
Issue Type: New Feature
Components: wicket
Affects Versions: 1.5-RC1
Reporter: Craig Tataryn
Would like to try implementing Component Resolutions based on CSS selectors instead instead of Wicket IDs as per this thread:
http://apache-wicket.1842946.n4.nabble.com/CSS-Selector-Enhancement-td3265224.html
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-3434) Allow Component Resolution by CSS
Selector
Posted by "Craig Tataryn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991690#comment-12991690 ]
Craig Tataryn commented on WICKET-3434:
---------------------------------------
Problems to be tackled:
17:01 < ThaDon> ivaynberg: ComponentResolver is what I should be looking at right (re: CSS selector JIRA)
17:02 < ivaynberg> no
17:02 < ivaynberg> component resolver maps wicket:id to components in hierarchy
17:02 < ivaynberg> you wont have wicket:id
17:02 < ivaynberg> it will probably be a lot more invasive then that
17:03 < ivaynberg> you will have to extract the current code into a strategy
17:03 < ivaynberg> that resolves a markup tag to a component
17:03 < ivaynberg> the problem right now is that wicket chunks markup
17:03 < ivaynberg> so unless a tag has a wicket:id in it, its considered raw
17:03 < ivaynberg> and consecutive raw tags are concatenated into a string
17:03 < ivaynberg> and rendered as is
17:04 < ivaynberg> all that would have to be changed
17:04 < ivaynberg> and thats a big change
> Allow Component Resolution by CSS Selector
> ------------------------------------------
>
> Key: WICKET-3434
> URL: https://issues.apache.org/jira/browse/WICKET-3434
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Craig Tataryn
>
> Would like to try implementing Component Resolutions based on CSS selectors instead instead of Wicket IDs as per this thread:
> http://apache-wicket.1842946.n4.nabble.com/CSS-Selector-Enhancement-td3265224.html
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WICKET-3434) Allow Component Resolution by CSS
Selector
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst updated WICKET-3434:
-------------------------------------
Priority: Minor (was: Major)
> Allow Component Resolution by CSS Selector
> ------------------------------------------
>
> Key: WICKET-3434
> URL: https://issues.apache.org/jira/browse/WICKET-3434
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-core
> Affects Versions: 1.5-RC1
> Reporter: Craig Tataryn
> Priority: Minor
>
> Would like to try implementing Component Resolutions based on CSS selectors instead instead of Wicket IDs as per this thread:
> http://apache-wicket.1842946.n4.nabble.com/CSS-Selector-Enhancement-td3265224.html
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-3434) Allow Component Resolution by CSS
Selector
Posted by "Craig Tataryn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991687#comment-12991687 ]
Craig Tataryn commented on WICKET-3434:
---------------------------------------
I'll start investigation on this and update the JIRA and mailing thread as I make progress.
> Allow Component Resolution by CSS Selector
> ------------------------------------------
>
> Key: WICKET-3434
> URL: https://issues.apache.org/jira/browse/WICKET-3434
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Craig Tataryn
>
> Would like to try implementing Component Resolutions based on CSS selectors instead instead of Wicket IDs as per this thread:
> http://apache-wicket.1842946.n4.nabble.com/CSS-Selector-Enhancement-td3265224.html
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-3434) Allow Component Resolution by CSS
Selector
Posted by "Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3434.
-------------------------------------
Resolution: Later
I see there is no activity here.
If you have any code or ideas then I'll reopen it.
> Allow Component Resolution by CSS Selector
> ------------------------------------------
>
> Key: WICKET-3434
> URL: https://issues.apache.org/jira/browse/WICKET-3434
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Craig Tataryn
> Priority: Minor
>
> Would like to try implementing Component Resolutions based on CSS selectors instead instead of Wicket IDs as per this thread:
> http://apache-wicket.1842946.n4.nabble.com/CSS-Selector-Enhancement-td3265224.html
--
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