- Pharo-dev - lists.pharo.org

[Pharo-project] About 1.2
by StÃ©phane Ducasse Feb. 27, 2011

Feb. 27, 2011

Hi guys 1.2 should go out. Marcus and me should spend their time on 1.3, OPAL and the rest. Now for PharoDev we want to remove packages that are not about tools. If you want XML, openDBX... help us using Metacello to build distributions = something that will work in 1.2 when we will be in Pharo 10. Right now this is not normal that a problem in XML in 1.2 impacts the builds in 1.1. Proposing bloated images DOES NOT HELP US. Why? Because the goal is to have an INFRASTRUCTURE to take a small image with a metacello description repository and load whatever we want. In the future we want to use metacello to manage core and not to have a distinction between core and dev. We should be able to load all the time RBEngine and use it all the time to fix the system. Right now we are LOSING TIME on fixing 1.2 configs while we should invest in the infrastructure that will enable to be agile and load whatever configuration we/you will develop. So can we be focus on the infrastructure? The concept and tools that we will make us be really powerful in the future? So if the community does not hear our call, we the board will take actions. We do not want to do that but if this is necessary we will do it because we want 1.2 to get out. Stef

5 6

[Pharo-project] MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:
by GermÃ¡n Arduino Feb. 27, 2011

Feb. 27, 2011

Hi: Frequently, working on a 1.2 image downloaded from Hudson page, I get the subject error using the browser. It get also a red rectangle with yellow diagonal. A quick search on the open 1.2 issues not shown nothing. It's a know problem? Exist some workaround? Thanks. -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

2 3

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Package Monticello leaves Obsolete class after tests
by pharo＠googlecode.com Feb. 27, 2011

Feb. 27, 2011

Updates: Summary: [Failing Tests] Package Monticello leaves Obsolete class after tests Comment #3 on issue 3575 by marcus.d...@gmail.com: [Failing Tests] Package Monticello leaves Obsolete class after tests http://code.google.com/p/pharo/issues/detail?id=3575 (No comment was entered for this change.)

1 2

[Pharo-project] Do we want to integrate Keymappings? What's the way to follow? [WAS] More on Keymappings
by Guillermo Polito Feb. 26, 2011

Feb. 26, 2011

Stef and everybody, I'd love to have it too, and I'd like to know what should a solution have to be integrated :). Should we integrate it in the core? or let it in the Dev? I know that a minimum solution should be to have this keymapper replace completely the old and hardcoded keymappings. Once it is integrated, it'll be easier to change and go on. Guille On Sat, Feb 26, 2011 at 2:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks this is still on my todo to have a look at them. > I want a good keymapper in the system... :) > > Stef > > On Feb 26, 2011, at 5:42 AM, Guillermo Polito wrote: > > > What do we have now? > > > > - Can provide settings for a set of morphs > > > > - Can provide settings for a TextEditors (Smalltalk editor and related) > > > > - Settings integration > > I added some methods to the Settings Tree Builder in order to avoid > references from the users code. > > > > - I ran Slint over it and cleaned it a lot more :). ( And learnt that > Slint is there :P ) > > > > More info in here: http://guilleel3.blogspot.com/ > > > > Guille > > >

3 4

[Pharo-project] Fwd: [Metacello] Metacello 1.0-beta.28.3.1 released
by Dale Henrichs Feb. 26, 2011

Feb. 26, 2011

Begin forwarded message: From: Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> Date: February 25, 2011 9:12:04 PM PST To: Metacello <metacello(a)googlegroups.com<mailto:metacello@googlegroups.com>> Subject: [Metacello] Metacello 1.0-beta.28.3.1 released Reply-To: "metacello(a)googlegroups.com<mailto:metacello@googlegroups.com>" <metacello(a)googlegroups.com<mailto:metacello@googlegroups.com>> Targeted at Pharo1.2 - fix Issue 3758: Metacello has 12 failing tests in 1.2 http://code.google.com/p/pharo/issues/detail?id=3758 - well ... add expectedFails for the tests are failing due to the fix for Pharo Issue 3660 Dale

2 1

Re: [Pharo-project] we cannot add attachment anymore on the bug tracker
by Marcus Denker Feb. 26, 2011

Feb. 26, 2011

On Feb 26, 2011, at 1:15 AM, David T. Lewis wrote: >> . >> > > I do not think it was meant to be rude. I am guessing that this was > just a way to say thank you to Nathanael SchÃÂ¤rli, an esteemed > Squeak (Pharo) alumnus who IIRC is now working for Google. > Lukas does, too. (the black hole is sucking everyone in...) > For myself, I don't know any of the Squeak/Pharo folks personally, > so I don't think there is anything wrong with that :) Of course there is something wrong with that! ;-) It's actually a lot of fun to meet in person... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] Hudson build script for Pharo-1.2 image
by Marcus Denker Feb. 26, 2011

Feb. 26, 2011

On Feb 26, 2011, at 6:31 AM, Dale Henrichs wrote: > Marcus, > > When you get a chance could you give me a pointer to the build script that you use to build the Pharo-1.2 image? > this code is executed: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… The Metacello config loaded is this: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] 2 days vs 2 day
by Edouard Poor Feb. 26, 2011

Feb. 26, 2011

I ran across this across this a couple week ago but didn't know whether to enter a defect for it or not. "2 days" evaluates to a duration of 2 days but, "2 day" evaluates to a duration of 1 day. I've been thinking about it, and I think I can understand who this came about, but silently giving a user the wrong answer if they mistype "days" or write some code like "[ :n | n day ]" (I did this one) seems wrong. If "day" should only answer with the singular value, than perhaps it should throw an exception for any values other than -1 or 1. I'd actually prefer it just called days, and damn English grammar. So what do you think, should I enter a defect or not? (Also I'm new to the community, so I wasn't even sure where I should ask a question like this!) Cheers, Edouard.

3 2

[Pharo-project] SHParserST80 and the types: #- and #'$'
by Edouard Poor Feb. 26, 2011

Feb. 26, 2011

I was trying to write the most compact source code to HTML/CSS I could come up with: parser := SHParserST80 new. code := OrderedCollection sourceCodeAt: #sort:. ranges := parser rangesIn: code classOrMetaClass: OrderedCollection workspace: nil environment: nil. dict := Dictionary with: 1->#whitespace. ranges do: [ :range | dict add: range start -> range type; add: range end + 1 -> #whitespace ]. spans := dict associations sorted overlappingPairsCollect: [ :a :b | '<span class="', a value, '">', (code copyFrom: a key to: b key - 1), '</span>' ]. but SHParserST80's use of #- and #'$' might mess things up a little. What do you think about replacing those two symbols with textual versions (like #minus #characterPrefix)? I'm kind of serious - Shout's two non-textual type names seem ugly. Cheers, Edouard.

2 1

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes
by Marcus Denker Feb. 26, 2011

Feb. 26, 2011

On Feb 26, 2011, at 1:44 AM, Dale Henrichs wrote: > I've downloaded a Pharo1.2 image from Hudson to see what's happening and I notice that there are a number of validation issues with the ConfigurationOfPharo ... so I think that the XMLSupport issues have been addressed ... yes. > this build is yello and the earlier build was red ... > > Is that right? yes > Or are there other things that I don't know about? > Maybe that 1.1 is now broken: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.1/ -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0