Brick should be changed upstream. Doru
On Tue, Aug 11, 2015 at 9:25 AM, Peter Uhnák <[email protected]> wrote: > Well adding description/caching is trivial. > > The Brick on the other hand may be more complex, and I don't know if Brick > is officially part of Pharo, or is introduced from Glamour and thus should > be fixed upstream. > > Peter > > On Tue, Aug 11, 2015 at 9:16 AM, Torsten Bergmann <[email protected]> wrote: > >> Hi Peter, >> >> Not a bug - more a feature request. I had no time lately to continue >> working on Spotter integration >> for new Catalog Browser. As always we need more resources to work on it. If >> you like open >> an issue for Pharo 5 on FogzBugz and (if possible) help/try to fix it. >> >> Thanks >> T. >> >> *Gesendet:* Dienstag, 11. August 2015 um 08:38 Uhr >> *Von:* "Peter Uhnák" <[email protected]> >> *An:* "Pharo Development List" <[email protected]> >> *Betreff:* Re: [Pharo-dev] GTSpotter on CatalogBrowser >> Should this be reported to FogzBugz or upstream (Moose?)? >> >> On Sat, Aug 8, 2015 at 6:51 PM, Peter Uhnák <[email protected]> wrote: >>> >>> Hi, >>> >>> when previewing CatalogBrowser projects via GTSpotter, there's a lot of >>> empty space in the preview window >>> >>> the result is that the data that I am actually interested in are >>> cropped. >>> >>> Also I think project's description should be available there. >>> >>> >>> And final question: >>> to my knowledge http://catalog.pharo.org/catalog/json is being updated >>> only once a day, so there is not much point of downloading it and parsing >>> it every time single time I open spotter. >>> >>> Also I have to wait after typing something before the projects actually >>> show up. So why not use a time-based cache/singleton? >>> >>> Thanks, >>> Peter >>> >>> >> > -- www.tudorgirba.com "Every thing has its own flow"
