I agree Hal, however, will this still work for those of us that have to use
> FuseBox during the "fleshing out" phase?
>
> When you work for a big corp, you dont always have the luxury of saying
"We
> need and extra 2 weeks to do this because it makes sense.". We have way to
> many overzealous project managers who like to cut your dev time in half so
> we do the "look and feel" as we are developing the app in FuseBox. When
the
> look and feel is completed (usually way before the coding) we can drop in
> the header and footer files and let the client take a look see.
>
> This is where Devnotes would be great for us. However, I am understanding
> from list traffic that if you use them in a FuseBox app the notes are not
> unique for each page. Am I misunderstanding this?
I'm in the same boat as you and that's why I chose to implement them into
the Fusebox structure from the start. The idea though, is that you can do
what ever you want, when ever you want, with any good idea
(Fusebox,Devnotes,naming conventions) they're all just ideas that people
voice and you should take the important parts and do with them what you
will. Hal never said to do it his way or that his way was the only way,
just the way that works for him. I'll say Devnotes works really good for me
when I start the design as a Fusebox site...mind you i've only ever used
them, well, not even on a whole project yet so I may be a bit premature on
my position.
To answer your question, I have devnotes working through a Fusebox app and
they display by page(Fuseaction).
Cheers,
Emilio
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
