At 09:14 AM 4/28/01 +0100, Matt Sergeant wrote:
>On Sat, 28 Apr 2001, Gunther Birznieks wrote:
>
> > As I think I mentioned, it's great that the people like you on this list
> > have a passion for delivering cool software.
> >
>[snipped]
> >
> > People rarely look at toolkits like payment gateways and messaging servers
> > unless there is an application that fits their needs that they can use
> > which happens to use these backend components.
>
>Actually there's an exception to this rule. Look at Zope.
But Zope has an application? -- content management. A template engine is
not an application, but a content management tool built upon templates
surely is?
I thought you would recognize this as you are building something to allow
this on AxKit?
Of course, I guess you could consider AxKit an application because
presumably it comes with scripts to allow aggregration of news content in
RSS format? I consider this a really nice application.
But it's also a bit difficult to tell that this is what AxKit does. You
might consider separating AxKit the engine from AxKit the applications to
allow people to find your site looking for applications (eg news, content
management) so that they want to use AxKit. And then when they want to use
AxKit, they will want to use mod_perl.
