I'm putting together a presentation for the conference that I'll make
available on Fusebox.org.
-----Original Message-----
From: Steve Nelson [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 27, 2000 9:08 AM
To: [EMAIL PROTECTED]
Subject: Re: FuseDoc specification
I'd like to see someone write a white paper about these documentation
ideas and I'll post it to Fusebox.org. This is important stuff for
everyone to read.
Steve
John Quarto-vonTivadar wrote:
>
> Hi I am going to start moving ahead with the general form of Lee's
> specification for now. I agree with how he is handling it and
> I think it gives the maximum flexibility for expansion in the future. I
> disagree with him that the conversation should be expanded to the cf-talk
> list rather than the fusebox list since I see that as a guarantee that
> nothing will ever be decided. *IF* the Fuseboxers can come to a consensus
> about a suggested format *then* we could present that to the cf-talk list
as
> a suggestion for how anyone outside of Fusebox could use that same format
> for their own use. But, for my own selfish reasons I guess, i want
progress
> on this topic *now* so I'm loathe to spend much time on the cf-talk list
> talking about it--I think the distribution is way to large to get anything
> done.
>
> (As it is I think the Spec discussion should have been moved to the
fusebox
> standards committee for a version 1.0, then to the fusebox list for a
> discussion and suggested changed for 1.01)
>
> ----- Original Message -----
> From: "John Foulds" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, August 27, 2000 12:55 AM
> Subject: Re: FuseDoc specification
>
> > Fred, I like your approach. It is consistent with how I code, and I
could
> > easily adopt it.
> >
> > Also, standards are not evil. Consider Fusebox. And if you document
> > consistently to a standard, the benefits via a spidering parser are
> > tremendous.
> >
> > Thanks John, for adding "++>, <++, and <+> seem to work too", that was
> lost
> > on me.
> >
> > As a matter of fact, between your comments, Fred's example, and what I
can
> > make out about FuseDoc - we're all on slightly different pages about it.
> >
> > Hal, you mentioned that you posted the current Fusedoc standard a couple
> of
> > days ago. Do you mean the 15-line refresher and example? I can't find
> > anything anywhere else in here.
> >
> > If there was an easily available specification or style guide of the
> > "standard", perhaps we might all be more in tune with each other.
> >
> > Perhaps on www.fusedoc.com?
> >
> > >Does anyone have any concrete suggestions for improvements?
> >
> > Yeah, I'm working on it.
> >
> >
> > John Foulds
> > Ottawa, Canada
> >
> >
>
> --------------------------------------------------------------------------
> ----
> > To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
>
> --------------------------------------------------------------------------
----
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
