See comments in line:

> -----Original Message-----
> From: Jerome Jacobsen [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 23, 2003 11:07 AM
> To: Struts Users Mailing List
> Subject: RE: The <display:*> tag library
>
>
> I think a complete rewrite is needed AND a new API (same tags but
> different
> tag attributes).  Thus I would say an entirely new tag library.  I'll call
> the new version display2 and the current one display1 for clarity below.
>
> - Follow JSTL conventions for attribute names and support JSTL-EL.
> (Actually make use of the JSTL Tag support classes).  This means
> JSP 1.2 is
> baseline.  Assuming JSTL-EL capable attributes allows us to make a simpler
> tag API.  Less attributes are needed.  For example we don't need the
> Struts-like bean-name and bean-property attributes.
+1

>
> - Drop the sorting feature.  The user can provide this functionality by
> making their column names links to actions which resort their list.  Or
> their query form can have order by criteria.  The display1 taglib only
> provides resort of contents in current page which I think is confusing to
> users if there are multiple pages.
+1

>
> - The display2:table tag should work as an IterationTag.  The display1
> doesn't therefore you cannot access a scripting variable for the
> current row
> of the iteration.  You are forced to use Decorators.  This is non-standard
> as per Struts or JSTL.  I vote for removing the Decorator functionality.
+1

>
> - The display2:column should allow optional body content.  If present its
> output is used in the table cell.
+1

> Any thoughts on this?

What do you think of two tag libs:

<pager:*>
<table:*>

The <pager:*> uses the base paging API where the
<table:*> builds on the paging API to incorporate HTML generation
to provide the widget.

I think this would provide a more flexible library for those
developers that want to use the paging functionality but whose
design constraints are not met by the HTML generation functionality.

robert






--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to