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

Re: [Pharo-dev] Updated XMLPullParser for SIXX?

by stepharo

Check because Hernan did something and there is a chapter on pfte On 28/7/14 14:52, Mariano Martinez Peck wrote: > Hi guys, > > I was reading this post: > http://kentreis.wordpress.com/2009/06/01/deep-sixx-with-xml-pull-parser/ > > about using a XMLPullParser with SIXX. This is from 2009 and I guess I > guess SIXX and XML parsers have been changing in the last years. > So...does somebody know if there is an updated version of a XML Pull > Parser? And second question, any integration with SIXX? > > Thanks in advance, > > -- > Mariano > http://marianopeck.wordpress.com

July 28, 2014

Re: [Pharo-dev] Configuration readonly archives

by stepharo

BTW an important point. We cannot load any moose versions of the past (except the ones we snapshotted), to me this is a sign of problems. never be able to get back in a previous state is a problem. Stef

July 28, 2014

Re: [Pharo-dev] Configuration readonly archives

by stepharo

We will discuss that on a black board at ESUG. A release is a release and when you release code you do not want to rely on something that somewhere could change. Christophe told me that they are doing that in Java world and this is working. Now for development you load your baseline and you load symbolic version of foreign code. Stef >> I agree. This is why I also think that released should point to version >> and not symbolic version. > I strongly disagree. A configuration should only change when > there is a meaningful change. Changes in dependencies that do not > change relevant behavior should not propagate. > > We achieve that by using #'releasex.x' style versioning. Changes that > are not supposed to change observable behavior and bug fixes get > new numbered versions within the release. > #development versions are updated in place This is the purpose of symbolic versions to avoid propagation. > > In Moose we did not encounter a situation where a month-old numbered > version configuration was still loadable in the latest Pharo. ??? > > There is a use case for snapshots of exact versions. They don't belong > in configurations. I do not get what you mean. Now if I want to deliver exactly the same version I do not see how we can avoid versions. And this "nothing observable changes" is a nice idea but what I see is that often pharo breaks because of a nothing observable change. > > Focussing improvements in Versioner on releasing more often numbered > versions is counter productive. It just generates more work to keep > configurations working. I do not think so - in dev you use baseline for you and development for foreign code - when releasing you freeze. With nice tool support I do not see why this would not work. > > I have been fixing lots of configurations on ci, and nearly all problems > have to do with not using #'releasex.x' style symbolic versioning. I did not get it so you should explain it better :) > There are two problems: > - Configurations using numbered versions. They break as soon as a > dependent project changes functionality or does a bug fix, often as > a result of underlying code in Pharo changing. > - Configurations using #stable, where the dependent project does > a new release. Most of the projects on Jenkins are not there to work against release but day to day changes in this case they should load latest. > > Now Seaside, Grease and Magritte have switched to this style of > versioning, the number of problems has reduced drastically. > > Stephan > > > >

July 28, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

looks like for some reason all my new commits fail to build the book in gitbook.io this is the error I am getting Tweaking book.json Failed to install extra plugins, maybe none to install Building Site, will upload Starting build ... Error Output /usr/bin/do-website: line 48: 34 Segmentation fault (core dumped) gitbook build in this link http://help.gitbook.io/book/errors.html says its a package.json file, dependencies, maybe pillar fails to build that file properly ? anyone else experiencing such a problem ? On Sun, Jul 27, 2014 at 8:39 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > no idea how to do that Serge. git repo url looks to me read only does not > allow me to modify it. It says I need to authenticate using the mail and > password from setting but does not tell how. I also cannot add webhooks for > UPBE git repo, I tried to fork to my own githube account still same > problem. > > > On Sun, Jul 27, 2014 at 6:59 PM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> Great work Kilon ! >> >> Apparently, you have to remove .git in the name of your git repo (look >> at the settings of your book), because everytime you click on star or >> watch icon there is a wrong URL. >> >> Regards, >> >> On Sun, Jul 27, 2014 at 5:53 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> > another stupid mistake I forgot to add the book. Ok all fixed. Book is >> > uploaded and here is the link >> > >> > https://www.gitbook.io/book/kilon/pbe >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >> >

July 28, 2014

Re: [Pharo-dev] Operating Smalltalkhub from Pharo

by kilon alios

thanks damien and esteban :) On Mon, Jul 28, 2014 at 2:56 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > https://ci.inria.fr/pharo-contribution/job/SmalltalkHub/? > > There is an undocumented REST API that the Amber client uses. > > On Sun, Jul 27, 2014 at 2:23 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > I wonder if there is a way to operate smalltalkhub from pharo. What would > > interest me is to browser smalltalkhub from pharo and do anything I can > do > > from the website with pharo. > > > > I am new with these things so I assume Zinc would be useful here , no ? > > > > is there any docs for smalltalkhub api ? > > > > Anyone tried something similar before ? > > > > I tried to load Smalltalkub configuration but it looks like that the > config > > does not define neither a stable or a developement version . > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

July 28, 2014

Re: [Pharo-dev] [Vm-dev] Delay machinery (was Re: Suspending a Process)

by Ben Coman

July 28, 2014

Re: [Pharo-dev] [Moose-dev] rethinking the print it action in Pharo

by Johan Fabry

That looks like a cool re-imagining of the print-it ! On Jul 27, 2014, at 7:33 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > In the course of revamping the Pharo environment, we stumbled across the print it action and we (Andrei and I) decided to rethink it. > <new-print-it.png> > > You can find more details here: > http://www.humane-assessment.com/blog/rethinking-print-it-in-pharo > > Let us know what you think. > > Cheers, > Doru > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

July 28, 2014

[Pharo4][Issue Tracker] All Failing added to the Issue tracker

by Marcus Denker

Hi, All failing 10 failing tests: https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/last… now have an entry on the issue tracker https://pharo.fogbugz.com (the Zinc related ones are already fixed upstream, I wanted to have already merged thatâ¦) Marcus

July 28, 2014

[pharo-project/pharo-core]

by GitHub

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

July 28, 2014

[pharo-project/pharo-core] 79ad77: 40134

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 79ad7763ec59235aadd6f11c299f271b9dde97e0 https://github.com/pharo-project/pharo-core/commit/79ad7763ec59235aadd6f11c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-28 (Mon, 28 Jul 2014) Changed paths: M Kernel.package/ProtoObject.class/instance/pointing to/pointersToExcept_.st M Refactoring-Core.package/RBMoveMethodToClassRefactoring.class/instance/printing/storeOn_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script134.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40134.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40134 13717 testUndeclared failing https://pharo.fogbugz.com/f/cases/13717 - recompile Image http://files.pharo.org/image/40/40134.zip

July 28, 2014