- Pharo-dev - lists.pharo.org

Re: [Pharo-project] CI down?

by Camillo Bruni

On 2013-01-16, at 20:43, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Camillo Bruni-3 wrote >> right, slightly messy everything :/, uploading those as well right now > > Thanks again! One small thing... somehow an extra 14557 got saved /after/ > 14559, so the "latest" link now downloads 14557. If that last file is > removed, I think we'll have it... thanks for checking, I am happy if someone else appreciates so much tidy server ;)

Jan. 16, 2013

Re: [Pharo-project] CI down?

by Sean P. DeNigris

Camillo Bruni-3 wrote > right, slightly messy everything :/, uploading those as well right now Thanks again! One small thing... somehow an extra 14557 got saved /after/ 14559, so the "latest" link now downloads 14557. If that last file is removed, I think we'll have it... -- View this message in context: http://forum.world.st/CI-down-tp4659453p4663801.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 16, 2013

[Pharo-project] the monkey is back in town

by Camillo Bruni

the 100% smalltalk monkey is back at work: https://code.google.com/p/pharo/issues/detail?can=2&q=7268 let's hope it will stay like this for a while!

Jan. 16, 2013

[Pharo-project] Android DrGeo release 12.12

by Hilaire Fernandes

Dear Mr Blake, There is indeed a problem with GooglePlay marking incompatible Galaxy Note for app. built with large and xlarge screen size (range 4" to 10"). Previous DrGeo built was for normal, large, xlarge screen size and GalaxyNote was compatible. But several users keep insisting installing DrGeo on 3.5" screen size devices and rated very badly DrGeo because it was of course too tiny and unusable. Beside a direct link to the free app. built, I don't have solution: https://gforge.inria.fr/frs/?group_id=1308&release_id=7777 By the way, if you have another Android device compatible with DrGeo, can you rate DrGeo? It is very helpful. Thanks Hilaire Le 16/01/2013 17:21, blake a Ã©crit : > I saw your comment about the Note: When I try to install on the Note, > Play says it's not compatible. > > On Wed, Jan 16, 2013 at 6:10 AM, Hilaire Fernandes > <hilaire.fernandes(a)edu.ge.ch <mailto:hilaire.fernandes@edu.ge.ch>> wrote: > > Here it is > http://www.drgeo.eu/home/dr-geo-news/androiddrgeorelease1212 > > Thanks to Dimitry Golubovsky for his long support adapting the Android > Stack VM to my needs, the Pharo community to its supports and a > tribute > to Andreas Raabs who first ported the interpreter VM to Android. > > Hilaire > > >

Jan. 16, 2013

Re: [Pharo-project] [Update] Zinc-SSO OAuth 1.0 & OpenID Alpha Code & Live Demos

by Yanni Chiu

On 16/01/13 3:15 AM, Sven Van Caekenberghe wrote: > > The easiest solution is to switch to 2.0 where this repackaging conflict is already resolved. Porting my code to 2.0 makes it not the easiest solution at the moment. > For a non-interactive CI build based on Metacello loading, this should work: > > [ ConfigurationOfZincHTTPComponents load ] > on: MCMergeOrLoadWarning do: [ :warning | > Transcript crShow: 'Ignoring with Load anyway ', warning printString. > warning resume: true ]. That worked fine.

Jan. 16, 2013

[Pharo-project] Android DrGeo release 12.12

by Hilaire Fernandes

Here it is http://www.drgeo.eu/home/dr-geo-news/androiddrgeorelease1212 Thanks to Dimitry Golubovsky for his long support adapting the Android Stack VM to my needs, the Pharo community to its supports and a tribute to Andreas Raabs who first ported the interpreter VM to Android. Hilaire

Jan. 16, 2013

[Pharo-project] [update 2.0] #20476

by Marcus Denker

Jan. 16, 2013

[Pharo-project] [update 2.0] #20475

by Marcus Denker

Jan. 16, 2013

[Pharo-project] Fwd: Problem installing Neptuno

by Stephan Eggermont

Frank Church wrote: >Is it okay for me to say that something isn't right here? Yes, you are right. Unfortunately, changing this takes time. The infrastructure to do automated builds is currently Jenkins based, and does not provide automated feedback upstream (the blame plugin is not suitable for a project with as many downstream projects as Pharo). The number of projects with automated builds is also still limited, and there are a lot of projects with insufficient maintenance. As a result many packages don't get updated regularly, only when users notice something is wrong. The good news is that it is already a lot better than a few years ago, and we see much better stability/possibilities to change in the packages that are build automatically. Unfortunately, Neptuno is not yet build like that. Ideally, every Pharo project would have its own automated build server that provides (test) feedback upstream. Stephan Eggermont

Jan. 16, 2013

[Pharo-project] [update 2.0] #20474

by Marcus Denker

20474 ----- Issue 7263: clean spec from experimental packages http://code.google.com/p/pharo/issues/detail?id=7263& Issue 7259: Re-enable #signalProgress in MCHttpRepository>>#httpClient http://code.google.com/p/pharo/issues/detail?id=7259 Issue 7258: Simplify HTTP client usage in Unicode-Initialization http://code.google.com/p/pharo/issues/detail?id=7258 Issue 7241: Failing test: RBSmalllintTest>>testBadMessage Issue 7241: Failing test: RBSmalllintTest>>testBadMessage Issue 7047: Source pane font permanently changes after switching to Group view and selecting one http://code.google.com/p/pharo/issues/detail?id=7047 Diff information: http://ss3.gemstone.com/ss/Pharo20/Zinc-HTTP-MarcusDenker.336.diff http://ss3.gemstone.com/ss/Pharo20/Unicode-Initialization-MarcusDenker.4.di… http://ss3.gemstone.com/ss/Pharo20/Refactoring-Tests-Critics-MarcusDenker.8… http://ss3.gemstone.com/ss/Pharo20/Morphic-MarcusDenker.1323.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.742.diff

Jan. 16, 2013