i applaud people for figuring out the stuff since now its accesible to me, i applaud the people who put it out there for everyone since now its availible to me. i applaud the whole osflash idea and the way its streamlined my work processes. i just think this is api related, and thus far there has been no other api stuff on osflash. its a case of: "should this class go in the utils package or into my model package" i personally think people should blog the information as they see fit put it out on the mailing list and all the rest, as for the wiki it is not there for api specs IMO. leave it take it away i don't care, the info is floating around in the ether allready, and using google i can extract it as i wish. so...its a point of view, i think this and you think that. let the admins decide (and they have). zeitgeist!
On 7/14/05, Tim Walling <[EMAIL PROTECTED]> wrote: > > Unless, of course it violates whatever laws or something. > > Agreed. If anything posted on this was acquired through people under NDA's or > it violates laws, agreements, etc then it probably shouldn't be posted. > > I'm pretty sure MM knew they'd be exposing some of this when they released a > public player. I happened before with previous public releases. > > > > > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > -- j:pn _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
