good points, Gary but >> "attributename" methodology is much safer and easier to maintain.
to a point. Passing attributes by name worries me and goes against the way I work. This tightly couples the calling code to the tag. Sure that's how tags usually work but *tags != functions != fullyReusableCode*. If I create an attribute within the tag and later change it (poor choice of name, etc), all the code that uses that tag gets HAS TO change as well. Possible in the scheme of things. Hey, even MM depricates tags and they have more resources than me to think ahead. maybe it's just I'm missing *real* objects and pointers (or at least byRef) and trying to shoe-horn CF into a "black-box" component design... any thoughts? cheers barry.b -----Original Message----- From: Gary Menzel [mailto:[EMAIL PROTECTED] Sent: Monday, 11 August 2003 12:34 PM To: CFAussie Mailing List Subject: [cfaussie] RE: taglib quick question I wouldn't do it as a list. The concept of the CFIMPORT is that you are extending the tag space (cross-reference how XML namespaces can extend the tagspace on the client side). You should be approaching it as though you are just writing new tags. And should use the currently accepted conventions for tags - i.e. <tagname attributename="value"..... /> By using a list you then have to REMEMBER what the order needs to be. The "attributename" methodology is much safer and easier to maintain. Your parameters can be in and order and you can detect the presence (or otherwise) inside the tag code. 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 [EMAIL PROTECTED] wrote on 08/11/2003 12:02:29 PM: > > Hmmm that's do-able. > > OK, personal prefrence question: > > would you (a) put in all arguments in the call, leaving spaces for no values > (as in vb/vbs) > > <siteTags:menuLink attr="index.cfm,,home"> > > or (b) treat it as an array in the tag code > > { > if (arrayLen(arguments) GT 2) optionalThirdParam = arguments[3] > } > > or (c) is there an easier/better way? > > cheers > barry.b > > > > -----Original Message----- > > From: Lindsay Evans [mailto:[EMAIL PROTECTED] > Sent: Monday, 11 August 2003 11:49 AM > To: CFAussie Mailing List > Subject: [cfaussie] RE: taglib quick question > > > > How about something like this: > > <siteTags:menuLink attr="index.cfm,home"> > > Then access the attribute as a list. > > -- > Lindsay Evans. > Developer, > Red Square Productions. > > [p] 8596.4000 > [f] 8596.4001 > [w] www.redsquare.com.au > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Beattie, > > Barry > > Sent: Monday, August 11, 2003 11:25 AM > > To: CFAussie Mailing List > > Subject: [cfaussie] taglib quick question > > > > > > OK, taglibs make more sence for output than CFC's. > > > > so, using an example on http://blog.daemon.com.au/archives/000143.html > > > > is there any way I don't have to specify the *name* of the > > attribute to pass > > to the tag > > > > eg: instead of > > <siteTags:menuLink link="index.cfm" linkText="home"> > > > > which relys on > > <cfparam name="attributes.link" default="home.cfm"> > > <cfparam name="attributes.linkText" default="home"> > > > > I can just use the order the attributes are passes (this doesn't work)? > > <siteTags:menuLink "index.cfm", "home"> > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to > [EMAIL PROTECTED] > > MX Downunder AsiaPac DevCon - http://mxdu.com/ > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > > MX Downunder AsiaPac DevCon - http://mxdu.com/ **************************************************************************** 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 currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
