struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abdullah Jibaly" <Abdullah.Jib...@aeroxchange.com>
Subject RE: Themes
Date Tue, 14 Jun 2005 20:12:46 GMT
While Tiles is better for page composition I think you'll find SiteMesh better suited for overall
site layout, especially for things like custom CSS/JavaScript/... based on request or session
level parameters.

-- 
Abdullah

-----Original Message-----
From: Wiebe de Jong [mailto:wiebedj@shaw.ca]
Sent: Tuesday, June 14, 2005 11:48 AM
To: 'Struts Users Mailing List'
Subject: RE: Themes


Use CSS. Use one JSP/tile to get your content together, then based on the
company setting, choose a CSS style sheet to go with it. The style sheet
would contain your graphics, fonts, layouts, etc.

Take a look at http://www.csszengarden.com/ to see the possibilities of this
approach.

Wiebe

-----Original Message-----
From: Martin Ravell [mailto:struts@rave-tech.com.au] 
Sent: Monday, June 13, 2005 5:22 PM
To: Struts User Mailing List
Subject: Themes

I have a requirement to build a 'Themes' (think 'skins') capability into the
UI of my Struts app and would just like to poll the list for ideas on the
best way to approach such a mechanism. Multiple customers use the same app
but they need to be presented with a view that meets their specific
requirements. For example graphics, fonts and even layout would be specific
to the user's login (actually their company/organization which is stored in
the database).

 

Now, for ease of use I guess something relying on CSS would be a way to go.
Since I already use stylesheets for most HTML elements specifying a
particular theme's stylesheet would not be hard. 

 

The tricky part is that I'd also like to be able to specify different jsp
pages (mainly for Tiles layouts) in case I need to modify the layout beyond
what is easy to do with CSS. Ultimately I may well have functionality in the
app itself that is specific to a given customer so this concept should deal
with handling customisation to that level well.

 

Ideally I'd like to have a concept of an 'alternate source' directory that
is used by the app to load it's jsp. i.e. the app first looks under the
appropriate alternate directory for a jsp and uses the page it finds there
if it exists but falls back to the standard jsp dir if there is no
alternate. This would mean that I could create a theme with only those pages
that need to be modified rather than copying and modifying the entire jsp
source tree.

 

If anyone has had to implement something along these lines I'd love to hear
from you. What sort of mechanisms have you found work well within the
structure of a Struts app? My architecture is Struts, Tiles, Spring and
Hibernate if you are interested but I'm thinking that it's the Struts area
that I'll be looking at mostly for this job.

 

Are there any Struts sub-projects that touch on this sort of thing?

 

 

 

Regards

Marty

 

 

 



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
View raw message