[Grok-dev] new grokui.admin issues
uli at gnufix.de
Wed May 19 08:33:50 EDT 2010
Martijn Faassen wrote:
> Wichert Akkerman wrote:
> > Can you make that warning log at a level that isn't normally shown for
> > grok 1.1.1? It's not a terribly important (or useful) warning, so there
> > should not be any harm.
> That's a good idea.
Yep, I also like it.
> It's a useful warning if it actually works (just to encourage not
> leaving dead code around), but it's indeed not very important. I'd be
> willing to do away with this warning at normal warning levels.
> Could you look into this, Uli? I think it requires a new grokcore.view.
> We'd also need a bit of documentation somewhere saying how to turn up
> the warning level in case people are interested in this.
Sure, but I cannot promise to finish that before weekend.
grokui.base 0.2.1 and grokui.admin 0.6.2 are out, BTW. They should not
emit the faulty warnings anymore when grokked. What groktoolkit files do
I have to edit to 'register' the new versions? Just replace the old
version number in groktoolkit/trunk/grok.cfg?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20100519/7d8e1859/attachment.bin
More information about the Grok-dev