[wp-hackers] Less than Core, More than Plugins/Themes: Proposing Optional Modules.

[Matt Walters]

I'm not saying that the Module idea is not worth it (I'm more or less
indifferent).  But I do think modules could potentially compound this
concern.  I get what you're saying in that even currently, a theme may
not work without x, y and z plugins, but adding in Modules would only
expand the risk of running into those issues.

I'm fairly certain that this could be handled elegantly though, for
instance some sort of notification along the lines of, "This theme
requires Module E, would you like to install it now?" (along the lines
of one click upgrades, etc)

---------------------------------
Matt Walters
http://mattwalters.net/

On Mon, Feb 2, 2009 at 7:25 PM, Mike Schinkel
<mikeschinkel at newclarity.net> wrote:
> 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.
>
> -Mike Schinkel
> http://mikeschinkel.com/
>
> ----- 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
> might face?
>
> Theme-X needs module Y
>
> Plugin-A needs module B
>
> etc...
>
> Just throwing it out there as that's the first thing that came to my
> mind, but no one mentioned it.
>
> ---------------------------------
> Matt Walters
>
>
>
>
> 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
>> http://mikeschinkel.com/
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>