[Grok-dev] grokui.admin 0.1.1 released
Peter Bengtsson
peter at fry-it.com
Wed Aug 6 08:05:40 EDT 2008
>
> * Move all to `++grokadmin++`
>
> Next step is to move all functionality into an own URL namespace
> like `++grokadmin++`.
>
+1
> * Bind rootfolder
>
> There _will_ however, stay a view bound to the rootfolder, that
> offers the same (or a similar) intro screen as now. There are some
> pros and cons about this behaviour, but I think it is important for
> starters with grok to have something they can play around with.
>
> You can, of course, define your own view for the rootfolder and
> override the one defined by 'grokui.admin' in your own projects.
>
> Another option would be to move everything in an own URL namespace
> and people had to enter `localhost:8080/++grokadmin++/ to get the
> intro screen.
>
+1
Keep it. It's a nice start for beginners. Having to RTFM to get the
admin interface is a no-no.
> * Remove `documentation`
>
> As soon as grokui.introspector is in a nice shape, the whole docgrok
> thing ('documentation' in the menu), will be removed from
> `grokui.admin` and you then have to require the introspector package
> explicitly in `setup.py`.
>
> * Add `grokui.admin` to grokproject
>
> I would like to add `grokui.admin` to the requirements of new
> grokprojects, so that they will have an admin-UI by default.
>
> Developers could remove that from their projects if they want.
>
> This would mean some minor changes in `grokproject`.
>
+1
> What do you think?
>
> Best regards,
>
> --
> Uli
>
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
>
>
--
Peter Bengtsson,
work www.fry-it.com
home www.peterbe.com
hobby www.issuetrackerproduct.com
More information about the Grok-dev
mailing list