Latest and Greatest 1.0 User's Guide

["Craig R. McClanahan" <Cr...@eng.sun.com>]

I've just posted the most recent version of the Struts documentation on the
Struts web site at:

    http://jakarta.apache.org/struts/

The User's Guide pages have had the XSLT stylesheet used to create them spruced
up a bit, so that the visual appearance is similar to the rest of the Struts
documentation.

Craig McClanahan

Re: Latest and Greatest 1.0 User's Guide

["Steven D. Wilkinson" <st...@acm.org>]

Ted Husted wrote:
> 
> Since the chapters tend to start with generic headings, like
> "Overview", I think it would read better if we set the chapter title
> out at the top of the body, where the reader's attention is focused.
> 
I like that.  Then its easier to know where you are relative to the quick
links.  It is a little hard now since the quick link doesn't have a Section
number on it and the Section page doesn't have a Section heading on it.  Thanks
Ted.  BTW, big improvement in the documentation both in content and layout. 
Thanks to everyone who contributed!

Steve

Re: Latest and Greatest 1.0 User's Guide

[Ted Husted <ne...@husted.com>]

On 1/21/2001 at 5:16 PM Craig R. McClanahan wrote:
> It's the title of the HTML document -- isn't that good enough?  If
not, that is
a pretty straightforward change.

Since the chapters tend to start with generic headings, like
"Overview", I think it would read better if we set the chapter title
out at the top of the body, where the reader's attention is focused. 

-T.

Re: Latest and Greatest 1.0 User's Guide

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Ted Husted wrote:

> Very, very kewl.
>
> Short Term Plan
>
> I'm about through the Users Guide, and will refresh my CVS and post
> some very minor  fixes.
>
> I'll also update the struts.xls to reflect a 2001 copyright (forward
> into the present!)
>
> Meanwhile,
>
> Any thoughts on a better approach to formatting the example code. I've
> seen the same problem with other subprojects.
>

The most important issue is to use spaces rather than tabs inside a <pre>
block.  The whitespace you use is copied verbatim.

In the page source, I typically left justify my <pre> blocks, and use four
spaces of indent in front of the code lines.

>
> Also (extremely nitty but), The chapter title (2. Building Model
> Components) is not  displayed over the first section (2.1 Overview).
>

It's the title of the HTML document -- isn't that good enough?  If not, that is
a pretty straightforward change.

>
> Don't know enough about XML/XLS to even think about messing with the
> stylesheet to address either concern.
>
> -Ted.

Craig

Re: Latest and Greatest 1.0 User's Guide

[Ted Husted <ne...@husted.com>]

Very, very kewl. 

Short Term Plan

I'm about through the Users Guide, and will refresh my CVS and post
some very minor  fixes. 

I'll also update the struts.xls to reflect a 2001 copyright (forward
into the present!)

Meanwhile, 

Any thoughts on a better approach to formatting the example code. I've
seen the same problem with other subprojects. 

Also (extremely nitty but), The chapter title (2. Building Model
Components) is not  displayed over the first section (2.1 Overview). 

Don't know enough about XML/XLS to even think about messing with the
stylesheet to address either concern.

-Ted.

Re: doc/1.0 - HTML:options

[Joshua Hill <jh...@appliedtheory.com>]

It works for me. What the tag does is to use the bean associated with the
html:form tag
which may or may not be a ActionForm. This bean must have a property for
both the
select tag and the options tag. Here's an example that generates a select
box of colors
with "yellow" selected.

<%@ page import="test.Widget" %>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>

<%
Widget widget = new Widget();
widget.setColor("yellow");
//widget.getColorList() returns Vector {"red", "orange", "yellow"...}
request.setAttribute("widget", widget);
%>

<html:form name="widget" type="test.Widget" scope="request">
<html:select property="color">
<html:options property="colorList"/>
</html:select>
</html:form>

doc/1.0 - HTML:options

[Ted Husted <ne...@husted.com>]

The in documentation for the HTML options tag, we say 

"Only property is specified - The value of this attribute is the name
of a property of the ActionForm bean associated  with our form, which
will return the collection. "

But I haven't been able to get this to work ...

Starting with a bean that worked fine seperately, I also put a copy on
the Action, and tried
 
<form:select property="year">
<form:options property="salesYearsList"/>
</form:select>
// Servlet exception, ClassCast exception
 
<form:select property="year">
<form:options property="salesYearsList.value"/>
</form:select>
//No getter method available for property salesYearsList.value for bean
under name null
 
<form:select property="year">
<form:options property="salesYearsList" labelName="value"
labelProperty="label"/>
</form:select>
// Cannot find bean under name value
 
<form:select property="year">
<form:options property="salesYearsList" name="value"
labelProperty="label"/>
</form:select>
// Cannot find bean under name value
 
<form:select property="year">
<form:options property="salesYearsList" name="value"/>
</form:select>
// Cannot find bean under name value
 
<form:select property="year">
<form:options property="salesYearsList" labelProperty="label"/>
</form:select>
// No getter method available for property label for bean under name
null

Thoughts?

-Ted.

-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/