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

Re: [Pharo-dev] 11920 NewValueHolder should use value instead of contents

by Nicolas Cellier

That was my impression too. But the interaction with RPackage Annoucement etc.. makes it hard to isolate. I suspect these layers, because I use MC everyday in Squeak where it's much more robust. That means that tests are not currently sufficient and we should focus on this (MC used to have a fairly good coverage). 2013/11/5 Camillo Bruni <camillobruni(a)gmail.com> > So there must be some serious MC issue. > > On 2013-11-05, at 11:15, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > Indeed, it seems to not be in the system. > > > > Most probably because afterward another spec related issue has been > integrated, > > and that the diff were not properly detected. > > (Already happened) > > > > Ben > > > > On 04 Nov 2013, at 23:06, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > >> I will tomorrow :) > >> > >> Ben > >> > >> On 04 Nov 2013, at 13:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> > >>> Ben > >>> > >>> this is strange when I look at these changes I do not really see that > value is used instead of contents. > >>> Can you check to see if your changes got really integrated? > >>> > >>> Stef > >>> On Nov 3, 2013, at 8:17 PM, GitHub <noreply(a)github.com> wrote: > >>> > >>>> Branch: refs/heads/3.0 > >>>> Home: https://github.com/pharo-project/pharo-core > >>>> Commit: a5bce43720062026ab415167af4db194d3958d62 > >>>> > https://github.com/pharo-project/pharo-core/commit/a5bce43720062026ab415167… > >>>> Author: Jenkins Build Server <board(a)pharo-project.org> > >>>> Date: 2013-11-03 (Sun, 03 Nov 2013) > >>>> > >>>> Changed paths: > >>>> A ScriptLoader30.package/ScriptLoader.class/instance/pharo - > scripts/script199.st > >>>> A ScriptLoader30.package/ScriptLoader.class/instance/pharo - > updates/update30544.st > >>>> M > ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > >>>> M Spec-Core.package/TextModel.class/definition.st > >>>> M Spec-Core.package/TextModel.class/instance/initialization/ > initialize.st > >>>> A > Spec-Core.package/TextModel.class/instance/protocol-events/whenMenuHolderChanged_.st > >>>> M > Spec-Core.package/TextModel.class/instance/protocol/codePaneMenu_shifted_.st > >>>> A Spec-Core.package/TextModel.class/instance/protocol/menuHolder.st > >>>> A Spec-Core.package/TextModel.class/instance/protocol/menuHolder_.st > >>>> A > StartupPreferences.package/extension/SettingBrowser/instance/exportAllSettings_by_withBasename_.st > >>>> M > StartupPreferences.package/extension/SettingBrowser/instance/exportSettings.st > >>>> A > StartupPreferences.package/extension/SettingBrowser/instance/exportSettings_toFileNamed_.st > >>>> > >>>> Log Message: > >>>> ----------- > >>>> 30544 > >>>> 12061 SettingBrowser>>exportSettings need refactoring > >>>> https://pharo.fogbugz.com/f/cases/12061 > >>>> > >>>> 11920 NewValueHolder should use value instead of contents > >>>> https://pharo.fogbugz.com/f/cases/11920 > >>>> > >>>> 11819 TextModel>>#codePaneMenu:shifted: should work with a value > holder > >>>> https://pharo.fogbugz.com/f/cases/11819 > >>>> > >>>> http://files.pharo.org/image/30/30544.zip > >>>> > >>>> > >>>> > >>> > >>> > >> > > > >

Nov. 5, 2013

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

