webwork-devel Mailing List for WebWork (Page 44)
Brought to you by:
baldree,
rickardoberg
Menu
▾
▴
webwork-devel — WebWork development
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(316) |
Dec
(117) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(197) |
Feb
(229) |
Mar
(293) |
Apr
(177) |
May
(84) |
Jun
(40) |
Jul
(43) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: matt b. <ba...@us...> - 2001-12-20 18:24:58
|
Update of /cvsroot/webwork/webwork/src/resources/web In directory usw-pr-cvs1:/tmp/cvs-serv12643 Modified Files: expr.jsp index.jsp numguess.jsp Log Message: fixed LF |
|
From: matt b. <ba...@us...> - 2001-12-20 18:23:59
|
Update of /cvsroot/webwork/webwork/src/resources/web/template/standard In directory usw-pr-cvs1:/tmp/cvs-serv12469 Modified Files: select.jsp selectcascading.jsp selectgroupmap.jsp selectmap.jsp Log Message: added size attribute |
|
From: matt b. <ba...@us...> - 2001-12-20 18:23:45
|
Update of /cvsroot/webwork/webwork/src/resources/web/template/standard In directory usw-pr-cvs1:/tmp/cvs-serv12426 Added Files: label.jsp Log Message: new |
|
From: matt b. <ba...@us...> - 2001-12-20 18:23:32
|
Update of /cvsroot/webwork/webwork/src/resources/web/template/standard In directory usw-pr-cvs1:/tmp/cvs-serv12377 Modified Files: checkbox.jsp Log Message: fixed LF |
|
From: matt b. <ba...@us...> - 2001-12-20 18:22:43
|
Update of /cvsroot/webwork/webwork/src/resources/web/WEB-INF/classes/META-INF In directory usw-pr-cvs1:/tmp/cvs-serv12190 Modified Files: taglib.tld Log Message: add label tag and size attribute to select |
|
From: matt b. <ba...@us...> - 2001-12-20 18:21:14
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv11839 Modified Files: index.xml jsp-attrib.xml jsp.xml jspref.xml Added Files: jsp-label.xml Log Message: added label tag |
|
From: matt b. <ba...@us...> - 2001-12-20 18:20:57
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv11755 Modified Files: jsp-select.xml Log Message: add size attribute |
|
From: matt b. <ba...@us...> - 2001-12-20 18:20:35
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv11679 Modified Files: jsp-textfield.xml Log Message: removed duplicate readonly attribute |
|
From: Matt B. <ma...@sm...> - 2001-12-20 11:37:50
|
>Hm... I'm too tired to figure out a good solution to this one right now. > If someone has an idea of how to solve it, that's great, but >otherwise we should put it into the RFE tracke on SourceForge, so that >it's not lost. It's an important point. > >/Rickard > >-- >Rickard Öberg >Chief Architect, TheServerSide.com >The Middleware Company added _______________________________________________ Webwork-devel mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webwork-devel |
|
From: Matt B. <ma...@sm...> - 2001-12-20 11:31:33
|
I'll just add label tag. -Matt ----- Original Message ----- From: "Rickard" <ri...@mi...> To: "Matt Baldree" <ma...@sm...> Cc: "Mike Cannon-Brookes" <mi...@at...>; "Webwork-Devel" <web...@li...> Sent: Thursday, December 20, 2001 12:36 AM Subject: Re: [Webwork-devel] New UI tags? - <ui:hidden> and <ui:textlabel> Matt Baldree wrote: > +1. I would prefer this over mixing INPUT HIDDEN tags. Looks nicer. > Obviously, you can produce the text label with HTML and PROPERTY tag but > having a UI tag will give you the same format treatment you are using with > other controls. Assuming others are okay, I'll add it in. I'm ok with the label tag, since it at least fits the skinning capability requirement of the UI tags, but I don't quite see the point of the hidden tag. /Rickard -- Rickard Öberg Chief Architect, TheServerSide.com The Middleware Company _______________________________________________ Webwork-devel mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webwork-devel |
|
From: Rickard <ri...@mi...> - 2001-12-20 05:40:25
|
Matt Baldree wrote: > Obviously size is easy and I think it should be added. >=20 > IMHO multiple is more complicated. Right now the Action setter for the > select would be called multiple times for each selected item when the f= orm > is submitted. This is fine if you are building the list via the setter = but > to display the appropriate selected items on the load would be the prob= lem. > Right now "value" is used to set the SELECTED item and it assumes only = one > item. I'll let Rickard chime in on this but this seems like a 1.1 featu= re. Hm... I'm too tired to figure out a good solution to this one right now.=20 If someone has an idea of how to solve it, that's great, but=20 otherwise we should put it into the RFE tracke on SourceForge, so that=20 it's not lost. It's an important point. /Rickard --=20 Rickard =D6berg Chief Architect, TheServerSide.com The Middleware Company |
|
From: Rickard <ri...@mi...> - 2001-12-20 05:38:04
|
First off, it's awesome that you're taking the lead in this effort, and=20 you're doing some great stuff to get this done. I really appreciate it! Matt Baldree wrote: > Intro - Rickard? > HMVC - Rickard? > Model-1/2 Yup, I'll do these. I'm in Austin/TX right now, with TheServerSide, and=20 don't have much time, but I have a very very long flight back to Sweden=20 this weekend, which could be spent writing :-) > Base classes - need more info. of what this section would look like This is about how you use base classes as a technique for doing security=20 or other kind of "interceptor"-ish handling. /Rickard --=20 Rickard =D6berg Chief Architect, TheServerSide.com The Middleware Company |
|
From: Rickard <ri...@mi...> - 2001-12-20 05:35:09
|
Matt Baldree wrote: > +1. I would prefer this over mixing INPUT HIDDEN tags. Looks nicer. > Obviously, you can produce the text label with HTML and PROPERTY tag bu= t > having a UI tag will give you the same format treatment you are using w= ith > other controls. Assuming others are okay, I'll add it in. I'm ok with the label tag, since it at least fits the skinning=20 capability requirement of the UI tags, but I don't quite see the point=20 of the hidden tag. /Rickard --=20 Rickard =D6berg Chief Architect, TheServerSide.com The Middleware Company |
|
From: Rickard <ri...@mi...> - 2001-12-20 05:31:54
|
Mike Cannon-Brookes wrote: > I'd like to propose two new UI tags >=20 > <ui:hidden> which generates a form hidden field, the template is very > simple as it just spits out the input control and no HTML at all is > necessary What value would this have over doing raw HTML? With the other tags the=20 idea is to 1) have a simple way of showing and modifying data and 2) to=20 be able to control the l&f of the UI control. A hidden field tag would=20 accomplish neither. What am I missing? > <ui:textlabel> (better name?) - basically this is useful when you want > to spit out some text for the user, which is not submitted with the for= m > - but in the same style. >=20 > eg > <ui:textlabel label=3D"'Project'" name=3D"'selectedProject/name'" /> > <ui:textfield label=3D"'Summary'" name=3D"'summary'" /> >=20 > generates something like (imagine an HTML table ;)) >=20 > Project: Project1 > Summary: <<textfield>> >=20 > IMHO both should take 5 minutes, but will make the form library a littl= e > more comprehensive. >=20 > Thoughts? For the style part you could just use HTML with the CSS classes to get=20 the same style. But, yes, it might be a point to do a tag for it. /Rickard --=20 Rickard =D6berg Chief Architect, TheServerSide.com The Middleware Company |
|
From: matt b. <ba...@us...> - 2001-12-20 03:22:38
|
Update of /cvsroot/webwork/webwork/src/main/webwork/taglib/ui In directory usw-pr-cvs1:/tmp/cvs-serv25332 Modified Files: CheckBoxTag.java ComboBoxTag.java RadioTag.java SelectTag.java TextAreaTag.java TextFieldTag.java Log Message: fixed LF |
|
From: Matt B. <ma...@sm...> - 2001-12-20 03:10:39
|
Obviously size is easy and I think it should be added. IMHO multiple is more complicated. Right now the Action setter for the select would be called multiple times for each selected item when the form is submitted. This is fine if you are building the list via the setter but to display the appropriate selected items on the load would be the problem. Right now "value" is used to set the SELECTED item and it assumes only one item. I'll let Rickard chime in on this but this seems like a 1.1 feature. -Matt ----- Original Message ----- From: "Mike Cannon-Brookes" <mi...@at...> To: "Webwork-Devel" <web...@li...> Sent: Wednesday, December 19, 2001 8:19 PM Subject: [Webwork-devel] <ui:select> > Missing attributes size and multiple? > > -mike > > -- > Cheers, > Mike > > -- > Mike Cannon-Brookes :: mi...@at... > > Atlassian :: http://www.atlassian.com > Supporting YOUR J2EE World > > > > _______________________________________________ > Webwork-devel mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-devel > > |
|
From: matt b. <ba...@us...> - 2001-12-20 02:24:26
|
Update of /cvsroot/webwork/webwork/src/resources/web/WEB-INF/classes/META-INF In directory usw-pr-cvs1:/tmp/cvs-serv7600 Modified Files: taglib.tld Log Message: fixed LF |
|
From: Mike Cannon-B. <mi...@at...> - 2001-12-20 02:16:54
|
Missing attributes size and multiple? -mike -- Cheers, Mike -- Mike Cannon-Brookes :: mi...@at... Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World |
|
From: Matt B. <ma...@sm...> - 2001-12-20 01:50:07
|
Well, I think it's time to make a sprint for the finish line and get that documentation done. With the holidays coming, people may be bored and have lots of time on their hands wishing they had something to do :-). I have listed below the areas in the doc's TOC that have not been assigned. If any section listed below interests you, just go to the project home page and file a bug stating that a certain documentation section is incomplete and you plan to write it. If you feel you would like to revise a section assigned to somebody else, then just let your intentions be known and go for it. Together we can divide and conquer this thing and get 1.0 released. -Matt Intro - Rickard? HMVC - Rickard? Model-1/2 Action API WW API - primarily just point to JavaDoc? Velocity - Victor? Base classes - need more info. of what this section would look like Forms Error handling Wizards i18n Features - need a sample of the features we should list here License - probably just cut and paste? |
|
From: Matt B. <ma...@sm...> - 2001-12-20 01:45:25
|
+1. I would prefer this over mixing INPUT HIDDEN tags. Looks nicer. Obviously, you can produce the text label with HTML and PROPERTY tag but having a UI tag will give you the same format treatment you are using with other controls. Assuming others are okay, I'll add it in. -Matt ----- Original Message ----- From: "Mike Cannon-Brookes" <mi...@at...> To: "Webwork-Devel" <web...@li...> Sent: Wednesday, December 19, 2001 6:25 PM Subject: [Webwork-devel] New UI tags? - <ui:hidden> and <ui:textlabel> > I'd like to propose two new UI tags > > <ui:hidden> which generates a form hidden field, the template is very > simple as it just spits out the input control and no HTML at all is > necessary > > <ui:textlabel> (better name?) - basically this is useful when you want > to spit out some text for the user, which is not submitted with the form > - but in the same style. > > eg > <ui:textlabel label="'Project'" name="'selectedProject/name'" /> > <ui:textfield label="'Summary'" name="'summary'" /> > > generates something like (imagine an HTML table ;)) > > Project: Project1 > Summary: <<textfield>> > > IMHO both should take 5 minutes, but will make the form library a little > more comprehensive. > > Thoughts? > > -- > Cheers, > Mike > > -- > Mike Cannon-Brookes :: mi...@at... > > Atlassian :: http://www.atlassian.com > Supporting YOUR J2EE World > > > > _______________________________________________ > Webwork-devel mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-devel > > |
|
From: Mike Cannon-B. <mi...@at...> - 2001-12-20 01:15:32
|
Apologies - this appears to work now ;) I really have to get this dyslexic keyboard replaced. -mike On Thu, 2001-12-20 at 12:05, Mike Cannon-Brookes wrote: > Is anyone against changing the param tag to take two forms: > > <ui:param name="foo" value="bar" /> > > OR > > <ui:param name="foo"> > bar > </ui:param> > > The second form is useful when you want to create a very complicated > parameter (such as a string of HTML that is generated using other tags). > It also makes the tag much more flexible. > > eg > <ui:param name="label"> > Project: <br> > (<a href="SelectProject!default.action<webwork:url value="oldProject" > />">Select New Project</a>) > </ui:param> > > > Thoughts? > > -mike > > -- > Cheers, > Mike > > -- > Mike Cannon-Brookes :: mi...@at... > > Atlassian :: http://www.atlassian.com > Supporting YOUR J2EE World > > > > _______________________________________________ > Webwork-devel mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-devel -- Cheers, Mike -- Mike Cannon-Brookes :: mi...@at... Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World |
|
From: Mike Cannon-B. <mi...@at...> - 2001-12-20 01:02:50
|
Is anyone against changing the param tag to take two forms: <ui:param name="foo" value="bar" /> OR <ui:param name="foo"> bar </ui:param> The second form is useful when you want to create a very complicated parameter (such as a string of HTML that is generated using other tags). It also makes the tag much more flexible. eg <ui:param name="label"> Project: <br> (<a href="SelectProject!default.action<webwork:url value="oldProject" />">Select New Project</a>) </ui:param> Thoughts? -mike -- Cheers, Mike -- Mike Cannon-Brookes :: mi...@at... Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World |
|
From: Mike Cannon-B. <mi...@at...> - 2001-12-20 00:22:39
|
I'd like to propose two new UI tags <ui:hidden> which generates a form hidden field, the template is very simple as it just spits out the input control and no HTML at all is necessary <ui:textlabel> (better name?) - basically this is useful when you want to spit out some text for the user, which is not submitted with the form - but in the same style. eg <ui:textlabel label="'Project'" name="'selectedProject/name'" /> <ui:textfield label="'Summary'" name="'summary'" /> generates something like (imagine an HTML table ;)) Project: Project1 Summary: <<textfield>> IMHO both should take 5 minutes, but will make the form library a little more comprehensive. Thoughts? -- Cheers, Mike -- Mike Cannon-Brookes :: mi...@at... Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World |
|
From: Victor S. <sa...@us...> - 2001-12-19 18:18:38
|
Update of /cvsroot/webwork/webwork/src/main/webwork/action/factory In directory usw-pr-cvs1:/tmp/cvs-serv2283 Modified Files: DefaultActionFactory.java Log Message: Changed the order of when CommandActionFactoryProxy is used. |
|
From: matt b. <ba...@us...> - 2001-12-18 23:20:07
|
Update of /cvsroot/webwork/webwork/src/docs In directory usw-pr-cvs1:/tmp/cvs-serv28208 Modified Files: community.xml expr.xml Log Message: initial rev |
34982 messages has been excluded from this view by a project administrator.
