Re: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-13 Thread Steven Noels
On 10 Jun 2005, at 04:07, Mark Leicester wrote: * Newly created pages are invisible until they are published (by someone with publishing rights). It's a little like flying blind. I had to remember document IDs in order to cross-link (unpublished pages don't show up in the link chooser). I

Re: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-13 Thread Steven Noels
On 13 Jun 2005, at 11:18, Linden H van der (MI) wrote: Unpublished versions are only shown to people with write access to these documents. True for the SimpleDocument, but not for the navigation tree. I cannot quickly see changes in the navigation tree unless I publish the latest version. Ah

RE: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-13 Thread Linden H van der (MI)
> Unpublished versions are only shown to people with write access to > these documents. True for the SimpleDocument, but not for the navigation tree. I cannot quickly see changes in the navigation tree unless I publish the latest version. Or am I doing something wrong? Bye, Helma

Re: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-13 Thread Steven Noels
On 10 Jun 2005, at 10:12, Linden H van der (MI) wrote: So what I want is a navigation section that basically displays all documents available (including the unpublished ones). The only problem now is to whom it will be visible. Unpublished versions are only shown to people with write access to

RE: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-10 Thread Linden H van der (MI)
> Another question: how do include anchors within pages? Should I do it > manually with the HTML view? No idea, do check it as I'm not sure it'll pass the HTMLCleaner config. Bye, Helma

Re: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-10 Thread Mark Leicester
One more thing: I just discovered that when I retire a document, the document disappears immediately! Is that right?! I would've expected a publisher to need to approve my retiring of a document first. Mark On 10 Jun 2005, at 17:40, Linden H van der (MI) wrote: Really, you want it so that e

RE: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-10 Thread Linden H van der (MI)
> Really, you want it so that editors and publishers can see it, but > guests can't. Eh, yes, but since publishers 'automagically' get the editors role as well, I mentioned the editors only. > Maybe a switch between published and latest would be good. This exists for a SimpleDocument (but only

Re: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-10 Thread Upayavira
Linden H van der (MI) wrote: Hi Mark, The navigation (and every document for that matter) can include queries. So what I want is a navigation section that basically displays all documents available (including the unpublished ones). The only problem now is to whom it will be visible. Really, you

Re: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-10 Thread Mark Leicester
Hi Helma, On 10 Jun 2005, at 09:12, Linden H van der (MI) wrote: However, I don't think it's a good idea to put this info at the bottom of the wiki page. I'd rather put it on the top like: The content of this page is moved to . Updates to the content will be done there. This page will no longe

RE: [Docs] Refactoring, porting Wiki content, and evaluating Daisy

2005-06-10 Thread Linden H van der (MI)
Hi Mark, Thanks for putting in all the work. I have reviewed the documents, straightened out some layout glitches and put them live. So you should now be able to see your work. > I created a CategoryInDaisy page in the Wiki, so that it is easy to > record a wiki page as having been transferred.