These are almost always preference issues. These are the guidelines I follow. If what is currently (or latently) part of a larger fuse but can re used elsewhere in its own right, I would create a separate fuse.
Overall I like to make our projects and applications as understandable/transparent to other Fuseboxers as possible, I try to avoid very long fuses. Those are my thoughts...briefly for once. Kind Regards - Mike Brunt, CTO Webapper http://www.webapper.com Downey CA Office "Webapper - Making the NET work" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 9:00 AM To: [EMAIL PROTECTED] Subject: How atomic does each fuse need be? Hi all, I'm doing something very basic here, and I thought it would serve as a good place to make sure I'm on the right track. It may just come down to a matter of preference, but I'd just liek to double check. I need to display listing of records and then the individual records detail. I was thinking about having two fuses: qry_records & dsp_records, and just using conditional logic in both the query fuse and the display fuse to determine both what query to run and which format to display. Is this wrong? I mean, I can certainly break it down into 2 query fuses and two display fuses, but is this necessary? I know this is a simple example, but it will serve to better understand just how atomic each fuse needs to be. Thanks! ==^================================================================ 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 ==^================================================================
