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

[pharo-project/pharo-core] dfdd25: 30700

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: dfdd255891e92f21f81e1fcc63a2cd439a44e042 https://github.com/pharo-project/pharo-core/commit/dfdd255891e92f21f81e1fcc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-16 (Thu, 16 Jan 2014) Changed paths: M SUnit-UI.package/TestRunner.class/instance/actions/addDeclaredPackagesUnderTestTo_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script353.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30700.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30700 12656 Code coverage does not work anymore with specified #packageNamesUnderTest https://pharo.fogbugz.com/f/cases/12656 http://files.pharo.org/image/30/30700.zip

Jan. 16, 2014

[HELP] Phratch translation

by jannik.laval

Dear smalltalkers, phratchers and everybody interested to help Phratch development. We need you as an international community. Phratch needs your help to be multilingual. The most of work is already done, It is based on the Scratch work (Thank you for all the supported languages). Now, as Phratch has a lot of new features, we need to translate each of these new features. For each of the following languages (ar, bg, ca, cs, da, de, el, es, et, eu, fa, fi, fr_CA, gl, he, hr, ht, hu, id, is, it, ja_hira, ja, kn, ko, lt, mk, mn, mr, ms, ne, nl, no, pl, pt_br, pt, ro, ru, rw, sk, sl, sv, th, tr, uk, vi, zh_cn, zh_tw), we need to complete the lines available in the phratch issue tracker (https://code.google.com/p/phratch/issues/detail?id=120) You can post your work as a comment or send me a mail, I will then integrate it in Phratch. For each expression there is a msgid in english, that should not be changed. Then, there is a msgstr that should be complete in the specific language. All elements in the $$ (like $Number$) are variables, they should not be changed but they have to be integrated in your translation. For example, in french: === msgid "replace costume $Number$ with $NewCostume$" msgstr "remplacer le costume $Number$ avec $NewCostume$" === There is less than 130 small expressions. It is 1 or 2 hours of work, and it helps us a lot. Thank you for your help. Cheers, Jannik

Jan. 16, 2014

Re: [Pharo-dev] Pharo 3 bugs on Linux with openWorldWithSpec?

by Damien Cassou

On Sat, Jan 11, 2014 at 11:24 AM, kmo <voxkmp(a)gmail.com> wrote: > I have tried this on Windows 7 and I do not get this behaviour - the > ComposableModel fills the pharo window immediately and correctly. > > Any thoughts - should I be raising these as bugs? I confirm this behavior. This also happens with the Pharo Launcher. Someone told me it might be related to the VM not sending the events. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 16, 2014

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

by Damien Cassou

On Tue, Jan 7, 2014 at 6:08 PM, <btc(a)openinworld.com> wrote: > Now from the Start menu > All Programs > Pharo folder > I felt a bit awkward clicking on Pharo when I knew it was actually > PharoLauncher. I think it would be good to keep the distinction between > Pharo the programming environment and PharoLauncher the application. People > should not be developing their own applications inside Pharo Launcher, but > should be developing inside Pharo images started from Pharo Launcher. What is Pharo for you? What would you like to see when you click on a Pharo icon? A terminal saying that you didn't pass an image to the VM? For me, the entry point to Pharo should be the launcher. Just like the entry point to Eclipse is the workspace selector. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 16, 2014

Re: [Pharo-dev] [ANN] Pillar release 0.6

by Damien Cassou

On Wed, Jan 15, 2014 at 9:24 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > By the way, is there any change log available? none -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 16, 2014

Re: [Pharo-dev] [ANN] Pillar release 0.6

by Damien Cassou

On Wed, Jan 15, 2014 at 6:17 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I'm proud to announce the 0.6 release of Pillar, a syntax and > associated tools to write and generate documentation and books. I forgot to say who where the contributors, sorry about that: - Lukas Renggli created Pier a long time ago from which I extracted the document model, parser and many unit tests - Benjamin van Ryseghem contributed the Mardown exporter - Benjamin van Ryseghem helped me a lot about the command-line interface, the STON configuration interpreter and many other stuffs - Guillermo Polito fixed a bug - Steph for its continuous feedback from the beginning of the project and his original idea -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 16, 2014

Re: [Pharo-dev] after an software update the current changeset is unnamed - literally

by Marcus Denker

On 16 Jan 2014, at 08:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > We are doing a #cleanUpForRelease when loading the updateâ¦ > We could maybe > -> just call âSmalltalk #cleanUpâ on update (preserves the change sets) > -> do the full cleanup *only* on the CI server > > Yes, that sounds better. I will add an issue for that. > https://pharo.fogbugz.com/f/cases/12663/cleanUpForRelease-should-only-be-ru…

Jan. 16, 2014

Re: [Pharo-dev] after an software update the current changeset is unnamed - literally

by Marcus Denker

We are doing a #cleanUpForRelease when loading the updateâ¦ We could maybe -> just call âSmalltalk #cleanUpâ on update (preserves the change sets) -> do the full cleanup *only* on the CI server Yes, that sounds better. I will add an issue for that. The reason why I want to do a release clean is that the idea of the CI server is that we build *the artefact of release*, with not even the tiniest human intervention needed. In the past we finished, and then, completely burned out, called #cleanUpForRelease in the manual build of the download, â> everything broken. If we would have build the complete release automatically, that would never have happened. There is another proof: Of course what we do not do is anything related to .sources and .changes, and even condensing the changes file is brokenâ¦ Marcus On 15 Jan 2014, at 22:26, Nicolai Hess <nicolaihess(a)web.de> wrote: > This is what happens duing an update (30697 - 30698) > > save old cs Unnamed > new changes 30698-Pha-Update > new changes ScriptLoader30-MarcusDenker.853 > new changes 30698-Pha-Update > new changes Metacello-MC-MarcusDenker.696 > new changes 30698-Pha-Update > ChangeSet cleanup > new changes Unnamed > restore old cs <no name -- garbage?> > new changes <no name -- garbage?> > > the old changeset is saved > update stream starts-> > every package update creates a new changeset > scriptloader calls cleanup > update stream ends > old (cleanuped) cs is restored > > > now every change goes to this unnamed changeset. > If you open the changesorter it calls "ChangeSet current" > which creates a new unnamed ("Unnamed") changeset and > of course the prior changes are lost. > > > Is this inevitable?

Jan. 16, 2014

Re: [Pharo-dev] [ANN] Pillar release 0.6

by Torsten Bergmann

Jan. 16, 2014

Re: [Pharo-dev] [ANN] Pillar release 0.6

by Torsten Bergmann

Tudor wrote: >In case someone wants to load Pillar in a Pharo image, here is a load snipper: No need for that - it is also in the config browser. World Menu -> Configuration BrowserÂ -> Pillar

Jan. 16, 2014