- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] "Pharo" Name Overload

by Pierce Ng

On Tue, Jan 26, 2016 at 06:24:48PM +0000, Dimitris Chloupis wrote: > Why ? We did not have Pharo-stack.app and Pharo-cog.app and none complained I've also renamed Pharo to "Pharo Cog" or whatever as the case may be using Finder. Using Terminal rename Pharo.app to "Pharo Cog.app". Pierce

Jan. 26, 2016

Re: [Pharo-dev] "Pharo" Name Overload

by Pierce Ng

On Tue, Jan 26, 2016 at 06:56:00AM -0800, Sean P. DeNigris wrote: > I now have three Pharo.app files on my Mac - Launcher, Spur, and non-Spur. It > would be great if we can agree to call one thing Pharo, and add appropriate > modifiers to the other two names. Using more Linux than OSX these days coz my MB battery is crapping out but I recall in the days of compiling source from squeakvm.org and early Cog versions that the OSX app icon has a different colour depending on version - pastel pink and light blue for squeakvm versions and gold for Cog. Perhaps the same can be done now, or make the words like Launcher, Spur etc part of the icon. Pierce

Jan. 26, 2016

Re: [Pharo-dev] The shortcuts learnability is awesome, thank you!

by Dimitris Chloupis

gave it a try, i love it, it should become a default feature :) On Tue, Jan 26, 2016 at 11:54 PM Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > oh super cool , thanks, my connection is down for days now and it takes > time for me to download things. Thats indeed very useful feature to have. > > On Mon, Jan 25, 2016 at 5:06 PM Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Grab very last image (as of today), evaluate this code: >> >> ShortcutReminder enabled: true. >> >> (or enable that via settings) >> >> And then simply start using the image, and you will see Growl-like popups >> on the bottom left reminding you the shortcut for the action you just did :) >> >> >> >> On Mon, Jan 25, 2016 at 11:52 AM, Dimitris Chloupis < >> kilon.alios(a)gmail.com> wrote: >> >>> Any more info about this, I was sick lately and I did not understand >>> what was that about . >>> >>> On Mon, Jan 25, 2016 at 2:45 PM Mariano Martinez Peck < >>> marianopeck(a)gmail.com> wrote: >>> >>>> This is just to say a big thanks to all those that contributed to the >>>> new shortcut learnability. This is awesome. I love it. >>>> >>>> Bye, >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >

Jan. 26, 2016

Re: [Pharo-dev] Menus are broken in diff tools pane

by Nicolai Hess

2016-01-14 16:14 GMT+01:00 stepharo <stepharo(a)free.fr>: > Alain told me that he can help. > We should give him a list of problems. > There *IS* already a apretty long list at http://forum.world.st/fixing-our-tools-tp4864859.html and many many bug reports. > > Stef > > menus are broken almost everywhere: > > I thnk, responsible for these issues are only two changes for Rubric and > the Suggestions-Menu > > http://forum.world.st/fixing-our-tools-tp4864859.html > > > > > 2016-01-14 12:54 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> >> >> > >

Jan. 26, 2016

Re: [Pharo-dev] fixing our tools

by Nicolai Hess

2015-12-03 9:16 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > Yes, I think we really need to unify both the editor (get really rid of > the old one) and > the toolsâ¦ e.g. it is strange that all the changes we did for breakpoint > visuals now have > to be redone 3 times to get them in all toolsâ¦ > > I will have a look at these, many seem to be related to the > suggestions-menu. > I added a fix to 17385 <https://pharo.fogbugz.com/f/cases/17385/DiffMorph-menus-are-broken> DiffMorph menus are broken this will fix the menu in some, but not all tools. > > > On 03 Dec 2015, at 08:47, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > please take a look at this errors: > > > > (I don't want to open 20 bug entries, and I think those issues are > related > > to two changes for Suggestions menu and one problem on rubric (the > current menu builder > > does not work for all tools where rubric is used) > > So, maybe there are only 2 or 3 "real" issues. > > > > Help appreciate, especially for the rubric issue. Every time I tried to > fix one > > tool, there is at least one other tool with a broken menu. > > > > Open Nautilus on a method: > > (Morph>>#drawOn:) browse > > without any other interaction, right click on the code pane > > -> a menu appears with embedded "why you see this menu/debug" debug menu > > caused by empty selection interval > > as soon as you select once one method entry, the right click menu works > again. > > > > Open VersionBrowser (or any other tool (MC-changes / merge) with diff > morph > > right click in one of the diff code panes > > -> error contextFor: 'Not defined context for a RubEditingArea' > > > > Open Transcript > > right click > > -> error contextFor: 'Not defined context for a RubEditingArea' > > > > Open Finder > > right click in the lower code pane > > -> 'Not defined context for a RubEditingArea' > > > > Open ProcessBrowser > > right click in the lower code pane > > -> 'Not defined context for a RubEditingArea(808452096)' > > > > Open TimeProfiler > > select an entry from the time-"tree" > > right click in the code pane > > deprecation warning -> The method SmalltalkEditor > class>>smalltalkEditorMenuOn: has been deprecated. > > > > Open a basic inspector (EyeInspector) > > right click in the workspace pane > > -> EyeIntegerInspector(Object)>>doesNotUnderstand: #selectedMessage > > > > Open ChangesBrowser > > right click in the lower code pane (regardless whether you select a > changed class and method > > or not you'll get always) > > -> ChangeSorterApplication(Object)>>doesNotUnderstand: #selectedMessage > > > > Open CriticsBrowser > > right click on the code pane > > -> SingleCodeCriticResultList(Object)>>doesNotUnderstand: > #selectedMessage > > > > Open recover lost changes > > right click on the lower code pane > > -> ExternalChangesBrowser(Object)>>doesNotUnderstand: #selectedMessage > > > > The same in external browser > > ExternalBrowser(Object)>>doesNotUnderstand: #selectedMessage > > > > Open debugger > > select a inst var or context var > > right click in the var "value"-pane > > -> MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed > > > > Open VersoinBrowser > > change from "Side-by-Side" to "Source" view > > right click in the code pane > > -> UndefinedObject(Object)>>doesNotUnderstand: #ast > > > > >

