> I understand what you are saying about clearly stating the > inputs (and the outputs) to make sense of what is going into > the tag... But in this case, we are basically passing variable > datasource and table names, color settings and such... Any > noticable parameters are being passed as attributes to the > tag specifically. > > Would this be considered poor practice? Since we are calling > our preference file with each page load, I would hate to call > it again in the custom tag .. and using calling. can be a bit > wordy ... maybe I am off base, but trying to make things clear > to those who dig into the tags.
In principal, I might prefer simply passing all values that the custom tag needs as attributes. However, I can understand why people might not do that in practice. So, while I might have a preference that differs from your approach, I wouldn't say that your approach is poor practice. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
