[dojo-contributors] Question about licensing excanvas

Nathan Toone toonetown at dojotoolkit.org
Thu Sep 11 11:29:01 EDT 2008


And dojoc would be a way to address the licensing of it as well -  
correct?  (though I've already heard back from 2 of the three people  
from Google...)

-Nathan

On Sep 11, 2008, at 9:21 AM, Peter E Higgins wrote:

> It really comes down to support. Do we really want to copy and  
> maintain
> that copy in our own codebase? I like the idea of being able to  
> utilize
> dojo.require/dojo build/shrinksafe out of the box with excanvas, but
> wouldn't want to be the one assigned the title of 'ownership' ...
> perhaps dojoc can be used here to make it publicly available while
> keeping it "off the radar" of official support.
>
> Regards,
> Peter Higgins
>
> Tom Trenka wrote:
>> Here's the thing--IMHO, not *everything* needs to live in the Dojo
>> codebase, especially when the code in question is easily linkable via
>> externals or something to that effect.  I don't have a problem with
>> the idea of using excanvas, I just have a problem with the need to
>> make a copy of it and slap in DojoX...
>>
>> regards,
>> trt
>>
>> On Thu, Sep 11, 2008 at 10:01 AM, Nathan Toone
>> <toonetown at dojotoolkit.org <mailto:toonetown at dojotoolkit.org>> wrote:
>>
>>    That's fine as well...I just wanted to make it a bit easier to  
>> include
>>    using dojo.require...and to provide a "stepping stone" (perhaps)  
>> for
>>    starting to migrate canvas-based code to using dojox.gfx.
>>
>>    I'm not tied to including it in the dojo codebase...I just had  
>> thought
>>    that it might be useful for others...
>>
>>    -Nathan
>>
>>    On Sep 11, 2008, at 7:53 AM, Tom Trenka wrote:
>>
>>> Just curious,
>>>
>>> Why does this need to move into dojo as one of our extension
>>> libraries?  The excanvas license allows anyone to pick it up there
>>> already if they want to, and we wont have to field questions
>>    about it
>>> and its limitations.
>>>
>>> In fact, I agree: I don't see any reason to move this into the Dojo
>>> codebase at all.  Why not just use svn:externals to consume it, or
>>> do what we've done in the past and give instructions on how to
>>    get it?
>>>
>>> regards,
>>> trt
>>> _______________________________________________
>>> dojo-contributors mailing list
>>> dojo-contributors at dojotoolkit.org
>>    <mailto:dojo-contributors at dojotoolkit.org>
>>> http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors
>>
>>    _______________________________________________
>>    dojo-contributors mailing list
>>    dojo-contributors at dojotoolkit.org
>>    <mailto:dojo-contributors at dojotoolkit.org>
>>    http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> dojo-contributors mailing list
>> dojo-contributors at dojotoolkit.org
>> http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors
>>
>
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
> http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors




More information about the dojo-contributors mailing list