Or just expand the names to be descriptive. CalypsoClassBrowser would be cool
> On Apr 13, 2018, at 5:39 AM, Esteban Lorenzano <esteba...@gmail.com> wrote: > > > >> On 13 Apr 2018, at 14:33, Andrew Glynn <aglyn...@gmail.com >> <mailto:aglyn...@gmail.com>> wrote: >> >> I find NPM as obscure as Pharo, honestly, and VA Smalltalk is worse (wth >> does abt or sst stand for?). Grunt, Gulp, etc., how do the names relate to >> what they do? > > yes… but we actually have a problem there. > I would like to be able to add “tags" to tools, to be able to say: > > Calypso -> a class browser -> some more info > etc. > > Esteban > >> >> Electron is as obscure as Phobos (although a phobia with web pages turned >> into desktop apps may be appropriate). >> >> Andrew >> >> On Fri, 2018-04-13 at 14:18 +0200, Peter Uhnák wrote: >>> On Fri, Apr 13, 2018 at 2:05 PM, Richard O'Keefe <rao...@gmail.com >>> <mailto:rao...@gmail.com>> wrote: >>>> There are a lot of subsystems in Pharo, and being a bear of >>>> very little brain, I have a hard time relating Zinc, Calypso, >>>> &c &c to, well, whatever they are. I presume there is >>>> somewhere a list of topic/name/PFX triples for guidance. >>>> Can some kind soul tell me where it is? >>>> >>> >>> Until we have mature package manager (similar to Cargo or npm), you have to >>> use google. >>> On the bright side, with the move to git(hub), people are much more likely >>> to actually describe what their project does, and maybe even a bit of >>> documentation. This was almost non-existent with SmalltalkHub. >>> >>> Peter >
