Actually for sandbox (which I have not yet changed) I was going to recommend the following:
Change the identifier to be "sbx" in the TLD. Change <x:foo> to <sbx:foo> in the xdocs (website documentation) and the javadoc for the TLD. Finally change <x:foo> to <t:foo> in the examples. NOTE: I am suggesting <t:foo> for the examples instead of <sbx:foo>. This makes it easier to convert the examples when they move out of the sandbox. I plan on following the same convention in my own jsp so if I want to use sandbox components in my app, I don't have to change *anything* in my jsp once the component moves to tomahawk. (Eventually I could delete the <[EMAIL PROTECTED] ...> for the sandbox but it wouldn't be necessary. sean On 8/9/05, Korhonen, Kalle <[EMAIL PROTECTED]> wrote: > > -----Original Message----- > > From: Sean Schofield [mailto:[EMAIL PROTECTED] > > Subject: Re: [proposal] TLD changes > > picke their own. I just prefer the docs, etc. use 't' b/c it > > looks better than the other options. I would also prefer 's' > > for sandbox but that might cause confusion with shale. > > At least to me, "ts" for sandbox as in "tomahawk sandbox" makes perfect > sense - most of the things in sandbox are new components. Then later, > once the component gets promoted, it can drop the "s" from its > definition. > > Kalle >
