Ordering in Models

[nija]

New feature wanted!
Definition order preserved in models.

For some of our models, we do complex ordering server side.
The ordering is lost client side in Opera and Chrome browsers, since
they do not respect definition order, but automatically sort on
numeric keys.

If there is a trick to preserve definition order let me know.
Otherwise it must be a general feature desired by the lots.

V/Niels

[irium]

Yes, it's definitely very needed feature. I'm also posted a question
to Stackoverflow just about this:

http://stackoverflow.com/q/7168983/347309

For now, I had figured it out by using JavaScript's Array.sort()
function, but it could much more useful if Spine.Model has support for
some sort of "sortFields" list or "sort" callback.

[Erfan Imani]

+1 :)

In Firefox, the server-side ordering is retained, unlike Chrome.

[Alex MacCaw]

Trouble is, we're storing the records in a hash (object literal) for fast ID lookups. Although it's not standardized by the spec, most browsers keep the order (I was sure Chrome did - maybe it's only the dev versions). I'm not sure of the correct solution, it's a bit of a trade off. Usually, when I want to sort the records I use the JS array.sort() function, on a callback function defined on the model. 

On Thu, Aug 25, 2011 at 10:39 AM, Erfan Imani <erfan...@gmail.com> wrote:

+1 :)

In Firefox, the server-side ordering is retained, unlike Chrome.

--

Alex MacCaw

+12147175129
@maccman

http://alexmaccaw.co.uk | http://www.leadthinking.com | http://socialmod.com

[Ivan Virabyan]

It would be good, if a refresh() method stored ids of the records in a separate array, preserving order. Then methods like recordsValues() could iterate trough this array and pick records from hash.

[Macario Ortega]

We have encountered this issue in Chrome, I've been overriding @all and sorting using Array.sort(), but then @first and @last records are not guaranteed to be the expected ones. I imagine it is allright to override @recordsValues with a sorted.

[Aaron Eischeid]

there is some good work on this ordering issue in a branch on github. Maybe we can get that in for a 1.1 release of spine before to long. https://github.com/spine/spine/tree/chrome_order_fix 

[defl...@gmail.com]

+1 this is must have feature. Looks like very nice solution in this branch, wait eagerly for it to be released.

среда, 27 февраля 2013 г., 0:34:40 UTC+4 пользователь Aaron Eischeid написал: