[jQuery] Plugin Development Process

2007-02-18 Thread Mattias Hising
Hi all,

I have been thinking about the plugin development process for jquery.
As it is today we have a wide variety of plugins and some of them are
officially supported. The problem as I see it today are the following:

- Version management, some plugins that are official do not change in
the same speed as the jquery core, leaving end-users to either not
upgrade the core or make their own changes to offical plugins. This is
not optimal. I believe that in order to become an official plugin, the
author(s) of the plugin has to verify what plugin versions works with
what core versions. If this is not possible, we must create a way to
identify how to work with plugins and version without forcing the
end-user to manually hack the core of jquery or the plugins. Maybe we
should look at PEAR or other libraries and see how they handle version
management for plugins.

- Offical plugins becomes official by word-of-mouth today, that is the
only way as it is now. Maybe offical plugins also should be able to
become official by adding requirement specifications for future
plugins to the jquery plugin library and letting development-teams
take on these requirements.

- Coding conventions. I believe that in order to make a plugin
official it has to follow strict coding conventions, otherwise it is
difficult for people to take on development whenever the orginal
author feels he/she do not have the time or focus for keeping the work
up.

This is just my thoughts and I am sure that John and the rest of the
core team has big ideas in this area, I just hope to create a bigger
discussion about how to work with official plugins and how to handle
requests for plugins, which I think is an important step in order to
jquery to become more stable, user-friendly and the de-facto choice
for javascript-libraries.

Best regards,
Mattias Hising
Front-End Architect PokerRoom.com

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


Re: [jQuery] Plugin Development Process

2007-02-18 Thread John Resig
You should post this to the development mailing list:
http://jquery.com/mailman/listinfo/dev_jquery.com

We've been discussing plugin-related issues over there. Along with
drafting up the new plugin requirements and spec.

--John

On 2/18/07, Mattias Hising [EMAIL PROTECTED] wrote:
 Hi all,

 I have been thinking about the plugin development process for jquery.
 As it is today we have a wide variety of plugins and some of them are
 officially supported. The problem as I see it today are the following:

 - Version management, some plugins that are official do not change in
 the same speed as the jquery core, leaving end-users to either not
 upgrade the core or make their own changes to offical plugins. This is
 not optimal. I believe that in order to become an official plugin, the
 author(s) of the plugin has to verify what plugin versions works with
 what core versions. If this is not possible, we must create a way to
 identify how to work with plugins and version without forcing the
 end-user to manually hack the core of jquery or the plugins. Maybe we
 should look at PEAR or other libraries and see how they handle version
 management for plugins.

 - Offical plugins becomes official by word-of-mouth today, that is the
 only way as it is now. Maybe offical plugins also should be able to
 become official by adding requirement specifications for future
 plugins to the jquery plugin library and letting development-teams
 take on these requirements.

 - Coding conventions. I believe that in order to make a plugin
 official it has to follow strict coding conventions, otherwise it is
 difficult for people to take on development whenever the orginal
 author feels he/she do not have the time or focus for keeping the work
 up.

 This is just my thoughts and I am sure that John and the rest of the
 core team has big ideas in this area, I just hope to create a bigger
 discussion about how to work with official plugins and how to handle
 requests for plugins, which I think is an important step in order to
 jquery to become more stable, user-friendly and the de-facto choice
 for javascript-libraries.

 Best regards,
 Mattias Hising
 Front-End Architect PokerRoom.com

 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/