UML and Flash

[Groady]

This is something I have been thinking about for a while and was hoping to get other peoples opinions. I've been considering teaching myself UML, specifically to use with Actionscript 3.0. I guess the question I want to put out there is, is it worth it? By that I mean as a sole-coder (or 'dev-igner'), someone who may never work in a team.

As someone who works as a feelance Actionscript developer I can honestly say the majority of other Flash 'people' I have encountered are really getting by on the basics. Meaning they are non object oriented timeline scripters. I get that UML may be more suited to the Flex devs but what about us Flash people? Is there a need there?

Just wanting to get some opinions from you guys. Are you interested in UML?

[ASWC]

If you like the concept of UML then go for it. It's true that we think of it as a team oriented tool. But it's obvious that anybody can benifit form it even if you work alone. note that UML is not the only code planning approach.

[Flash Gordon]

I find UML helps me to organize my thoughts and think about the archetict of the application before I begin the coding process. It's important to seperate design from development. You shouldn't be designing your archetict (patterns and such) while you are trying to programming. UML helps me, but that doesn't mean it will help you. And so far, I've not actually stuck with a UML diagram once I begin the coding. I find other things I didn't anticpate, but it gives me a basic start and approach for structure.

[jsebrech]

The point is that you make diagrams. UML is just a standard set of diagram patterns that may or may not help you to make diagrams. I make diagrams, but I don't make UML diagrams, because I find that just sketching them out on paper is enough for me, and UML (in my opinion) is overkill for that.

[yell0wdart]

Yea, UML may be a bit overkill for what you need, but learning it would definitely help you out on your path to becomming a good developer, even if you just take away some good practice on diagramming.

I'd also strongly suggest getting your head around design patterns as well, if you haven't already. I'd highly recommend the O'Reilly Head First Design Patterns book if/when you start to do some research on the subject. Great read, and it's invaluable in the sense that it'll help you unlock the real power behind OOP.

[MSFX]

I make diagrams, but I don't make UML diagrams, because I find that just sketching them out on paper is enough for me, and UML (in my opinion) is overkill for that.

I agree, unless your going hardcore with your classes etc then I personally feel there is no need for much more than a sketch, unless of course your working within a team environment...

[jsebrech]

I work within a team environment. It's a very rare case that I need to sketch out a diagram for an analysis document. If I do need to do that, I use visio.

Although I did recently make a few diagrams with violet uml editor, and I must say I like it. It's very simplistic, but it gets the job done (for class diagrams).

[Groady]

I'd also strongly suggest getting your head around design patterns as well, if you haven't already.

I've got O Reilly's ActionScript 3.0 Design Patterns. I haven't picked in up in a while so will have to go through it again. I think UML may be on the cards as something to learn next. Anyone know of a good UML book?

[Flash Gordon]

reading about design patterns and you'll learn uml by default. Btw, I hated OReilly's ActionScript 3.0 Design Patterns. I thought it pretty much sucked compared to other books out there like Head First

[yell0wdart]

I've got O Reilly's ActionScript 3.0 Design Patterns. I haven't picked in up in a while so will have to go through it again. I think UML may be on the cards as something to learn next. Anyone know of a good UML book?

Yea, I can't comment about AS3.0 Design Patterns... but I can highly recommend, like FG, the Head First Design Patterns book is wonderful. It uses Java, but Java is very similar to AS3.

[panel]

reading about design patterns and you'll learn uml by default. Btw, I hated OReilly's ActionScript 3.0 Design Patterns. I thought it pretty much sucked compared to other books out there like Head First
Agree HeadFirst rules :)

In case of small project UML, won't help you much, but if you are creating big application UML will be very helpfull.
There is tool worth mention called Enterprise Architect (http://www.sparxsystems.com.au/products/ea/index.html)witch allows you to create UML diagrams and generate Actionscript code from them. So if you design your application well you can generate 'application skeleton' in a while. You can also generate diagram from existing set of classes :cool:

[mryarbles]

I've been looking for diagraming software that outputs stub code for as3. I've tried:

1. Enterprise Architect - its bloated with a lot of options and as far as I can tell has a big learning curve. It also generates as2 not as3.

2. Vasgen - It has potential. It's very simple and if you can get it to work it outputs AS3 rather well. Problem is it's completely undocumented and buggy as shit - you can't move one package to another package if you change your mind.

3. gModeller - as2 only. Wish he'd update it to as3 and make an air app out of it!

If any one knows a modelling package that generates as3 stub code please post.

Thanks

[panel]

Enterprise Architect have as3 support

[jsebrech]

In case of small project UML, won't help you much, but if you are creating big application UML will be very helpfull.

I'm of the opinion that when you reach that scale you need to restructure your app so it has self-contained class groups that communicate with message passing or defined interface API's.

I don't think UML class diagrams should ever be allowed to get into the position where they are a lifesaver.

[hangalot]

check out the emf, gmf plugins for eclipse.