[wp-hackers] Multiwidget Support

[Chris Williams]

+1 for a clean, simple class that implements this in core.  And true enough
that the exception should be a single instance one, not the other way
around.

Spent the last 36 hours trying like heck to get a multi-widget to work
right.  It's almost like magic spell incantation, try something, hope it
works, try something else :)

> From: scribu <scribu at gmail.com>
> Reply-To: <wp-hackers at lists.automattic.com>
> Date: Fri, 6 Feb 2009 00:13:26 +0200
> To: <wp-hackers at lists.automattic.com>
> Subject: Re: [wp-hackers] Multiwidget Support
> 
> On Thu, Feb 5, 2009 at 11:59 PM, Austin Matzko <if.website at gmail.com> wrote:
> 
>> On Thu, Feb 5, 2009 at 3:55 PM, Chris Jean <gaarai at gaarai.com> wrote:
>>> I've suffered through development of widgets that support multiple
>> instances
>>> many times. Recently, I began wondering some things:
>>> 
>>>  1. Why is the method for producing multiwidgets so obscure and
>>>     complicated?
>>>  2. Why is there any need to support a single-instance widget?
>>>  3. Why aren't all the core widgets multiwidgets?
>>>  4. Couldn't the method of registering and controlling widgets be
>>>     improved to automatically make all widgets multiwidgets?
>>> 
>>> Of course, for that last option to work, the storage mechanism would have
>> to
>>> be standardized. That's not a bad idea though.
>> 
>> I think this is a step in the right direction:
>> 
>> http://trac.wordpress.org/ticket/8441
> 
> 
> +1 for core.
> 
> I was also thinking of making a class for multiple widgets. Thanks for
> saving me the trouble.
> 
> Another thing, why do you have to register a widget after 'plugins_loaded' ?
> By the way they are implemented, they still feel like part of a plugin, yet
> you can't disable them from the plugins menu.