I'm also not a fan of 'faded lettering behind the page'. At the same time, it would be useful to have some visual cue for the type of content your reading. In my project, the most useful use of this would be to have a clear indication that the wiki page is old or potentially out of date.
I've been looking at using a #pragma time-sensitive # that checks when rendering the page is the page hasn't been edited in over "#" time-periods. The background (or CSS div) would change based on that. This is a visual cue for somebody on the project team to review the content and ensure is it still current. Minimally, they only have to edit the page and add to the comment block ## Review 8/8/2007 by Keith. Another use I've been looking at is to add a div section with such information on it (float box in the lower corner of the box) with information like this is an Orphaned Page, Abandoned Page (not-edited in some time), etc. Anyway, my 2 cents ]<eith "Divide and rule, a sound motto. Unite and lead, a better one." - Goethe >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:moin-user- >[EMAIL PROTECTED] On Behalf Of Roger Haase >Sent: Wednesday, August 08, 2007 8:52 AM >To: [email protected] >Subject: Re: [Moin-user] watermark backgrounds > > >--- Ted Stern <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> Some users want to add a kind of watermark on the page, warning >> readers that all the documentation is proprietary, restricted, or >> some >> other status. For the sake of discussion, let's assume the label is >> "Restricted". >> >> I can think of two possibilities that would work: >> >> 1) add a diagonally repeated "Restricted" in light gray to the >> background of a page, in the same way that "Draft" is currently shown >> during Edit Previews. If it's analogous to Draft, it would scroll >> with the text. >> >> 2)Add a large diagonal transparent (translucent?) "Restricted" to the >> page. It would stay in the same place as the text scrolled. I'm not >> sure how to implement this ... CSS? >> >> Any ideas? Perhaps this could be implemented as some kind of macro >> or >> #pragma. >> >> Ted > >I am not a big fan of watermarks on the screen display because they >make the text harder to read. Monitors are inconsistent, a soft orange >on yours may be hot pink on mine. An alternative is to make use of >page_header1/2 and/or page_footer1/2 in your wikiconfig.py to display >your copyright/proprietary/restricted message and maybe use a watermark > for printed output by tweaking the print.css of your theme. > >Roger > > > >_______________________________________________________________________ ____ >_________ >Park yourself in front of a world of choices in alternative vehicles. Visit >the Yahoo! Auto Green Center. >http://autos.yahoo.com/green_center/ > >----------------------------------------------------------------------- -- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Moin-user mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/moin-user ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Moin-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/moin-user
