Return-Path: Delivered-To: apmail-click-dev-archive@www.apache.org Received: (qmail 68419 invoked from network); 4 Mar 2010 09:49:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Mar 2010 09:49:00 -0000 Received: (qmail 21646 invoked by uid 500); 4 Mar 2010 09:48:50 -0000 Delivered-To: apmail-click-dev-archive@click.apache.org Received: (qmail 21627 invoked by uid 500); 4 Mar 2010 09:48:50 -0000 Mailing-List: contact dev-help@click.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@click.apache.org Delivered-To: mailing list dev@click.apache.org Received: (qmail 21620 invoked by uid 99); 4 Mar 2010 09:48:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Mar 2010 09:48:50 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Mar 2010 09:48:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 47153234C4DF for ; Thu, 4 Mar 2010 09:48:29 +0000 (UTC) Message-ID: <550694926.63681267696109290.JavaMail.jira@brutus.apache.org> Date: Thu, 4 Mar 2010 09:48:29 +0000 (UTC) From: "Adrian A. (JIRA)" To: dev@click.apache.org Subject: [jira] Commented: (CLK-529) Refactor Prototype based controls to org.apache.click.extras.prototype MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.