by news{＠bestley.co.uk

Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > I've just made a .dmg file for installing Pharo on MacOSX. Please try it > and report problems: > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/16/ar > tifact/pharo-build/Pharo%203.0.0.dmg > > Best, On Mavericks on a 2013 Mac Mini. I copied the app to /Applications and tried to run and got Pharo.app is damaged and can't be opened. You should move it to the Trash This is due to Gatekeeper I think. I managed to open it by choosing Open in the right click menu in Finder. see <http://support.apple.com/kb/ht5290> I think you need to sign the app The Launcher looks for and save images in ~/Library/Preferences/Pharo This is wrong it should be ~/Library/Application/Support/Pharo for general use, there is a case for using ~/Library/Containers to fit in with Apple's sandboxing. Or better allow us to chnage the directory - I save images in a Dropbox directory for easy backing up and use on other machines. The icons are odd, trying to get a new Pharo 3 image it says hit refresh icon which took me some time to find. Although I am bad at all icons so might just be me. -- Mark

Nov. 5, 2013

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

by Norbert Hartl

Wow! That is really great and it works like with an other application. Awesome! Norbert Am 05.11.2013 um 11:18 schrieb Damien Cassou <damien.cassou(a)gmail.com>: > Hi, > > I've just made a .dmg file for installing Pharo on MacOSX. Please try > it and report problems: > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/16/art… > > Best, > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Nov. 5, 2013

Re: [Pharo-dev] Writing jpeg files to disk

by Usman Bhatti

Here is a slice the corrects the bug. I cannot commit to pharo inbox. Usman On Tue, Nov 5, 2013 at 11:49 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > https://pharo.fogbugz.com/f/cases/12073/Writing-jpeg-files-to-disk > > > On Tue, Nov 5, 2013 at 11:34 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > >> Hello, >> >> Due to the changes in Pharo 3.0, I cannot write jpeg files on the disk. >> This happens because when writing a jpeg file, we delete any precedent >> version of the file to be exported. However, now DiskStore>>delete: throws >> an exception when the file to be deleted is not present >> >> delete: path >> | pathString encodedPathString | >> (self exists: path) >> ifFalse: [ ^ FileDoesNotExist signalWith: path ]. >> ... >> >> Hence, we need to fix PluginBasedJPEGReadWriter>>putForm: quality: >> progressiveJPEG: onFileNamed: to not delete files not present. >> >> To reproduce the problem: >> Display writeJPEGfileNamed: 'display.jpeg' progressive: true >> >> If confirmed, I'll open a bug report and propose a slice because >> correction is quite simple ;) >> >> regards, >> Usman >> > >

Nov. 5, 2013

Re: [Pharo-dev] Writing jpeg files to disk

by Usman Bhatti

https://pharo.fogbugz.com/f/cases/12073/Writing-jpeg-files-to-disk On Tue, Nov 5, 2013 at 11:34 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > Hello, > > Due to the changes in Pharo 3.0, I cannot write jpeg files on the disk. > This happens because when writing a jpeg file, we delete any precedent > version of the file to be exported. However, now DiskStore>>delete: throws > an exception when the file to be deleted is not present > > delete: path > | pathString encodedPathString | > (self exists: path) > ifFalse: [ ^ FileDoesNotExist signalWith: path ]. > ... > > Hence, we need to fix PluginBasedJPEGReadWriter>>putForm: quality: > progressiveJPEG: onFileNamed: to not delete files not present. > > To reproduce the problem: > Display writeJPEGfileNamed: 'display.jpeg' progressive: true > > If confirmed, I'll open a bug report and propose a slice because > correction is quite simple ;) > > regards, > Usman >

Nov. 5, 2013

Writing jpeg files to disk

by Usman Bhatti

Hello, Due to the changes in Pharo 3.0, I cannot write jpeg files on the disk. This happens because when writing a jpeg file, we delete any precedent version of the file to be exported. However, now DiskStore>>delete: throws an exception when the file to be deleted is not present delete: path | pathString encodedPathString | (self exists: path) ifFalse: [ ^ FileDoesNotExist signalWith: path ]. ... Hence, we need to fix PluginBasedJPEGReadWriter>>putForm: quality: progressiveJPEG: onFileNamed: to not delete files not present. To reproduce the problem: Display writeJPEGfileNamed: 'display.jpeg' progressive: true If confirmed, I'll open a bug report and propose a slice because correction is quite simple ;) regards, Usman

Nov. 5, 2013

Re: [Pharo-dev] Bringing external documentation internally , Deep Into Pharo , PBE

by kilon alios

Neither, I am using the existing Help Browser which I extend with my own class called Prometheas. Currently it fixes only the refresh button problem but in the future I will completely redesign it cause it is part of my larger project Ephestos that will bring a new GUI API (using Athens) and I will base it on that. Size wise, we have discussed it before, its only text so it should be negligible. Probably a few Mbs , so nothing major. Just to be clear this will be part of Ephestos that I will keep external to Pharo that you will be able to install via Configuration Browser, So if you dont want it you don't install it. The beauty of freedom of choice ;) Thanks for the info Alexander I will copy paste the credits from these books. On Tue, Nov 5, 2013 at 12:08 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > How do you want to bring it ? With class comments, method with comment > only ? > > I guess it is not a problem as long as it does not take too much memory (I > mean as long as it is not a Mb). > > > 2013/11/5 kilon alios <kilon.alios(a)gmail.com> > >> Is this a problem ? I want to bring external documentation inside the >> Pharo image, and I was wondering if I need permission and such. I will be >> editing also some documentation to make it easier to read and more current. >> I am already working on Nativeboost documentation. >> > >

Nov. 5, 2013

[FEEDBACK] Install Pharo on MacOSX

by Damien Cassou

Hi, I've just made a .dmg file for installing Pharo on MacOSX. Please try it and report problems: https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/16/art… Best, -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 5, 2013

Re: [Pharo-dev] 11920 NewValueHolder should use value instead of contents

by Camillo Bruni

So there must be some serious MC issue. On 2013-11-05, at 11:15, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Indeed, it seems to not be in the system. > > Most probably because afterward another spec related issue has been integrated, > and that the diff were not properly detected. > (Already happened) > > Ben > > On 04 Nov 2013, at 23:06, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> I will tomorrow :) >> >> Ben >> >> On 04 Nov 2013, at 13:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Ben >>> >>> this is strange when I look at these changes I do not really see that value is used instead of contents. >>> Can you check to see if your changes got really integrated? >>> >>> Stef >>> On Nov 3, 2013, at 8:17 PM, GitHub <noreply(a)github.com> wrote: >>> >>>> Branch: refs/heads/3.0 >>>> Home: https://github.com/pharo-project/pharo-core >>>> Commit: a5bce43720062026ab415167af4db194d3958d62 >>>> https://github.com/pharo-project/pharo-core/commit/a5bce43720062026ab415167… >>>> Author: Jenkins Build Server <board(a)pharo-project.org> >>>> Date: 2013-11-03 (Sun, 03 Nov 2013) >>>> >>>> Changed paths: >>>> A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script199.st >>>> A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30544.st >>>> M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>>> M Spec-Core.package/TextModel.class/definition.st >>>> M Spec-Core.package/TextModel.class/instance/initialization/initialize.st >>>> A Spec-Core.package/TextModel.class/instance/protocol-events/whenMenuHolderChanged_.st >>>> M Spec-Core.package/TextModel.class/instance/protocol/codePaneMenu_shifted_.st >>>> A Spec-Core.package/TextModel.class/instance/protocol/menuHolder.st >>>> A Spec-Core.package/TextModel.class/instance/protocol/menuHolder_.st >>>> A StartupPreferences.package/extension/SettingBrowser/instance/exportAllSettings_by_withBasename_.st >>>> M StartupPreferences.package/extension/SettingBrowser/instance/exportSettings.st >>>> A StartupPreferences.package/extension/SettingBrowser/instance/exportSettings_toFileNamed_.st >>>> >>>> Log Message: >>>> ----------- >>>> 30544 >>>> 12061 SettingBrowser>>exportSettings need refactoring >>>> https://pharo.fogbugz.com/f/cases/12061 >>>> >>>> 11920 NewValueHolder should use value instead of contents >>>> https://pharo.fogbugz.com/f/cases/11920 >>>> >>>> 11819 TextModel>>#codePaneMenu:shifted: should work with a value holder >>>> https://pharo.fogbugz.com/f/cases/11819 >>>> >>>> http://files.pharo.org/image/30/30544.zip >>>> >>>> >>>> >>> >>> >> >

