[haiku-web] Re: CMS

On 2006-03-22 at 15:36:13 [+0100], Waldemar Kornewald <wkornew@xxxxxxx> wrote:
> > It shouldn't be slow on a single
> 
> Well, I still have a dual-Celeron-466... :)

That might explain it - Python implements global-locking I think so you will 
only get 1 processor doing the work and, of course, the Celeron's castrated 
cache will take a hit. Zope runs fine on my notebook: P-III 833 + 512 MB 
along with PostgreSQL and MySQL.

> Is it bad that Plone does not yet support Zope 3?

No, I don't think so. It's not in the least a problem. Zope 3 has been around 
for two years now and is being back-ported to Zope 2 to make migration 
possible. But Zope 3's programming model appeals more directly to modern 
developers.
 
> Definitely they should be auto-generated from the title. It doesn't
> matter much if it could look a little bit better by specifying the exact
> ID. In most cases the human-chosen and computer-generated ID would be
> the same, anyway. In general, the ID is not very important as long as it
> is readable.

I agree.
 
> No, I don't want to switch within a single page, either. The
> translations may behave like totally distinct websites that use the same
> design. That would suffice. Most pages won't need to be translated, anyway.

This won't be a problem.
 
> We can add that later. For now, a better separation should work, so we
> don't have to answer on forums *and* ML. We could even link to the most
> important mailing lists from within the forums, so people know how to
> contact the developers...

Yes, teach the forum morons how to communicate properly.
 
> >> What do you mean with "the most work"? :)
> > 
> > Development.
> 
> What did you have in mind, exactly?

Any CMS requires developers to do the plumbing. Like single-sign on.
 
> Isn't TALES a template language? You are talking about customizing Zope,
> I guess.

You always have to do some customisation and I'd expect you'd want to be able 
to make new templates for the content. So you'll need to be able to work with 
TALES and some minimal Python statements. But, as I said, you'll essentially 
be insulated from the application itself.
 
> Which low-level stuff do you mean? I'd like to know what has to be done
> in detail.

So would I. Will be able to say more when we have a running system to discuss 
in detail.
 

> ASAP would be nice, of course. :)
> But if, on the long run, Plone/Zope means having a lot of problems
> (performance, limited into Zope space, maintenance, ...) then it is
> better to wait.

I don't know what you mean about "limited into Zope space". I don't see any 
performance problems and maintenance with Zope isn't much of an issue even if 
some of the code base is now 10 years old.

We need a system that matches as much of your feature set as possible, is 
reliable and maintainable and we need people who are both prepared and able 
to develop and maintain it. I don't see any alternatives.

Charlie
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: