February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Please port external libraries & frameworks to Pharo 3.0 NOW !

by Stephan Eggermont

Sven wrote: >That is great, Stephan! > >Would you say that all the important libraries that you depend on in Pharo 2.0 are already available for Pharo 3.0 or not ? Which ones are missing >from your standpoint ? Pier3 with add-ons. I want to be able to deploy a Pier website like you showed in https://github.com/svenvc/zinc/blob/master/build-and-deploy-1st-webapp/buil… (and then need to solve the issue of allowing comments on the production site to propagate back to development, but that is a nice to have). Diego and I did some work on the code based pier exporter and are now fixing configurations. Lots of configurations... Stephan

Feb. 7, 2014

Re: [Pharo-dev] Please port external libraries & frameworks to Pharo 3.0 NOW !

by Sven Van Caekenberghe

That is great, Stephan! Would you say that all the important libraries that you depend on in Pharo 2.0 are already available for Pharo 3.0 or not ? Which ones are missing from your standpoint ? On 07 Feb 2014, at 12:22, Stephan Eggermont <stephan(a)stack.nl> wrote: > ConfigurationOfForum done. > > Stephan >

Feb. 7, 2014

Re: [Pharo-dev] Please port external libraries & frameworks to Pharo 3.0 NOW !

by Stephan Eggermont

ConfigurationOfForum done. Stephan

Feb. 7, 2014

Please port external libraries & frameworks to Pharo 3.0 NOW !

by Sven Van Caekenberghe

Dear fellow Pharoers, Pharo 2.0 was released in March 2013, after which development of Pharo 3.0 started. Since December 2013 we stopped adding new features and started concentrating on fixing bugs. We plan to release Pharo 3.0 in March 2014. You can help: please port external libraries & frameworks to Pharo 3.0 NOW, before it is released, not after. You can help us tremendously by doing this. Together we can improve the quality and polish for a great release. Today we already have quite some external libraries, frameworks and applications running successfully in Pharo 3, among them large ones like Moose (https://ci.inria.fr/moose/job/moose-5.0/) and Seaside (https://ci.inria.fr/pharo-contribution/job/Seaside/) But we need more and we need people collaborating, because real life projects have lots of dependencies that need to be available. Luckily there is a CI infrastructure available to help you. You should also follow some conventions to fit into the ecosystem. - have good unit tests - use Monticello for source code management - store code publicly, preferably at http://www.smalltalkhub.com/ - use Metacello for package and configuration management - add your configuration where the configuration browser can find it, at least in http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main - use the CI infrastructure at https://ci.inria.fr/pharo-contribution/ For example, Neo-CSV, can be loaded in Pharo 3.0 using its Metacello configuration with just one click on 'Install Stable Version': The code lives in various repositories, including on StHub, at http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo There is a CI job checking all unit tests each time either Pharo 2.0, Pharo 3.0 or the library code changes, https://ci.inria.fr/pharo-contribution/job/NeoCSV/ and reporting all failures immediately. You can test both stable and development (or bleedingEdge) versions for a real build matrix. And there is external documentation, https://github.com/svenvc/docs/blob/master/neo/neo-csv-paper.md ;-) Even if you are not the original author, but just a user of (a) particular package(s), it would be useful if you tried loading the package(s) you need and see if all is well. Each action, however small, counts. Give feedback now. Remember, it is your Pharo. Thank you! On behalf of the whole team, Sven

Feb. 7, 2014

Please help beta test Pharo 3.0 NOW !

by Sven Van Caekenberghe

Dear fellow Pharoers, Pharo 2.0 was released in March 2013, after which development of Pharo 3.0 started. Since December 2013 we stopped adding new features and started concentrating on fixing bugs. We plan to release Pharo 3.0 in March 2014. You can help: please help beta test Pharo 3.0 NOW, before it is released, not after. You can help us tremendously by doing this. Together we can improve the quality and polish for a great release. http://www.pharo-project.org/pharo-download/beta-3-0 http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher http://get.pharo.org The mailing lists are one way to give feedback, but it is even better to report problems as issues. https://pharo.fogbugz.com/ Remember, it is your Pharo. Thank you! On behalf of the whole team, Sven

Feb. 7, 2014

Re: [Pharo-dev] Fwd: working on pharo 3.0?

by Guillermo Polito

The slaves are dead. I will talk with christophe as soon as i arrive to the office :) Le 7 fÃ©vr. 2014 05:42, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > It seems that the jobs do not manage to finish :( > > Doru > > > On Thu, Feb 6, 2014 at 1:47 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> The ci jobs :). I didn't want to announce them (and actually i didn't do >> it properly) until having them finished at some good degree. >> >> The ci jobs for dbxtalk will give the people doing dbxtalk so muuuuch air >> (no more manual testing on 3 platforms x 5+ different database engines per >> change). >> + binaries available and built every day >> >> >> >> >> On Thu, Feb 6, 2014 at 1:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> What was a bit secret? >>> >>> Doru >>> >>> >>> On Thu, Feb 6, 2014 at 12:25 PM, Guillermo Polito < >>> guillermopolito(a)gmail.com> wrote: >>> >>>> Well, it was a bit secret, but I was starting on my free time to setup >>>> some ci jobs to build automagically all the opendbx libraries + test them. >>>> >>>> https://ci.inria.fr/dbxtalk/ >>>> >>>> Now my problem is that my free time for hacking on non phd stuff -> 0 >>>> lately... :/ >>>> >>>> >>>> On Thu, Feb 6, 2014 at 12:13 PM, Torsten Bergmann <astares(a)gmx.de>wrote: >>>> >>>>> And Sven insist on still cutting/copying/evaluating one-liners >>>>> in the age of a configuration browser where loading is just mouse >>>>> clicking ;) >>>>> >>>>> But putting jokes aside - it would IMHO be really important to >>>>> have DBXTalk running for Pharo 3.0. Without good database >>>>> support one would loose any argument for Pharo in the >>>>> business world... >>>>> >>>>> It would also be a real bonus if the necessary support DLL's/shared >>>>> libs >>>>> could be easily provided or installed. >>>>> >>>>> For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides >>>>> the current binaries on Github https://github.com/mumez/PunQLite >>>>> >>>>> Or the NaCl (a binding for Crypto-Nacl library) directly downloads >>>>> and installs them when you install the config (see ConfigurationOfNacl >>>>> in >>>>> config browser of Pharo 3.0). >>>>> >>>>> Easy access without much hazzle is always a plus... install, connect to >>>>> the DB and go! >>>>> >>>>> Thx >>>>> T. >>>>> >>>>> > Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr >>>>> > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >>>>> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>>>> > Cc: dbxtalk(a)googlegroups.com >>>>> > Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0? >>>>> > >>>>> > Ah, it is just because you insist on using old school two line code >>>>> ;-) >>>>> > >>>>> > On 06 Feb 2014, at 11:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> > >>>>> > > Gofer new >>>>> > > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >>>>> > > package: 'ConfigurationOfOpenDBXDriver'; >>>>> > > load >>>>> > > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge >>>>> > > >>>>> > >>>>> > Gofer new >>>>> > smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >>>>> > configurationOf: 'OpenDBXDriver'; >>>>> > loadVersion: #bleedingEdge. >>>>> > >>>>> > Just joking, >>>>> > >>>>> > Sven >>>>> > >>>>> > >>>>> >>>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Feb. 7, 2014