Nov. 5, 2013

Re: [Pharo-dev] 11920 NewValueHolder should use value instead of contents

by Benjamin

Indeed, it seems to not be in the system. Most probably because afterward another spec related issue has been integrated, and that the diff were not properly detected. (Already happened) Ben On 04 Nov 2013, at 23:06, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > I will tomorrow :) > > Ben > > On 04 Nov 2013, at 13:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Ben >> >> this is strange when I look at these changes I do not really see that value is used instead of contents. >> Can you check to see if your changes got really integrated? >> >> Stef >> On Nov 3, 2013, at 8:17 PM, GitHub <noreply(a)github.com> wrote: >> >>> Branch: refs/heads/3.0 >>> Home: https://github.com/pharo-project/pharo-core >>> Commit: a5bce43720062026ab415167af4db194d3958d62 >>> https://github.com/pharo-project/pharo-core/commit/a5bce43720062026ab415167… >>> Author: Jenkins Build Server <board(a)pharo-project.org> >>> Date: 2013-11-03 (Sun, 03 Nov 2013) >>> >>> Changed paths: >>> A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script199.st >>> A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30544.st >>> M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>> M Spec-Core.package/TextModel.class/definition.st >>> M Spec-Core.package/TextModel.class/instance/initialization/initialize.st >>> A Spec-Core.package/TextModel.class/instance/protocol-events/whenMenuHolderChanged_.st >>> M Spec-Core.package/TextModel.class/instance/protocol/codePaneMenu_shifted_.st >>> A Spec-Core.package/TextModel.class/instance/protocol/menuHolder.st >>> A Spec-Core.package/TextModel.class/instance/protocol/menuHolder_.st >>> A StartupPreferences.package/extension/SettingBrowser/instance/exportAllSettings_by_withBasename_.st >>> M StartupPreferences.package/extension/SettingBrowser/instance/exportSettings.st >>> A StartupPreferences.package/extension/SettingBrowser/instance/exportSettings_toFileNamed_.st >>> >>> Log Message: >>> ----------- >>> 30544 >>> 12061 SettingBrowser>>exportSettings need refactoring >>> https://pharo.fogbugz.com/f/cases/12061 >>> >>> 11920 NewValueHolder should use value instead of contents >>> https://pharo.fogbugz.com/f/cases/11920 >>> >>> 11819 TextModel>>#codePaneMenu:shifted: should work with a value holder >>> https://pharo.fogbugz.com/f/cases/11819 >>> >>> http://files.pharo.org/image/30/30544.zip >>> >>> >>> >> >> >

Nov. 5, 2013