[Nitro] [PATCH] Og patches

[Judson Lester]

On some level, though, I'd like to see some reminder of the step, because I
know I'll forget in 6 months when I take my next Og project to production.

A link to an article that discusses all the pitfalls, maybe?

More ambitiously, catch the errors caused by a missing class management and
reference the same article?

Judson

On 5/8/07, Jonathan Buch <john at oxyliquit.de> wrote:
>
> Hi,
>
> > Is it worth emitting a warning or something with the current detected
> > version of that line?
> >
> > So, if you perform some version of "Og.manager.manage_classes()" it
> > emits a warning like:
> >
> > INFO: for more speed, consider "Og.manager_options.update(:classes =>
> > [Some, More, OgClasses])"
>
> no, this is a good idea but I think it should remain a 'optimization',
> as it can cause very misleading error messages and backtraces.
> When you forget a single class, things break havoc.  A newbie might
> think 'oooh, speed, good, let's use it', but doesn't consider the
> 'side effects'.
>
> Jo
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
Q: How does a hacker escape handcuffs?
A: Backslashes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070508/7860985c/attachment.html