The application creation process now triggers the ApplicationInitiali…

…zedEvent.

This is a quite major change, so I changed the version to 0.7.0. We probably need tests for the event triggering.

CHANGES.txt

@@ -1,10 +1,16 @@
 grokui.admin changes
 ********************
 
-0.6.3 (unreleased)
+0.7.0 (unreleased)
 ==================
 
-* None yet...
+* The ApplicationInitializedEvent newly introduced in Grok is now
+  triggered while an application is created and persisted. This is an
+  important event, allowing to hook handlers that need local utilities
+  and catalog indexes that are not yet present at the
+  ObjectCreatedEvent stage.
+
+* ...
 
 0.6.2 (2010-05-19)
 ==================

setup.py

@@ -14,7 +14,7 @@ def read(*rnames):
     return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
 
 setup(name='grokui.admin',
-      version='0.6.3dev',
+      version='0.7.0dev',
       description="The Grok administration and development UI",
       long_description=(
           read(os.path.join('src', 'grokui', 'admin', 'README.txt')) +

src/grokui/admin/views.py

@@ -74,6 +74,7 @@ def render(self, application, name):
             new_app = app()
             grok.notify(grok.ObjectCreatedEvent(new_app))
             self.context.root[name] = new_app
+            grok.notify(grok.ApplicationInitializedEvent(new_app))
             self.flash(u'Added %s `%s`.' % (application, name))
         except (DuplicationError, KeyError):
             self.flash(u'Name `%s` already in use. '