- Pharo-dev - lists.pharo.org

Re: [Pharo-project] pharo-seed and pharo
by Marcus Denker March 2, 2012

March 2, 2012

On Mar 2, 2012, at 10:06 AM, Tudor Girba wrote: > Hi, > > I believe everyone agrees that one important goal in Pharo is to get > to a small code/kernel/seed. During the Pharo Sprint at Bern we saw > that the only reason for now having a unified image is just a > temporary convenience that stems from two things: > 1. Until Pharo 1.3, the core team worked in the core image, and this > was frustrating because they were missing proper tools > 2. After 1.3, building a pharo image out of a seed image was perceived > as being too long and not fitting for the process of integration > > It's clear that the core team needs development tools. However, we > think that 2 can be actually quite cheap if the build starts from the > latest seed, and not from the original seed of 1.4 as it currently > seem to happen. Nope, 1.3 is build from the very latest 1.3Core. Build takes 42 Minutes. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] odd bug in Squeak 4.3, also in Pharo 1.3?...
by Marcus Denker March 2, 2012

March 2, 2012

On Mar 2, 2012, at 4:25 AM, Lawson English wrote: > I was creating a new video tutorial to show how to find all comments in all classes but I'm getting errors in both Squeak 4.3 and Pharo 1.3. > > In Squeak 4.3, the error is: Key not found: Comment > > In Pharo 1.3, the error is: Improper store into indexable object. commentsIn: returns a collection, not a string. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] leaking semaphores
by Milan Mimica March 2, 2012

March 2, 2012

Hi! I am continuing my search of why does my remote headless image run out of semaphores eventually. I have found the culprit this time. It is most definitively related to RFBServer. I am using version 38 from http://source.lukas-renggli.ch/unsorted. Every time I disconnect from the image with my VNC client (I click the disconnect icon) the count of leaked semaphores increases by 3. Since there is 3 semaphores per socket, I guess this is related to sockets. Now what do I do? What do I check? I am running the a Pharo image and Cog I got from CI server yesterday. This is the script I use to count leaked semaphores: | semaphores arr res | arr := ExternalSemaphoreTable unprotectedExternalObjects. semaphores := arr reject: #isNil. res := semaphores collect: [:sema | sema pointersTo reject: [:ptr | ptr == arr or: [ptr == semaphores ] ] ]. res := res select: [ :each | each isEmpty ]. res size. -- Milan Mimica http://sparklet.sf.net

3 5

[Pharo-project] CRC in System-Hashing?
by Max Leske March 2, 2012

March 2, 2012

I need to calculate CRC for Git and couldn't find it in the system packages (I guess I'd find it in Cryptography). Since Pharo has a system package called "System-Hashing" I was wondering if anyone sees a reason why CRC should not be part of that package. That would also allow the Zip implementation to use the system CRC function (at the moment Zip implements its own CRC check). Another thing: going through Sytem-Hashing I noticed that there are two implementations for SHA1: "SHA1" and "SecureHashAlgorithm". They both have the exact same class comment but vary slightly in the messages they implement (although most of them are present in both classes). Can we remove one? Cheers, Max

2 1

[Pharo-project] Nautilus version 4.0.4
by Benjamin March 2, 2012

March 2, 2012

Hi guys, I really want to thank you all for your feedbacks which give me the will to always add cool features to Nautilus. Thanks to that, let me introduce the new stable version with some new features: - better groups (now the granularity is method and no longer class) - better algorithm for coloring protocols and methods - more menu entries and shortcuts - Monticello integration - OCompletion integration - a lot of new icons :) (and some cleans in the code but ^^) Thanks every one for your good energy :) Ben

8 20

[Pharo-project] Give it five minutes - (37signals)
by Sven Van Caekenberghe March 2, 2012

March 2, 2012

Coming from someone who is often accused of having a big ego: http://37signals.com/svn/posts/3124-give-it-five-minutes Well written. I am equally guilty sometimes. Sven

2 1

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3
by Marcus Denker March 2, 2012

March 2, 2012

> > I think this attitude is what will continue to hold Pharo back from wider > adoption. I've found 1.4 to be unusable for daily development. And yet > there's no interest in fixing problems in 1.3. There is. But we need to be reasonable... we can not back-port everything. Even fixing bugs changes the system so that it leads to incompatibility and new problems. > > And lest you think I don't want to contribute, I'll point you to > > http://code.google.com/p/pharo/issues/detail?id=4549&can=1&q=test%20runner&… > > where I > a) submitted a bug report > b) included a video demonstrating the bug > c) included a patch fixing the bug > Yes, and I only understood the problem last week. Because I use a mouse, and it works with a mouse with right-click... it even works when your track-pad is configured with right click. It only does not work if not. > responses were > - "not a showstopper -> move it to 1.4" > - "for me the bug entry is not really relevant" > Then complain! There are 450 open reports in the database... we closed nearly 5000 issues. There will be mistakes. The thing is that we could have not released 1.3 until we fixed all bugs.... then we would never have released it. So we go through all reports and decide: what needs to be really really fixed? Yes, we make mistakes. I do not know how to not do mistakes, sorry. > seven months later it finally made its way in. > Because *I* pushed. Ben is using a mouse, so he just did not see the problem. In general, there are just not enough people to look at bugs... if nobody helps, it takes a looong time. > I can see saying, "move it to 1.4" if 1.4 is right around the corner. We could have blocked the release of 1.3 and then we would have not released 1.3 until now. (keep in mind there are 450 other open issues besides the one you are talking about). > > As long as 1.3 is the prime time release - i.e. the release suitable for > active development - you have to support it and care about the people using > it. This is not some backward compatibility thing. It's a daily usability > thing. You can't tell people, "yeah that is fixed, but only in 1.4, but 1.4 > isn't really ready for you to use yet." And if I submit a patch for 1.3, > then accept the damn patch for 1.3. Don't tell me "it'll go into 1.4" when I > can't even use 1.4 myself. That's how you alienate users and keep the > community tiny. We can not backport everything... especially as the amount of people looking at stuff is very small. yes, we should release more often... E.g. since I asked for help on 1.3 issues: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 There was *no reaction at all*. Nothing. Zero. Sometimes I think we should just stop and do something else. This is clearly not working. Marcus -- Marcus Denker -- http://marcusdenker.de

