On Aug 29, 2007, at 1:00 PM, William M Conlon wrote:
One of the things that has disappointed me is the lack of an
ecosystem for witango components that can be shared, including
Custom Meta Tags.
I'm curious how others implement these:
* are your custom tags assembled in a single class file, or do you
use a separate tcf for each tag?
We have "clumps" of related custom tags - these are within a single
tcf. And the xml is a single file with all of the methods within a
single tcf.
* what are your naming conventions for the class files and methods
within the class?
Mainly we follow Witango's guidance and use a two word tag name
(e.g. <@ajax_header
For general functions like the ajax stuff, they all start with
<@ajax_ but most our stuff is just limited to our application and
we haven't worried too much about naming conventions other than that.
* how do you propagate the custom tags to your users, for example
integrating them into the studio, and explaining their use. (BTW,
wouldn't it be nice if the tag description could be pulled into the
studio so the tag could appear in the snippets, along with
description of the method and attributes).
The custom tags have a description area, and the methods called
usually have a (commented out) description at the top of the method.
(And yes, your suggestion is a great one...)
* do you use the witango meta tag generator, or just edit the file
yourself?
Once we had it generated once for us, that worked as a template, and
now we edit these files ourself. It's easy.
* do you use meta tags developed by someone else?
We purchased SpitFireCharts and used their custom tags + tcf.
Unfortunately the tcf couldn't be migrated to classfiles where most
of our work is these days, so that's kind of languished for us.
thanks
Bill
William M. Conlon, P.E., Ph.D.
To the Point
2330 Bryant Street
Palo Alto, CA 94301
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
