"css freedom!"

liberate this page!

watch this humble page change before your very eyes!

contains:

1-"notebook" prototheme; 1-control bar, minimally functional; 1-content area, internal, scrolling; 1-gratuitous waterstamp. (if you tweek the styles/divs, remember to substitute ` for " characters, and no blank lines.)

"oh no! it's... alive!"

what it is.

"total chaos!"

imagine the possibilities...

each page can override just the aspects of it's appearance that it want's to tweek. arbitrarily position panes of additional content: artistic &/or functional.

combine with a modular wikipage.pt (like WikipageX using metal macros) to create plug-and-play customized WikiPage?'s, and start having too much fun!

"beware!"

a horrible hack

if the general concept here is useful, a cleaner implementation would add logic somewhere to scan for leading &/or trailing <style> and <div> sections and copy them directly to the right places in the generated html.

"nsesnone"

just look at this nice page fill... urm... list formatting

Lorem Ipsum Dolor Omniservum

"zzzz..."

ps-

ymmv

developed using windoze mozilla 1.4
not as pretty, but seems to function tolerably well w/ ie5.5
lorem ipsum dolor sit amet,

consectetaur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

comments

requested... ...tia!


comments:

note --simon, Sat, 08 Nov 2003 13:09:58 -0800 reply
Choose the wikipagex skin in UserOptions? to enable this feature.

feedback --simon, Sat, 08 Nov 2003 19:14:58 -0800 reply
Fun!

People can quickly see this at http://zwiki.org/PerPageStylesHack?skin=wikipagex .

It creates a scrollbar in my main mozilla window, which isn't so pretty.

We briefly had the site stylesheet coming from a wiki page; it extracted the relevant part of the page text in TAL, something like:

 <style tal:content= 
   "python:here.text()[ 
       here.text().find( '<!--beginstyle-->' )
     : here.text().find( '<!--endstyle-->' ) 
     ]" />

At one point it did actually invoke the page ("here(REQUEST=request)" ?) so DTML could be used for cool time-varying effects. This trick of passing information via REQUEST.set is another way to do that, and now it's per-page - perfect for prototyping. :) I don't see this as a must for the default skin due to the security/surprise factor.. but let's see what it leads to.

feedback --dan mcmullen, Sun, 09 Nov 2003 07:04:24 -0800 reply
simon wrote:

> It creates a scrollbar in my main mozilla window, which isn't so
pretty.<<<

true. this is a trade off for the benefit of having a control/search bar at a non-scrolling, predictable position. anyone know a better way?

feedback --dan mcmullen, Sun, 09 Nov 2003 17:13:42 -0800 reply
simon wrote:

> It creates a scrollbar in my main mozilla window, which isn't so
pretty.<<<

ps- originally, the scrolling area in this page was as wide as the window, so the scrollbar was more or less in it's usual position at the right. that's easy to undo. making the content area narrower is an experiment in using text column width to avoid overloading a user with too much text on the screen.

also, the scrollbar goes away if the content fits in the window.

another approach is to get creative with user interface. here's an interesting placement of the scrollbar, plus some bells and whistles. it only works in minimal mode until i get the updated WikipageX done:

PerPageStylesHack2

(aka- http://zwiki.org/PerPageStylesHack2?skin=wikipagex)

feedback --Samotnik, Tue, 11 Nov 2003 17:32:15 -0800 reply
Ha! Funny, esp. this little organization :).

However, in this v. 2.0 three tiny red lines cover right words of bottom blue menu (in my Mozilla 1.5)

feedback --dan mcmullen, Tue, 11 Nov 2003 17:55:56 -0800 reply
Samotnik wrote:

However, in this v. 2.0 three tiny red lines cover right words of
bottom blue menu (in my Mozilla 1.5)<<<

thanks. i have not upgraded to moz v1.5 yet from v1.4. will do that & check this out.

if you see this, would you try the latest v2:

PerPageStylesHack2

the menus at the bottom should be brownish now. do the red decoration lines still cover the bottom menus?

tia, dan

feedback --Samotnik, Tue, 11 Nov 2003 18:02:47 -0800 reply
Unfortunately, the bottom menu inside the window is not visible now.

feedback --Samotnik, Tue, 11 Nov 2003 18:04:51 -0800 reply
Last line visible is:

(*The Kindness Of Your Feedback Is Requested)

Below the window only the line top comments bottom · full simple minimal · edit · and small window is visible

feedback --Samotnik, Tue, 11 Nov 2003 18:08:21 -0800 reply
Oh, yes, maybe misunderstud (?). In my first feedback I meant the blue menu INSIDE the window.

feedback --dan mcmullen, Tue, 11 Nov 2003 18:16:12 -0800 reply
Samotnik wrote: >>>Last line visible is: (*The Kindness Of Your Feedback Is Requested)

Below the window only the line top comments bottom full simple minimal edit and small window is visible<<<

that sounds kind of right. there isn't a comment box in simple mode, which the fancy link i email puts you into temporarily. the quick links to home/etc are now at the bottom of the right hand column in a smaller font.

or, do you mean that the line "top comments ..." isn't showing completely ? that would be a problem. the bottom line is supposed to have about 5% of the screen height. is that what it looks like to you?

what operating system do you use mozilla 1.5 with?

any other interesting things about your setup? window/font sizes? anything?

tia, dan

comment/rename/reparent oddities --DanMcmullen, Tue, 11 Nov 2003 18:32:08 -0800 reply
as Samotnik has discovered, there are some odd bits in the way the comment and rename/reparent forms display when they are inside the scrolling content area at the end. a better approach, which will be used in any real skins, is to put comment/rename/reparent in their own section below the scrolling text. the formatting glitches won't bite so bad, and it will let you scroll about the content while composing a comment. (oooh!) :-)

these are still, alas, only prototype skins. :-P

comment/rename/reparent oddities --Samotnik, Wed, 12 Nov 2003 03:04:06 -0800 reply
Excuse me I went out, it was 3:08 AM here :).

You're right. Such things as comment, rename etc are more convenient if palced below the scrolling window. In fact, the section takes some 5% of screen. In my case it is about 1 cm. However, I have two remarks more.

My new notebook has 1024 by 768 px resolution on rather big screen (17''? - Toshiba Satellite Pro 4200), 75 Hz. WYSIWYG, so the fonts of this page are displayed as 12 points. Win 2000.

comment/rename/reparent oddities --Simon Michael, Fri, 14 Nov 2003 16:18:20 -0800 reply

for average user. I still don't know what are placeholder and upgarde all for. Things MUST be kept sipmple!

Agreed, but -

Does this help ?

comment/rename/reparent oddities --Samotnik, Sat, 15 Nov 2003 07:38:42 -0800 reply
Sorry, I didn't check what's going on in simple mode.

Of course, the concept is correct that average user has simple tools to use, and more advanced options are for heavy user and in the cases of heavy work.

Mouse-over help is enough, hovewer it doesn't work for "placeholders" and "update all". As far as I remember, there is any way to implement that in non-link words, at least in XHTML.

comment/rename/reparent oddities --Simon Michael, Sat, 15 Nov 2003 12:32:40 -0800 reply

Mouse-over help is enough, hovewer it doesn't work for "placeholders" and "update all". As far as I remember, there is any way to implement

Oh dear. For reference, what browser are you using ? These and the other tooltips work in mozilla.

comment/rename/reparent oddities --dan mcmullen, Sat, 15 Nov 2003 12:41:36 -0800 reply
Simon Michael wrote: >>>

Mouse-over help is enough, hovewer it doesn't work for
"placeholders" and "update all". As far as I remember, there is any way to implement<<<
Oh dear. For reference, what browser are you using ? These and the other tooltips work in mozilla.

actually, i think the problem may be that the mouse over is only active over the actual check boxes, and not over the label text. Samotnik: try putting the mouse cursor exactly on top of a check box. does that work?

i'm guessing the checkbox label needs to be independant of the checkbox so the font can be changed. Simon: it's probably possible to put the checkbox label text inside an "href-less" A tag with a title so it shows the mouse-over text.

comment/rename/reparent oddities --dan mcmullen, Sat, 15 Nov 2003 13:22:49 -0800 reply
i wrote:>>>

i'm guessing the checkbox label needs to be independant of the checkbox so the font can be changed.<<<

scratch that. (crossed wire somewhere.)

Simon: it's probably possible to
put the checkbox label text inside an "href-less" A tag with a title so it shows the mouse-over text.<<<

like so:

 <a title="when renaming, replace references... Caution!"
   style="text-decoration: inherit; color: inherit; font: inherit;"
   >update all</a>

comment/rename/reparent oddities --Simon Michael, Sat, 15 Nov 2003 15:02:37 -0800 reply
Sorry Dan, we are way off-topic on your page.. but to continue a little longer..

good trick with the a tag. However I am leaning towards Samotnik's original point of view - I tend to agree they don't carry their weight in the page management panel and should be removed. Disabling these options is something you need only rarely, and can be accomplished via the ZMI or entering a url manually.

comment/rename/reparent oddities --dan mcmullen, Sat, 15 Nov 2003 15:17:29 -0800 reply
Simon Michael wrote:>>>

...I tend to agree they don't carry their weight in the page management panel and should be removed. Disabling these options is something you need only rarely, and can be accomplished via the ZMI or entering a url manually.

i agree for update links. however, leaving a placeholder is something i rarely do. it would be tedious to almost always need to delete the placeholder after renaming. leaving a placeholder is an easier concept than updating links. is it clear enough to leave in the ui?