-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I agree with John 100%, and to add to this, it would conform more to:
1- JSP Custom tags 2- Generally correct syntax for XML , XHTML etc... You really want WiTango to 'look' like it follows those standards, not only to give a positive impression, but to help anyone on the outside to be able to adapt to the way you write code in Tango without having to second guess everything. Imagine you had a tag called <security> which hid information from a user if they didn't have the proper security credentials. Like John said, do you really want to stick all your html inside the security tag? In JSP you do: <util:security access="root"> ... some html you want to show and hide properly here </util:security> Can't do this right now, and am generally relegated to using an include inside the security tag so I can keep the code clean. Using an include is yet another tag the app server has to process, which means more overhead. R John McGowan wrote: |Gauthier, | |The uses for these types of tags are endless... Imagine where you'd be if |the <@FOR> or the <@IF> tag didn't have end tags... how would you like to |put all your outputted code in an attribute called "code". Well, having |this type of limitation on our custom tags is hampering our ability to make |easy to use custom tags. | |Example... | |<@FOR START=1 STOP=10 STEP=1> |a bunch of html and tango code goes here... |possibly spanning over several lines, or pages of code... |'</@FOR> | |would have to be... | |<@FOR START=1 STOP=10 STEP=1 CODE=" |a bunch of html and tango code goes here... |possibly spanning over several lines, or pages of code..."> | |I have at least a half a dozen custom tags that I would develop if I could |define a variable that comes from the "body" of the tag instead of an |attribute. | |The main reason is that the first example is much easier to teach to |someone, I have people totally unfamiliar with Witango using our custom |tags. | |/John | | | |----- Original Message ----- |From: "[Gauthier]" <[EMAIL PROTECTED]> |To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> |Sent: Thursday, September 12, 2002 3:57 PM |Subject: Re: Witango-Talk: Custom Tag Limitation Question | | |>Hi |> |>I'm unsure but I currently don't see any concrete use of closing metatags |>appart for loops or sessions, so I'm unable to say if could be usefull for |>the developer, maybe for managing some sort of constraints, but I think | |this | |>would be too complex to manage with. |> |>Does anyone see any use for this? |> |>However I'm not against the addition of the <@WHILE> metatag ;) |> |>Gauthier |> |>----- Original Message ----- |>From: "Mike Tyranski" <[EMAIL PROTECTED]> |>To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> |>Sent: Thursday, September 12, 2002 10:23 PM |>Subject: Witango-Talk: Custom Tag Limitation Question |> |> |>>Currently with Tango there is a limitation with custom tags |>> |>>"All custom meta tags are "empty" tags; that is, custom meta tags can |>>have attributes but not content, because they do not have start and end |>>tags." |>> |>>Does Witango overcome or plan to overcome this limitation with custom |>>tags? It would be a great addition to the product and open up the doors |>>to many different possibilities. |>> |>>Mike |>>________________________________________________________________________ |>>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] |>> |>> with unsubscribe witango-talk in the message body |> |> |>________________________________________________________________ |>Etudiant: Wanadoo t'offre le Pack eXtense Haut Dibit soit 150,92 euros | |d'iconomies ! | |>Et pour 1 euro de plus, regois le CD-ROM du jeu Dark Age of Camelot |>+ 1 mois de jeu en riseau offert ! |>Clique ici : http://www.ifrance.com/_reloc/mail.etudiant |> |>________________________________________________________________________ |>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] |> with unsubscribe witango-talk in the message body | | |________________________________________________________________________ |TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | with unsubscribe witango-talk in the message body -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9geXsK/1j/4sLi/ARAo1RAJ9lPQGh6QY9xmMQ022UYyn1l6nJWACfdGlh p9C/gT7I4anf2fjOUkA9YA8= =m+RO -----END PGP SIGNATURE----- ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
