tag:robotlegs.tenderapp.com,2009-10-18:/discussions/questions/796-documenting-mvcs-and-projectRobotlegs: Discussion 2018-10-18T16:35:35Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/129387512012-01-16T16:02:32Z2012-01-16T16:02:32ZDocumenting MVCS and Project.<div><p>Hi Dortega,</p>
<p>can you give some more information about what kind of
documentation<br>
you want to create? Depending on that, there's a lot of
different<br>
tools you could use.</p></div>Till Schneidereittag:robotlegs.tenderapp.com,2009-10-18:Comment/129387512012-01-16T17:11:04Z2012-01-16T17:11:05ZDocumenting MVCS and Project.<div><p>Hi, thanks for the quick reply.</p>
<p>The arquitecture, events, classes, database, user manual,
everything involved.</p>
<p>From Views to Database.</p>
<p>D. O.</p></div>Diego Ortegatag:robotlegs.tenderapp.com,2009-10-18:Comment/129387512012-01-16T18:09:17Z2012-01-16T18:09:17ZDocumenting MVCS and Project.<div><p>Hi Dortega,</p>
<p>that's a very wide-ranging question, then. In my experience,
a<br>
combination of using tools like AsDoc to create basic API docs<br>
automatically, then a diagramming tool such as OmniGraffle, Visio
or<br>
Gliffy for flow diagrams and, most importantly, a hand-written<br>
documentation of the most important activities occurring in the
entire<br>
application is a good mix.</p>
<p>There really isn't one good tool for all of these parts, so you
have<br>
to mix and match until you're satisfied.</p>
<p>On another note: that's really not that much of a
Robotlegs-specific<br>
question, so you'll probably get much better answers in a less<br>
specific forum such as stackoverflow.com.</p>
<p>hope that helps,<br>
till</p></div>Till Schneidereittag:robotlegs.tenderapp.com,2009-10-18:Comment/129387512012-01-16T18:12:20Z2012-01-16T18:12:20ZDocumenting MVCS and Project.<div><p>Thanks Till, i will look into it!</p></div>Diego Ortega