Jan. 26, 2016

Re: [Pharo-dev] The shortcuts learnability is awesome, thank you!

by Dimitris Chloupis

oh super cool , thanks, my connection is down for days now and it takes time for me to download things. Thats indeed very useful feature to have. On Mon, Jan 25, 2016 at 5:06 PM Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Grab very last image (as of today), evaluate this code: > > ShortcutReminder enabled: true. > > (or enable that via settings) > > And then simply start using the image, and you will see Growl-like popups > on the bottom left reminding you the shortcut for the action you just did :) > > > > On Mon, Jan 25, 2016 at 11:52 AM, Dimitris Chloupis <kilon.alios(a)gmail.com > > wrote: > >> Any more info about this, I was sick lately and I did not understand what >> was that about . >> >> On Mon, Jan 25, 2016 at 2:45 PM Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> This is just to say a big thanks to all those that contributed to the >>> new shortcut learnability. This is awesome. I love it. >>> >>> Bye, >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com >

Jan. 26, 2016

Re: [Pharo-dev] "Pharo" Name Overload

by Damien Cassou

Dimitris Chloupis <kilon.alios(a)gmail.com> writes: > Spur will become the default soon enough and you will forget about the > other as you forgot about stack vm. I'm not sure this is what will happen. I have the impression that we will have one VM for Pharo 4, one VM for Pharo 5, one VM for Pharo 6... -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 26, 2016

Re: [Pharo-dev] "Pharo" Name Overload

by Damien Cassou

"Sean P. DeNigris" <sean(a)clipperadams.com> writes: > I now have three Pharo.app files on my Mac - Launcher, Spur, and non-Spur. It > would be great if we can agree to call one thing Pharo, and add appropriate > modifiers to the other two names. I'm not an OS X user, but I have the impression that .app is reserved for graphical applications, one you can start with a double click. For me, no Pharo VM is a graphical application and thus none deserve its .app file in /Applications. On the contrary, what we currently call the Pharo Launcher is a graphical application so it deserves a .app file. I called it just Pharo.app because I didn't see any concurrence on the name and some in the Pharo board would like the launcher to be the default Pharo download (the one behind the big Download button on the website). We could improve the situation by putting all Pharo VMs inside the Pharo Launcher's .app file. Who volunteers? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 26, 2016

newly class instances defined iv kept as symbol?

by stepharo

WebServer class instanceVariableNames: 'uniqueInstance' Object class allInstVarNames --> "#('superclass' 'methodDict' 'format' 'layout' 'instanceVariables' 'organization' 'subclasses' 'name' 'classPool' 'sharedPools' 'environment' 'category' 'traitComposition' 'localSelectors')" WebServer class allInstVarNames -->"#('superclass' 'methodDict' 'format' 'layout'instanceVariables' 'organization' 'subclasses' 'name' 'classPool' 'sharedPools' 'environment' 'category' 'traitComposition' 'localSelectors' #uniqueInstance)" I found strange that we get a symbol. Stef

Jan. 26, 2016

Re: [Pharo-dev] "Pharo" Name Overload

by Dimitris Chloupis

To tell you the truth your idea sound unconventional to me as a Macos user. I never seen an app to put in its name nothing more than the name of the app, maybe just maybe the version though even that is rare. App is essentially just a folder you can navigate . I don't see a good reason for the average Pharo user to name Pharo,app anything but that. Since most of us we won't care or at least thats the way I see it. On Tue, 26 Jan 2016 at 20:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > kilon.alios wrote > > none complained before > > This has been a consistent complaint about PharoLauncher's branding as just > "Pharo", when "Pharo" already means something else. The Cog/Spur just made > it a bit worse. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Pharo-Name-Overload-tp4874242p4874285.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Jan. 26, 2016