RE: [flexcoders] Re: Adding AS3 support to 3rd party editors - legal question

Thu, 03 Aug 2006 23:11:48 -0700

I see what you’re saying now.  I’m not sure that would be the end of the world (the lawyer canceled the meeting so I won’t get to talk to him till next week) but a more traditional approach would be to get your editor to understand the AS3 source format.  Since we ship the source in the SDK you could just parse that and get all the information you need.  I think understanding the source format is going to be more flexible than manually entering information from livedocs.  Of course the real thing to do is understand the bytecode format, but we haven’t documented that as of yet.

 

I have asked legal for help in getting an official answer to “What can I use from the SDK if I wanted to write my own IDE?”.  It will be a few days before I can answer that, but I can tell you that the spirit of our EULA is not meant to prevent you from doing that.  So we are not trying to throw up legal roadblocks to you building an editor.  Which is not to say we’re actively looking for competitors to start up when we’re still trying to sell Flex Builder ;-)

 

Matt

 

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ben.clinkinbeard
Sent: Thursday, August 03, 2006 1:33 PM
To: [email protected]
Subject: [flexcoders] Re: Adding AS3 support to 3rd party editors - legal question

 

I see what you mean, I guess I am just confused on why it would matter
if someone went through the site and manually typed out all the info
or if they were able to write a script that could do it automatically.
The information is there, why would it matter who/what accesses it?

Also just to clarify, the way I understand it the files would only
need to be generated once; the screen scraping would not be something
the app did as part of its operation.

Thanks,
Ben

--- In [EMAIL PROTECTED]ups.com, "Adam Dorritie" <[EMAIL PROTECTED]..> wrote:
>
> On 8/3/06, ben.clinkinbeard <ben.clinkinbeard@...> wrote:
> > Thanks for the reply, Matt. If this is not ok, what would be
> > acceptable methods for accomplishing things like code completion in
> > third party editors? Obviously, doing this requires knowledge of the
> > structure of all AS3 classes and Livedocs seems like the best/only
> > 'open' and free to the public source of this information. I really
> > don't think any serious developer would consider an editor adequate
> > without this functionality.
>
> I think that you're confusing 2 separate issues. The first is whether
> you can configure an editor to recognize (highlight, complete,
> whatever) ActionScript code using information obtained from publicly
> available documentation. The answer to this, as far as I know, is
> absolutely. The second issue, and the one which I believe that Matt
> has concerns about, is whether or not you can obtain the data you need
> to enable this feature by screen-scraping Adobe documentation. I can
> see potential issues with that. Manually enter the AS3 information
> into your editor and I would bet that you would be fine.
>
> Adam
>

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to