March 2015 - Pharo-dev - lists.pharo.org

PharoLauncher: Great Tool, Confusing Name

by Sean P. DeNigris

PharoLauncher is cool!! Once I realized I could specify the image folder with "PhLDirectoryBasedImageRepository location: aFileReference", I was very happy (I won't start the "images don't belong in ApplicationSupport thread again, promise ;)). There is however one thing that I think could be very confusing... the build artifact is called "Pharo_0.2.4.dmg". Now I understand the rationale that for a new user we are trying for "PharoLauncher = Pharo", but even I was a little confused seeing version 0.2.4. Since it's only an installer, if we really need its version number in the artifact, how about "Pharo_Installer_0.2.4.dmg" or even the more verbose but perhaps clearer "Pharo_4.0_ Installer_0.2.4.dmg"? The application ultimately gets installed as "Pharo" anyway. Some cool things: - the fullscreen UI is neat - dropping down into developer mode is seemless and works well One other suggestion: I'm sure this must have been brought up before, but it seems to download a fresh image every time (e.g. even if two images are created from the same template within a few seconds). It seems like it should be possible to do some caching here... ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoLauncher-Great-Tool-Confusing-Name-tp4813698.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-dev] [Pharo4] 203 issues tagged tagged for Pharo4

by Marcus Denker

52. Much better! some are even already fixed (but not integrated) so we will be below 50 soon. > On 20 Mar 2015, at 10:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 68 > >> On 19 Mar 2015, at 08:50, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> 88. >> >> https://pharo.fogbugz.com/f/filters/103/4-0-All >> > >

March 20, 2015

Re: [Pharo-dev] Duration year

by Richard Sargent

Maximiliano Taborda wrote > Hi all. > > The same examples using ChaltÃ©n: > February twentyninth, 2012 next: 1 yearMeasure. "=> February 28th, > 2013" This I don't get. Why would <February 28th> + 1 day + 1 year ever not be March 1st? ~75% of the time it would be, but ~25% it would be a day less? > March first, 2011 next: 1 yearMeasure. "=> March 1st, 2012" > March first, 2011 next: 12 monthsMeasure. "=> March 1st, 2012" > > Hilaire, In ChaltÃ©n a year is a year so you don't need to care about of > the > number of days in it. > > Regards. > Maxi > > > 2014-12-02 16:37 GMT-03:00 Chris Cunningham < > cunningham.cb@ > >: > >> GenericYear does this. The generic Year will take >> '2/29/2000' asDate + 1 year "=> 28 February 2001" >> In other words, we want it at the same time next year; more importantly >> the same month and close to what we have now. >> Also: >> '3/1/2001' asDate - 1 year "=> 1 March 2000" >> Still, same month - we want to be at the beginning of the month the >> previous year. >> >> Basically, my idea (and, more importantly, what I expect - hence my code) >> is that I want to pretend that we do have a field-based representation >> and >> make it work that way. except better (since there is no 2/29/2001). >> >> > Ej, which one of the followings is OK? >> > '2011-03-01' asDate + 1 year "=> 2012-02-29" >> >> Well, I have a bug here. That needs to be fixed. >> >> -cbc >> >> >> On Tue, Dec 2, 2014 at 8:34 AM, Sean P. DeNigris < > sean@ > > >> wrote: >> >>> Esteban A. Maringolo wrote >>> > Ej, which one of the followings is OK? >>> > '2012-02-29' asDate + 1 year "=> 2013-02-28" >>> > '2011-03-01' asDate + 1 year "=> 2012-02-29" >>> >>> One solution (just ignore the source ha ha) - >>> >>> http://msdn.microsoft.com/en-us/library/system.datetime.addyears%28v=vs.110… >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/Duration-year-tp4791727p4793656.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >> -- View this message in context: http://forum.world.st/Duration-year-tp4791727p4813662.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] dc5304: 40570

by Ben Coman

I'd like to see it in Pharo 5. cheers -ben On Sat, Mar 21, 2015 at 1:23 AM, stepharo <stepharo(a)free.fr> wrote: > We should rollback this change. > I did it and I will keep it for me. > > Stef > > > Le 20/3/15 17:40, Ben Coman a Ã©crit : > > > > On Fri, Mar 20, 2015 at 11:42 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> GitHub wrote >> > 14890 Browsing a different class should select by default the previously >> > browsed method >> > https://pharo.fogbugz.com/f/cases/14890 >> >> Ugh. This breaks my workflow. I often click the "Class-side" checkbox to >> get >> to the class template, but now it keeps the method selected. At first, I >> sat >> there like a monkey (no offense Ulysses ;)) and kept hitting it repeatedly >> with a perplexed look on my face. Later I saw this issue and connected the >> dots. I'm not saying its a bad change (I'm not entirely clear on the use >> case), but... >> >> Policy Suggestion: Tool UI changes /must/ be discussed on the list prior >> to >> integration. >> >> >> > I've actually been wanting this for a long time (thank you). The use > case is to make it easier to observe differences between super/subclasses > and sibling classes for the same method. For example, click on > DelayScheduler>>shutDown, then click on its two subclasses to observe the > different implementations. > > However the current implementation makes it difficult to view class > definitions. Continuing the previous example, after selecting #shutDown, > try view the class definitions of DelayScheduler and subclasses. > > Useful additional behaviour would be that clicking on a class that is > already selected would change to class-definition-mode . Clicking on the > class again would toggle back to previous-method-mode. Ideally modes would > hold between change in class selection, however its a bit late to be > experimenting with this. It would probably be simplest to just reset the > previous-method when a selected class is clicked on again, and also when > class-side button is clicked - or otherwise roll back and leave it for > Pharo 5. > > cheers -ben > > >

March 20, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] dc5304: 40570

