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

Re: [Pharo-dev] Exporting Setting preferences

by Tudor Girba

Hi, The problem is that the export exports all values, not the delta between what was chosen and what comes by default. In our case, if I want to choose to always send the anonymous usage information for Spotter, I also have to commit to using a dedicated set of icons. This constraint does not match well the use case. I think we should be able to save selected settings, or just the settings that we modified explicitly. Cheers, Doru On Mon, Mar 16, 2015 at 5:23 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 16 Mar 2015, at 17:11, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > > > > Hi, > > > > I have just realized that once someone exportes preferences in Pharo > image, it overrides a lot of things in Moose image, e.g., debugger, icons. > I do not really like it! Everyone who use both Pharo and Moose image will > be surprised and unhappy. > > Yes, that is why I never use this export feature, it is broken by design, > for me. > > An image is a persistent world which can hold its own settings. > > I can imagine some people want some automatic loading in each new image, > but that should be opt-in. > > > If someone exports preferences in Moose, he/she will always have > debugger window at the beginning. I have written about it recently in > another post. > > > > Technically speaking once someone exports preferences, he/she should > always use the same kind of image. > > Talking about recent Spotter preference about âsending usage dataâ: we > have already changed the preferences the way it uses Pharo settings; but do > we really want it with all the consequences written above? I believe that > we can still change it back for Pharo 4 and improve the whole preference > mechanism in Pharo 5. > > > > Cheers, > > Juraj > > > -- www.tudorgirba.com "Every thing has its own flow"

March 16, 2015

Re: [Pharo-dev] Exporting Setting preferences

by Sven Van Caekenberghe

> On 16 Mar 2015, at 17:11, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > > Hi, > > I have just realized that once someone exportes preferences in Pharo image, it overrides a lot of things in Moose image, e.g., debugger, icons. I do not really like it! Everyone who use both Pharo and Moose image will be surprised and unhappy. Yes, that is why I never use this export feature, it is broken by design, for me. An image is a persistent world which can hold its own settings. I can imagine some people want some automatic loading in each new image, but that should be opt-in. > If someone exports preferences in Moose, he/she will always have debugger window at the beginning. I have written about it recently in another post. > > Technically speaking once someone exports preferences, he/she should always use the same kind of image. > > Talking about recent Spotter preference about âsending usage dataâ: we have already changed the preferences the way it uses Pharo settings; but do we really want it with all the consequences written above? I believe that we can still change it back for Pharo 4 and improve the whole preference mechanism in Pharo 5. > > Cheers, > Juraj

March 16, 2015

Exporting Setting preferences

by Juraj Kubelka

Hi, I have just realized that once someone exportes preferences in Pharo image, it overrides a lot of things in Moose image, e.g., debugger, icons. I do not really like it! Everyone who use both Pharo and Moose image will be surprised and unhappy. If someone exports preferences in Moose, he/she will always have debugger window at the beginning. I have written about it recently in another post. Technically speaking once someone exports preferences, he/she should always use the same kind of image. Talking about recent Spotter preference about âsending usage dataâ: we have already changed the preferences the way it uses Pharo settings; but do we really want it with all the consequences written above? I believe that we can still change it back for Pharo 4 and improve the whole preference mechanism in Pharo 5. Cheers, Juraj

March 16, 2015

Re: [Pharo-dev] VM Crash

by Franck Warlouzet

Hello, I tried to reproduce this bug, I have also an error with the same configuration. I don't have his problem, however when I quit Pharo, the connection shutdown makes Pharo crashes, but when I only do the connection shutdown, it works. I downloaded the dll here : https://ci.inria.fr/dbxtalk/view/OpenDBX/job/CLibrary-OpenDBX-1.4.6-Mysql/P… Cheers, Franck WARLOUZET Date: Sat, 14 Mar 2015 11:56:00 -0700 From: ml-node+s1294792n4811903h64(a)n4.nabble.com To: franck.warlouzet(a)hotmail.fr Subject: VM Crash Hello, My VM crashes every time I open it. I ran the scripts below before crash occurs. | settings platform connection | settings := DBXConnectionSettings host: 'localhost' port: '3306' database: 'mysql' userName: 'root' userPassword: ''. platform := DBXMySQLBackend new. connection := DBXConnection platform: platform settings: settings. connection connect. connection open. I'm using: - Windows 8.1- OpenDBX dll files.- mysql-connector-c-6.1.5-win32- mysql 5.6.21- Pharo 3.0- OpenDBX driver stable package. I also attached the error pop-up and crash dump, please check. I'm looking forward for your advices. Best regards,Nico -- You received this message because you are subscribed to the Google Groups "DBXTalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. error.PNG (12K) Download Attachment crash.dmp (197K) Download Attachment If you reply to this email, your message will be added to the discussion below: http://forum.world.st/VM-Crash-tp4811903.html To start a new topic under DBXTalk, email ml-node+s1294792n3718169h10(a)n4.nabble.com To unsubscribe from DBXTalk, click here. NAML

