Hi Matt, > To help with this what I'll do is make it easier to subclass a > plugin. This should allow you to fix some functionality in a plugin
> but still benefit from updates to the core plugin. Does that sound > better than the current situation? Absolutely - that's more along the the line I hoped for. > I'm glad you tried it, but if these weaknesses are too much for > your development to handle then you should probably go back to > AxKit1. I'd love to - but Ax1 is becomming more and more of a problem as it requires Apache 1.x. Newer Linux distributions only includes Apache 2.x, and requiring an average user to build Apache and mod_perl by hand is much too much ;-) It's acceptable when it's included with the distribution and can be installed with a few mouseclicks, but by hand? No way... It's also difficult to explain to potential customers why a brand new product is built on top of such ancient software :-( > Note though that AxKit1 is end-of-life now. There will be 1 more > update to AxKit1 (to fix libxml2 support) and that will probably > be it - but lack of updates is more because it is stable, not because > we don't want to fix bugs :-) I absolutely second that! > As Jörg said - please be specific about where the docs are weak as > that can be fixed fairly easily. Presumably more tutorials are > needed, but it's hard to know what people will want tutored on. When I get some more time I'll volunteer to write some docs myself; right now I have a deadline of October 1st to demonstrate as much VDMS as possible - and it will be running on top of AxKit2. Regards, Lars -- Lars Skjærlund Skovengen 111 2980 Kokkedal Denmark Tel.: +45 70 25 88 10 http://www.skjaerlund.dk/lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
