[Grok-dev] ApplicationInitializedEvent feedback

[Souheil CHELFOUH]

Hello,

Up to now, Grok doesn't handle anything in the life cycle of an application.
It has handlers for the ObjectAddedEvent, nothing else.
The whole creation process, currently, is left to grokui.admin, which
triggers the ObjectCreatedEvent (the ObjectAddedEvent being fired by
the container, while the application is persisted.)

So yes, in my mind, the event was to be trigged by grokui.admin, as
it's the only tool that handles the creation process. I'm not sure how
we could implement the full process in zope itself. From the top of my
head, i could think of something doing :  def
create_application(factory, container, name): ...

For the documentation, yes, it will be done. i'm currently working on
grokui.{admin,base} and I thought I'd wait to use it to be sure that
there will be no other changes. I was also thinking of adding a
IApplicationUpdatedEvent to deal with the update of utilities/indexes.

The test I wrote for the init event could be used as doc, as it's
quite explicit and detailed. I could copy that with minor changes to
the dev doc.

2009/10/9 Martijn Faassen <faassen at startifact.com>:
> Hi there,
>
> Souheil, thanks very much for working on ApplicationInitializedEvent. A
> few comments:
>
> I don't understand why this event isn't triggered by Grok itself. What
> in your mind would be triggering this event? grokui.admin?
>
> I think Grok should have an API for installing an application that
> grokui.admin and other potential installation tools can use. The
> implementation in Grok *should* send the ApplicationInitializedEvent.
> Grok just shouldn't subscribe to this event itself.
>
> Another point is that at least the reference documentation should be
> updated to talk to this event. I think also the developer's notes.
>
> Regards,
>
> Martijn
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>