Hello Cameron,
> So you can focus on the technical:
> * What is the download size of the library, can the size be limited to
> the browsers that require it.
> * How much technical effort is required to port to Ajaxslt?
> * How well does Ajaxslt perform? From memory, the XSL performance was
> repor
David Ortega wrote:
> Vincent Heurteaux escribió:
>
>> Hi,
>>
>>
>>
>>> Why is an inconvenient?
>>>
>>>
>> I guess Jean-Sebastien wanted to know if there was some compatibility
>> problem between BSD and LGPL licenses.
>>
>> So what's the best way to deal with cross platfor
Vincent Heurteaux escribió:
> Hi,
>
>
>> Why is an inconvenient?
>>
> I guess Jean-Sebastien wanted to know if there was some compatibility
> problem between BSD and LGPL licenses.
>
> So what's the best way to deal with cross platform needs, replacing
> Sarissa with google-xslt or port
Hi,
> Why is an inconvenient?
I guess Jean-Sebastien wanted to know if there was some compatibility
problem between BSD and LGPL licenses.
So what's the best way to deal with cross platform needs, replacing
Sarissa with google-xslt or porting some google-xslt code to sarissa ?
If google-xslt
baklouti escribió:
> hi all,
> to implement xslt processor et xpath function for safari there is an
> another way ,it is to use AJAXSLT from google .
> http://goog-ajaxslt.sourceforge.net/.
> Google uses this library for google map , gmail .
> AJAXSLT implements its own Xslt procesor et xpath fun
Hi Jean-Sebastien
AFAIK BSD license shouldn't be a problem with LGPL and APL, not entirely
sure about GPL. But Sarissa is available under the first two, so I guess
that's not a problem. (I'm not an expert in licensing though)
168K is quite big, do you mean with 'to complete sarissa' that you wan
hi all,
to implement xslt processor et xpath function for safari there is an
another way ,it is to use AJAXSLT from google .
http://goog-ajaxslt.sourceforge.net/.
Google uses this library for google map , gmail .
AJAXSLT implements its own Xslt procesor et xpath function.But an
inconvenient is t
