OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] WebHelp display issue


Hi David,

On the other hand, I still think that adding all that color
information is a glitch. As the name implies, positioning.css is
about where<div>s and other things should be positioned, rather
than how they should look like.

Ok, submit a patched version of it that excludes the things that don't
belong. I'll give it a shot. On the one hand we want it to be
configurable, on the other we want it to look ok out of the box. We
could add another css for skinning, but that would be another http
request.

That would basically be the 1.76.1 version with the min-width fix. Please find it attached.

I've thought about this over the weekend, and I'm wondering if the approach I'm taking is the right thing to do. Basically, I've copied over the webhelp/templates directory to a "safe" location. Of course, that copy will eventually go out of sync with the templates folder included in the XSL style sheets, unless I sync over changes manually.

I've done the "fork" for the following reasons:

* The images folder contains a set of images that we (and probably many others) will want to replace with their own, customized, images.

* The jquery folder contains a certain theme, theme-redmond. Again, we will want to customize that by either using a different theme from the jQuery UI gallery, or by rolling our own from http://jqueryui.com/themeroller/.

* We will want to use a different favicon.

* Regarding files in content/search, we're considering using the search improvements made by Peter Desjardins, the most important one being the ability to search for "search strings in quotes", expanding the one-word search that exists by default.

Granted, the last item could be done as a contribution to the XSL style sheets, rather than as a customization, if Peter or I can find the time to extract the changes he made, and provide a patch. But for the rest of the items (images, jQuery theme, favicon), I see no viable way of accomplishing customization other than by "forking" the templates folder, or by "polluting" the original style sheets with customized stuff. Both options don't seem to be optimal.

There's a third option, which would be to make many more things customizable in the webhelp style sheets. Configuration options would include:

* Using a different images folder (with the exact same file names), for example "/custom/path/webhelp/ui-images/".

* Using a different jquery/theme-redmond folder, for example "/custom/path/webhelp/theme-darkside".

* Using a different favicon.ico file (with the same name), for example "/custom/path/webhelp/favicon.ico".

Not sure how viable this would be, though. What do you think?

--
Cheers,

Stefan Hinz <stefan.hinz@oracle.com>, MySQL Documentation Manager

Phone: +49-30-82702940, Fax: +49-30-82702941, http://dev.mysql.com/doc

ORACLE Deutschland B.V.&  Co. KG
Registered Office: Riesstr. 25, 80992 Muenchen, Germany
Commercial Register: Local Court Of Munich, HRA 95603
Managing Director: Jürgen Kunz

General Partner: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Register Of Chamber Of Commerce: Midden-Niederlande, No. 30143697
Managing Directors: Alexander van der Ven, Astrid Kepper, Val Maher
body { font: 12px Verdana, Geneva, sans-serif; }
p, ul, ol, li { font: 10pt Verdana, Geneva, sans-serif; }
h1 { font: bold 15pt Arial, Helvetica, geneva; }
h2 { font: bold 14pt Arial, Helvetica, geneva; }

#header {
    background: white url(../images/header-bg.gif) repeat-x;
    position: fixed;
    width: 100%;
    height: 95px;
    top: 0;
    right: 0;
    bottom: auto;
    left: 0;
    border-bottom: 2px solid #cccccc;
    z-index: 2000;
}

#leftnavigation {
/* background-color:#91e7b3;*/
    overflow: auto;
    position: fixed;
    height: auto;
    top: 90px;
    bottom: 0;
    left: 0;
    width: 280px;
    z-index: 1500;
    border-right:2px solid #CCCCCC;
}

#content {
    position: relative;
    top: 90px; /* left: 240px;*/
    right: auto; /*  bottom: 20px;  */
    margin: 0px 0px 0px 280px;
    width: auto;
    height: inherit;
    padding-left: 5px;
    padding-right: 30px;
    color: #000000;
    /*border-left: 2px solid #cccccc; overflow :scroll;*/
    z-index: 1000;

    max-width: 70em;
    min-width:200px;
}

#navheader {
    position: fixed;
    top: 65px;
    right:4px;
}

#content h1, #content h2 { color: #cc0000; }
.navfooter { bottom: 2%; }
.highlight { background-color: #c5d3c3; }
.highlightButton{ font-size: 0; }

/*  Show Hide TOC tree */
.pointLeft {
    background: url("../images/showHideTreeIcons.png") 0 0 no-repeat;
    height: 28px;
    width: 15px;
    display: block;
    font-size: 0;
    cursor: pointer;
}
.pointRight {
    background: url("../images/showHideTreeIcons.png") -15px 0 no-repeat;
    height: 28px;
    display: block;
    font-size: 0;
    cursor: pointer;
}

/* Search results Styling */
.searchExpression {
    color: #0050A0;
    background-color: #EBEFF8;
    font-size: 12pt;
}
.searchresult li a {
    text-decoration: none;
    color: #0050A0;
}
.searchresult li {
    color: #0050A0;
}
.shortdesclink {
    color: gray;
    font-size: 9pt;
}
.searchText {
    border: #BFCEE9 solid 1pt;
    width: 11em
}
.searchButton {
        margin-left: 3px;
    background: #EBEFF8;
    color: #0050A0;
    border: #BFCEE9 solid 1pt;
    font-weight: bold;
    font-size: 10pt
}

.title, div.toc>p{
        font-weight: bold;
        }       


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]