> I'd like to have a religious war on whether to use CFCs or Custom Tags
for
> display.  I tried to start one on CF-Talk a few weeks ago, but it didn't
get
> much of a response.  I've never seen this fleshed out very well
anywhere.

Might as well jump in on this.

I think it is important to decide on a per instance basis what is going to
work best.

If there is a rich data model and you want to have multiple ways of
displaying it - AND you want to allow non-programmers a family mechanism
of creating those displays - then a mixture of CFC's Custom Tag's would
sound sensible.

There could be multiple ways the data may end up being displayed that the
designer of the backend never envisaged.  So you are better off separating
out the display logic right from the beginning.

Sometimes you need "complex" layout and creating that up in a CFC by
appending strings to a variable is a pain in the butt.  This is better
done in a tag format that a procedural language with strings.  You can, of
course, use CFSAVECONTENT (but the next question would be - "Why not
separate that out into a custom tag?").

On the other hand, you may have a system where how the data is displayed
is critical and you dont want any "novices" tinkering around with the
layout.  Then you are probably better off encapsulating that in the CFC.

I am going to disagree with the "self documenting methods" comment because
sometimes display logic is better "self documented" as tags rather than a
conatenation into a string variable.

It partly depends on how much of your display logic needs to be "strict"
as opposed to being "flexible".

Putting it in a CFC makes it much stricter than putting it into a Custom
Tag.

I dont think you will get a religious war on CFC vs Custom Tags - because
sometimes it makes sense to do the output portions in different ways.


Gary Menzel
Web Development Manager
IT Operations Brisbane -+- ABN AMRO Morgans Limited
Level 29, 123 Eagle Street BRISBANE QLD 4000
PH: 07 333 44 828  FX:  07 3834 0828


****************************************************************************
If this communication is not intended for you and you are not an authorised
recipient of this email you are prohibited by law from dealing with or
relying on the email or any file attachments. This prohibition includes
reading, printing, copying, re-transmitting, disseminating, storing or in
any other way dealing or acting in reliance on the information.  If you
have received this email in error, we request you contact ABN AMRO Morgans
Limited immediately by returning the email to [EMAIL PROTECTED]
and destroy the original. We will refund any reasonable costs associated
with notifying ABN AMRO Morgans. This email is confidential and may contain
privileged client information. ABN AMRO Morgans has taken reasonable steps
to ensure the accuracy and integrity of all its communications, including
electronic communications, but accepts no liability for materials
transmitted. Materials may also be transmitted without the knowledge of ABN
AMRO Morgans.  ABN AMRO Morgans Limited its directors and employees do not
accept liability for the results of any actions taken or not on the basis
of the information in this report. ABN AMRO Morgans Limited and its
associates hold or may hold securities in the companies/trusts mentioned
herein.  Any recommendation is made on the basis of our research of the
investment and may not suit the specific requirements of clients.
Assessments of suitability to an individual's portfolio can only be made
after an examination of the particular client's investments, financial
circumstances and requirements.
****************************************************************************

----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]

Reply via email to