Opened 14 years ago

Closed 14 years ago

#7352 closed defect (wontfix)

need alias for dojox.widget's that have moved to dojox.form

Reported by: Chris Mitchell Owned by: Nathan Toone
Priority: lowest Milestone: tbd
Component: DojoX Widgets Version: 1.1.1
Keywords: Cc:
Blocked By: Blocking:


Please add an alias with deprecation warning in dojox.widget to map old dojox.widget names to dojox.form widget names. Although these are experimental, this small change helps applications that are already using widgets from dojox.widget from breaking right off the bat, with a kinder warning message explaining new use. These changes should be added to the 1.1-1.2 migration doc page.

Change History (2)

comment:1 Changed 14 years ago by dante

Owner: changed from dante to Nathan Toone
Priority: normallowest

these changes are noted on the 1.2 release notes, and each change is referenced on the ticket #6243. I'm against putting several stub files in to deprecate experimental widgets. If we don't have this luxury with dojox, combined with a clear experimental() call, what is the point in declaring "some of these widgets may disappear entirely"? Grid being a reasonable exception, I was under the impression DojoX was not subject to the deprecation policy in place for Dojo Core and Dijit projects. There are a LOT of small changes in experimental widgets above the simple renaming of !dojox.widget.Thinger to !dojox.form.Thinger, and while I agree it would be helpful to some to provide stubs, I think it should only be considered being applied to things not experimentally tagged. Where in Dojo can the developers and community have "fun" if not for sharing and developing experimental code?

comment:2 Changed 14 years ago by Nathan Toone

Resolution: wontfix
Status: newclosed

I tend to agree with pete here - it's one thing to stub in the grid - but to create a bunch of small stub files (and maintain them as well) for quite minor widgets is another thing completely.

As mentioned, these changes have been documented in the release notes for 1.2.

Note: See TracTickets for help on using tickets.