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

[Pharo-project] Issue 3762 in pharo: Refactor TextEditor >> dispatchOn:

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3762 by camillob...(a)gmail.com: Refactor TextEditor >> dispatchOn: http://code.google.com/p/pharo/issues/detail?id=3762 very unreadable. changed in System-Text-CamilloBruni.147

Feb. 26, 2011

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

by Camillo Bruni

Hi, I am currently writing a more complete set of commands for the editors. I ll post soon. m(^_-)m camillo On 2011-02-26, at 14:12, Francisco Ortiz PeÃ±aloza wrote: > Guille i was using 1.4 and worked excellent, just tried 1.5 and on > every stroke i made i've got a DNU on #realtarget > > Installed on last PharoCore 1.2, should i try it on 1.3? > > Great work, > Fran > > On Sat, Feb 26, 2011 at 5:29 AM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: >> >> 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] MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:

by GermÃ¡n Arduino

mmm, may be is related with an old Cog version. Seems not happen with 2361. 2011/2/26 GermÃ¡n Arduino <garduino(a)gmail.com>: > 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 > ================================================= >

Feb. 26, 2011

[Pharo-project] MessageNotUnderstood: LargePositiveInteger>>pixelValueForDepth:

by GermÃ¡n Arduino

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 =================================================

Feb. 26, 2011

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

by Mariano Martinez Peck

"solo sprint" hahahaha AWESOME. Lots of us do solo sprints :) On Sat, Feb 26, 2011 at 8:20 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > 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] [ANN] More on Keymappings

by Francisco Ortiz PeÃ±aloza

Guille i was using 1.4 and worked excellent, just tried 1.5 and on every stroke i made i've got a DNU on #realtarget Installed on last PharoCore 1.2, should i try it on 1.3? Great work, Fran On Sat, Feb 26, 2011 at 5:29 AM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > 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] 2 days vs 2 day

by Mariano Martinez Peck

On Sat, Feb 26, 2011 at 10:40 AM, Edouard Poor <edouard.lists(a)gmail.com>wrote: > 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 have to admit that sounds weird > 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!) > > welcome!! yes, this is the perfect place to ask cheers mariano

Feb. 26, 2011

Re: [Pharo-project] 2 days vs 2 day

by Johan Brichau

+ 1 The method makes _no_ sense at all. On 26 Feb 2011, at 10:40, Edouard Poor wrote: > 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.

Feb. 26, 2011

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

by pharo＠googlecode.com

Updates: Status: Fixed Comment #11 on issue 3743 by Benjamin...(a)gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 I just posted the version 27 on PharoInbox wich fix those two points :) Are event send as an argument instead of a character only for Tree or have you fixed that for list too ?

Feb. 26, 2011

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

by Benjamin Van Ryseghem

JB and I were discuting about changing the SHParser by PetitParser, maybe your problem is a good excuse to do it :Â° Ben 2011/2/26 Edouard Poor <edouard.lists(a)gmail.com> > 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