> It's about learning and > understanding the whole concept of flash, eg. timelines, frames, etc. > I think, if you never worked with the Flash ide, you'll never > understand Flash completely.
I dont think thats true. You may not understand the history and progression of flash if thats what you mean by understanding flash completely, but you dont need the IDE to understand the concepts like timelines and frames. For some I think the IDE is a barrier to understanding. Some programmers i've talked to only really understood the IDE when i explained it in terms they already knew or were familiar with. What are movieclips , basically high-powered sprites that exist in a tree-structure etc.. > So the point is, people should start with the Flash ide, and if they > encounter serious problems in their workflow, they should come back to > osflash and see, what solutions are provided. I don't agree with that at all. There is no need for people to even look at Adobe's IDE. It also runs counter to one of the purposes of open source. 'Before you can use the free tools you better start with this commercial product' Unless you are on Linux, or you cant afford it once your 30 days are up, or you just want to do some programming without being confronted with what looks like a weird photoshop. What i feel is lacking is clarity, like joao has said, we require more content that guides people through definite tasks. How to get from A to B and which tools you need for the job. If you are a lone developer using windows who wants to write a game or you are a manager or lead developer organising or researching how to get tooled up for team-based application development on linux there should be some clear and focused tutorials or guides. _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
