3 ms·
If by 'working with flash' you actually mean, 'producing a SWF to run in the Flash Player'... 1) I've been using Vim for years to produce SWFs. I hate their to
by richard-lyman 17y ago
If by 'working with flash' you actually mean, 'producing a SWF to run in the Flash Player'...
1) I've been using Vim for years to produce SWFs. I hate their tool too - that's why I don't use it. You can use any text editor you want.
2) The 'Flash UI' is very skinnable (not as skinnable in Flex3 as in the upcoming Flex4, see: http://www.mikechambers.com/blog/2008/08/27/everything-there-is-to-know-about-flex-4-gumbo/ http://www.mikechambers.com/blog/2008/08/27/everything-there... )
3) I'm not sure what you mean by tedious. You might be referring to the Flash editor's use of the timeline. If that's the case then you'll want to look into the Flex SDK I mentioned. I haven't used a timeline for over 5 years.
- zackattack 17y ago"1) I've been using Vim for years to produce SWFs. I hate their tool too - that's why I don't use it. You can use any text editor you want." This makes no sense at all to me. Are you coding Flex? How do you design the interfaces for your apps? Pardon my ignorance.
- cjbos 17y agoAs a programmer my design skills are mostly implementable with the graphics class. But when I do work with flash designers, I have them create assets in the Flash IDE and publish a .swc which I import into flex builder. This gives me nice intellisense access to all the graphic elements. I very rarely open up the IDE, usually it's to rename an asset which the designer had forgot or incorrectly named.