Skip to main content

Search and Top Navigation

#8390 closed enhancement (wontfix)

Opened June 08, 2012 05:05PM UTC

Closed June 08, 2012 05:13PM UTC

Last modified June 08, 2012 06:01PM UTC

ComboBox is a Widget, not a Code Example

Reported by: jeremy Owned by:
Priority: minor Milestone: 1.9.0
Component: ui.core Version: 1.8.21
Keywords: Cc:
Blocked by: Blocking:
Description

Code examples are (supposed to be) small snippets of code that demonstrate the functionality of a jQuery UI widget. A user should be able to look at them to see how to use the various methods/properties of a widgets.

One example however does not fit this mold: the "combo box" example of the AutoComplete widget. If you look at the code for combo box, you'll see that it's actually a 100+ line $.widget of its own. As such, it really deserves to be a (simple) first-class UI widget. This would make it much easier to find, since people looking for a combo box don't inherently know to look at autocomplete. It would also make the example code much simpler (instead of 100+ lines you'd have $('input').combobox(); which would you say is easier for a new user to "grok"?).

Plus, showing jQuery UI's true number of widgets (instead of hiding one inside another) would make the library look more mature.

Attachments (0)
Change History (5)

Changed June 08, 2012 05:11PM UTC by jeremy comment:1

Oh, one more big reason why this would be great: every user would get combo box "for free" with jQuery UI, and get it updated whenever they update jQuery UI (as opposed to now, where they have to find the secret code hidden in the "view source" of an example, then copy/paste it in to their own codebase separate from jQuery UI, then check back in the documentation every time they upgrade jQuery UI to get the updated code).

Changed June 08, 2012 05:13PM UTC by scottgonzalez comment:2

_comment0: Combobox is not an officially supported widget. We may make it one in the future, but it is not today. We have a not on the demo page about this, but it apparently wasn't merged into 1-8-stable, so it doesn't show up on jqueryui.com :-/ \ \ There's a lot of work that goes into making combobox a full widget and we're not ready to take on that work.1339175656562007
resolution: → wontfix
status: newclosed

Combobox is not an officially supported widget. We may make it one in the future, but it is not today. We have a note on the demo page about this, but it apparently wasn't merged into 1-8-stable, so it doesn't show up on jqueryui.com :-/

There's a lot of work that goes into making combobox a full widget and we're not ready to take on that work.

Changed June 08, 2012 05:19PM UTC by jeremy comment:3

I see. While I'm certainly willing to wait until it is fully supported, is there any sort of compromise that could be reached in the meantime? In other words, is there any way to include just the version you've already written in jQuery UI proper (solving the maintenance issue and simplifying the sample code so it's actually useful to new users), without promoting it to a full-blown widget?

Changed June 08, 2012 05:28PM UTC by jeremy comment:4

By the way, in deciding whether or not to promote combo box, I recommend googling and/or searching Stack Overflow for jQuery UI combo box. Whether the jQuery UI team decides to promote it or not, people are already treating it as a real widget (which is understandable given how significant the combo box is in modern web development). People need an autocomplete widget, and it's a testament to how popular/useful jQuery UI is that they take an unspported secret bit of code in an example over using a new UI library :-)

Changed June 08, 2012 06:01PM UTC by scottgonzalez comment:5

Replying to [comment:3 jeremy]:

I see. While I'm certainly willing to wait until it is fully supported, is there any sort of compromise that could be reached in the meantime? In other words, is there any way to include just the version you've already written in jQuery UI proper (solving the maintenance issue and simplifying the sample code so it's actually useful to new users), without promoting it to a full-blown widget?

No. Releasing it would mean that we support it.