Regarding an AccDC module for jQuery

16 views
Skip to first unread message

Bryan Garaventa

unread,
Dec 6, 2012, 12:39:09 AM12/6/12
to free...@googlegroups.com
Hi,
In case it's of interest, I've just finished building an AccDC module for jQuery, which is available on GitHub at
Similarly, AccDC Bootstrap for jQuery is available at
 
The AccDC module is tied into the latest release of jQuery, so that the minified source is only 55kb.
 
Even though it's a jQuery module, it is still the full API, and includes all of the same properties and methods as documented at WhatSock.com.
 
The value of this, is that all of the accessible component modules can be used interchangeably within the full API, or within the jQuery module, without having to modify the code. This also makes it possible to use the same accessible components in Dojo for example, with equal results.
 
Hopefully this addition will be helpful for the jQuery UI guys as well.
 
Best wishes,
Bryan
 

Scott González

unread,
Dec 12, 2012, 11:42:14 PM12/12/12
to free...@googlegroups.com
Thanks Bryan, though the licensing actually prevents me from looking at the code. I can't really look at LGPL code for ideas on how to improve MIT licensed code because that opens a legal can of worms.


--
You received this message because you are subscribed to the Google Groups "Free ARIA Community" group.
To post to this group, send email to free...@googlegroups.com.
To unsubscribe from this group, send email to free-aria+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/free-aria?hl=en.

Bryan Garaventa

unread,
Dec 13, 2012, 2:25:47 PM12/13/12
to free...@googlegroups.com
Ah, what's the conflict?

Scott González

unread,
Dec 13, 2012, 2:45:51 PM12/13/12
to free...@googlegroups.com
The conflict is that LGPL isn't MIT compatible, so if I look at the code, then implement the same (either consciously or subconsciously) and release under a license that doesn't meet the LGPL requirements (which MIT does not), it could result in copyright infringement.

Bryan Garaventa

unread,
Dec 13, 2012, 4:15:25 PM12/13/12
to free...@googlegroups.com
Thanks, I wasn't aware of that.
 
Where would be the best place for me to read the MIT license? I'd like to find where the two aren't compatible.
 
If it's necessary for me to update the license to make it possible for more people to use it without conflict, I can easily do this. I just need to know which parts are in conflict. I've never made open source software before, and all of the differences between the open source license types, are confusing.
 
My intent is to make the code available for anyone who wants to use it, not to restrict it's use.
 
If AccDC were made available under the MIT license, would this have a similar affect of making it impossible for people to use AccDC within LGPL licensed software, for the same reason?

Scott González

unread,
Dec 13, 2012, 4:44:39 PM12/13/12
to free...@googlegroups.com
Here's a copy of the MIT license: http://opensource.org/licenses/MIT

The reason it's not compatible is because *GPL is viral and MIT is extremely permissive. Code that is licensed under MIT is *GPL compatible. That is to say, the you can put MIT code into a GPL project, but you cannot put GPL code into an MIT project.

Bryan Garaventa

unread,
Dec 13, 2012, 10:43:56 PM12/13/12
to free...@googlegroups.com
Ah, I get it.
 
I've converted AccDC and all associated modules to be distributable under the terms of the OSI MIT License, in the same manner as jQuery is.
 
This is true for the
standalone AccDC API (https://github.com/accdc/accdc),
the AccDC jQuery module (https://github.com/accdc/accdc-jquery),
the standalone AccDC Bootstrap module (https://github.com/accdc/bootstrap),
and the AccDC Bootstrap jQuery module (https://github.com/accdc/bootstrap-jquery).
 
Hopefully this will help.
 
Please let me know if I've overlooked anything.
Reply all
Reply to author
Forward
0 new messages