On 2008-10-23 20:57+0200 Werner Smekal wrote:
> The easiest would be to change the colors only a bit, let's say e.g. #menubar
> ul background color is the same as A hover/link/visited/... (#ff6600). So
> let's set the background color for #menubar ul to #ff6601 and they are not
> the same anymore, but the users eye won't see any difference and we don't
> have to look for new colors which fit well. Warnings are also gone
> We could also change the color for visited links, e.g. to a darker orange or
> something like that if you wish.
>> BTW, I could not find our present colour scheme at the DesignsByDarren.com
>> site. Did you grab it from another site?
> It's actually from http://www.oswd.org and the theme is called fruitopia:
> http://www.oswd.org/design/preview/id/3181 or
> http://www.oswd.org/files/designs/3181/Fruitopia/ .
Thanks for those comments/ideas.
Here is the current status:
I have now changed over to configuring style_liquid.css and style_static.css
from one common file, style.css.in. So far, I have only done the
dimensional configuration, and not the colour one, but the idea works well.
Configuring the colours should work well also; relatively few CMake
variables are needed to describe our website colours since they are done
with a consistent colour scheme that repeats colour data often for various
CSS contexts. Also, I will use separate variables when the consistency is
too much (as in the background colour warnings we are getting). When I am
done with this it should be possible to easily adjust our colour scheme by
changing a relatively small number of CMake variables.
I am also in the process of replacing the simple www/Makefile and
www/announce/Makefile with a CMake-based approach because the latter handles
access to the build tree (where all the configured files now reside) simply
The current status of www/announce is the CMake-based build system now
validates the DocBook source for our historical release announcements and
also builds html and text versions that agree with what the old
www/announce/Makefile produced. I am working on putting together CMake
custom rules for uploading our base website similar to what www/Makefile
does now. That upload contains all our historical formal release
announcements now, and I am assuming in the future it will include future
formal release announcements as well (see <aside> below).
<aside> I must say, it should be incredibly easy to do formal announcements
of future releases the way they have been done historically. Currently our
website only points to detailed release notes (the README.release file that
Hazen uploads to SF as part of the release). Those notes certainly have
their place, but I also think there is a place for a short formal release
announcements as well on our website like we used to do until the process
stopped when Tom Duck took over from Rafael as the release manager. I have
put some notes into www/announce/README about what would need to happen if
we decide to make a formal release announcement for the next release.
Anyhow, Hazen this is something to think about.</aside>
I am keeping scripts/generate_website.sh up to date as I change things
around. Thus, once I am completely finished with my changes, the release
manager's task of updating the website will remain the same which is simply
to run the script.
In sum, there are still some fairly trivial bits of updating our website
that still need changes and testing, but by the end of this weekend I hope
to be done with everything affecting our website update procedure.
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project