- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Oct. 31, 2014

[pharo-project/pharo-core] 787596: 40343

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 787596aa8a0f20acb55a923f9afa63ec22417f9d https://github.com/pharo-project/pharo-core/commit/787596aa8a0f20acb55a923f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-31 (Fri, 31 Oct 2014) Changed paths: M Polymorph-Widgets.package/ThemeIcons.class/class/instance creation/current.st M Polymorph-Widgets.package/ThemeIcons.class/class/instance creation/current_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script343.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40343.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40343 Current http://files.pharo.org/image/40/40343.zip

Oct. 31, 2014

LRUCache for high latency stuff

by Thierry Goubier

Hi all, I tried to use LRUCache for some application of mine with a two stages, over-the-internet data requests, and I couldn't find a way of using it. My use case was: - retrieve some data with high latency (over 10 seconds) - in a interactive application, where I need to be able to continue while the data is being loaded. So I designed it in two stages: - Have a cache - if the data isn't in the cache -- trigger a load with a fork -- put some temporary data in the cache (something which says loading) -- continue - When the data load is terminated -- replace the cached temporary data with the final version. The thing is that I couldn't do the last one with the LRUCache (there is not at:put:, only a at:ifAbsentPut: []). Did I miss something? Thierry

Oct. 31, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 31, 2014

[pharo-project/pharo-core] c6c309: 40342

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: c6c309f9fa7f1093c0e6171ee00eec329230156a https://github.com/pharo-project/pharo-core/commit/c6c309f9fa7f1093c0e6171e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-31 (Fri, 31 Oct 2014) Changed paths: M Polymorph-Widgets.package/ThemeIcons.class/definition.st M Polymorph-Widgets.package/ThemeIcons.class/instance/initialization/initializeIcons.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script342.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40342.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40342 14326 ThemeIcons should use LRUCache https://pharo.fogbugz.com/f/cases/14326 14357 add Current class var to ThemeIcons https://pharo.fogbugz.com/f/cases/14357 http://files.pharo.org/image/40/40342.zip

Oct. 31, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 31, 2014

[pharo-project/pharo-core] 500663: 40341

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 500663af6f157acf73edc166a46f5be4e8868ac6 https://github.com/pharo-project/pharo-core/commit/500663af6f157acf73edc166… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-31 (Fri, 31 Oct 2014) Changed paths: M NautilusCommon.package/AbstractKeyPressedPlugin.class/README.md M NautilusCommon.package/AbstractNautilusPlugin.class/README.md M NautilusCommon.package/AbstractNautilusPlugin.class/class/information/description.st M NautilusCommon.package/AbstractNautilusPlugin.class/class/information/possiblePositions.st M NautilusCommon.package/AbstractNautilusPlugin.class/class/position/defaultPosition.st M NautilusCommon.package/AbstractNautilusPlugin.class/instance/display/display.st M NautilusCommon.package/AnnotationPanePlugin.class/instance/private/buildString.st A NautilusCommon.package/CountingKeyPressedPlugin.class/README.md A NautilusCommon.package/CountingKeyPressedPlugin.class/class/information/description.st A NautilusCommon.package/CountingKeyPressedPlugin.class/class/position/defaultPosition.st A NautilusCommon.package/CountingKeyPressedPlugin.class/definition.st A NautilusCommon.package/CountingKeyPressedPlugin.class/instance/accessing/stringMorph.st A NautilusCommon.package/CountingKeyPressedPlugin.class/instance/accessing/stringMorph_.st A NautilusCommon.package/CountingKeyPressedPlugin.class/instance/announcement/keyPressed_.st A NautilusCommon.package/CountingKeyPressedPlugin.class/instance/display/display.st A NautilusCommon.package/CountingKeyPressedPlugin.class/instance/initialization/initialize.st R NautilusCommon.package/DummyKeyPressedPlugin.class/README.md R NautilusCommon.package/DummyKeyPressedPlugin.class/class/information/description.st R NautilusCommon.package/DummyKeyPressedPlugin.class/class/position/defaultPosition.st R NautilusCommon.package/DummyKeyPressedPlugin.class/definition.st R NautilusCommon.package/DummyKeyPressedPlugin.class/instance/accessing/stringMorph.st R NautilusCommon.package/DummyKeyPressedPlugin.class/instance/accessing/stringMorph_.st R NautilusCommon.package/DummyKeyPressedPlugin.class/instance/announcement/keyPressed_.st R NautilusCommon.package/DummyKeyPressedPlugin.class/instance/display/display.st R NautilusCommon.package/DummyKeyPressedPlugin.class/instance/initialization/initialize.st M NautilusCommon.package/DummyPackageSelectedPlugin.class/README.md M NautilusCommon.package/DummyPackageSelectedPlugin.class/definition.st R NautilusCommon.package/IgorsPlugin.class/README.md R NautilusCommon.package/IgorsPlugin.class/class/as yet unclassified/description.st R NautilusCommon.package/IgorsPlugin.class/definition.st R NautilusCommon.package/IgorsPlugin.class/instance/as yet unclassified/buildString.st M NautilusCommon.package/KonamiCodePlugin.class/README.md M NautilusCommon.package/KonamiCodePlugin.class/definition.st M NautilusCommon.package/MondrianPlugin.class/README.md M NautilusCommon.package/MondrianPlugin.class/definition.st M NautilusCommon.package/NautilusBreadcrumbsPlugin.class/class/information/description.st M NautilusCommon.package/PackageTasksPlugin.class/instance/announcement/packageSelected_.st M NautilusCommon.package/PackageTasksPlugin.class/instance/display/buildTaskList.st M NautilusCommon.package/PackageTasksPlugin.class/instance/display/updateMethodSelection_.st M NautilusCommon.package/URLPlugin.class/instance/private/buildString.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script341.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40341.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SlotTests.package/SlotAnnouncementsTest.class/instance/helpers/subscribeOn_.st M System-Announcements.package/AnnouncementLogger.class/instance/as yet unclassified/subscribeTo_.st Log Message: ----------- 40341 14356 Replace Announcer>>#on:send:to:s senders in System-Announcements https://pharo.fogbugz.com/f/cases/14356 14355 Replace Announcer>>#on:send:to:s senders in SlotTests https://pharo.fogbugz.com/f/cases/14355 14352 Cleaning, fixing and documenting NautilusPugin https://pharo.fogbugz.com/f/cases/14352 http://files.pharo.org/image/40/40341.zip

