Opened 11 years ago
Closed 8 years ago
#7102 closed enhancement (wontfix)
Allow DnD containers to be referenced another way than solely by the jsId
Reported by: | guest | Owned by: | Eugene Lazutkin |
---|---|---|---|
Priority: | low | Milestone: | future |
Component: | DnD | Version: | 1.1.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Provide a way for a developer to be able to reference a DnD container some other way than using the jsId object directly. For example, perhaps there could be some function getContainer("jsId_name_string"), which would return the object which was created from the jsId attribute for that container.
For more info, see the following post: http://dojotoolkit.org/forum/dojo-core-dojo-0-9/dojo-core-support/how-do-you-reference-source-target-custom-creator-functio#comment-14370
Change History (5)
comment:1 Changed 11 years ago by
Milestone: | → tbd |
---|
comment:2 Changed 11 years ago by
Milestone: | tbd → future |
---|---|
Status: | new → assigned |
comment:4 Changed 8 years ago by
Keywords: | needsreview added |
---|---|
Priority: | high → low |
i'm trying to identify stale tickets. if there is a need to keep this ticket open, please replace the "needsreview" keyword with "reviewed". if there is no need to keep this ticket open then please close it.
comment:5 Changed 8 years ago by
Keywords: | needsreview removed |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
i think this can be closed. You could use the dijit/registry if you really wanted DnD containers to get registered, although you'd need to subclass dojo.dnd.Source to register itself. But basically, I don't see a problem with using data-dojo-id (nee jsId).
mark all (open) tickets w/blank milestones to be "tbd"; their milestones need to be set to a version number or to "future"