jQuery Forum

Yeah, there are definitely two different use cases for creating a new widget from an existing widget. One is inheritance where you're base functionality is the same or very similar (accordion from panel, draggable from mouse). The other is a complex widget that uses existing widgets for part of the functionality (autocomplete using menu).
In addition there are extensions to existing widgets (close button for tabs) which use the proxy pattern and event delegation. Though these don't have anything to do with inheritance.

Soo, any reason not to pull the widgetfactory branch into dev or trunk?
Jörn

<div class="gmail_quote">On Wed, Dec 16, 2009 at 2:41 AM, Jörn Zaefferer <span dir="ltr"><<a href="mailto:joern.zaefferer@googlemail.com">joern.zaefferer@googlemail.com</a>></span> wrote:
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Soo, any reason not to pull the widgetfactory branch into dev or trunk?
</blockquote></div>
There are a few reasons I've been holding off:
1) We need full test coverage of the existing widget factory to make sure the new one isn't missing any features.
2) $.ui.mouse needs to be converted to an actual plugin so that other plugins can inherit from it.
3) Moving it into dev requires updating all dev plugins to use it, which means no plugin could cleanly move to trunk without it.
With that being said, updating an existing plugin to use the new widget factory is, I believe, a two line change per plugin. So #3 isn't a concern of time or code changes, just that of a commitment.

--