On 11/28/12 11:35 AM, "Franck Wolff" <franck.wo...@graniteds.org> wrote:
> Alex,
>
> Sorry for the delay, I have been very busy last week with the new GraniteDS
> release, among other things.
>
> My answers below:
>
> 2012/11/14 Alex Harui <aha...@adobe.com>
>
>>>
>>> Good point. All classes from the org.granite.math package were written
>> from
>>> scratch, but part of the BigDecimal code is inspired (not copied though)
>>> from the Java implementation. What do you suggest in order to make sure
>>> that there is no legal issue?
>> If you've never seen their code, I think we are good.
>>
>
>
> Well, I did see their code but I didn't copy it and I don't think this a
> problem. However, you can double-check upon this potential issue.
OK, well Copyright is about copying so if there isn't an obvious copy of the
Java code I think we're ok there.
>
>
>>>> 2) Packaging: All the packages are currently org.granite.*. Do you
>> have a
>>>> large body of users who will complain loudly if you change the package
>>>> name?
>>>>
>>>
>>> I don't think so: changing package names is just a research / replace
>>> operation...
>> OK, we'll I'm open to suggestions for package names and the swc name. I
>> think it shouldn't have granite in it because it is your company's name. So
>> org.apache.flex.math
>> org.apache.flex.reflect
>> org.apache.flex.validation
>> And for the swc, other than the Container dependency and ObjectUtil
>> dependency, I didn't see a lot of other Flex dependencies so I think all of
>> these classes can go in one new swc? I don't see a reason to put it under
>> "experimental". I considered names like "asjava.swc" since these are all
>> based on java features?
>>
>
>
> Ok, I can be whatever the community wants.
Just pick something for now. We can change it later. We just need to not
use granite.
>
>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
