_k parameter at the end of the path?

Hi -

Is there any way to move the _k parameter to the end of the path in
Seaside 3.0 so it appears after my other entries in queryFields?

Thanks

Paul
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

When #updateUrl: is called on your component tree _k (and if necessary
_s) are already present. GROrderedMultiMap appends new values by
default, but it would be easy to add a variation that prepends new
query fields.

Lukas

On 26 October 2011 19:40, Paul DeBruicker <[hidden email]> wrote:


--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I'm curious as to what the motivation may be?

-Boris


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Lukas
Renggli
Sent: Wednesday, October 26, 2011 2:03 PM
To: Seaside - general discussion
Subject: Re: [Seaside] _k parameter at the end of the path?

When #updateUrl: is called on your component tree _k (and if necessary
_s) are already present. GROrderedMultiMap appends new values by
default, but it would be easy to add a variation that prepends new query
fields.

Lukas

On 26 October 2011 19:40, Paul DeBruicker <[hidden email]> wrote:


--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 11-10-26 11:04 AM, Boris Popov, DeepCove Labs wrote:
> I'm curious as to what the motivation may be?
>
> -Boris


Purely for the aesthetics.  Reading left-to-right I'd rather have the _k
parameter at the end so the query fields in the url are organized in
increasing order of meaninglessness to a human reader as you get to the
end of the url.  I'd want the same for the _s parameter but I'm using
cookies at the moment so its not in the url path.



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 11-10-26 11:02 AM, Lukas Renggli wrote:
> When #updateUrl: is called on your component tree _k (and if necessary
> _s) are already present. GROrderedMultiMap appends new values by
> default, but it would be easy to add a variation that prepends new
> query fields.
>
> Lukas
>

Thanks for the tip.  This does what I want:

WARequestFields>>#at:add:

        at: aKey put: aValue
        ^self prepend: aKey and: aValue


WARequestFields>>#prepend:and:
        prepend: aKey and: aValue

        |newKeys newValues|
        size = keys size ifTrue: [ self grow ].
        newKeys:=Array new: (size:=size+1).
        newValues:=Array new: size.
        newKeys at: 1 put: aKey.
        newValues at: 1 put: aValue.
        1 to: (size-1) do:[:index |
                newKeys at: index+1 put: (keys at: index).
                newValues at: index+1 put: (values at: index)].
        keys:=newKeys.
        ^values:=newValues.


Paul



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside