Re: Page preview can now be implemented rather easy

> So I think preview needs to:
> - display all body content, including any [[include: text
> - list any directives (noheader, nogroupheader, etc) perhaps as an unordered 
> list
> - make it obvious that it's a preview (the script I made puts "Edit 
> Group.Page" or "Preview Group.Page" as an <h1>)

Does your preview appear in the same window as the edit box, or is
it appearing in a separate window?

-- same window, I put out a title, then the preview, then the edit box; one of 
the reasons for omitting things like headers and footers is screen real estate 
(I tested it on a 12 inch laptop screen)

Unfortunately the "include / not include" rules are starting to sound
real ad-hocish to me.  I'm not sure I can explain it all clearly to
someone who isn't familiar with the details.  ("Well, include: directives 
are handled in a preview, but GroupHeaders are not even though they are 
normally handled after include: directives when browsed, and any WikiStyle
definitions you put in a GroupHeader won't show up in your preview,
but they will if you referenced them via an include:, and ... ")

Pm

-- I think of the page like this:
header
group header
body and includes
group footer
footer

My starting point was that a preview should show the body with its includes and 
everything else is optional. However, your point about user defined styles in 
the group header is well taken. But then why make visible the effects of some 
directives (eg [[nogroupheader]]) but not others (eg [[noheader]]). But if you 
show everything, then screen real estate becomes problematic.

What about a page layout that's landscape, instead of portrait, eg:

Edit view here                 Preview view here

the buttons                    the headers

the edit box                   the body

the edit quick reference       the footers

a jump to the right link       a back to left top link

Just an idea... JR