Hi Ori! Sorry for the long wait in replying.
I'd love to see it. I hope I have time to read it properly. I'm interested
in your comments on PHP's object model too; I have read recently that it's
too immature (after the PHP Kongress in Colonge).
We have an extensive rewrite in OO as well, done by Jeff Dairiki. Have you
seen it? It has all the features (I think) of the 1.1.7 release plus some
improvements.
I've added the task to our Task List on Sourceforge to objectify the
database access. This generally makes things easier for the developer:
packaging data and the functions that operate on that data. But PHP
doesn't seem to offer much more after that.
Couple this with the problem that object systems can be much harder to
understand than procedural ones, and that gives me second thoughts about
introducing OO into PhpWiki.
In a well designed OO system, the classes are loosely coupled, they form
subsystems that are easy to understand, and they are easy to discover and
modify. If we only objectify one interface, we would have to do quite a
bit of surgery on the code (if we stick with the current code base, and I
don't see why not) for what might be little gain.
What would be infinitely better is if we used some kind of generic DB
library, like Perl's DBI/DBD. Then PhpWiki could run on any relational
database, and we would only have to maintain one interface and the various
schemas. If we were really lucky, this library would support flat file and
DBM access as well, but we can wish all day for PHP to be Perl and it's
not going to happen ;-)
cheers
sw
On Wed, 1 Nov 2000, Ori Folger wrote:
> Hi
>
> I have written an OOP based Wiki in PHP a while back, before I knew of
> phpwiki. It's not as feature rich as phpwiki, but I think it's a good start.
>
> Would you be interested in seeing it?
>
> Ori
>
...............................ooo0000ooo.................................
Hear FM quality freeform radio through the Internet: http://wcsb.org/
home page: www.wcsb.org/~swain
|
