<div class="gmail_quote">On Tue, Jul 10, 2012 at 10:51 PM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Jul 10, 2012 at 10:41 PM, Eli Barzilay <<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>> wrote:<br>
><br>
> 10 minutes ago, Robby Findler wrote:<br>
>> It is the future visualizer so I thought it belonged with the<br>
>> visualizer. No?<br>
><br>
> (You mean "... belonged with the futures", right?)<br>
<br>
</div>Right. :)<br>
<div class="im"><br>
>> Alternative suggestions welcome.<br>
><br>
> I think that it fits well with other meta-analysis kind of tools like<br>
> errortrace and the profiler, so a new toplevel collection seems to<br>
> make perfect sense. I don't have a concrete suggestion better than<br>
> "future-visualizer" though since I don't know what it does exactly.<br>
> Maybe "future-debugger" or "future-tracker" or something like that?<br>
<br>
</div>I think we have too many top-level collections and making a new one,<br>
especially with "future-" in the name seems like a step in the wrong<br>
direction.<br>
<br>
("visualizer" is a better word than "debugger" or "tracker" for what<br>
it does, IMO, altho it has elements of those. But if you read the docs<br>
in the Guide about it, you should get some idea what it does.)<br></blockquote><div><br></div><div>Agreed, "debugger" and "tracker" don't really adequately describe it. Maybe "future-profiler" is another option, but maybe confusing since we already have "profiler". (But I still think "visualizer" is best, IMHO).</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Robby<br>
</font></span></blockquote></div><br>