[wp-hackers] a plugin of a theme's own

[Robert Deaton]

Well, at this point I think we are supposed to hold off on documenting
1.6 features, and I've been meaning to pull up a thread on the Docs
list on if we should copy to Page_1.6 and start documentation, since a
lot of APIs are changing. If someone else wants to start it, It would
be apprecitaed.

On 9/19/05, Trevor Turk <trevorturk at yahoo.com> wrote:
> > In WordPress, as in other pluginophilic packages, it
> > is up to the
> > plugin authors to handle plugin-to-plugin
> > incompatibilities. They can
> > use coordination, documentation, option panels or
> > conditional function
> > declarations.
> >
> > In the interest of keeping the core light and fast,
> > the options in the
> > stock user interface minimal  and plugin authors
> > responsible, I would
> > let this very convenient new include stand like it
> > is.
> >
> > Andy
> >
> 
> OK. I just wanted to go over it because I thought it
> might be a support issue in the future. But this
> sounds right to me. Thanks for clarifying - I think it
> was worth going over, at least it was to me!
> 
> I'm not seeing this ability documented anywhere
> (http://codex.wordpress.org/Theme_Development ?) so
> I'll ask the doc people if it exists somewhere or
> write it up.
> 
> - Trevor
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> 


-- 
--Robert Deaton
http://somethingunpredictable.com