World: r4wp

so it would be:
sort/compare/skip/index series :sf 2 2

testing it now...

doh... that's my old modified sort func...

compare is used for the index and the func... hum.

I think you get blocks of fields when you use /compare with /skip

>> blk: [1 [2  3] 0 [4 8] 5 [4 3]]
>> sort/skip blk 1
== [0 [4 8] 1 [2 3] 5 [4 3]]

sorry - that should read 
>> sort/skip blk 2

ok - am failing with the test, probably because i specified the problem 
wrongly

h: #hash! [k-a object! [
    name: "wonderwoman"
    attribs: make hash! ["1993-1994" #object! [
            rebal-year: 1993
            m: 160.018245
        ] "1992-1993" #object! [
            rebal-year: 1992
            m: 104.293
        ] "1991-1992" #object! [
            rebal-year: 1991
            m: 26.628
        ]]
...and so on...

my keys - for both the main hash and the inner hash are strings

i need to sort the hash h by the m attribute of the attribs hash
any ideas? would the same :sf work?

ok, so to get complete records, you need the /all refinement...

>> sort/skip/compare/all [1 [2  "a"] 0 [4 "z"] 5 [4 "m"]] 2 func 
[a b][a/2/2 < b/2/2 ]
== [1 [2 "a"] 5 [4 "m"] 0 [4 "z"]]

a, m, z are sorted.

yup - that works...
but would it work for the structure i posted?

yes, you just need to adapt the paths you lookup.  the sort func 
gets a pair of blocks which are the whole records, which is why I 
start with a /2 to get the second field, which is the block ... in 
your case, that would be the object

ok - thanks maxim
trrying it now

any luck with the new release of mod-web-api?

...and the json data structure?

the mod has been so heavily modified, its almost a complete rewrite. 
 its also heavily embeded within our production environement (libs 
and stuff) so that making it a stand-alone mod again will take some 
time... some time which currently, I don't have.  though note that 
we didin't actually add json support but greatly increased the flexibility 
of the i/o format conversion.

sounds great...since i'm a noob, not sure i can help, but will gladly 
pitch in

we neededed to support, xml rest, SOAP and direct get/post interface 
to the same functions, and that is now working via a configuration, 
which allows you to tweak how the url is read and switch interfaces 
on the fly.

I also added path support for the mod so that you can use the same 
domain for web and api services.

wow - cool!

any chance i can get to play with the code?

like I said , right now I can't rip it out easily because a lot of 
the code is shared with the code it serves (which is not part of 
the open source package).   It wasn't built with the task of making 
it independent... but it can be done.  It just takes time, which 
I currently don't have.

no worries - am happy to wait!

sorry maxim - not having any luck with the sort function

>> sf: func [a b][o: select a/attribs "1991-1992" m: select b/attribs 
"1991-1992" o/m > m/m ]
>> sort/skip/compare/all comps 2 :sf
** Script Error: Invalid path value: attribs
** Near: o: select a/attribs "1991-1992"

help?

One of your objects does not have the 'attribs word.

this is the structure i'm using:
h: #hash! [k-a object! [
    name: "wonderwoman"
    attribs: make hash! ["1993-1994" #object! [
            rebal-year: 1993
            m: 160.018245
        ] "1992-1993" #object! [
            rebal-year: 1992
            m: 104.293
        ] "1991-1992" #object! [
            rebal-year: 1991
            m: 26.628
        ] ] k-b object! [
    name: "wonderwoman"
    attribs: make hash! ["1993-1994" #object! [
            rebal-year: 1993
            m: 160.018245
        ] "1992-1993" #object! [
            rebal-year: 1992
            m: 104.293
        ] "1991-1992" #object! [
            rebal-year: 1991
            m: 26.628
        ] ]

The first element in that has does not appear to be an object.

that has = that hash

yes - its actually a string

shouldnt sort/skip/compare/all comps 2 :sf pick up the object?

I'm not sure if it's possible, but you may then need to use 4 parameters 
instead of 2 in the compare function. Then use the string/object 
pairs for comparison.

I'm not certain that SKIP can be used with COMPARE.

ah - so i should do:

>> sf: func [a b c d] [ o: select b/attribs "1991-1992" m: select 
d/attribs "1991-1992" o/m > m/m]
??

Untested, but yes, that's what I meant. I really don't know if it 
works.

i get:
>> sort/compare comps :sf
** Script Error: Invalid argument: ?function?
** Near: sort/compare comps :sf

>> sort/compare/all comps :sf
** Script Error: Invalid argument: ?function?
** Near: sort/compare comps :sf

Back to the drawing board Sujoy and displaying the elements you want 
to use in your function piece by piece and maybe dump-obj is of any 
use?
(Now you don't use a and c)

the sort/compare works great if its an object...am stuck because 
its a hash

Testing your code. What is COMPS?

sorry - comps should be h - the hash

ok, the sort function must only have 2 parameters.

not quite understanding how to use sort with this structure...

The structure is a little strange. Are you trying to sort the outer 
hash or the inner hash?

both actually - need the outer hash sorted based on a property of 
the object inside the inner hash

ideally, would like to keep the hash h intact for retrieval by the 
keys