Oct. 31, 2014

Re: [Pharo-dev] VersionnerRepositoriesManager - Why clear okAction?

by Christophe Demarey

Hi Sean, Le 23 oct. 2014 Ã 23:16, Sean P. DeNigris a Ã©crit : > No class is safe from my wrath he he... > > VersionnerRepositoriesManager class>>#open > | dialog | > dialog := remotesUI openDialogWithSpec. > dialog okAction: [ ] > > - why were we wiping the okAction? "dialog okAction: [ ]" does not reveal > any intention. At minimum, a comment would be good I fully agree. I wrote the code some months ago and I forgot the reason ... I think the setting of the okAction is useless. I often put a comment but i miss this one. Thanks for the feedback. > - it would be good to return something here so users can customize more > easily. Even though this is tightly integrated with Versionner, a tiny bit > of care makes the system more easily extensible. We should record some > patterns here... Maybe what you need is RemotesManager. I extracted this component from Komitter.

Oct. 31, 2014

Re: [Pharo-dev] Time Series in Smalltalk

by Serge Stinckwich

> On 31 Oct 2014, at 10:50, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Dear Serge, > Bonjour Vincent, > That's nice but I will need more statistical functions to calculate autocorrelations. Yes having some statistical functions and tests is definitively something we are looking for SciSmalltalk. > These functions are already implemented in R (http://www.r-project.org/) > So, there is two solutions: > - As the sources are open, implement them in Pharo (but it is some thousands of linesâ¦) This is R code ? Do you have a link to this source ? Iâm also interested to have a native solution in Pharo. Maybe we can join our forces ;-) > - With nativeboost, use the R libs (written in C) > > As I prefer the second solution, I began to write some code with native boost and it seems to work well. Iâm a little bit worried with performance issue for the second solution ;-) or R libs are not written in R ? > I can add them in SciSmalltalk package if I have the rights. But I don't know how to package the R libraries for the different OSâ¦ > Yes, this is a nice idea. We can give you access to the SciSmalltalk repo. Please join the ml: https://groups.google.com/forum/#!forum/scismalltalk What could be nice is write tests so we can use this tests latter if we want to have a native solution. Thank you. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Oct. 31, 2014

Re: [Pharo-dev] Time Series in Smalltalk

by Blondeau Vincent

Dear Serge, That's nice but I will need more statistical functions to calculate autocorrelations. These functions are already implemented in R (http://www.r-project.org/) So, there is two solutions: - As the sources are open, implement them in Pharo (but it is some thousands of lines...) - With nativeboost, use the R libs (written in C) As I prefer the second solution, I began to write some code with native boost and it seems to work well. I can add them in SciSmalltalk package if I have the rights. But I don't know how to package the R libraries for the different OS... Regards, Vincent Blondeau -----Message d'origine----- De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Serge Stinckwich EnvoyÃ© : vendredi 24 octobre 2014 09:56 Ã : Pharo Development List Objet : Re: [Pharo-dev] Time Series in Smalltalk > On 23 Oct 2014, at 14:52, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi ! > Dear Vincent, > > > I am looking for a time series library available for Pharo. > > Serge Stinckwich asked the same thing a year ago (http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-February/07…) and I would know whether any improvement has been made since? > > We started a really simple implementation of time series. Look at the class : KETimeSeries and KETimeSeriesTest in this repository: http://smalltalkhub.com/#!/~UMMISCO/Kendrick Please feel free to extract these classes and extend them. Maybe we can move them in the SciSmalltalk repository. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Oct. 31, 2014