[ 
https://issues.apache.org/jira/browse/TAPESTRY-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543747
 ] 

Kevin Menard commented on TAPESTRY-1827:
----------------------------------------

Yeah.  There certainly are ways to work around it locally.  It just struck me 
as something that should probably be addressed at the framework level for the 
benefit of all.

> "Checkbox" component should be named "CheckBox"
> -----------------------------------------------
>
>                 Key: TAPESTRY-1827
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1827
>             Project: Tapestry
>          Issue Type: Wish
>          Components: Core Components
>    Affects Versions: 4.1.3
>            Reporter: Kevin Menard
>            Priority: Minor
>
> All of the components with composite names use camel-case naming, except for 
> "Checkbox".  It can be very confusing for amateur and veteran alike.
> I'd recommend renaming the component and then aliasing "Checkbox" over for 
> backward compatibility, at least on 4.1.x.  Since 5.0.x has already renamed 
> some core components, there may be less of a need to maintain backward 
> compatibility.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to