Hi,
maybe you already noticed. The latest update for Pharo 5 which is 50103 (see [1]). includes a new tool called "Catalog Browser". Where to go =========== You will find it under "Tools" -> "Catalog Browser" and it will display the configs together with the catalog metadata like project description. The code is managed with a configuration similar to what we have for a few other packages/projects. The tool was written by Esteban Lorenzano with small improvements like spotter integration from my side. Feel free to contribute more features. The repository can be found on SmalltalkHub [2]. This new tool basically gives you access to all available configurations aggregated at [3]. You can use a small UI to search and load the configs (see world menu -> "Tools" -> "Catalog Browser". But you can also use Spotter to load a config. Example on how to load ScriptManager config: ============================================ - open Spotter (SHIFT + ENTER on Windows, ...) - type in "Script" and you will find a spotter category "Catalog Projects" with "ScriptManager" in it - just hit enter and the config is loaded Same for all others, so try with "Seaside", "MongoTalk", ... In the short/mid-term this new tool should replace the existing config browser as it gives more informations about the projects. What to do next: ================ - give feedback - we should update all our configs with catalog descriptions - it would be nice if the spotter integration would include also a preview of the project description - ... If you want to contribute just tell Esteban so he can add you to the project. Thanks Esteban & Torsten [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-June/110964.html [2] http://www.smalltalkhub.com/#!/~estebanlm/CatalogBrowser [3] http://catalog.pharo.org/catalog/json catalogBrowser.png (67K) Download Attachment |
Really cool! About the spotter integration, it is really nice to be able to search and find new projects like this. Well done. But, there are two things that I would change: - Right now, the processor order is 10. If you search for GTSpotter, you will get the catalog project before the class: I would rather prefer the order to be next to the Metacello configurations, so I would make it 90. The reason is that the things that are in the image should take precedence because they are much more often used. - For the preview, I would put the details that we have about the project. - Also, if you are at it, it would be nice to add an inspector extension for showing all projects of a CatalogProvider and to add a load action for a CatalogProject object :) Cheers, Doru On Thu, Jun 11, 2015 at 8:55 AM, Torsten Bergmann <[hidden email]> wrote: Hi, |
In reply to this post by Torsten Bergmann
Hi,
> On 11 Jun 2015, at 08:55, Torsten Bergmann <[hidden email]> wrote: > > Hi, > > maybe you already noticed. The latest update for Pharo 5 which is 50103 (see [1]). > includes a new tool called "Catalog Browser". > > Where to go > =========== > > You will find it under "Tools" -> "Catalog Browser" and it will display the > configs together with the catalog metadata like project description. this is the most important, so people can actually know what a project is about :) but of course, that depends on you providing information in catalog methods! > > The code is managed with a configuration similar to what we have for > a few other packages/projects. The tool was written by Esteban Lorenzano with small > improvements like spotter integration from my side. Feel free to contribute more features. > > The repository can be found on SmalltalkHub [2]. > > This new tool basically gives you access to all available configurations > aggregated at [3]. You can use a small UI to search and load the configs > (see world menu -> "Tools" -> "Catalog Browser". > > But you can also use Spotter to load a config. > > Example on how to load ScriptManager config: > ============================================ > - open Spotter (SHIFT + ENTER on Windows, ...) > - type in "Script" and you will find a spotter category "Catalog Projects" with "ScriptManager" in it > - just hit enter and the config is loaded > > Same for all others, so try with "Seaside", "MongoTalk", ... > > In the short/mid-term this new tool should replace the existing config browser as it > gives more informations about the projects. > > What to do next: > ================ > - give feedback > - we should update all our configs with catalog descriptions > - it would be nice if the spotter integration would include also a preview of the project > description +1 > - ... > > If you want to contribute just tell Esteban so he can add you to the project. well no… I just made it public access, so anyone can commit changes there… :) (And I will move it to PharoExtras team soon, that’s the correct place once integrated in image… but well… time is tyrant :P) Esteban ps: Thanks Torsten to look at it! > > Thanks > Esteban & Torsten > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-June/110964.html > [2] http://www.smalltalkhub.com/#!/~estebanlm/CatalogBrowser > [3] http://catalog.pharo.org/catalog/json<catalogBrowser.png> |
Esteban wrote:
> > If you want to contribute just tell Esteban so he can add you to the project. > well no… I just made it public access, so anyone can commit changes there… :) > (And I will move it to PharoExtras team soon, that’s the correct place once integrated in image… but well… time is tyrant :P) I moved it to PharoExtras, MCZs are copied and config adopted (with a new version 0.5): http://smalltalkhub.com/#!/~PharoExtras/CatalogBrowser/ This is tracked for integration in: https://pharo.fogbugz.com/f/cases/15744/CatalogBrowser-moved-to-PharoExtras BTW: IMHO we can close https://pharo.fogbugz.com/f/cases/15703/ Thanks T. |
In reply to this post by Torsten Bergmann
On Thu, Jun 11, 2015 at 2:55 PM, Torsten Bergmann <[hidden email]> wrote:
> Hi, > > maybe you already noticed. The latest update for Pharo 5 which is 50103 (see [1]). > includes a new tool called "Catalog Browser". > > Where to go > =========== > > You will find it under "Tools" -> "Catalog Browser" and it will display the > configs together with the catalog metadata like project description. > > The code is managed with a configuration similar to what we have for > a few other packages/projects. The tool was written by Esteban Lorenzano with small > improvements like spotter integration from my side. Feel free to contribute more features. > > The repository can be found on SmalltalkHub [2]. > > This new tool basically gives you access to all available configurations > aggregated at [3]. You can use a small UI to search and load the configs > (see world menu -> "Tools" -> "Catalog Browser". > > But you can also use Spotter to load a config. > > Example on how to load ScriptManager config: > ============================================ > - open Spotter (SHIFT + ENTER on Windows, ...) > - type in "Script" and you will find a spotter category "Catalog Projects" with "ScriptManager" in it > - just hit enter and the config is loaded Just had a quick try. Its nice to get descriptions, like for "TaskIT". However I think there should be a confirmation dialog before actually loading a Configuration, which is a potentially destructive/undoable action. Its too easy that habits pressing <enter> for other functions assert themselves and load a configuration accidentally. Perhaps an alternative is to open a window with more information from the other fields of the catalog that has a button to load the Configuration. > > Same for all others, so try with "Seaside", "MongoTalk", ... > > In the short/mid-term this new tool should replace the existing config browser as it > gives more informations about the projects. I don't think its a total replacement for the Configuration Browser. The new function suits the case of searching for a configuration you already know about, bu tmany times I like catalog browsers when I'm not searching for something. That is, when I don't know what is there and I'm *browsing*. Indeed, if you are searching for a particular configuration then you probably already know what it is and the additional info is then not needed. cheers -ben > > What to do next: > ================ > - give feedback > - we should update all our configs with catalog descriptions > - it would be nice if the spotter integration would include also a preview of the project > description > - ... > > If you want to contribute just tell Esteban so he can add you to the project. > > Thanks > Esteban & Torsten > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-June/110964.html > [2] http://www.smalltalkhub.com/#!/~estebanlm/CatalogBrowser > [3] http://catalog.pharo.org/catalog/json |
But is a superset. We do not want to keep two tools with same functionality (we already did this a lot in the past, but we are like alcoholics in recovery now… :P) Esteban ps: when you already know what you want, most probably you just load through a command line (or a script)… at least that’s what I do :)
|
On Thu, Jun 11, 2015 at 11:11 PM, Esteban Lorenzano <[hidden email]> wrote:
> > On 11 Jun 2015, at 16:42, Ben Coman <[hidden email]> wrote: > > On Thu, Jun 11, 2015 at 2:55 PM, Torsten Bergmann <[hidden email]> wrote: > > Hi, > > maybe you already noticed. The latest update for Pharo 5 which is 50103 (see > [1]). > includes a new tool called "Catalog Browser". > > Where to go > =========== > > You will find it under "Tools" -> "Catalog Browser" and it will display the > configs together with the catalog metadata like project description. > > The code is managed with a configuration similar to what we have for > a few other packages/projects. The tool was written by Esteban Lorenzano > with small > improvements like spotter integration from my side. Feel free to contribute > more features. > > The repository can be found on SmalltalkHub [2]. > > This new tool basically gives you access to all available configurations > aggregated at [3]. You can use a small UI to search and load the configs > (see world menu -> "Tools" -> "Catalog Browser". > > But you can also use Spotter to load a config. > > Example on how to load ScriptManager config: > ============================================ > - open Spotter (SHIFT + ENTER on Windows, ...) > - type in "Script" and you will find a spotter category "Catalog Projects" > with "ScriptManager" in it > - just hit enter and the config is loaded > > > Just had a quick try. Its nice to get descriptions, like for > "TaskIT". However I think there should be a confirmation dialog > before actually loading a Configuration, which is a potentially > destructive/undoable action. Its too easy that habits pressing > <enter> for other functions assert themselves and load a configuration > accidentally. Perhaps an alternative is to open a window with more > information from the other fields of the catalog that has a button to > load the Configuration. > > > > Same for all others, so try with "Seaside", "MongoTalk", ... > > In the short/mid-term this new tool should replace the existing config > browser as it > gives more informations about the projects. > > > I don't think its a total replacement for the Configuration Browser. > The new function suits the case of searching for a configuration you > already know about, bu tmany times I like catalog browsers when I'm > not searching for something. That is, when I don't know what is there > and I'm *browsing*. Indeed, if you are searching for a particular > configuration then you probably already know what it is and the > additional info is then not needed. > > > But is a superset. > We do not want to keep two tools with same functionality (we already did > this a lot in the past, but we are like alcoholics in recovery now… :P) > > Esteban > > ps: when you already know what you want, most probably you just load through > a command line (or a script)… at least that’s what I do :) > I worked out that typing #cat gave me what I wanted. However when I down-arrow from GraphViz, it cycles back to the top to A4BP. I can't believe there are no configurations after GraphViz :) cheers -ben |
In reply to this post by EstebanLM
Esteban wrote:
>But is a superset.
>We do not want to keep two tools with same functionality (we already did this a lot in the past, but we are like alcoholics in recovery now… :P
Hi Esteban,
you removed the Config Browser in Pharo5.0 Latest update: #50111 much too early. As I stated in the bug (https://pharo.fogbugz.com/f/cases/15703) I would have kept both tools for a while as the Catalog Browser is not yet a real replacement. Your assumption that it is a superset is not (yet) right. We have to check more deeply and give people time for feedback. Did you know for instance that
(after a request in the past) on the mailinglist I added the possibility to ConfigBrowser to allow for own repositories with own configs. So you can not only use the tool with teh default MetaRepo's but custom ones as well. As it was requested and delivered I assume people use that and Catalog Browser offers no alternative for that. I agree that we should move quickly and reduce amount of code to maintain. But when introducing new tools
replacing old ones we should at least give the opportunity to discuss or wait for feedback if problems
arise from moving over. I do not see any value in having the existing Config Browser removed
so quickly as it can be done at any time and until people are used to the new Catalog Browser - which
was announced just this week waiting for feedback and future improvements (including further feature synchronization).
Thanks
Torsten |
In reply to this post by Torsten Bergmann
Thanks!!!
Le 11/6/15 08:55, Torsten Bergmann a écrit : > Hi, > > maybe you already noticed. The latest update for Pharo 5 which is 50103 (see [1]). > includes a new tool called "Catalog Browser". > > Where to go > =========== > > You will find it under "Tools" -> "Catalog Browser" and it will display the > configs together with the catalog metadata like project description. > > The code is managed with a configuration similar to what we have for > a few other packages/projects. The tool was written by Esteban Lorenzano with small > improvements like spotter integration from my side. Feel free to contribute more features. > > The repository can be found on SmalltalkHub [2]. > > This new tool basically gives you access to all available configurations > aggregated at [3]. You can use a small UI to search and load the configs > (see world menu -> "Tools" -> "Catalog Browser". > > But you can also use Spotter to load a config. > > Example on how to load ScriptManager config: > ============================================ > - open Spotter (SHIFT + ENTER on Windows, ...) > - type in "Script" and you will find a spotter category "Catalog Projects" with "ScriptManager" in it > - just hit enter and the config is loaded > > Same for all others, so try with "Seaside", "MongoTalk", ... > > In the short/mid-term this new tool should replace the existing config browser as it > gives more informations about the projects. > > What to do next: > ================ > - give feedback > - we should update all our configs with catalog descriptions > - it would be nice if the spotter integration would include also a preview of the project > description > - ... > > If you want to contribute just tell Esteban so he can add you to the project. > > Thanks > Esteban & Torsten > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-June/110964.html > [2] http://www.smalltalkhub.com/#!/~estebanlm/CatalogBrowser > [3] http://catalog.pharo.org/catalog/json |
In reply to this post by Torsten Bergmann
Hi,
I’m sorry I didn’t see that functionality. In any case this is Pharo 5 super-alpha… so there is no need to keep things going until we replace them :) Is also a good moment to reflect about how to implement things missing. In case of add own repositories, I’m not sure anyone used it… but in case we decide we still need it, we can think how… I do not want to maintain another tool but maybe we can extend monticello, for instance, to have it. Which other functionality you think we should add? Esteban
|
Administrator
|
IMHO it's not too much to ask to keep the old tool *at least* until the release when we've have time to adapt and have these discussions. If we removed it because we want to encourage use of the new tools, maybe the old one could be buried a bit more in the menus e.g. World->Tools->Deprecated. This seems eerily familiar to the discussions around GT... I was :) It's very useful for e.g. private projects, forked configs w. different stable/default groups, etc. I guess I've gotten used to our lightning-quick development pace because, when my startup script which adds the repos got an error, I assumed another cool tool had been introduced, and found the Catalog Browser. But now I'll have to go back to 4.0 for some tasks for a while... [OT]: now that the tool is getting more comprehensive, can we add the ability to load #development, or #bleedingEdge? I understand we may want to bury them a bit not to confuse new users, but IMHO the lack makes the tool much less useful for non-newbies (me at least!)...
Cheers,
Sean |
Administrator
|
In reply to this post by EstebanLM
Browse configuration class from context menu when present
Cheers,
Sean |
> EstebanLM wrote
> > Which other functionality you think we should add? > > Browse configuration class from context menu when present > > ----- > Cheers, > Sean I just added this in "Tool-Catalog-TorstenBergmann.14" ("allow to browse the config class when loaded similar to what Config browser had"). Will be integrated with the next release version. Thanks T. |
Administrator
|
Thanks :)
Cheers,
Sean |
In reply to this post by Sean P. DeNigris
On Sat, Jun 13, 2015 at 5:47 AM, Sean P. DeNigris <[hidden email]> wrote:
> EstebanLM wrote >> In any case this is Pharo 5 super-alpha… so there is no need to keep >> things going until we replace them :) > > IMHO it's not too much to ask to keep the old tool *at least* until the > release when we've have time to adapt and have these discussions. If we > removed it because we want to encourage use of the new tools, maybe the old > one could be buried a bit more in the menus e.g. World->Tools->Deprecated. > This seems eerily familiar to the discussions around GT... And/Or you could add "Deprecated" to the window title text. cheers -ben |
Free forum by Nabble | Edit this page |