grrr shorcuts.. then I found AutomaticMethodCategorizerApplier which I don&#39;t care. <br>And I don&#39;t care if I need to close and open again the TestRunner.<br><br>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?� <br>
<br>Thanks!<br><br><br><br><br><div class="gmail_quote">On Fri, Sep 23, 2011 at 7:52 PM, Mariano Martinez Peck <span dir="ltr">&lt;<a href="mailto:marianopeck@gmail.com">marianopeck@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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&#39;t really find too many listeners. I found TestRunner &gt;&gt; initialize and MCPackageManager <br>
<font color="#888888">
<br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>