June 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Please test Pharo 1.3!
by Marcus Denker July 1, 2011

July 1, 2011

Please test Pharo 1.3! There is no magic.. what is now here: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ Will be the release. Issues fixed until the released are just those that will be detected and fixed. There is no magic. For those who only run released software: Version Number is 1.3. Consider this released. There will be no RC. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

11 11

[Pharo-project] 1.3 profiler - nice stuff!
by Schwab,Wilhelm K July 1, 2011

July 1, 2011

Recent mention of the profiler prodded me to take a look at the profiler in 1.3. Very nice! Some "quick" changes that I think would be good: (1) Shout in the code pane; (2) Use tabs to show the gc data or the code; (3) Add a tab to show the result rather than using a modal notifier (which probably quickly gets dismissed, and then missed<g>). A non-quick change, if it's even possible... Some of the slickest Dolphin goodies in existence include: Ian Bartholomew's ChunkBrowser (Pharo's lost changes is close and useful, but not the same) and Profiler, the SUnitBrowser (nicer than the SUnit test runner), and Ghoul. Ghoul is well named. It presents Dolphin crash dumps in a debugger-like view: http://metagnostic.org/DolphinSmalltalk/Ghoul.html If there is, or could/should be enough data in a profile to do the same thing, it would make an interesting addition. Then interacting with the code includes the ability to see the values of variables. Bill

2 2

Re: [Pharo-project] Silly Tweet
by Stephan Eggermont June 30, 2011

June 30, 2011

Igor wrote: >On 29 June 2011 15:56, Schwab,Wilhelm K <bschwab at anest.ufl.edu wrote: >> Having an archive seems sufficient - those who need old versions for use or research can get them; they don't have to be clogging up the build server. Sounds great. > >Indeed. If people would like to use older releases, they should look >for another place, not for build server. >Since build server are there to build & test bleeding-edge (under >development) versions, but not ones which already released and years >old. Ok, so you simply do not want the builds to be used by others. That's fine. Stephan Eggermont

8 10

Re: [Pharo-project] Silly Tweet
by Marcus Denker June 30, 2011

June 30, 2011

On Jun 30, 2011, at 9:57 AM, Fernando Olivero wrote: > Why do people still use an older image? Even as older as Pharo1.1 and 1.2. > > It doesn't take much to update to Pharo1.3 or Pharo1.4, and its > totally worth the nuisance of updating a couple of classes references > and uses, because of the many many many improvements that get > integrated ( thanks for Marcus and Stef for the continuos improvements > integration and fixes) In a commercial setting, things are different... people need to really think hard to move to a new system. Time is money, bugs are expensive, there is always a deadline more important... One thing we want to do with Pharo over the next years is to actually make it easy to stay at an old version. And easy to gradually move to new versions. It's an interesting question how a language and system can support software evolution *for real*. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

Re: [Pharo-project] Silly Tweet
by Stephan Eggermont June 30, 2011

June 30, 2011

Stef wrote in response to my: >> Ok, so you simply do not want the builds to be used by others. >>That's fine. >why do you say that? Such a build server can have two purposes: - to directly help with the development of the software named in the build jobs; - it can provide a starting point for others to base their work on. Both are valuable, and it is acceptable if you want to want to focus on the first. For the second, as a commercial developer I have to be able to make my upgrade schedule as independent as possible from that of the projects I depend on. Depending on artifacts with an unknown availability is not possible. >What is the point to have a build server build all the time the same same same same same >same same image? A build server is used as we've learned there is no such thing as the same same image. There have been regressions because of vm changes or operating system updates, and I've seen 1.2.1 and 1.2.2. Also, while Pharo might be the same, both Zinc and Seaside change. Stephan

2 1

Re: [Pharo-project] Silly Tweet
by Marcus Denker June 30, 2011

June 30, 2011

On Jun 30, 2011, at 9:53 AM, Mariano Martinez Peck wrote: > > What I understood is that there could be activity and changes not in pharo, but in the other project that is build/tested in Pharo. > Say I am still quite developing Fuel, and I am commiting every day. No matter if it is on Pharo 1.2 or 1.3 what I want to say is that there is activity. > Ok, the resources let us to that with the latest Pharo, so that we can test both at the same time: pharo itself and the third party. > If you want third part with old pharo images, then you should get your own IC server. > It would be nice to have CI infrastructure available for everyone to just use. But this can not be me who edits text files by hand for such a service... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.4] #14021
by Marcus Denker June 30, 2011

June 30, 2011

14021 ----- Issue 4474: DNU when displaying search results in Comments http://code.google.com/p/pharo/issues/detail?id=4474 Issue 4473: About HTTP proxies, settings and MacOS http://code.google.com/p/pharo/issues/detail?id=4473 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Silly Tweet
by Marcus Denker June 30, 2011

June 30, 2011

On Jun 30, 2011, at 3:06 AM, Igor Stasenko wrote: > > Another aspect of it, that build servers has a limited space (Marcus > has to cut the number of builds , since they taking too much space). > While on gforge we can afford to keep much more. > Of course keeping latest 'frozen' build doesn't takes too much , > except of a little nuisiance after a couple of years > every time you open a jenkins, you will see a very long list of jobs, > where only few of them actually needed. > That's why i thinking that moving things to archive is preferable. > > In any way, i think everyone understands that nobody wants to hide > existing versions from public eyes. > Its only a question of finding appropriate place for them, after > development is done. Yes... we can keep 1.2 a bit. But what I don't want to keep are builds *on top* of 1.2. (the only left now is AIDA, but I removed already some). The amount of project on the build server is already very high: https://pharo-ic.lille.inria.fr/hudson/ and that with almost all 1.2 clients deleted and stuff moved to Jenkins: https://ci.lille.inria.fr/pharo/ But it's fun how something is seen as indespensable that we did not have some month ago (and that some people thought is not important *and* in the Squeak past even actively blocked from happening). How times change... ;-) What this shows is that what Jenkins/Hudson provide is essential, and we should think about to move that somehow deeper into our language... (nice research topic) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Pharo One Click 1.3 update: #13279 with Glorp
by Laszlo Zsolt Kiss June 30, 2011

June 30, 2011

aloha phaoers:) I have a problem with a Pharo 1.3 One ClickÂ update: #13279 with Glorp.I downloaded a clean Pharo 1.3 One Click today.Next I probed this: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfGlorpDBX'; load. ((Smalltalk at: #ConfigurationOfGlorpDBX) project version: '1.1') load I attached the error page. Please, help me. Thx Laszlo Zsolt

5 6

Re: [Pharo-project] About HTTP proxies, settings and MacOS
by Marcus Denker June 29, 2011

June 29, 2011

> Thanks Sven, that worked :) > Thanks Marcus for pointing us to the right place to fix it. > > Can we integrate it marcus for 1.3? > > Yes! please add something machine readable to the bug tracker issue: http://code.google.com/p/pharo/issues/detail?id=4473 -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

4 5