Re: Queries and display files

[Lee Borkman]

Hi Tom,   The most fundamental concept in Fusebox is to simplify.  Let's do some maths:   I have an app with 10 fuses.  I'm going to let fuses call each other directly, because that gives me more freedom, right?  So, how many potential fuse2fuse connections do I have?  10 x 9 = 90 possible interfuse connections, because the calls can go in both directions.   But now I'm going to apply some strict Fusebox rules, and say that fuses are not going to call other fuses directly.  Big meanie.  Even worse, I'm going to add yet another file, and call it "fbx_switch", and make the rule that only fbx_switch can call fuses directly.  So I now have 11 files, and bugger-all freedom in the way they call each other, right?  Now, how many potential connections between files do we have?  Well, there's only one file that's allowed to do any calling at all, and it has 10 possible fuses to call, so that makes 10 possible connections.   If you turned these into diagrams, where you draw every possible connection, then the first situation would look like a pit full of snakes from Raiders of the Lost Ark.  The second situation looks like something a human being can cope with - hell, the lines don't even cross!   Just so you can see the implications, if we have 1000 fuses instead of 10, free interconnections means 999000 lines, whereas Fusebox connections means only 1000 lines.  It's Order(n-squared) versus Order(n).   In practice, it means you always know where to look to see what files are being called.  There are no decisions to be made about where you should call from.  What you get is certainty, consistency, simplicity.  You lose freedom, yes, but with enormous gains in maintainability, reusability, etc, and without any loss in power.  And that's what we call "Fusebox".  Huzzah!!!   See ya, LeeBB     Bjork.NET - Postcards gratefully accepted. ----- Original Message ----- From: Tom Schreck   I know true FB3 methodology calls for separating query fuses from display fuses, but does this not produce more work having to remember to include calls to queries 1,2, and 3 before calling display page X?  What's the reason for not putting all necesarry query calls within the display page itself? ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================