<<snip>>

> >  1. I use Computer Age on Squeak 2.6 under Linux and WinNt.
> >     Nestcape cannot load properly all the taskbar image
> >     (edit/lock/unlock etc) but when I force the single image-load
> >     button all works fine. Scamper works.
> >     What is the problem? How can I fix it? Must I try the Squeak 2.7
> >     Image??!?!

This SOUNDS like the broken-network-primative problem, except that it
shouldn't happen when running under Linux (i.e. when running Comanche from a
Squeak image on a Linux box). If you're running Comanche on the WinNT box,
upgrade to Squeak 2.7 and BE SURE TO USE THE LATEST VERSION OF THE 2.7 VM
(Build 8 or later).

> >  2. Can I have a log of the server usage? Which file I must look for?
> >     Can I get some printed info in the Transcript?

In your Swiki's directory, make a subdirectory named 'logs' (i.e. at the
saem level as you'r Swiki's pages and uploads directories). Log files will
magically appear there.

> >  3. About the PWS--> Computer Age converter: where can I get a preview
> >     (beta are wellcome!!)???

Bolot passed out a copy of his conversion utility on this mailing list a
couple of weeks ago. You could ask him nicely, or better yet I'll just
e-mail you a copy.

> >  4. How can I rename a page?

Edit the page. The edit form has two fields: one for the page's name, and
another for its text; change the page's name by entering a new one into the
name field. When you save the change, all links (on other pages) will be
automatically updated to reflect the new name. (Well, not ALL links, just
*pagename* links, not HTML <a href="pagename"> links.)

> >  5. The XML used in the pages is "standard"? Or I must look for a
> >     special documentation?

Can't help you much there. Je77 and Bolot have promised full documentation
eventually (remember, this is all still beta). However, try looking at a
typical ComSwiki page e.g. the prototype 1.xml that you use to start a brand
new Swiki. There's a tag containing page-version information, a pair of tags
(<name></name>) containing the page's current name and another pair
containing its current text, and a pair containing settings. This last
(<settings></settings>) is empty on most pages, but can contain
page-specific stuff such as:

1. whether the page is locked, and if so, what the password is

2. page-specific color schemes

3. page-specific templates, reference caches, etc.

HTH

Lawrence Press



Reply via email to