CSS Style sheets

Hi All

I have just started in web development in the domino environment. Could anyone point me in the right direction on how to use style sheets. What I woud like is a page that is split up into 4 sections, a header section, a footer section, a body section and a menu section. I want the body section to chnge depending on what menu is selected. I dont want to use frames to do this.

Regrads

Djbell

Subject: CSS Style sheets

This can get your started:

http://www.dominoguru.com/dominoguru/home.nsf/0/18df61fe909e0cc985256dc70070fdac

This will show you some of the basics of getting started.

For your menues, header, footer, etc I would use Computed Subforms on a $$NavigatorTemplate for index.html/blank navigator combination as well as on a Display form so you can have your content as documents - therein you can search your web app for content!

Lemme know if I can help,

-Chris

Subject: Try a page…

Hi,

you can put the css-definitions on a page (Properties: HTML for Web !) and save it e.g. as “MyDefinition.css”.

To use this stylesheet put the following code in the HTML Head Content of the form:

“<link rel=stylesheet type="text/css" ref="/” + @ReplaceSubstring(@Subset(@DbName;-1);“\”;“/”) + “/MyDefinition.css">”

Subject: CSS Cascading Style sheets

Doug,

We don’t have all those sections you describe (we just have a header with pulldown menu options and a body) but we make heavy use of style sheets and a lot of logic to avoid hardcoding.

The way we do it is to stick the style sheets code into shared fields that reside in a separate shared code database. We then insert the style sheet shared fields at the top of each web form, with the setting to hide the fields from Notes users and web browsers. It is in the HTML Head Content where we reference the fields, one + another so that later code can set the class= parameter to select a style.

Since our header/menu has to appear on every page (we too do not use frames), we have the code that makes up the header reside in shared fields as well, and these we do NOT hide from users.

I was told by the designer of this application that subforms caused problems, and/or loaded too slowly, so we don’t use subforms at all. However, contrary to popular belief, shared fields do not bog down performance of a web app, so we use them quite a lot. We don’t even hardcode (on every web page) the path to a database, we use a shared field for that.

Good luck,

Ken