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

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Marcus Denker

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.

Feb. 26, 2011

Re: [Pharo-project] Hudson build script for Pharo-1.2 image

by Marcus Denker

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.

Feb. 26, 2011

Re: [Pharo-project] we cannot add attachment anymore on the bug tracker

by Marcus Denker

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.

Feb. 26, 2011

Re: [Pharo-project] Issue 3758 in pharo: Metacello has 12 failing tests in 1.2

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3758 by marcus.d...(a)gmail.com: Metacello has 12 failing tests in 1.2 http://code.google.com/p/pharo/issues/detail?id=3758 fixed in build #158

Feb. 26, 2011

[Pharo-project] 2 days vs 2 day

by Edouard Poor

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.

Feb. 26, 2011

[Pharo-project] SHParserST80 and the types: #- and #'$'

by Edouard Poor

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.

Feb. 26, 2011

Re: [Pharo-project] Fwd: [ANN] pharo focused sprint - bern, feb 26

by Tudor Girba

We are starting the sprint: - Twitter tag: #pharosprint - If someone wants to join remotely, let us know how to reach you. Gary, Alain? :) Cheers, Doru On 25 Feb 2011, at 20:39, Tudor Girba wrote: > Phenomenal :) > > Doru > > > On 24 Feb 2011, at 13:03, Jorge Ressia wrote: > >> I will be there too. >> >> Cheers, >> >> On Wed, Feb 23, 2011 at 10:44 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>> Excellent. >>> >>> Doru >>> >>> >>> On 23 Feb 2011, at 22:29, Lukas Renggli wrote: >>> >>>> I am coming too. >>>> >>>> Lukas >>>> >>>> On 23 February 2011 05:27, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>>>> Great. >>>>> >>>>> Doru >>>>> >>>>> >>>>> On 22 Feb 2011, at 19:47, Camillo Bruni wrote: >>>>> >>>>>> I'll be there. >>>>>> >>>>>> From what I have done this week so far, I would like to work on extending the IDE and reduce the amount of clicks / keystrokes to browse things... >>>>>> >>>>>> m(o_o)m >>>>>> camillo >>>>>> >>>>>> On 2011-02-21, at 19:42, Tudor Girba wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I would like to remind you that this Saturday, February 26, we organize a Sprint at SCG, University of Berne, Switzerland (room 107): >>>>>>> http://scg.unibe.ch/contact/maps >>>>>>> >>>>>>> Further details can be found below. Please let us know by mail if you plan to attend and what you would wish to work on (see below). >>>>>>> >>>>>>> Cheers, >>>>>>> Doru >>>>>>> >>>>>>> >>>>>>> >>>>>>> Begin forwarded message: >>>>>>> >>>>>>>> From: Tudor Girba <tudor.girba(a)gmail.com> >>>>>>>> Date: 1 February 2011 16:38:30 CET >>>>>>>> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> >>>>>>>> Cc: Adrian Lienhard <alienhard(a)netstyle.ch> >>>>>>>> Subject: [ANN] pharo focused sprint - bern, feb 26 >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> We would like to organize a Pharo Sprint on Saturday, February 26 at SCG, University of Berne, Switzerland (room 107): >>>>>>>> http://scg.unibe.ch/contact/maps >>>>>>>> >>>>>>>> Unlike other sprints, this would not be about fixing things from the tracker, but about building something new and reviewing the situation around one central topic. For this one, the main topic will be Morphic and the IDE. Why? Because it is time to rethink our day-to-day tools and bring them closer to this century (ok, maybe decade :)). It is Ok if you are not a specialist. It is more important to want to participate and learn. The rest will come in time. >>>>>>>> >>>>>>>> ***** Please let us know by mail if you plan to attend and what you would wish to work on (see below). >>>>>>>> >>>>>>>> Proposed tasks (other tasks are possible in the same area): >>>>>>>> - Enhancements of Morphic widgets: >>>>>>>> --- TabGroupMorph with lazy pages, closable tabs, overflow handling and toolbars (a start exists in Glamour) >>>>>>>> --- High level support for collapsable panes (based on the input of Gary) >>>>>>>> --- SearchMorph with multiple groups of items (like in Spotlight) >>>>>>>> --- MorphTreeMorph integrated with GeneralScrollPane to allow for space filling >>>>>>>> --- BreadcrumbMorph >>>>>>>> --- Hyperlinks in TextMorphs >>>>>>>> - Test and enhance the current IDE >>>>>>>> - Evaluate TextMorphs: NewTextMorph, PluggableTextMorph, SMxPluggableTextMorph etc >>>>>>>> - Prototype a new ToolSet solution >>>>>>>> - Enhancements of Glamour and of the Glamorous Toolkit >>>>>>>> --- Debugger >>>>>>>> --- Coder >>>>>>>> --- Multipage Workspace >>>>>>>> --- CodeBubbles >>>>>>>> - Develop WeakAnnouncement (start from the implementation of Lukas) >>>>>>>> - Evaluate the various keybinding implementations >>>>>>>> - Evaluate ToolBuilder >>>>>>>> - Evaluate the path to adopt SimpleMorphic >>>>>>>> >>>>>>>> A second working topic is getting Monticello faster, but this will only be tackled if there are enough people for the first one. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Adrian and Doru >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> www.tudorgirba.com >>>>>>>> >>>>>>>> "Be rather willing to give than demanding to get." >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> www.tudorgirba.com >>>>>>> >>>>>>> "It's not how it is, it is how we see it." >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Value is always contextual." >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "There are no old things, there are only old ways of looking at them." >>> >>> >>> >>> >>> >> >> >> >> -- >> Jorge Ressia >> www.jorgeressia.com > > -- > www.tudorgirba.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Feb. 26, 2011

