2011/9/23 Mariano Martinez Peck <marianopeck@gmail.com>
grrr shorcuts.. then I found AutomaticMethodCategorizerApplier which I don't care. And I don't care if I need to close and open again the TestRunner.
So....what I mean is that class creation notification increases Fuel classes materialization like 50%. Do you think this is un-important enough to provide a way to NOT notify? I mean, should I provide a way to avoid that and avoid the 50% ? or it will be totally unsafe?
I have no idea how notification works. I imagine that every class creation is notified. Perhaps it could be faster to notify only time that multiple classes have created. of course it requires a way to create classes without notifying. just an idea, Luc
Thanks!
On Fri, Sep 23, 2011 at 7:52 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Hi guys. I was checking who needs to be notified when a class is created. If I follow correctly senders of #notify:ofSystemChangesOfItem:change:using: and friends, I don't really find too many listeners. I found TestRunner >> initialize and MCPackageManager
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com