[
https://issues.apache.org/jira/browse/CLK-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841148#action_12841148
]
Adrian A. commented on CLK-529:
-------------------------------
> I don't see a reason for pushing this change as this stage.
There are a few reasons IMHO:
1. make place for jQuery components
2. prototype libraries need updates too, so those components will be modified
anyway (why not do the migration Malcolm proposed with this way?).
3. reduce confusion and make Click more predictable - I'm always asked about
jQuery, and what components don't work with it. Having prototype clearly
separated into a package makes all questions obsolete. The same is true for
mooTools and other ones.
4. users will also see that we don't favor the one over the other JS framework
since each one is in it's own separate package
5. as Malcolm mentioned, we can't have the results right away, but need two
major releases (2.2 deprecated, 2.3 removed), so we need to do it now to have
the results maybe in a year.
> Refactor Prototype based controls to org.apache.click.extras.prototype
> ----------------------------------------------------------------------
>
> Key: CLK-529
> URL: https://issues.apache.org/jira/browse/CLK-529
> Project: Click
> Issue Type: New Feature
> Components: extras
> Reporter: Adrian A.
> Fix For: 2.2.0
>
>
> Refactor the Prototype base Click controls to a separate package
> org.apache.click.extras.prototype.
> This would allow a nice separation and easy integration of other javascript
> frameworks too.
> It would be also much easier for the users, since there also might be
> duplicate components made with other javascript frameworks too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
