> Yuck, why "patch" the js file when a custom parser could just be > built?
IIRC, the custom parser changed from being able to sort as a set to go an item by item comparison, which eliminated being able to do a natural sorting algorithm. This is a bit different from Rodent's requirements but remains a difficulty nonetheless. How would you propose an custom parser for sorting naturally the following and retaining this order? z1.txt z2.txt z9.txt z10.txt z11.txt z12.txt z20.txt z100.txt On Nov 11, 7:37 am, MorningZ <[EMAIL PROTECTED]> wrote: > Here's an example if my question above is answered by "yes, that's > correct" > > http://paste.pocoo.org/show/90863/ > > Remove the "console.log" if you aren't using FireFox and Firebug > (which you should be as a JavaScript developer!) > > On Nov 11, 8:33 am, MorningZ <[EMAIL PROTECTED]> wrote: > > > Yuck, why "patch" the js file when a custom parser could just be > > built? > > > before that can happen though, something needs to be made more clear > > > in the examples above, you pretty much are just ignoring letters for > > sorting purposes? > > > On Nov 11, 2:51 am, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote: > > > > On Nov 11, 12:29 am, Mike Nichols <[EMAIL PROTECTED]> wrote: > > > > > I submitted a patch a long time ago to do this that implemented a > > > > natural sorting algorithm for this but it would never get applied and > > > > I couldn't get a response..I assumed the project was light or dead. > > > > I can send you the patched .js i had if you like. > > > > Sure. To what file(s) is it a patch, and does it still apply? > > > > Thanks!