3 2

[Pharo-project] odd bug in Squeak 4.3, also in Pharo 1.3?...
by Lawson English March 2, 2012

March 2, 2012

I was creating a new video tutorial to show how to find all comments in all classes but I'm getting errors in both Squeak 4.3 and Pharo 1.3. In Squeak 4.3, the error is: Key not found: Comment In Pharo 1.3, the error is: Improper store into indexable object. the code is: myNav := SystemNavigation default. (myNav allMethodsWithSourceString: '"' matchCase: false) do: [:each| Transcript show: each asString, ' => ', ( each actualClass commentsIn: each sourceString);cr ] In Pharo, the error shows up after the Transcript output: UndefinedObject>>DoIt (myNav is Undeclared) In Squeak the error shows up each time after the Transcript output: [...] AbstractSound class updateScorePlayers => an OrderedCollection('Force all ScorePlayers to update their instrument list from the sound library. This may done after loading, unloading, or replacing a sound to make all ScorePlayers feel the change.') UndefinedObject>>DoIt (myNav is Undeclared) UndefinedObject>>DoIt (myNav is Undeclared) Help? Error shows up in Squeak 4.3 image running both in the all-in-one distribution, and running on Cog VM. In Pharo 1.3 using Cog VM. Mac OS X 10.6.8. Thanks, Lawson

1 0

[Pharo-project] [Announce] S8 in the Concrete Jungle
by Elvio Fernandez March 1, 2012

March 1, 2012

Hi! Alejandro Reimondo (Ale) will make a presentation about S8 platform and U8 service on Tuesday March 6, 2012 to NYC Smallltalk Developerâs group. http://www.nycsmalltalk.org/2012/01/10/s8-release-candidate-smalltalk-on-js/ There is a lot of topics to talk about..., the topic of most interest (to us) is to explain what we are doing with S8. A breaf description of our regional point of view about OT and Smalltalk, and our proposal of a modern formulation of development using Smalltalk will be the starting point of the presentation. The S8 platform was implemented to let us(smalltalkers) be responsible of our execution environments (as it was in the early days of smalltalk). That impose a change of attitude and the formulation/idea must be supported by tools and evidence/experience of others in the same field. As a demostration on how we can do that with S8, Ale will mention the platforms we have implemented for using the U8 service (designed to make worldwide social development with smalltalk http://u8.smalltalking.net ). On technical side, to mention where a person can start application development and self-learning using U8, he will describe the frameworks we have implemented on top of S8 (we all know the importance of frameworks) and the process we are using for development/testing of frameworks. The presentation is also open to the topics of interest of the audience. And Ale will be happy to respond questions about how to use S8 in diferent contexts of development. Some of the technical points that will be of interest are: - how to use our FFI framework? (make API calls, use native libraries and implement callbacks using S8; 100% smalltalk code) - how to do server side development? (NodeJS framework) - how to use your code from other smalltalks? - how to use javascript libraries? and (more important) how to write interfaces to existing libraries fast and minimize errors / testing points? - how to develop for Android and phones? - how to use cloud services? - how to work using U8? How to contact experts and people to do development of frameworks using the U8 service? - why we minimized the toolset at this stage? and what powerfull features of smalltalk we support today. - what is not implemented yet? and how to contribute? - ... In all the presentations and coding events we made here (in Buenos Aires) the time has been short for going deep in groups, and the presentation was important to get in touch with people that has interest in global development as it is used to be in this decade. So, if you are near NY on March,6 join us. If you can't attend there next week, please contact us at info(a)smalltalking.net and consider we have open the Betatesting site to start contributing and using U8 from now and we are doing one betaworks meeting per week to let people put their hands on the frameworks, tools and S8 platform, in small groups. ...If you canÂ´t wait and want to start coding now/today, please visit the U8 page ( http://u8.smalltalking.net ) and register there to become a member of our community, to be in contact with people and companies interested in social development using Smalltalk. cheers, --------------- on behalf of Smalltalking Associationwww.smalltalking.net

1 0

Re: [Pharo-project] Nautilus version 4.0.4
by Marcus Denker March 1, 2012

March 1, 2012

On Mar 1, 2012, at 10:45 PM, patmaddox wrote: > Does this load on Pharo 1.3? I tried loading it but it barfed on something > like "Browser does not understand addGroup.." (don't entirely remember the > error message). No, we are at the same time improving the base system. e.g. - MC now emits announcements that Nautilus can react on. - Widgets are improved. Example: Multi-selection, lots more - Specs, declaratively define UIs. - RPackage: Merge SystemCategories with PackageInfo, for real. - Ring. This replaces MethodReferences and provides a meta-model for code. I think in the end it's a question of philsophy. Some people say that a project like Nautilus should run on 1.3 and 1.4 (and possibly Squeak and even VW and VA), and never ever improve anything in the systems We disagree ;-) Marcus -- Marcus Denker -- http://marcusdenker.de

1 0