On 2013-05-31, at 15:46 , Boris Zbarsky <bzbar...@mit.edu> wrote: > On 5/24/13 10:50 AM, Justin Lebar wrote: >> Consider for example how much better harthur's fileit and dashboard >> tools [1] [2] are than bugzilla's built-in equivalents.
Wasn't "fileit" integrated into the New Bug page? That search suggestion drop-down was a relatively recent addition. > > [2] http://harthur.github.io/bugzilla-todos/ > > So I actually tried using the dashboard you link to for the last week. > > It's actually worse at least for my use case than what I do in bugzilla right > now (which is just a saved search for review/feedback requests on me), > because: > > 1) It does not show feedback requests. This may explain why some people are > routinely ignoring them…. Good point. I filed: https://github.com/harthur/bugzilla-todos/issues/19 > 2) It's a lot slower to load than a saved search. With my current request queue it didn't seem that much slower. > 3) If left open (see #2) it does a bunch of JS off timeouts, causing > noticeable jank in my browser. It polls so you can see new requests come in "in real-time". One of the nice features is if you have it in an app tab, the favicon grows a little badge showing you the number of new requests you have. Of course, this requires some round-tripping with the server. > All of which is to say that use cases apparently differ, since I assume for > you the bugzilla-todos dashboard is in fact a lot better. > > Of course I would love something that did what this dashboard does in terms > of showing bugs to check in and whatnot without the drawbacks. ;) Fork and create! ;) I tend to use a mix of bugmotodo and the Bugzilla Dashboard. I find them both useful, though lately I've been using bugmotodo in an app tab and quite like it. As long as I can see review requests in a timely fashion, it's all good. :) ~ rob _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