March 16, 2015

[pharo-project/pharo-core] 51a168: 40560

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 51a1689721d6f24de32622fd1c19dd916ad11efe https://github.com/pharo-project/pharo-core/commit/51a1689721d6f24de32622fd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-16 (Mon, 16 Mar 2015) Changed paths: R Files.package/PharoFilesOpener.class/instance/open sources/openOrDownloadSources.st M Files.package/PharoFilesOpener.class/instance/public/sourcesFileOrNil.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script559.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script560.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40559.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40560.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/class/examples/example.st R Zinc-System-Support.package/extension/SmalltalkImage/instance/downloadSources.st R Zinc-System-Support.package/extension/SmalltalkImage/instance/sourcesDownloadClient.st Log Message: ----------- 40560 14383 VersionnerProjectBrowser>>example does not work https://pharo.fogbugz.com/f/cases/14383 15133 #downloadSources references PharoV30.sources https://pharo.fogbugz.com/f/cases/15133 http://files.pharo.org/image/40/40560.zip

March 16, 2015

[pharo-project/pharo-core]

by GitHub

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

March 16, 2015

[Pharo News] Pharo Sprints

by Jean-Christophe Bach

Hello, Pharo sprints are now planned: http://pharo.org/news/Pharo-Sprints The next sprint will be on Friday, 3rd April, at Inria Lille. -- Jean-Christophe Bach

March 16, 2015

Re: [Pharo-dev] ExtendedNumberParser now has its own repository

by Mariano Martinez Peck

On Sun, Mar 15, 2015 at 5:41 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > I did not want to lose the work of Nicolas Cellier around alternate number > parsers so I went > back in Pharo 30 and packaged them as a separate package (may be it was > already done but I could not find it). > > All the tests are green in Pharo 40. So I hope that everything is ok :) > > MCHttpRepository > location: 'http://www.smalltalkhub.com/mc/PharoExtras/ > ExtendedNumberParser/main' > user: '' > password: '' > > I did a configuration and published the code in the meta repository for > Pharo 40. > > Thanks Nicolas Cellier for the original code. > > Stef (I believe that we should pay attention that doing is difficult and > we should not lose good assets) > > Mariano can you verify if you can load it? > > Yes, I can load it. Regarding my own scenario, at least ExtendedNumberParser >> allowPlusSign answers true. But still, SqNumberParser >> exponentLetters does not contemplate upper cases. So I still need to override it to: exponentLetters ^'edqEDQ' -- Mariano http://marianopeck.wordpress.com

March 16, 2015

[pharo-project/pharo-core]

by GitHub

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

March 16, 2015

[pharo-project/pharo-core] 817960: 40559

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 817960d52ccb43204027697d5600d27040e111ff https://github.com/pharo-project/pharo-core/commit/817960d52ccb43204027697d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-16 (Mon, 16 Mar 2015) Changed paths: M ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/accessing/stable_.st M ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/baselines/baseline26_.st A ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/versions/version263_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script558.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script559.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40558.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40559.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/class/accessing/defaultPortForScheme_.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testDefaultPortUnknownScheme.st R Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testMissingScheme.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testNoScheme.st M Zinc-Tests.package/ZnClientTests.class/instance/testing/testLogging.st M Zodiac-Core.package/ZdcSecureSocketStream.class/instance/private in/fillBytes_startingAt_count_.st M Zodiac-Core.package/ZdcSimpleSocketStream.class/instance/private in/fillReadBuffer.st Log Message: ----------- 40559 15139 Update Zn+Zdc March 2015 https://pharo.fogbugz.com/f/cases/15139 http://files.pharo.org/image/40/40559.zip

March 16, 2015