[Grok-dev] Grok Application and content initialization

Souheil CHELFOUH trollfot at gmail.com
Thu Oct 1 07:40:59 EDT 2009

As I said previously, the event should be described in grok itself
but, of course, fired in grokui.admin, as the app is added

2009/10/1 Roger Erens <roger.erens at e-s-c.biz>:
> On Thu, Oct 1, 2009 at 11:57, Souheil CHELFOUH <trollfot at gmail.com> wrote:
>> That's not what is going on with the current grokui.admin
>> A generic solution should work with a base grok project, using grokui.admin
>> Well, that's my feeling at least
> I sympathize with you. But such a solution does not seem to be User
> Interface related, so is grokui the right place to have it in?
> Cheers,
> Roger
> ...
>>> On Thu, Oct 1, 2009 at 11:48, Souheil CHELFOUH <trollfot at gmail.com> wrote:
>>>> Yes, ok, but, don't you agree that we need a generic solution ?
>>>> This is a real issue. Having to run things by hand is not a solution
>>>> for me, it's a work around.
>>>> If I distribute a grok project, I'd rather have that automatized to
>>>> avoid telling the user to run the things by hand himself
>>>> 2009/10/1 Sebastian Ware <sebastian at urbantalk.se>:
>>>>> I put my app init code in an init view that I run manually once after
>>>>> creating an app. That way I don't experience this problem.

More information about the Grok-dev mailing list