by stepharo

We should rollback this change. I did it and I will keep it for me. Stef Le 20/3/15 17:40, Ben Coman a Ã©crit : > > > On Fri, Mar 20, 2015 at 11:42 PM, Sean P. DeNigris > <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > > GitHub wrote > > 14890 Browsing a different class should select by default the previously > > browsed method > > https://pharo.fogbugz.com/f/cases/14890 > > Ugh. This breaks my workflow. I often click the "Class-side" > checkbox to get > to the class template, but now it keeps the method selected. At > first, I sat > there like a monkey (no offense Ulysses ;)) and kept hitting it > repeatedly > with a perplexed look on my face. Later I saw this issue and > connected the > dots. I'm not saying its a bad change (I'm not entirely clear on > the use > case), but... > > Policy Suggestion: Tool UI changes /must/ be discussed on the list > prior to > integration. > > > > I've actually been wanting this for a long time (thank you). The use > case is to make it easier to observe differences between > super/subclasses and sibling classes for the same method. For > example, click on DelayScheduler>>shutDown, then click on its two > subclasses to observe the different implementations. > > However the current implementation makes it difficult to view class > definitions. Continuing the previous example, after selecting > #shutDown, try view the class definitions of DelayScheduler and > subclasses. > > Useful additional behaviour would be that clicking on a class that is > already selected would change to class-definition-mode . Clicking on > the class again would toggle back to previous-method-mode. Ideally > modes would hold between change in class selection, however its a bit > late to be experimenting with this. It would probably be simplest to > just reset the previous-method when a selected class is clicked on > again, and also when class-side button is clicked - or otherwise roll > back and leave it for Pharo 5. > > cheers -ben

March 20, 2015

[pharo-project/pharo-core] 93eb5c: 40571

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 93eb5ced08fb721a2448d25cdb6264468e083569 https://github.com/pharo-project/pharo-core/commit/93eb5ced08fb721a2448d25c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-20 (Fri, 20 Mar 2015) Changed paths: M ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/symbolic versions/stable_.st A ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/versions/version29_.st M MonticelloFileTree-Core.package/extension/MCFileRepositoryInspector/instance/refresh.st M MonticelloGUI.package/MCFileRepositoryInspector.class/definition.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/initialization/initialize.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/versionHighlight_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script570.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script571.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40570.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40571.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/accessing-ui/requiredProjectMenu_.st A Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/actions/browseProject_.st A Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/actions/browseSelectedProject.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/initialization/initializeProjectsWidget.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/initialization/unregister.st Log Message: ----------- 40571 15097 Monticello repository UI not bolding unloaded packages after Lazy MCVersionInfo integrated https://pharo.fogbugz.com/f/cases/15097 15179 Be able to browse dependent projects with Versionner https://pharo.fogbugz.com/f/cases/15179 http://files.pharo.org/image/40/40571.zip

March 20, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40571 Home: https://github.com/pharo-project/pharo-core

March 20, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] dc5304: 40570

by Ben Coman

On Fri, Mar 20, 2015 at 11:42 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > GitHub wrote > > 14890 Browsing a different class should select by default the previously > > browsed method > > https://pharo.fogbugz.com/f/cases/14890 > > Ugh. This breaks my workflow. I often click the "Class-side" checkbox to > get > to the class template, but now it keeps the method selected. At first, I > sat > there like a monkey (no offense Ulysses ;)) and kept hitting it repeatedly > with a perplexed look on my face. Later I saw this issue and connected the > dots. I'm not saying its a bad change (I'm not entirely clear on the use > case), but... > > Policy Suggestion: Tool UI changes /must/ be discussed on the list prior to > integration. > > > I've actually been wanting this for a long time (thank you). The use case is to make it easier to observe differences between super/subclasses and sibling classes for the same method. For example, click on DelayScheduler>>shutDown, then click on its two subclasses to observe the different implementations. However the current implementation makes it difficult to view class definitions. Continuing the previous example, after selecting #shutDown, try view the class definitions of DelayScheduler and subclasses. Useful additional behaviour would be that clicking on a class that is already selected would change to class-definition-mode . Clicking on the class again would toggle back to previous-method-mode. Ideally modes would hold between change in class selection, however its a bit late to be experimenting with this. It would probably be simplest to just reset the previous-method when a selected class is clicked on again, and also when class-side button is clicked - or otherwise roll back and leave it for Pharo 5. cheers -ben

March 20, 2015

Adding a class error, 40570

by stephan

When trying to run the Coral tests in Pharo 4, one of the tests raises an error when adding a class MNU receiver of "asNautilusSelection" is nil PPCoralCompilerTest>>testAccessIV "self debug: #testAccessIV" | c | self parse: '[ Object < #CoralTestC1 iv: ''bob'' ]'. self shouldnt: [c := Smalltalk at: #CoralTestC1] raise: KeyNotFound. I remember having seen something similar when creating classes in code. Stephan

March 20, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] dc5304: 40570

by Sean P. DeNigris

GitHub wrote > 14890 Browsing a different class should select by default the previously > browsed method > https://pharo.fogbugz.com/f/cases/14890 Ugh. This breaks my workflow. I often click the "Class-side" checkbox to get to the class template, but now it keeps the method selected. At first, I sat there like a monkey (no offense Ulysses ;)) and kept hitting it repeatedly with a perplexed look on my face. Later I saw this issue and connected the dots. I'm not saying its a bad change (I'm not entirely clear on the use case), but... Policy Suggestion: Tool UI changes /must/ be discussed on the list prior to integration. ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-dc5304-40570-tp4813535p48136… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2015