Opened 12 years ago

Closed 7 years ago

Last modified 7 years ago

#5939 closed task (wontfix)

extract a dijit._DataBound mixin, refactor data-bound widgets to use it

Reported by: alex Owned by: Jared Jurkiewicz
Priority: low Milestone: future
Component: Dijit Version: 1.0
Keywords: dijit, data, binding, mixin Cc:
Blocked By: Blocking:

Description (last modified by Jared Jurkiewicz)

currently, many widgets have some common data-binding properties and events. These should be extracted and codified. Namely, the following seem important for a first cut: 

{
  store: null,
  query: null,
  pageSize: 100,
  ...
}

Change History (6)

comment:1 Changed 12 years ago by alex

Component: General → Data
Keywords: dijit data binding mixin added
Owner: changed from anonymous to Jared Jurkiewicz

comment:2 Changed 11 years ago by Jared Jurkiewicz

Description: modified (diff)
Milestone: 1.2 → 1.3

Not enough time remaining in 1.2 to make a sweeping dijit change. Therefore moving this out.

comment:3 Changed 11 years ago by bill

Milestone: 1.3 → future
Type: enhancement → task

comment:4 Changed 7 years ago by ben hockey

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

Component: Data → Dijit
Resolution: → wontfix
Status: new → closed

I've heard various people claim this is important but if it's just those three attributes then I disagree. I'm going to close this ticket. If someone has a patch for this though I'd take a look.

comment:6 Changed 7 years ago by bill

Keywords: needsreview removed
Note: See TracTickets for help on using tickets.