Support for demos

by Stephan Eggermont

Iâve added an up to date build of a Pharo 3 version of the workshop image Iâve used at FOSDEM. The workshop itself was given with a Moose 5. Please feel free to (re)use. https://ci.inria.fr/pharo-contribution/job/Forum/ In a workspace, do FOTutorial open for the participant version and FOTutorial openPresentation for a presenter version with larger fonts. To see some roassal visualizations related to code quality, do FOBrowser open Stephan More tutorials, with exercises integrated in the tutorial browser, can be found in http://ss3.gemtalksystems.com/ss/SpaTutorial

Feb. 7, 2014

[pharo-project/pharo-core]

by GitHub

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

Feb. 7, 2014

[pharo-project/pharo-core] 3ff7d6: 30749

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 3ff7d66311d1ca89052ba3942b2b9c720977e658 https://github.com/pharo-project/pharo-core/commit/3ff7d66311d1ca89052ba394… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-07 (Fri, 07 Feb 2014) Changed paths: M SUnit-Core.package/UITestCase.class/instance/running/runCase.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script402.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30749.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30749 12825 SimulateMouseSpecification>>testSimulateClick https://pharo.fogbugz.com/f/cases/12825 http://files.pharo.org/image/30/30749.zip

Feb. 7, 2014

Re: [Pharo-dev] What will change in Pharo with Spur the new Cog memory manager ...

by Stephan Eggermont

ClÃ©ment wrote: >I wouldn't say no problem, I would say that images up to 1 Gb should be usable and should behave much better than they used to due to the lack >of full GC pauses. Now that's the theory we need to make it real and this summer we will see... I'm a bit confused by the term 'big image'. I regularly use 1GB images with cog, and they stay responsive enough for development work. As long as there is enough free space that the full gc doesn't have to happen very often, it's ok. Current home machines work with 32 GB ram though, so I hope the gc can handle somewhat larger images? Stephan Eggermont

Feb. 7, 2014