2008/7/13 Vladislav Vorobiev <[EMAIL PROTECTED]>:
> Hello,
>
>> Why does your url include a question mark? I think this is the problem.
>> You must add your parameters with KSS and not as part of the server
>> action's name.
>
> you are right. My URL consists of a complete URL with parameters. We
> discussed this matter in a parent thread. What I don't understand is:
> wy do I HAVE TO add my parameters as kssAttributes only? The other way
> works well enough. Could you explain this?
>
>> We need to put the question mark there, because "?" is obligatory in
>> front of the parameters. We should omit the "?" in case there are no
>> parameters at all, but that hardly makes any difference?
>
> Yes, it does! Because, if my URI already includes some parameters it
> does't work. It is a good idea to implement this.
>
>>> Maybe it is not a very good idea, but possibly it would be nice to
>>> implement some feature to turn of the question mark at the and of URL.
>>
>> Can you explain why the question mark is so important in your use case?
>
> It is simpler to handle. If I use kssAttributes only, I have to write
> kss for every single one of them.
>
> For example I have something like this
>
> <p><a href="myScript?a=a&b=b" class="myScriptKss kssattr-a-a
> kssattr-b-b" > AA</a></p>
> <p><a href="myScript?a=a&b=b&c=c" class="myScript2Kss
> kssattr-a-a kssattr-b-b kssattr-c-c" > BB</a></p>
>
>
> kss for this statment
>
> .myScriptKss:click{
> evt-click-preventdefault: true;
> evt-click-allowbubbling: true;
> action-server: myScriptKss;
> myScriptKss-a: kssAttr(a);
> myScriptKss-b: kssAttr(b);
> }
>
> .myScript2Kss:click{
> evt-click-preventdefault: true;
> evt-click-allowbubbling: true;
> action-server: myScriptKss;
> myScriptKss-a: kssAttr(a);
> myScriptKss-b: kssAttr(b);
> myScriptKss-c: kssAttr(c);
> }
>
>
> It makes a post request, but there is no difference for this example.
> ---
> Simply I've still not found how i attach parameters here:
> action-client: cacheability-serverAction;
> cacheability-serverAction-url: myScriptKss;
> myScriptKss-a:kssAttr(a); ?
> ---
>
>
>
> The other way I see is to make it simpler
>
> <p><a href="myScript?a=a&b=b" class="myScriptXKss
> kssattr-uri-myScriptKss%3Fa%3Da%26b%3Db"> AA </a></p>
>
> <p><a href="myScript2?a=a&b=b&c=c" class="myScriptXKss
> kssattr-uri-myScriptKss%3Fa%3Da%26b%3Db%26c%3Dc"> BB</a></p>
>
> My kss statement ist shorter in this case. Only one class for all of them.
>
> .myScriptXKss:click {
> evt-click-preventdefault: true;
> evt-click-allowbubbling: true;
> action-client: cacheability-serverAction;
> cacheability-serverAction-url: kssAttr(uri);
> }
>
>
> I do not understand why I can't use them. It works fine.
>here working example: http://mykniga.de/kssTest _______________________________________________ Kss-devel mailing list Kss-devel@codespeak.net http://codespeak.net/mailman/listinfo/kss-devel
