incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Left Right <>
Subject Re: [MENTORS] Handling Adobe Binaries
Date Wed, 02 May 2012 19:33:04 GMT
I'm still puzzled - why does that library contains actual code? Maybe
asking Adobe for a *normal* library without that code (which we seems like
don't even need!) would sort out the patents / copyright issues?

On the other hand, I feel bad telling someone they have to download a piece
of *software*, of which they, under any circumstances, will not use more
then 10%. This is sad / stupid / bizarre.

^ No, mxmlc *should'nt* need playeglobal.swc to compile anything - your
problem, however, will be that you won't be able to use String, int, XML,
DisplayObject etc. in your code, which kind of limits you... :) In the very
early days of SDK there used to be a *reduced* version of playerglobal with
Tamarin-only classes (i.e. the ES4 classes), and the Flash classes used to
be in a separate library, or even just plain text files... can't remember
If, and I hope it is still correct, MXMLC allows this situation to
continue, this would be the best option (consciousness-wise) to ask users
to download Tamarin's library and our own headers of AS classes. Tamarin
is, at least, a *friendly* license, and it may be possible to do something
about a binary package on Linux/BSD distros about it. But if that's coming
from Adobe - you can forget about binary package :(



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message