great MX2004 EULA discussion

[tg]

great read at grant skinners site right now about the new EULA for f04, and how developers are hindered for distributing base classes that have been modified (this includes components).

http://www.gskinner.com/blog/archives/000036.html

[farafiro]

This is a very good article, thanksTG
but, I don't understand this, the writer says u can't sell the build in components in a project or u can't modify then sell??

also, this fears me muchNow, this issue as it relates to sharing code in the community is one we can debate somewhat leisurely, as it doesn't have a major impact beyond slightly retarding the growth and learning of said community. The real problem arises when you look at how it impacts real, paid projects!!

[tg]

well, weve all seen in the components section, folks modifying the code of the macromedia components to add a new feature to the component... like adding a tool tip to the list box when the text is wider than the box...

so, under the new eula, you would not be able to distribute the source code for the modified component. his point is that many companies expect the source code when they pay for a product to be developed for them, but in this case you wouldn't be able to provide it, cause it would violate the mx2004 eula....

[farafiro]

heh
so, i'd make all the components again myself
like what he said

I don't know, but I don't think this is MM point
I didn't read EULA, but if so, why int he first place MM distrebute the component with Flash pro.
It should be sold then with the DevNet kit

[tg]

read thru more if the entries in the blog... some of the reasons are mentioned by nigel, i think both sides have valid points... it will be interesting to see where this goes.