>Hi Jason, >at my work we don't actually use any specific standard, but as far as >fusedocs are concerned we worked out you would write roughly 2 lines >of fusedocs for every line of code. > >no need to take twice as long to do everything. >some people love it but for me its like sand in your eye.
A 2:1 ratio sounds about right to me. This is actually the reason I'm asking this question. It's becoming a bit of a burden and I would very much like to find a quicker solution. I'm all for standards, but I think inline comments and some short descriptive info at the top of the file is probably all that's needed. The beauty of fusebox is that it breaks your code down into very small, easily manageable little chunks. So, for maintenance purposes I don't really think fusedocs are all that necessary. However, I still think they're a great way for a designer to provide a pseudo functional spec for fuse coders. But how many designers do you know you don't actually do the coding as well .. especially with cf? I bought Hal Helms' fusedoc generator plugin ($50 US) for cf studio and it does make it a bit quicker, but it doesn't really do a very good job. disappointed :( Just about everything is produces needs to be edited and it's parser misses a lot of variables. Jason Sheedy Senior Web Developer Voice International Limited www.voice.com.au