Re: [Pharo-project] [ANN] More on Keymappings

by laurent laffont

On Sat, Feb 26, 2011 at 5:42 AM, Guillermo Polito <guillermopolito(a)gmail.com > 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/ A new blog, cool ! Can I have Emacs-like keybinding in code editor, to switch browser, ... ? Laurent. > > > Guille >

Feb. 26, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint Portland, Oregon ... Saturday and Sunday

by laurent laffont

Thank you Dale. Laurent. On Sat, Feb 26, 2011 at 2:27 AM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Okay, okay.... I've been trying to keep a half dozen balls in the air for > the last few weeks and what that means is that I don't give enough attention > to any of them ... > > Pharo1.2 is close and Metacello is one of the bad boys with the failing > tests sooooo, I am going to do a solo sprint this weekend: > > 1. a quick release of Metacello with expectedFailures for the tests > that are failing in Pharo1.2. I have already fixed the tests > (only test changes are needed), but I now need to port the Gofer > changes to Squeak and GemStone which is a bigger job. A quick > surgical set of expectedFailures is the best thing to do here. > 2. in build #57 of Pharo1.2 I noticed some odd things that I want to > track down... > 3. I expect that some of the #57 issues can be revealed with the > validator, so I am thinking that I will run the validator over > all of the configurations that are used in Pharo1.2 and go about > identify and/or fixing the meaningful issues that I find. My main > goal will be to repair things that are broken, so I will be > reluctant to make semantic changes without checking with the > maintainers, but if the problem is really gruesome I will fix it > and apologize later:) > 4. I'm not going to spend a lot of time reading/writing email ... > this will be a sprint not a coffee klatch. With that said, if you > have a Metacello config issue that is related to Pharo1.2 drop me > an email with your question/thought but don't be offended if > I don't respond at all or just GRUNT in reply ... I may even take > action without letting you know... > 5. While working on the above task, I will work on the > MetacelloBrowser adding menu items for the operations that I > performso it will then be easier for other folks to perform the > same types of jobs in the future. I may do something funky like > hide the menu items behind a boolean so as not to pollute the > menu items with a whole bunch of advanced type operations (that > will be named poorly:)... > > I realize that I may be closing the barn door after the horse is gone - > build 57 is yellow afterall - but cleaning up validation issues is long > overdue. > > I don't plan on fixing Metacello bugs unless I find something that just > begs to be fixed ... the sprint is mainly about running the validator and > cleaning up the real nasty bits and track down the Metacello anomalies in > #57... > > Dale > >

Feb. 26, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint Portland, Oregon ... Saturday and Sunday

by Tudor Girba

Thanks indeed for all this nice work and commitment. Cheers, Doru On 26 Feb 2011, at 05:13, Miguel CobÃ¡ wrote: > Thanks Dale > > El vie, 25-02-2011 a las 17:27 -0800, Dale Henrichs escribiÃ³: >> Okay, okay.... I've been trying to keep a half dozen balls in the air >> for the last few weeks and what that means is that I don't give enough >> attention to any of them ... >> >> Pharo1.2 is close and Metacello is one of the bad boys with the failing >> tests sooooo, I am going to do a solo sprint this weekend: >> >> 1. a quick release of Metacello with expectedFailures for the tests >> that are failing in Pharo1.2. I have already fixed the tests >> (only test changes are needed), but I now need to port the Gofer >> changes to Squeak and GemStone which is a bigger job. A quick >> surgical set of expectedFailures is the best thing to do here. >> 2. in build #57 of Pharo1.2 I noticed some odd things that I want to >> track down... >> 3. I expect that some of the #57 issues can be revealed with the >> validator, so I am thinking that I will run the validator over >> all of the configurations that are used in Pharo1.2 and go about >> identify and/or fixing the meaningful issues that I find. My main >> goal will be to repair things that are broken, so I will be >> reluctant to make semantic changes without checking with the >> maintainers, but if the problem is really gruesome I will fix it >> and apologize later:) >> 4. I'm not going to spend a lot of time reading/writing email ... >> this will be a sprint not a coffee klatch. With that said, if you >> have a Metacello config issue that is related to Pharo1.2 drop me >> an email with your question/thought but don't be offended if >> I don't respond at all or just GRUNT in reply ... I may even take >> action without letting you know... >> 5. While working on the above task, I will work on the >> MetacelloBrowser adding menu items for the operations that I >> performso it will then be easier for other folks to perform the >> same types of jobs in the future. I may do something funky like >> hide the menu items behind a boolean so as not to pollute the >> menu items with a whole bunch of advanced type operations (that >> will be named poorly:)... >> >> I realize that I may be closing the barn door after the horse is gone - >> build 57 is yellow afterall - but cleaning up validation issues is long >> overdue. >> >> I don't plan on fixing Metacello bugs unless I find something that just >> begs to be fixed ... the sprint is mainly about running the validator >> and cleaning up the real nasty bits and track down the Metacello >> anomalies in #57... >> >> Dale >> > > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > -- www.tudorgirba.com "Speaking louder won't make the point worthier."

Feb. 26, 2011