[wp-hackers] Less than Core, More than Plugins/Themes:
Proposing Optional Modules.
mikeschinkel at newclarity.net
Tue Feb 3 00:25:49 GMT 2009
Those exact dependency issues are already concerns with the core vs. existing plugins and themes. This proposal doesn't modify those concerns at all.
The modules would be versions with the core. Modules could come out after a core update was released but would be associated with the current release. Version control can handle all that nicely.
----- Original Message -----
From: "Matt Walters" <mwalters8 at gmail.com>
To: wp-hackers at lists.automattic.com
Sent: Monday, February 2, 2009 7:15:38 PM GMT -05:00 US/Canada Eastern
Subject: Re: [wp-hackers] Less than Core, More than Plugins/Themes: Proposing Optional Modules.
Does there need to be any concern over dependancy issues the end-user
Theme-X needs module Y
Plugin-A needs module B
Just throwing it out there as that's the first thing that came to my
mind, but no one mentioned it.
On Mon, Feb 2, 2009 at 6:45 PM, Mike Schinkel
<mikeschinkel at newclarity.net> wrote:
> "scribu" <scribu at gmail.com> wrote:
>> As I understand it, it wouldn't be a single plugin framework,
>> but potentially one for each area of interest, for example:
>> podcasts, photo, video, themes etc.
>> WordPress would still be about web publishing, but it could
>> branch out into specific areas, while still being coordinated
>> by the dev team.
> Yes, that's the idea.
> There would, for example, be a real benefit to adding some more advanced concepts for image management but currently each plugin goes it's own way arbitrarily in areas that I would consider "infrastructure", i.e. filenaming conventions, locations, etc. Doing this would eventually empower plugin developers to do a lot more more quickly because they would have less that they would have to do "from scrach."
> -Mike Schinkel
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers