October 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] cd362a: 60263

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: cd362a678294bc04e142be303049939fdd04779b https://github.com/pharo-project/pharo-core/commit/cd362a678294bc04e142be30… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-19 (Wed, 19 Oct 2016) Changed paths: A AST-Core.package/RBArgumentNode.class/instance/testing/isBlockVar.st A AST-Core.package/RBProgramNode.class/instance/testing/isBlockVar.st A AST-Core.package/RBTemporaryNode.class/instance/testing/isBlockVar.st A Kernel.package/AdditionalMethodState.class/class/instance creation/new.st M SUnit-Core.package/TestExecutionEnvironment.class/instance/controlling/prepareForNewProcess_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60262.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60263.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60262.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60263.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Shout.package/SHRBTextStyler.class/instance/private/methodOrBlockArgStyleFor_.st A Shout.package/SHRBTextStyler.class/instance/private/methodOrBlockTempDeclStyleFor_.st A Shout.package/SHRBTextStyler.class/instance/private/methodOrBlockTempStyleFor_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitArgumentNode_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitSequenceNode_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitTemporaryNode_.st M Spec-Core.package/SpecDialogWindow.class/instance/accessing/model_.st Log Message: ----------- 60263 17743 Focusorder is broken with Spec dialogs https://pharo.fogbugz.com/f/cases/17743 19194 Failing Process tests while using FullBlockClosure https://pharo.fogbugz.com/f/cases/19194 19216 Add styler support for different temp vars (method/block arg/temps) https://pharo.fogbugz.com/f/cases/19216 http://files.pharo.org/image/60/60263.zip

Oct. 19, 2016

Pharo Monthly Newsletter: How to subscribe

by Marcus Denker

Hi, We are sending out a monthly (with a summer breakâ¦) newsletter. Of course if you read all the mails here, there is nothing new, but it is fun to get a mail every month with pointers to projects and news that one might have missed. Subscribe here: http://eepurl.com/byhgL9 Marcus

Oct. 19, 2016

Athens current version in Pharo 6.0

by Nicolai Hess

please! anyone! 18445 <https://pharo.fogbugz.com/f/cases/18445/ConfigurationOfAthens-is-not-in-syn…> ConfigurationOfAthens is not in sync with current Pharo packages 18657 <https://pharo.fogbugz.com/f/cases/18657/Rendering-text-in-athens-is-broken>Rendering text in athens is broken I don't know what to do with the current version.

Oct. 18, 2016

Re: [Pharo-dev] Pharo behind ALLSTOCKER marketplace

by Torsten Bergmann

"Masashi UMEZAWA" wrote: > From Torsten, I've received a request to post about some technical > details of ALLSTOCKER (http://pharo.org/success/AllStocker) . > I hope these notes will be interesting to Pharo web developers. Thanks a lot! It gives again more insights into what can used and what can be achieved with Pharo technologies and this is really good. Bye T.

Oct. 18, 2016

[pharo-project/pharo-core]

by GitHub

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

Oct. 18, 2016

[pharo-project/pharo-core] 905565: 60262

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9055659a7ec02b5755dca212ee0bfae92b9664c8 https://github.com/pharo-project/pharo-core/commit/9055659a7ec02b5755dca212… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-18 (Tue, 18 Oct 2016) Changed paths: M Kernel.package/Float.class/instance/comparing/closeTo_.st A Kernel.package/Float.class/instance/comparing/closeTo_precision_.st M Kernel.package/Number.class/instance/comparing/closeTo_.st A Kernel.package/Number.class/instance/comparing/closeTo_precision_.st M Refactoring-Tests-Core.package/RBNamespaceTest.class/instance/class tests/testModelImplementorsSenders.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60261.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60262.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60261.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60262.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60262 19212 Namespace and BrowserEnvironment both now select meta class methods (update test case) https://pharo.fogbugz.com/f/cases/19212 19213 closeTo:precision: should be introduced in Float https://pharo.fogbugz.com/f/cases/19213 http://files.pharo.org/image/60/60262.zip

