[Grok-dev] Re: grok futures: the return of the ZMI
wichert at wiggy.net
Tue Jan 8 03:03:39 EST 2008
Previously Martijn Faassen wrote:
> Paul Everitt wrote:
> >Thus, a new ZMI wouldn't have to do TTW *development*. We could leave
> >out restricted Python. We could even leave out ZPT. In fact, we could
> >freaking leave out the browser. Instead, it would be about
> >pointy-clicky model specification.
> What you describe is a slightly different area then the one I'd like to
> tackle with the ZPT step (though the model step is related). Allowing
> ZPT overrides indeed opens up the danger of untrusted people going in
> and breaking things. I hope that can be mitigated by allowing good
> export facilities to the filesystem-style of development.
> Also whatever it was worth, people *did* use the ZMI for TTW
> development, and it was very popular for a while until the drawbacks
> became clear. There's just about nothing that beats "Hello world" in the
> Zope 2 ZMI in speed of development.
There is a very important use case for Plone that may be just as
important for grok: being able to quickly make changes that are
immediately visible without any access to the filesystem or needing an
application restart. This is extremely useful when you get a support
call from a customer and you need to make a change without being
able to have access to the server. In my experience that is a common
scenario. Another useful benefit is being able to very quickly test
small changes (most often layout tweaks).
Wichert Akkerman <wichert at wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
More information about the Grok-dev