[webdev] Re: State of Website
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
> -----Original Message-----
> From: webdev-bounce@xxxxxxxxx [mailto:webdev-bounce@xxxxxxxxx]On Behalf
> Of thull2@xxxxxxx
> > And not to re-open an old can of worms... but why was
> > Zope chosen against?
>
> I was looking to do tool development, and I didn't like
> Zope's architecture and development model. If someone
> wants to champion Zope, please state your case.
>
> > And are there any other new-on-the-scene packages
> > that would be worth considering?
>
> I'm working on one, but it isn't anywhere near ready.
> It will be apache-php-postgresql based. I'm looking at
> dozens of packages, but mostly for ideas and plunder.
There is one other thing to add to the discussion about PostNuke. There exists
in beta a data bridge that allows other PHP based tools to be imbedded into
PostNuke. The bridge is actually in use at http://developers.postnuke.com ,
though it has not been released yet for general use. It looks promising in
being able to leverage other developed products by unifying the user space
(login, user prefs, etc). Hopefully this tool will be released soon and may
allow us more freedom to do the thing Tom has been looking into.
The one good thing that has come out of the PostNuke meltdown is that the new
deveopment team doesn't suffer from the "it wasn't invented here" syndrome.
They understand that it not neccessary to "reinvent the wheel" at every turn,
and are working to make it easy to integrate outside tools in a way that is
flexiable enough to adapt to changes in the foreign code without requiring a
major rewrite with every change.
It looks promising.
--dwh
---
Dale W Hodge - dwh@xxxxxxxxxxxxxxxx
Vice Chairman & Secretary - info@xxxxxxxxx
Air Capital Linux User's Group (ACLUG)
---
|
|