Oct. 18, 2016

Re: [Pharo-dev] Pharo behind ALLSTOCKER marketplace

by FranÃ§ois Stephany

This is a great overview, thanks for sharing. On Mon, Oct 17, 2016 at 3:05 PM, Masashi UMEZAWA <masashi.umezawa(a)gmail.com> wrote: > Hi all, > > From Torsten, I've received a request to post about some technical > details of ALLSTOCKER (http://pharo.org/success/AllStocker) . > I hope these notes will be interesting to Pharo web developers. > > - Seaside / Teapot > We are using Seaside as a main framework for ALLSTOCKER marketplace. > Seaside's component architecture is great for extending application in > an organized way. > ALLSTOCKER prototype was originally composed of only 3 class > categories. Now these were gradually grown to 70 categories. But we > still feel that they are manageable. > We also use Teapot for building Web-based API in a quick way. Recently > we've built webhook handlers for integration with other services. > > - Templating with Mustaside > We need a lot of responsive-design web pages for supporting various > mobile devices. (It is important especially for Southeast Asian > countries, where tablets are popular than PCs). > We would like to adopt existing Twitter Bootstrap templates for saving > time. So, Mustaside was our choice. > http://smalltalkhub.com/#!/~MasashiUmezawa/Mustaside > Before Mustaside, there were a lot of noisy #div: sends in our code. > Now they are gone. > > - Localization > Our business target is world-wide. So localization is very important > topic. Currently ALLSTOCKER supports 4 languages and we will add > Chinese languages soon. > Translation strings are not only in Smalltalk code, but also in > Mustache templates. So we selected Soup for extracting translatable > strings in those templates. > http://smalltalkhub.com/#!/~PharoExtras/Soup > For managing translations, we use Gettext package. > http://smalltalkhub.com/#!/~PharoExtras/Gettext > > - Databases > For transactional data, we chose Glorp. Although there are mapping > costs, we prefer RDB (Postgres). It is reliable for handling precious > order-related data. > However, for supporting complex search of machines, we use Neo4j - a > graph database. It supports very powerful query language called > Cypher. > We can avoid complex table joins and get aggregated results faster. > http://smalltalkhub.com/#!/~MasashiUmezawa/Neo4reSt > > - Keyword search > ALLSTOCKER supports free keyword search. We selected Elasticsearch for > search-engine. Elasticsearch has elaborated searching facilities and > those are easily accessible via REST API. > We have extended the existing Elasticsearch client for Pharo 5. > https://github.com/newapplesho/elasticsearch-smalltalk > > - Deployment > We are using AWS Elastic Load Balancer and running Nginx as a > front-end web server. Two back-end Pharo images are running and > load-balanced with sticky sessions. > It was sort of difficult to find the appropriate simultaneous number > of database connections and Pharo processes. We feel ALLSTOCKER is > pretty stable for now, but we need to adjust more for expanding our > services. > > Best regards, > -- > [:masashi | ^umezawa] > >

Oct. 18, 2016

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sven Van Caekenberghe

> On 18 Oct 2016, at 03:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> You could try doing... allowComplexMapKeys: true >> ... > > Hmm, if the default writing may use complex keys, shouldn't the default > reading do the same? I found it jarring to write using the defaults, and > then have the default read fail! Yes, you are right, the default should be true, I can't remember why I did not yet do it, it feels as if I am forgetting something, don't see all the consequences. > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919141.… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 18, 2016

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > allowComplexMapKeys: true BTW that worked. Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919142.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 18, 2016

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > You could try doing... allowComplexMapKeys: true > ... Hmm, if the default writing may use complex keys, shouldn't the default reading do the same? I found it jarring to write using the defaults, and then have the default read fail! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919141.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 18, 2016