[TYPO3-ect] Future of different AJAX-libs?

R. van Twisk typo3 at rvt.dds.nl
Tue Sep 12 19:54:03 CEST 2006


Elmar Hinz wrote:
>>>   
>>>       
>> That is dangerous territory to judge for me.... I never knew it was
>> possible
>> to re-license LGPL to GPL without being the copyright holder of the
>> modules.
>>
>> Ries
>>
>>     
>
> So who is a lawer? All we can do is to read the texts carefully.
>
> I guess if you are the copyright holder you can do any licence change
> you like. If you are not, you can only do licence changes that are
> explicitly encouraged by the original license.
>   
I can't tell, like I said... This territory is to dangerous for to talk 
about.

I can imagine that it is encouraged to change to GPL or to start of with 
GPL.
However when the license is set, a other person, NOT the copyright holder
of the software is NOT allowed to change the license from one to a other.

Maybe the T3 Association does have a lawyer who can tell us the final word,
since we both are not lawyers?

In regards to a other mail about MIT compatible with GPL:


    GPL compatibility

Many of the most common free software 
<http://en.wikipedia.org/wiki/Free_software> licenses, such as the 
original MIT/X license <http://en.wikipedia.org/wiki/MIT_License>, the 
BSD license <http://en.wikipedia.org/wiki/BSD_license> (in its current 
3-clause form), and the LGPL 
<http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License>, are 
"GPL-compatible". That is, their code can be combined with a GPLed 
program without conflict (the new combination would have the GPL applied 
to the whole). However, some open source software licenses are not 
GPL-compatible. Many have strongly advocated that open source software 
developers use only GPL-compatible licenses, because doing otherwise 
makes it difficult to reuse software in larger wholes.

Also see the List of software licenses 
<http://en.wikipedia.org/wiki/List_of_software_licenses> for examples of 
compatible and incompatible licenses.



Ries
PS: I want to stop discussing this xajax / prototype / TER thing
My conclusion is xajax as a life next to prototype and prototype can sit 
in TER.
For both libraries you need to know javascript, no matter how you look 
at it.
Prototype is 5% ajax, and 95% DOM manipulation
xajax is 95% ajax helps and 5% DOM manipulation.

xajax doesn't create DOM... it just can spit out X(HTML) which you can 
use with innerHTML
to 'update' your site.

Prototype and scripto.... can manipulate and create DOM on the client 
site perfectly,
and can do lot's of cool WEB 2 stuff (usability)


(percentages above guessed... but people get the idea).














> Regards
>
> Elmar
>
> _______________________________________________
> TYPO3-team-extension-coordination mailing list
> TYPO3-team-extension-coordination at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
>   


-- 
Ries van Twisk
Freelance Typo3 Developer
=== Private:
email: ries at vantwisk.nl
web:   http://www.rvantwisk.nl/freelance-typo3.html
skype: callto://r.vantwisk
=== Work:
email: ries at livetravelguides.com
web:   http://www.livetravelguides.com




More information about the TYPO3-team-extension-coordination mailing list