September 2013 - Pharo-dev - lists.pharo.org

[update 3.0] #30392

by Marcus Denker

30392 ----- 10913 Global Session object should have creation time stamp https://pharo.fogbugz.com/f/cases/10913 11568 World > System > System Reporter MNU #platformSubtype https://pharo.fogbugz.com/f/cases/11568 11539 Author fullName is 'MarcusDenker' even after changing/saving/restarting image https://pharo.fogbugz.com/f/cases/11539 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1250.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.9…

Sept. 12, 2013

Workspace Moprh Bug with image 30389

by Torsten Bergmann

Marcus wrote: >This should be fixed in 3.0 390â¦. at least I can't reproduce it anymore. Hi Marcus, No its not. I tried in the latest 3.0 image from today. To make sure I cleanly downloaded a fresh Pharo3.0 Latest update: #30391 and still can reproduce the problem. One has to do some moving on the Workspace. If you look you will into an updated image you will also see that still class var "TranslucentPatterns" in FormCanvas is uninitialized and class side methods on FormCanvas for initialization are missing. So the problem still persists ... Thx T.

Sept. 12, 2013

Re: [Pharo-dev] Workspace Moprh Bug with image 30389

by Fernando Olivero

Yes, this happened due to Monticello when integrating the Issue. Is fixed in the latest image. Messing up with Color's is both hazardous and difficult to integrate in the remote server! I'm having some problems with the integration of the issue whichs removes TranslucentColor.that I'm tackling now. Fernando On Thu, Sep 12, 2013 at 12:40 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Sep 12, 2013, at 12:36 PM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > >> kilon wrote: >>> this happens only when I try to create a new workspace issuing the commands >>> you see in the screenshot and it appears after I try to move the new >>> workspace. At first it appears as a small red box but while hitting enter it >>> expands to the final size you see here. >>> >>> Are you aware of this bug ? >> >> I can reproduce the problem. Looks like some code is missing and leads to an uninitialized >> class variable: >> >> The method #translucentMaskFor:depth: uses a class var "TranslucentPatterns" from FormCanvas. >> This class variable is nil and therefore it crashes. Looks like there is some initialization >> on the class side missing. >> >> Code is written by Fernando this week (9/11/2013) - so it is brand new. >> >> Looks like a side effect of fixing https://pharo.fogbugz.com/f/cases/11559 >> which was integrated in update #30389 >> >> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-September/0… >> >> If you look at the second changeset in this issue #11559 it includes an #initializeTranslucentPatterns >> method from Fernando - but it did not made it correctly into the image. >> >> Please open a new bug on http://bugs.pharo.org and maybe Fernando can have a look. >> > > This should be fixed in 3.0 390â¦. at least I can't reproduce it anymore. > > Marcus >

Sept. 12, 2013

Re: [Pharo-dev] Workspace Moprh Bug with image 30389

by Marcus Denker

On Sep 12, 2013, at 12:36 PM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > kilon wrote: >> this happens only when I try to create a new workspace issuing the commands >> you see in the screenshot and it appears after I try to move the new >> workspace. At first it appears as a small red box but while hitting enter it >> expands to the final size you see here. >> >> Are you aware of this bug ? > > I can reproduce the problem. Looks like some code is missing and leads to an uninitialized > class variable: > > The method #translucentMaskFor:depth: uses a class var "TranslucentPatterns" from FormCanvas. > This class variable is nil and therefore it crashes. Looks like there is some initialization > on the class side missing. > > Code is written by Fernando this week (9/11/2013) - so it is brand new. > > Looks like a side effect of fixing https://pharo.fogbugz.com/f/cases/11559 > which was integrated in update #30389 > > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-September/0… > > If you look at the second changeset in this issue #11559 it includes an #initializeTranslucentPatterns > method from Fernando - but it did not made it correctly into the image. > > Please open a new bug on http://bugs.pharo.org and maybe Fernando can have a look. > This should be fixed in 3.0 390â¦. at least I can't reproduce it anymore. Marcus

Sept. 12, 2013

Workspace Moprh Bug with image 30389

by Torsten Bergmann

kilon wrote: >this happens only when I try to create a new workspace issuing the commands >you see in the screenshot and it appears after I try to move the new >workspace. At first it appears as a small red box but while hitting enter it >expands to the final size you see here. > >Are you aware of this bug ? I can reproduce the problem. Looks like some code is missing and leads to an uninitialized class variable: The method #translucentMaskFor:depth: uses a class var "TranslucentPatterns" from FormCanvas. This class variable is nil and therefore it crashes. Looks like there is some initialization on the class side missing. Code is written by Fernando this week (9/11/2013) - so it is brand new. Looks like a side effect of fixing https://pharo.fogbugz.com/f/cases/11559 which was integrated in update #30389 http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-September/0… If you look at the second changeset in this issue #11559 it includes an #initializeTranslucentPatterns method from Fernando - but it did not made it correctly into the image. Please open a new bug on http://bugs.pharo.org and maybe Fernando can have a look. Thx T.

Sept. 12, 2013

Workspace Moprh Bug with image 30389

by kilon

I think the picture speaks for itself <http://forum.world.st/file/n4707810/Workspace_bug_morph.png> this happens only when I try to create a new workspace issuing the commands you see in the screenshot and it appears after I try to move the new workspace. At first it appears as a small red box but while hitting enter it expands to the final size you see here. Are you aware of this bug ? -- View this message in context: http://forum.world.st/Workspace-Moprh-Bug-with-image-30389-tp4707810.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 12, 2013

Re: [Pharo-dev] [Pharo-users] Pharo Sprint in Buenos Aires - this saturday!

by Marcus Denker

On Sep 11, 2013, at 3:51 PM, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Pharo Sprint in Buenos Aires! > When: sept 14 (This saturday!) We start at 10 and estimated finish at 17:00. You can join in any moment! > Where: 10Pines (Av Leandro N. Alem 693 5Â°B) > We will fix bugs and we are talking about improving usability (specially in Linux!) I will be available remotely to help integrating everything you fix. Marcus

Sept. 12, 2013

[update 3.0] #30391

by Marcus Denker

30391 ----- 11583 Removing TranslucentPattern and HighLightBitmap class vars of Color https://pharo.fogbugz.com/f/cases/11583

Sept. 12, 2013

Re: [Pharo-dev] [Off Topic] Some cartoons

by kilon

probably this is the counter argument to your comics <http://forum.world.st/file/n4707789/python.png> I think the worst scenario is when the code you hate reading is your own :D but overall I think pharo has some well written code fairly readable. The problem is that reading code itself does not explain to me fully how the lib suppose to work properly. Its not so much I have hard time figuring other's people code, but figuring out their intention and overall purpose/goal. -- View this message in context: http://forum.world.st/Off-Topic-Some-cartoons-tp4707787p4707789.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 12, 2013

Re: [Pharo-dev] How to state up to date with Pharo ?

by kilon

Ok so I decided from what I have read from here, thats the simplest solution is to just redownload from pharo main website the image and make certain that my code is kept in smalltalkhub to make porting it back to a new image much easier. I really like Pharolauncher . It definetly makes image customisation much easier so I am definetly keeping that around. Also the makefile approach makes sense to me, maybe I could create a bash script to automate the process or even better using pharo itself to auto download latest image and import my packages from the repo. But then its not as if I had so many imports to do anyway for the time being. So I am definetly keeping this approach in mind for when the manual process becomes too much. -- View this message in context: http://forum.world.st/How-to-state-up-to-date-with-Pharo-tp4707617p4707788.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 12, 2013