I know that we have customized all the various css classes for the display 
of the displaytag in our application. I expect that I won't have to go add 
class attributes to keep the existing functionality, therefore I think 
that the defaults for the class attributes should remain the same as they 
are in the current displaytag, then allow the user the ability to override 
those classes using properties.

John


On Wed, 18 Jun 2003, Fabrizio Giustina wrote:

> in the new version there are few css classes added by default:
> even & odd for the table rows
> sorted, order0 & order1 for the sorted columns.
>  
> Any other class can be added by the user.
> I removed any useless "static" css class, keeping classes only for changing 
> attributes (even and odd rows and dinamically sorted columns are the only two places 
> where this was needed).
> Anyway, I already thought about letting the user customize also these few hardcoded 
> classes: I already put some costant for them, loading initial values from a 
> properties file is a very easy thing to do now... you'll have that implemented 
> before a beta release, I promise ;)
>  
> fabrizio
>  
>  
> 
>       -----Original Message----- 
>       From: Torgeir Veimo [mailto:[EMAIL PROTECTED] 
>       Sent: Wed 6/18/2003 4:15 PM 
>       To: [EMAIL PROTECTED] 
>       Cc: 
>       Subject: RE: omit table tags (was: RE: [displaytag-devel] display09/src -New 
> directory)
>       
>       
> 
>       On Wed, 2003-06-18 at 14:02, Fabrizio Giustina wrote:
>       > 
>       > so you should also be able to not to display headers and not include a
>       > table body... or you want to display two table headers&body in the
>       > same table?
>       > speaking about table meaning in html, doing a such thing only to
>       > define the size of columns is not a good thing. If you want to control
>       > column width (presentation) you should use css.
>       
>       One thing I would like to see is the possibility to set the classnames
>       used for css, instead of the default ones. This is important when using
>       the taglib in a larger webapp.
>       
>       --
>       Torgeir Veimo <[EMAIL PROTECTED]>
>       
>       
>       
>       -------------------------------------------------------
>       This SF.Net email is sponsored by: INetU
>       Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>       Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>       INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>       _______________________________________________
>       displaytag-devel mailing list
>       [EMAIL PROTECTED]
>       https://lists.sourceforge.net/lists/listinfo/displaytag-devel
>       
> 
> 

-- 
John York
Software Engineer
CareerSite Corporation



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel

Reply via email to