Hi Jerzy, The general rule is that we separate data/content from presentation. Each fuse should do one and only one thing (eg., query a database or output some HTML, but not both). I describe fuses as "atomic".
Then the Fuseaction combines these atomic fuses to perform complete tasks (eg., query a database, then use the results to populate and display a form for editing the data). You can think of the fuses as the ingredients in your kitchen, and the fuseactions are recipes that combine the ingredients in different ways. Ingredients are *low-level* items - you don't have "choclate cake" as an ingredient (fuse), but you might have a recipe (fuseaction) for chocolate cake. So the whole concept of code re-use is essentially the same idea as cooking. You have a finite set of ingredients/fuses, and you can combine them using different recipes/fuseactions to create a squillion different things. See ya, LeeBB [EMAIL PROTECTED] wrote: > Hi, > > I am new into Fusebox and when I was reading basic and advance > techniques from www.fusebox.org site, I was confused. > > In advance example #4 > http://www.fusebox.org/index.cfm?Fuseaction=fusebox2.techniques2, there > is a sample how to reuse CF script to display form with tree different > stages: blank, query and form. In the second case, the data was taken > from cfquery. I also read that query should be separated and put into > qry_* files, when presentation html code should be kept separately > inside dsp_* files. > So is it an exception or we should feel flexible and join query and > presentation when we need it? > ==^================================================================ 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 ==^================================================================
