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

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Comment #8 on issue 3707 by Benjamin...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 I know where it is, I will take a look tomorrow, tonight it's party ^^

Feb. 26, 2011

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

by StÃ©phane Ducasse

so doru I just arrived after a trip from the nearly "westernest" town in france to nearly the "northest" one :) What are the results of the sprint. On Feb 26, 2011, at 9:42 AM, Tudor Girba wrote: > 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] Do we want to integrate Keymappings? What's the way to follow? [WAS] More on Keymappings

by StÃ©phane Ducasse

On Feb 26, 2011, at 6:59 PM, Guillermo Polito wrote: > 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 do not know good tests tested commented :) not too large for me the core of the keymapper should go in core and the extension in separate package. Stef > 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. OK I should have a look and somebody else too :) Stef > > 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 > > >

Feb. 26, 2011

Re: [Pharo-project] Issue 3763 in pharo: assert failure during Decompiler>>popIntoTemporaryVariable:

by pharo＠googlecode.com

Comment #3 on issue 3763 by da...(a)teleport.com: assert failure during Decompiler>>popIntoTemporaryVariable: http://code.google.com/p/pharo/issues/detail?id=3763 If I change the source to the following, I can bypass the MethodContext bug and get a debugger on the source of the problem: resolveToLoadableSpecs: required map: packageMap | reqd allReqd map spec newReqd | reqd := required copy. allReqd := Set new. map := self packages map. [ reqd isEmpty ] whileFalse: [ newReqd := Set new. reqd do: [:req | (self resolveToLoadableSpec: req forMap: map packages: packageMap) do: [:loadableSpec | newReqd addAll: loadableSpec requires. newReqd addAll: loadableSpec includes ]]. allReqd addAll: reqd. newReqd removeAllFoundIn: allReqd. reqd := newReqd ]. packageMap keys do: [:pkgName | (spec := (packageMap at: pkgName) resolveToLoadableSpec) == nil ifTrue: [ packageMap removeKey: pkgName ] ifFalse: [ packageMap at: pkgName put: (packageMap at: pkgName) resolveToLoadableSpec ]] The trick is to move the declaration of the two temps spec and newReqd out of the blocks and into the top level ... I suspect that newReqd was the bad boy ...

Feb. 26, 2011

[Pharo-project] introducing RPackage :)

by StÃ©phane Ducasse

Hi guys I would like to give a try to introduce RPackage = a complete rewrite of PackageInfo. Moose people use it and I will sync with them to know. It would be great if some of you could load and play with the system Gofer new squeaksource: 'PharoInbox'; package: 'ConfigurationOfRPackage'; load. (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. Note that RPackage is based on announcement. So there is just one place that register to systemNotifier. So one of the following goal is to remove SystemChangeNotifier and replace it with announcement. Stef

Feb. 26, 2011

[Pharo-project] Do we want to integrate Keymappings? What's the way to follow? [WAS] More on Keymappings

by Guillermo Polito

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

Feb. 26, 2011

Re: [Pharo-project] [COTDC] 19 - NaturalLanguageFormTranslator

by StÃ©phane Ducasse

this is a funny one Looks like a monty python one. ") On Feb 25, 2011, at 9:08 PM, laurent laffont wrote: > I don't know why I'm here. > > Laurent. > > On Thu, Feb 24, 2011 at 8:55 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Today: NaturalLanguageFormTranslator > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

Feb. 26, 2011

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

by StÃ©phane Ducasse

> > > Redmine (http://www.redmine.org/) supports sub-projects. Or maybe https://www.chiliproject.org/ (a fork of redmine). Does anybody has experience with them? It would be good to be able to play with them. Stef

Feb. 26, 2011

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

by Henrik Sperre Johansen

GermÃ¡n Arduino wrote: > > mmm, may be is related with an old Cog version. > > Seems not happen with 2361. > > Yes, it is :) Cheers, Henry -- View this message in context: http://forum.world.st/MessageNotUnderstood-LargePositiveInteger-pixelValueF… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 26, 2011

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

by Guillermo Polito

Camillo, What's a more complete set of commands? Can you be more Specific? hehe. Next thing I want to do is get rid of every hardcoded mapping (i.e from Editor and SmalltalkEditor) and configure it this way... But It's a lot of work I couldn't do. Maybe this two weeks I can do something on it since I am on vacation, but my girlfriend will kill me :). I'd love to know what you're working on so we don't do innecesary work! Guille On Sat, Feb 26, 2011 at 12:55 PM, Camillo Bruni <camillo.bruni(a)inria.fr>wrote: > 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