I use them for absolutely every template. I've even gotten into that habit of sending
my dba a fusedoc that explains the io of a required stored procedure.
Guess what... He likes it. He's even starting to send fusedocs back to me when he
creates a stored procedure on his own. It is becoming the defualt method of
documentation. The fudoc is simply saved as an xml file in a app specific
documentation directory. This means the dba doesn't have to be bothered every time a
cf developer wants to use a stored proc. The developer can go directly to the fusedoc
to find out how to use it.
Huge time saver.
---------- Original Message ----------------------------------
From: Wally Randall <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Thu, 23 May 2002 09:32:37 -0400
>---------- Original Message ----------------------------------
>I would like to raise an heretical issue. WHO USES FUSEDOCS? At various user group
>meetings I have discussed the use of Fusebox. Everyone seems to be using the coding
>methodology by NO ONE is using FUSEDOCS! The coders are structuring their code with
>Fusebox but not taking the time to use the design methods inherent in the development
>of FUSEDOCS.
>
>This has certainly been true in the last two large Fusebox projects I have been
>involved in. The developers do not want to spend 'coding time' developing Fusedocs
>and the managers have no interest in spending development time engaged in that level
>of planning detail.
>
>How are various developers planning their sites if they are not using FUSEDOCS?
>
>
>__________________________________________________________________
>Wallace Randall
>ICQ#: 157983785
> Current ICQ status:
>+ More ways to contact me
>__________________________________________________________________
>
>
>
>
>
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
