First:
about.abouthome you should have it be just
about.home or better yet, about.index... the about should be implied
by the circuit.
In my design model I would have a action on the about news and
anything else that would change up your navigation.. It would some
how set/return a navigation
Dustin Tinney wrote:
First:
about.abouthome you should have it be just
about.home or better yet, about.index... the about should be implied
by the circuit.
Yeah, I was going through all my circuits changing them probably at the
same time you were typing it ;)
In my design model I would
that would be one way to do it. Pre-fuseactions would give you that
functionality.
If I was using a pre-fuseaction I wouldn't have it pass back the nav
or print it out. instead I would have it set a variable.. such as
nav_template_file and then in your main template where you would have
your
Fusebox isn't really a changing of anything, all that it does it allow you
to have a more thought out way of managing your code. It borrows things from
oop where it applies. I use it as much as I can, I would not go back. It
allows me to reuse code much easier.
Robert Everland III
Dixon
Subject: RE: Fusebox Question
Fusebox isn't really a changing of anything, all that it does it allow you
to have a more thought out way of managing your code. It borrows things from
oop where it applies. I use it as much as I can, I would not go back. It
allows me to reuse code much easier.
Robert
Lot's of ways to get around that... like including the template name in
comments on each page.
!-- Here's an example //--
Mike
-Original Message-
From: Shawn Grover [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 12:02 PM
To: CF-Talk
Subject: RE: Fusebox Question
For me
Shawn,
For me, the concept of Fusebox is good, but in practicality it becomes a
pain to debug having to track back through ALL included files to find
an
error
Not sure what version of CF you are using, but CF4x and CF5 debug
information gives the file name of the template where the error
So how do you do the following in strict Fusebox style?
I have an app where to simplify matters for users they
only need enter a Search Term and hit Enter. (I tried
making them select an option before they hit enter, but
did not feel it was user-friendly enuf. BTW, this
kind of follows
Hey, my answers are indicated by below.
Gregory Harris
Los Angeles Information Technology Agency (ITA)
[EMAIL PROTECTED]
[EMAIL PROTECTED] 08/14 9:45 AM
I am new to the fusebox methodology, and hoping that someone might give me some
structural pointers.
It seems like there will be plenty
Thanks for the response. How are situations handled where you have a
query within a loop handled within Fusebox?
For example:
CFLOOP INDEX="CountLoop" FROM=1 TO=10
CFQUERY .
SELECT * FROM Table
WHERE ID = CountLoop
/CFQUERY
CFOUTPUT
You are at
I'm not sure if I understand you. But here it goes. This looks like a regular
programming construct that could be handled within any CF Block. Just use a query or
action file (qry_file or act_file) as appropriate.
Remember that templates can be dependent on other templates to do actions,
11 matches
Mail list logo