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

[Steve W. <sw...@wc...>]

On Sat, 15 Jul 2000, Arno Hollosi wrote:

> 
>  > That said, if you want something in 1.1.7 that isn't there now speak up;
> Maybe Jeff should clear up the ZIP issue first.
> As soon as 1.1.7 is out we can start TheBigRefactoringOfPhpWiki.

I've tried it and it works... you get a dump of all existing pages, sans
metadata, plus the other dumping features work reasonbly well (for beta
release), but I'll wait until tomorrow to see if Jeff wants to add
something more. (Or soonder if you reply now, Jeff! :-)

> A more rigorous testing of phpwiki would benefit us all :o)
> Maybe I just write a small perl script using wget and netcat.

Yeah, testing is always an issue. I don't know of anything that does what
we need, haven't looked though.
 
> 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.

What came to mind, reading your example, is that it's easy to switch back
and forth between UL and OL while editing (that is, if the user changes
their mind). 
For your example it would suffice to do:

# point one
** item one
** item two
[...]
**item ten
# point two
# point three
[...]
# point ten

But I'm splitting hairs here... it's just as simple to do mixed [#*]
anyway, and we're in agreement. Whether my example works is an issue of
testing :-)

> I'm not sure I'm for a 100% oop approach - I'll give this some more thought.

When I set out in December, I decided on a non-OOP approach at the time
because I didn't fully understand the Wiki problem yet. I read once that
you don't really understand a probem until you've solved it once, and I
would like to think I've solved it now... 

There have been times in the last few months where I found myself wanting
a DB object and a page object, because objects are easier to work with
than a data structure and function library (sometimes).

OTOH, good OO design is *hard*. I've had to work with some really *bad* OO
designs (in Perl, at the NYT) and it can be a total nightmare. This is the
single most compelling counterargument I have: PhpWiki is a scripted Web
application that is completely procedural in design, fairly small, and
easy to maintain. For a lot of users, webmasters, sysadmins, and
programmers that means it's easy to tinker with. Not a lot of people know
OOP and OOD.

I think I am definitely in favor of a DB class, somewhat in favor of a
page class, and I'm not sure about anything more after that. I'd like to
see some proposed classes and we can discuss it. (I wonder if we can model
the classes in the Wiki?)

sw

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain