On Jul 20, 2005, at 4:35 AM, Martin Wood wrote:
JesterXL wrote:
This has been discussed 10 billion times; the only reason it
wasn't resolved is because anyone who ever resolved a thread that
popped up wasn't a certified laywer that could answer the
questions that arose after said post.
Since I'd prefer to keep the world turning, and thus repeat
history, *ahem*:
:)
i guess i must have been away for the discussions.
personally i would suggest that a bug fix adds significant business
value for a company involved in software.
but, whaddaiknow, im not a lawyer. (i have the feeling that phrase
has also been used approx 10 billion times)
Maybe Nicolas and I can hook up with the EFF folks at OSCON in August
and ask them to interpret the MM license for us.
erm, well, on the mtasc list David pointed out that the 'std'
directory doesnt actually contain MM code, just intrinsic class
definitions.
I guess this is the route we should go down so we can at least have
a legal way of type checking against other MM code like remoting.
Or we implement an open-source alternative to Remoting. Is it just
me or does the fact that the base classes that are core to the "Flash
platform" cannot be redistributed unless you own the Macromedia Flash
IDE when there are alternative ways to use these libraries seem
odd?. We own several licenses to MM products, and I don't mind (at
all) them making good money on products like their IDE, but on a
couple thousand lines of ActionScript code that are easily
reproducible? They claim this code is part of a "Flash Platform"?
It bugged me with the Flex components and bugs me now. I started
ActionStep because of the license that prevents reuse of the "Flash
Platform"'s standard components. I guess we will just have to move
to do Flash Remoting. I already have a library for binary
serialization/deserialization of ActionScript objects, that could be
a start.
What other "Flash Platform" libraries do we need open-source
alternatives for? Maybe we should just make a list on osFlash and
recruit people. Of course, the problem with all of this is the
"Flash Platform" is reduced to the player and intrinsic classes and
everything else will fork...bummer.
as for actually compiling using modified versions of code, well, i
guess we could sneak around like some mysterious subterranean
coding group : 'have you got the patched MM code?' , 'no, but i
know someone who does, the IP is dynamic and changes every 20
minutes...be quick..'
:)
or, how about this for a crazy idea. MM actually set up a page
where we can submit fixes for them. The ultimate in software
benevolence, we pay them 100's of whatever our local currency is
for their tools, then we fix various parts and give them back for
free. Then if karma does work, we'll be sorted.
maybe i should eat my breakfast and think about it some more.
martin
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
