[wp-hackers] Custom Post Types and pending incompatibilities

[Charles Frees-Melvin]

What if we were to have a Codex page where plugin authors can list their custom post type there by allowing other plugin authors to see the most used post type for their niche. Then list any that are specific or need to be different be prefixed with the plugin name as mentioned.

In this format the core team can choose a name not listed, or pre-reserve a custom post type when a patch or ticket is in Trac.

Just a thought, but would require a tough luck approach if core chooses one that was not on said list.
--
Charles E. Frees-Melvin
charles at cefm.ca
www.cefm.ca
506-640-1007

Sent from my iPhone 3G

On 2010-07-10, at 17:09, Mike Schinkel <mikeschinkel at newclarity.net> wrote:

> On Jul 10, 2010, at 4:05 PM, Otto wrote:
>> One would hope that plugins would use a prefix naming convention for
>> their custom types in the same way we recommend making function names
>> and such. plugin_whatever and so forth.
> 
> One would hope, but none of the examples I've seen online are doing that so I doubt that many people will think to do so. 
> 
> Not sure how to get that "best practice" out there so that it becomes widely know?
> 
>> I like your ideas, and I would also suggest that plugin authors doing
>> the same sort of things in their plugins start to collaborate amongst
>> themselves to build larger plugins with many authors.
> 
> +1
> 
> -Mike
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers