[Grok-dev] Re: an application installation script?

Lennart Regebro regebro at gmail.com
Fri Oct 5 05:56:52 EDT 2007


On 10/5/07, Philipp von Weitershausen <philipp at weitershausen.de> wrote:
> * the grok.Application subclass were the root object by default, without
> having to do an extra step (when I start out, there's usually just one
> application anyay).

I usually only have one application too, which is Plone. When I look
around in other parts of the world, you typically have multiple
applications, like a CMS a blog an discussion forum and so on. I see
that as a reasonable use case.

And although I, today, have only one application, I have many
instances of it. I don't see how anyone can develop on a CMS for
example, without having several instances to test stuff and make sure
things make sense in teh userinterface in different cases and such.

> Flexibility is nice, but Grok is all about making
> sensible choices for you, at least in the beginning.

Yes. Assuming that you only want one instance of one application is
not a sensible choice, IMO. Maybe that's what people expect, but I
don't think it's sensible. If they expect this, then maybe we should
just explain to them that it's a much better idea to not to that.

-- 
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64


More information about the Grok-dev mailing list