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 (JIRA)" <ji...@apache.org> on 2007/04/11 21:12:32 UTC

[jira] Created: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
-------------------------------------------------------------------------------

                 Key: WICKET-460
                 URL: https://issues.apache.org/jira/browse/WICKET-460
             Project: Wicket
          Issue Type: Improvement
          Components: wicket
            Reporter: Igor Vaynberg
         Assigned To: Igor Vaynberg
             Fix For: 1.3


some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Thomas Singer (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488167 ] 

Thomas Singer commented on WICKET-460:
--------------------------------------

You could write <wicket:fragment wicket:id="foo">? If so, what about taking the part right beside the colon (or maybe a customizable character) as <wicket:*>-tag and keep the part before the colon as id:

<div wicket:id="foo:extend"> becomes <wicket:extend wicket:id="foo"> internally

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488146 ] 

Igor Vaynberg commented on WICKET-460:
--------------------------------------

see http://www.nabble.com/Multi-page-inheritance-tf3553631.html

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488164 ] 

Igor Vaynberg commented on WICKET-460:
--------------------------------------

after thinking about it some more i dont think reusing wicket:id was the best idea because, for example, wicket:fragment do make user of wicket:id

so the new format is

<div wicket:tag="extend"> </div wicket:tag="extend">

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Johan Compagner (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488170 ] 

Johan Compagner commented on WICKET-460:
----------------------------------------

i guess it is not really "now becomes" but "now can also be" ?
 because else we break much.

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-460.
----------------------------------

    Resolution: Won't Fix

users can do this themselves by implementing and register an IMarkupFilter

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488175 ] 

Eelco Hillenius commented on WICKET-460:
----------------------------------------

IMO wicket:tag is a lot more elegant

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg reopened WICKET-460:
----------------------------------


we cant agree on a good format to support this

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488171 ] 

Igor Vaynberg commented on WICKET-460:
--------------------------------------

@Thomas: why do that? whats wrong with wicket:tag?

@Johan: yes, you are right. this is strictly an alternative

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WICKET-460) allow vanilla html alternatives to wicket namespaced tags such as wicket:extend

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-460.
----------------------------------

    Resolution: Fixed

these tags are now supported

<html>
<body>
<wicket:extend>
header
<wicket:child/>
footer
</wicket:extend>
</body>
</html>

now becomes

<html>
<body>
<div wicket:id=":extend">
header
<div wicket:id=":child"/>
footer
</div wicket:id=":extend">
</body>
</html>

notice the use of ":" as the first characater in wicket:id that acts as an escape character
notice that both open AND close tags need wicket:id attrs

> allow vanilla html alternatives to wicket namespaced tags such as wicket:extend
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-460
>                 URL: https://issues.apache.org/jira/browse/WICKET-460
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Igor Vaynberg
>         Assigned To: Igor Vaynberg
>             Fix For: 1.3
>
>
> some people do not like special tags like wicket:extend and would prefer something like <div wicket:id=":extend"> instead

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.