Re: [Phpwiki-talk] 1.1.7 and re: Catching up

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

 > That said, if you want something in 1.1.7 that isn't there now speak up;
 > otherwise I will release 1.1.7 over the weekend.

No special wishes this time :o)
Maybe Jeff should clear up the ZIP issue first.
As soon as 1.1.7 is out we can start TheBigRefactoringOfPhpWiki.

Because of 1.1.6 I had a look into testing suites for web-applications.
So far I haven't found anything proper. I found tools that check
for links and stuff. But what we'd need is a tool that requests
specific URL's, does POSTs as well, and then checks not only that
a page is returned, but verifies the returned HTML as well (simple
diff or by using regexp rules) Does anyone know of a beast like that?
A more rigorous testing of phpwiki would benefit us all :o)
Maybe I just write a small perl script using wget and netcat.


 > > [...lists...]
 > Yes, but I'm confused. Is there a reason to allow arbitrary mixing?

E.g. you have a list of "10 steps to do this&that"
So you have a numbered list for those steps (level 1).
Point 1 checks if everything is here "* tool x, * tool y, * tool z"
The tools don't have any order - so I'd like to use simple bulleted lists.
Voila - bulleted list inside numbered list.


 > > About /lib vs. /admin:
 > > I think /lib is cleaner and reduces the clutter in the main
 > Hmm. I guess I'm in the minority on this one!

As I said: it isn't urgent. We have more important things to do.
In the long run /lib seems more appropriate.


 > * moving to PATH_INFO. Ari has code we can use. This involves more than
 > you think because we get things like $copy, $edit, $info for free now from
 > PHP and using PATH_INFO means we'll have to roll them by hand;

Shouldn't be too hard.

 > * refactoring the database interface, which will start with the DBM
 > changes and then involve a lot of search/replace of variable names
 > (renaming all instances of $ArchiveDataBase to $ArchiveTable, or something
 > better, for example);

I think this should go into 1.1.8
I'm not sure I'm for a 100% oop approach - I'll give this some more thought.

/Arno