Opened 14 years ago

Closed 10 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:


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:

Change History (5)

comment:1 Changed 14 years ago by bill

Milestone: tbd

mark all (open) tickets w/blank milestones to be "tbd"; their milestones need to be set to a version number or to "future"

comment:2 Changed 14 years ago by Eugene Lazutkin

Milestone: tbdfuture
Status: newassigned

comment:3 Changed 14 years ago by Eugene Lazutkin

Moving all open ticketd to the future.

comment:4 Changed 10 years ago by ben hockey

Keywords: needsreview added
Priority: highlow

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 10 years ago by bill

Keywords: needsreview removed
Resolution: wontfix
Status: assignedclosed

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).

Note: See TracTickets for help on using tickets.