[Phpwiki-talk] catching up ...

[Arno H. <aho...@in...>]

Hi there,

I'm back and try to catch up with you guys.

> It might be interesting to do a user survey to find out just
> what environments phpwiki is being run in.
> What do you and Arno deal with?

I'm using a vanilla installation from Suse Linux: Apache+php3+mysql
mySQL is updated to the latest stable version which is 3.22.32


> o Page meta-data (author, version, etc...) is saved in a special custom
>   header field in the zip file.   This information is not accessible via
>   any standard zip tools, but I plan on writing an unzipper which can
>   use this information to restore a Wiki from the zip file.  (The zip file
>   is (should be) still readable using any unzipper.)

Hm, I don't think using special fields within the ZIP is a good idea.
That way, if someone should touch the ZIP for whatever reason, that
data will be lost. I suggest using an extra file, or a meta-file for every
page-file.


> I want to add more DBM files to add the new functionality we've been
> adding, and I will change the way the DBM files are opened... I want to
> set it up so that we only need one call to OpenDataBase(), and we can do

Good idea.

> I added two new markup rules tonight. I want to do away with the use of
> tabs in the markup language since tabs are too difficult to use in Windows
> browsers. Right now we have:
> * one level, ** two levels, *** three levels
> # one, # two, ## one, ## two

I would like to be able to mix those two, e.g.

# one
#* some here
#* more there
#** even more here
#** even more there
#* some there
#*# some there . one
#*# some there . two
# two

Should be quite easy to do, no?
Use a regexp like "^([#*]*)([#*])" - the last char determines the
list type. The size of \1 plus \2 determines the level. If level or
type changes then close current list and issue apropriate HTML tags.

> 2. The line
>     [[Link] produces [Link].
>   gets munged.

Oddly enough I already had fixed this one a while ago.
Apparanetly some changes outside wiki_transform invalidated my fix.


> 3. '''''Bold italic''' and italic''

This is tricky. I suggest to use the new markup instead:
     ''__Bold italic__ and italic''

About /lib vs. /admin:
I think /lib is cleaner and reduces the clutter in the main
directory. But it's not an urgent issue.



When will 1.1.7 be shipped?
Where is Ari's code?

/Arno