> > On this matter, when I named my project, "Grafoscopio" I thought in > something evocative and unique, because of the Spanish words "grafo" > (graph) and grafía[1][2] (graphy, related with writing like in > "ortografía" "orthography". After naming it I discover there was a old > device related with writing and visualization, also called > Grafoscopio[3][4], but I got good search rankings because of the > uniqueness of the word[5][6].
Obviously and well done! I like when developers are talking about names: They use a mac and not a computer, they were nike, lewis and not shoes and pants.... May be we should rename Pharo: programming language. And Voyage: Layer And Athens, Cairo: Canvas And git: versioning system Hibernate? JavaFX?, Graddle?, Travis?, Bintray? Do you want more Docker? So guys can we focus our energy on positive things. Stef > > Being my first project and lacking any programming style, the "Smalltalk > with Style" book didn't make any sense at that time, but now, with more > experience, I wonder, from time to time, how I could/should (re)name the > software and its classes. > > [1] http://www.wordreference.com/definicion/graf%c3%ada > [2] http://www.wordreference.com/es/en/translation.asp?spen=graf%C3%ADa > [3] > https://www.museodelprado.es/actualidad/multimedia/el-grafoscopio/722c13b2-8f3c-42a0-a1ab-1374bbca9d5f > [4] > https://www.museodelprado.es/en/whats-on/exhibition/the-graphoscope/81bfb972-aade-4c24-93b2-dbd7e26e5e4a > [5] https://duckduckgo.com/?q=grafoscopio&t=ffsb&atb=v76-7&ia=web > [6] https://www.google.com/search?hl=en&q=grafoscopio > > Cheers, > > Offray > > On 13/04/18 09:01, Esteban A. Maringolo wrote: >> On 13/04/2018 10:41, p...@highoctane.be wrote: >>> A somewhat unique name makes it easier to google for it (like Roassal >>> Pharo, or DeepTraverser Pharo, or Zinc Pharo). >>> These will give us hits that are relevant. >>> >>> Try System Browser, Inspector... >>> >>> And Apple has worked with NSObject and stuff like that without too much >>> trouble (at a much larger scale for whatever XyzKit they released). >>> Ah, yes, they used the "Kit" suffix. Maybe can we have something like >>> that with Pharo. Like SystemBrowserKit ( nah, too Appleish. >> >> But I prefer these names: >> * Calypso System Browser >> * Calypso Debugger >> * Iceberg Source Control Management >> * Zinc HTTP Client >> * Zinc HTTP Server >> * Fuel Serialization >> * Glamorous Spotter [*] >> * etc. >> >> [*] I particularly dislike "Glamorous" adjective. >> >> In the case of wrapper for libraries I'm hesitant to decide whether to >> indicate pharo name in it or not. >> I mean stuff like a NaCl wrapper calling it "NaCl-Pharo" instead of >> calling "Salty". >> >> >>> Let's try SystemBrowserMeccano (longish), or SystemBrowserPack (too >>> bland), or SystemBrowserGear (why not), SystemBrowserRig (this one >>> sounds cool actually)). >> Fortunately in the past the lack of namespaces caused the use of >> prefixes instead of suffixes. >> >> With time prefixes become invisible. >> >> A suffix, instead, will get into all your names, bothering with other >> existing suffixes like `Component`, `Model`, `Collection`, and so on. >> >> >> >> >> >> >> > > >
