Re: i18n and (change it!)

[Johan Compagner <jc...@j-com.nl>]

Change it!
Got my vote!

2 options are still open for me:

struts-forms: Only form specifiek  and struts-html: other besides form.
or
struts-html: All including forms.

The first approache is in my eyes slightly better but if you think struts-forms can
be used better for something else then use the second one.

Johan



----- Original Message ----- 
From: "Craig R. McClanahan" <Cr...@eng.sun.com>
To: <st...@jakarta.apache.org>
Sent: Wednesday, December 27, 2000 7:07 PM
Subject: Re: i18n and <form:html>


> Johan Compagner wrote:
> 
> > The naming convention is a bit strange the form tag lib that has also other things
> > that can be used besides forms. Maybe there should be a html tag lib for link/img/html ect ect.
> > and the form tag lib contains only tag's about forms.
> >
> 
> Yah, I've been thinking about this bit of ugliness quite a bit.
> 
> In retrospect, it would have been better to call this tag library "struts-html" instead of
> "struts-form", because nearly all of the rendering tags are HTML-specific.  It would also leave the
> name "struts-form" open for potential use with a library that is totally devoted to XForms or
> something like that.
> 
> There is still time to make that change before 1.0 -- and if we are ever going to, now is
> definitely the time.
> 
> What do you think?
> 
> >
> > johan
> 
> Craig
> 
> 
> 

Re: i18n and (change it!)

[Michael Westbay <we...@seaple.icc.ne.jp>]

Compagner-san wrote:

> Change it!
> Got my vote!
> 
> 2 options are still open for me:
> 
> struts-forms: Only form specifiek  and struts-html: other besides form.
> or
> struts-html: All including forms.

I agree, now is the time.

I would lean toward the second option as it would make porting easier.  And as
McClanahan-san mentioned, it would leave struts-form open to something else like
XForm.  (But then again, why not struts-xform for that?)

The major benifit from the first option, a separate form-centric taglib would be
to distinguish those things that can ONLY be found within <form:form>...
</form:form> tags from the rest of the HTML tags - which can go anywhere.  (But
then again, if you break the tags up that far, would you go to breaking up
header-centric, body-centric, and frame-centric tags into other libraries as
well?)

Hmm.  I contridict myself twice in one message.  After due deliberation with
myself, I think that now I'm agreeing more with Compagner-san, struts-html AND
struts-forms, even with the additional porting task, would be the best bet.

--
Michael Westbay
Work: Beacon-IT http://www.beacon-it.co.jp/
Home:           http://www.seaple.icc.ne.jp/~westbay
Commentary:     http://www.japanesebaseball.com/