I never said that it is OO. I'm just using OO
terminology to understand it.
I don't believe XFB components are truly
encapsulated, because I can't necessarily use
them without messing with their insides.
The idea of reusing circuits is not rediculous.
It's one of the most basic features of
Fusebox. But I think nesting makes reusability
more difficult. The notion that nesting improves
reusability (indeed, allows one to "drag and
drop" a new circuit into an application) is
what I find so rediculous.
What exactly is the goal of nesting circuits? What
problem does it solve?
I thought it made it easy to snap-together components
like legos. Atomic components snap together to
make compound components, which snap together to
make bigger compound components.
But by flattening out all of the components with
circuits.cfm, this process becomes difficult. Before
I can "snap on" a new component, I have to make sure
it has a unique name. And if not, I have to go into
the code and change it in a dozen places.
If you just left the heirarchy the way it is,
without flattening it out with circuits.cfm, I
wouldn't have to worry about it. Why have
circuits.cfm? So you can break pieces off of the
tree and move them to other parts after they've
been snapped together? What's the advantage of
that? WHY in the WORLD would you ever want to
do that?
IMHO, this makes about as much sense organizing
HTML pages in a directory structure, and then
putting links to every single page on the home
page, and using that as your only navigation system.
I'm starting to figure this out, I think. It's
just that pesky circuits.cfm that I don't get. You
guys all act like it's really important, but I've
found that it's destructive. I must be missing
something. What is it?
Patrick
> -----Original Message-----
> From: Hal Helms [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 30, 2001 12:55 PM
> To: Fusebox
> Subject: RE: Nesting circuits: I just don't get it! :(
>
>
> XFB is not an OO framework. It's more component-based. I assure you that I
> use encapsulation (no. 2) routinely to test circuits in
> stand-alone mode, so
> don't throw it out too fast! And I reuse circuits, too, so it's not too
> ridiculous.
>
> Hal Helms
> Team Allaire
> [ See www.halhelms.com <http://www.halhelms.com> for info on training
> classes ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
