• Browse Blogs
  • My Blog
  • My Updates

+Tags Get help with tags?

  • View as cloud  | list

+ Similar Entries

photo

OpenNTF shows PRODUC...

Blog:  Erik Brooks
Erik Brooks
Updated 
No RatingsRatings 0     CommentsComments 1
photo

2009 - The Year of X...

Blog:  Beyond The Ye...
Peter Presnell
Updated 
No RatingsRatings 0     CommentsComments 1
photo

Are You A Legend (Ye...

Blog:  Beyond The Ye...
Peter Presnell
Updated 
No RatingsRatings 0     No CommentsComments 0
photo

Preview: Discussion ...

Blog:  Beyond The Ye...
Peter Presnell
Updated 
No RatingsRatings 0     CommentsComments 2
photo

OpenNTF - free hosti...

Blog:  TexasSwede
Karl-Henry Martinsso...
Updated 
No RatingsRatings 0     CommentsComments 1

+ Blog Authors  

OpenNTF Thoughts - Part 4 - XPages Theme Manager

Bruce Currier |   | Tags:  openntf | Comments (2)  |  Visits (636)
   Hopefully this will be a little safer topic then my last two posts.  I was thinking that with the advent of XPages, all kinds of new and exciting applications are going to either be created and/or updated on OpenNTF.  I'm am currently playing with TaskJam, XPages Phonebook, & XPages Wiki on a test V8.5 server.  I'm loving what can be done with them and how they look.

   However, there is one issue I would have with moving them into my production environment (once I had a production V8.5 server that is).  The current design of all three applications (at least it looks likes it to me) is based on them being standalone websites (like IdeaJam.net is).  I would like to have some common branding across all of my internal website (which is currently Domino-based, although the code is atrocious V6 0, I hacked alot of it together so I should know - lol).  If we had some kind of central Theme Manager Application that could hold "global" css and images resources that other applications could reference it would be easier to make everything look like it was all part of the same website.

   I was thinking this would be done in similiar fashion to how a number of OpenNTF applications are now coming with the ability in the configuration of the application to choose wether to use the OpenLog application for all logging functions.  I know this would be more difficult because the application would have to be designed so it could either run as a standalone website or as part of a whole enterprise-wide website.

   I think I'll leave this idea for now and come back later with some thoughts on what the Theme Manager application would need to do.

UPDATE
My other related posts on this subject
Part 1 - Background
Part 2 - Signing Applications
Part 3 - Replicating Templates


No RatingsRatings 0

Comments (2)

photo
1 Jo Grant commented   Permalink No RatingsRatings 0

I've got an article in the works on how to share custom controls across applications. It might have some applications here.

photo
2 Declan Lynch commented   Permalink No RatingsRatings 0

Themes are nice but at the end of the day they need two things, css and class names in the html markup.

For a theme repository you would need to ensure that all apps use the same class names in their markup so that you can apply different themes.

While I think it's a great idea i just can't see it working very well because all your apps will need the same layout etc.

The oneUI layout from IBM is very nice but it's not suitable where I work, We have built our own companyUI and setup guidlines for the html markup so that the same css can be applied across all our new xpage apps but that markup would be probably useless outside of the company and therefore our css would be useless in a theme repository.

I do think, however, that for certain apps on OpenNTF the oneUI should be used where possible as it gives the downloader an instantly nice looking application. Then if they want to deviate away they can do it on their own.

Add a Comment Add a Comment

Previous |  Main  | Next
Skip to main content link. Accesskey S
IBM Lotus Connections Help Tools About