November 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Not happy with the issues feed from Google

by Torsten Bergmann

>We can try but I don't think it will work particularly well. Our >infrastructure should best support the people that actively work on Pharo so >I don't see any problem sending tons of mails to pharo-project at ... >mailing list if this helps. For users who don't want to see all these >details there already is a separate list (pharo-users at ...). +1 Bye T. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

Nov. 19, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by Adrian Lienhard

On Nov 18, 2010, at 22:58 , StÃ©phane Ducasse wrote: > Thanks for sharing that with us. > We will create a separated mailing-list to see how it works. We can try but I don't think it will work particularly well. Our infrastructure should best support the people that actively work on Pharo so I don't see any problem sending tons of mails to pharo-project@... mailing list if this helps. For users who don't want to see all these details there already is a separate list (pharo-users@...). An additional list has similar drawbacks as an RSS feed. One is less likely to read it. One cannot reply directly to start a discussion (well, we can reply in this new list, but then it gets messy because we start discussing in two separate lists). just my 2 cents... Adrian

Nov. 19, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by StÃ©phane Ducasse

Yes! we were discussing with alain about that. Please sync with alain. Fernando here is also what I would like to have :) A classVar Binding and an instance var binding. **All** the methods only access binding binding get initialized with the default table defined in Binding => we can have table binding sharing => we can have instance based customization. Does it make sense to you? Stef On Nov 19, 2010, at 8:21 AM, Fernando Olivero wrote: > Hi Alain, i took a better look at the changes and have to say...once > again..excellent! > > I think the next step is to improve the keybindings hardcoding in > TextEditor>>initialize > self initializeCmdKeyShortcuts. > self initializeShiftCmdKeyShortcuts. > > I have a keybindings/command model in Gaucho, for applying a > keybinding to any morph. > I will work on decoupling it from GauchoMorph into Morph. > And later rewrite the Morphs for textediting to use this. > > So for example, if you want to delete any GauchoMorph from the system > by pressing cmd-w, you have to: > > binding := GMKeyBinding > actingOn: $w asciiValue > modifiedBy: #(#command) > satisfying: ( GMCondition compositeWith: #( > #understandsKeyBindingCommandCondition #uneditedCondition ) ) > applying: #close. > m := NewTextMorph new. > m addKeyBinding: binding . > > > If people agree, i will create an issue and start working on it. > > Fernando > > On Thu, Nov 18, 2010 at 9:23 AM, Alain Plantec <alain.plantec(a)free.fr> wrote: >> Due to a change in PragmaMenuBuilder, the world menu is not well updated >> anymore. >> Simply evaluating >> World resetWorldMenu >> fixes that. >> So it should be done before the next release is published. >> Cheers >> Alain >> >> >> >

Nov. 19, 2010

Re: [Pharo-project] Issue 3210 in pharo: SimpleMorphic Integration

by StÃ©phane Ducasse

On Nov 18, 2010, at 11:29 PM, Fernando Olivero wrote: > This is really cool! Nice to have it already in the image. > > I like particulary like the UIManager integration, to easily "plug" > diferent morphics and tools. > For example UIManager default openInspector: self asMorphOn: anObject > withLabel: aLabel! . > > Stef and Juan: > > 1)how did the UIManager impact on the current facilities in > SystemNavigation for browsing senders, references and others? > Did the UI related parts got decoupled from SystemNavigation into UIManager? I do not think so. There is still a lot of things to clean in SystemNavigation > For example SystemNavigation returns the list of method references, > but the UIManager opens the proper Morph/tool to present it. > Currently SystemNavigation also does the Morph part. > > 2) What are the plans for the Simple morphic changeset? Package it in a separate package. Create a Squeaksource project Add it as a package in pharo-dev so that people can have a look at it. Stef > > Fernando > > > > > On Thu, Nov 18, 2010 at 9:47 PM, pharo(a)googlecode.com > <pharo(a)googlecode.com> wrote: >> >> Comment #3 on issue 3210 by stephane.ducasse: SimpleMorphic Integration >> http://code.google.com/p/pharo/issues/detail?id=3210 >> >> part one two and three are integrated >> >> >> >

Nov. 19, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by Tudor Girba

I agree :). Doru On 19 Nov 2010, at 08:21, Fernando Olivero wrote: > Hi Alain, i took a better look at the changes and have to say...once > again..excellent! > > I think the next step is to improve the keybindings hardcoding in > TextEditor>>initialize > self initializeCmdKeyShortcuts. > self initializeShiftCmdKeyShortcuts. > > I have a keybindings/command model in Gaucho, for applying a > keybinding to any morph. > I will work on decoupling it from GauchoMorph into Morph. > And later rewrite the Morphs for textediting to use this. > > So for example, if you want to delete any GauchoMorph from the system > by pressing cmd-w, you have to: > > binding := GMKeyBinding > actingOn: $w asciiValue > modifiedBy: #(#command) > satisfying: ( GMCondition compositeWith: #( > #understandsKeyBindingCommandCondition #uneditedCondition ) ) > applying: #close. > m := NewTextMorph new. > m addKeyBinding: binding . > > > If people agree, i will create an issue and start working on it. > > Fernando > > On Thu, Nov 18, 2010 at 9:23 AM, Alain Plantec <alain.plantec(a)free.fr> wrote: >> Due to a change in PragmaMenuBuilder, the world menu is not well updated >> anymore. >> Simply evaluating >> World resetWorldMenu >> fixes that. >> So it should be done before the next release is published. >> Cheers >> Alain >> >> >> > -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

Nov. 19, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by Fernando Olivero

Hi Alain, i took a better look at the changes and have to say...once again..excellent! I think the next step is to improve the keybindings hardcoding in TextEditor>>initialize self initializeCmdKeyShortcuts. self initializeShiftCmdKeyShortcuts. I have a keybindings/command model in Gaucho, for applying a keybinding to any morph. I will work on decoupling it from GauchoMorph into Morph. And later rewrite the Morphs for textediting to use this. So for example, if you want to delete any GauchoMorph from the system by pressing cmd-w, you have to: binding := GMKeyBinding actingOn: $w asciiValue modifiedBy: #(#command) satisfying: ( GMCondition compositeWith: #( #understandsKeyBindingCommandCondition #uneditedCondition ) ) applying: #close. m := NewTextMorph new. m addKeyBinding: binding . If people agree, i will create an issue and start working on it. Fernando On Thu, Nov 18, 2010 at 9:23 AM, Alain Plantec <alain.plantec(a)free.fr> wrote: > Due to a change in PragmaMenuBuilder, the world menu is not well updated > anymore. > Simply evaluating > World resetWorldMenu > fixes that. > So it should be done before the next release is published. > Cheers > Alain > > >

Nov. 19, 2010

Re: [Pharo-project] Issue 3210 in pharo: SimpleMorphic Integration

by Fernando Olivero

This is really cool! Nice to have it already in the image. I like particulary like the UIManager integration, to easily "plug" diferent morphics and tools. For example UIManager default openInspector: self asMorphOn: anObject withLabel: aLabel! . Stef and Juan: 1)how did the UIManager impact on the current facilities in SystemNavigation for browsing senders, references and others? Did the UI related parts got decoupled from SystemNavigation into UIManager? For example SystemNavigation returns the list of method references, but the UIManager opens the proper Morph/tool to present it. Currently SystemNavigation also does the Morph part. 2) What are the plans for the Simple morphic changeset? Fernando On Thu, Nov 18, 2010 at 9:47 PM, pharo(a)googlecode.com <pharo(a)googlecode.com> wrote: > > Comment #3 on issue 3210 by stephane.ducasse: SimpleMorphic Integration > http://code.google.com/p/pharo/issues/detail?id=3210 > > part one two and three are integrated > > >

Nov. 18, 2010

[Pharo-project] [update 1.2] #12246

by StÃ©phane Ducasse

12246 ----- - Issue 3210: SimpleMorphic Integration. Part two and three. -SMx02-PharoEnhAndPreliminariesCoda.1.cs contains some refactorings needed to make it possible to add another GUI to Pharo. - SMx03-ExtensionMethodsPart1.3.cs contains a few useful methods, not specific to SimpleMorphic, but optional anyway. You might integrate this into Pharo or consider it part of SimpleMorphic. Stef

Nov. 18, 2010

Re: [Pharo-project] ANyone have a fix for Scanner isLiteralSymbol: #<=?

by Levente Uzonyi

On Thu, 18 Nov 2010, Eliot Miranda wrote: > Hi All, > > In trunk > > Scanner isLiteralSymbol: #<= > > answers false ?!?! > > This is breaking my Cog generated code disassembly decoration so that > instead of > > 000a572c: movl $0x0045a458=#<=, %ecx : B9 58 A4 45 00 > 000a5731: call .+0xfff5ad5a (0x00000490=ceSend1Args) : E8 5A AD F5 FF > > I'm merely getting > > 000a572c: movl $0x0045a458, %ecx : B9 58 A4 45 00 > 000a5731: call .+0xfff5ad5a (0x00000490=ceSend1Args) : E8 5A AD F5 FF > > Anyone have a fix? There seems to be a fix in the method, but it's commented out to be compatible with the previous version of the method: type == #xBinary ifTrue: [^i = 1]. "Here we could extend to ^(2 to: i) allSatisfy: [:j | ascii := (aSymbol at: j) asciiValue. (TypeTable at: ascii ifAbsent: []) == #xBinary]" Levente > > best > Eliot >

Nov. 18, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by StÃ©phane Ducasse

>> > > Stef, > > I'm subscribed to some issues through standard Google Code "star this > issue" feature. So, I'm aware of the changes happening to these bugs. > I'm also subscribed to the RSS channel of the Pharo Google Code site, same here > but I do not follow it closely so far -- just have not enough time. So > my point is that interested people still are able to follow the > bugflow without subscribing the whole list to the updates. yes but you have to individually register. > > And if you want to make sure people are aware of the work you're > doing, I'd rather recommend you to pay more attention to the news page > of the pharo-project.org website. We cannot do that if this is not automated. Then the news are reviewed by native english speakers..... Probably we should have a dev news where we could push the issues comments but so far I do not know if this is possible > And having a list of immediate goals > and time line for them could also help, I think. Yes this is why I propose a IRC monthly meeting > Forcing people to follow all the minor activities happening on the tracker (I mean > changing milestones, statuses and so on) won't rather help (IMHO). > I've also created a filter to ignore all such messages after I've seen > them flooding my inbox. So I even don't see them and this fact somehow > contradicts to your point of making people aware. So other people just read them. I have a filter and I read them in batch. Sometimes just passing 0.5 s on an issue. > I still think important things are worth talking abouth them. I mean bootstraping > from kernel or new compiler or something else but in the form of > goals, plans, progress made and so on. Yeah, I know it's easier to > speak than actually do :), but effect might be better. Yes we do not want to replace the communication :) > You may now ask, why I'm so concerned about this issue, if I do not > even receive these autogenerated emails :) Ok, I just think that it's > wrong. But I may be wrong too of course :) There are two things I find > not practical. One of them is that replying to autogenerated mail in > the list and not copying these replies to the tracker actually splits > the discussion and makes it harder for people to track it later. Yes true may be we will need more discipline. > The other thing is mailing list archives like the one on Nabble. It's just > becoming harder to surfe them. And I'm not aware of the other > opensource projects doing the same with their mailing lists. > >> What is the last time you look at the code of the fixes that got integrated? Because if you do not read >> it how can we do quality control? So if I could I would send the diff of all the package in the mailing-lits as this is done in squeak. > > You can't do quality control this way. Oh yes believe you do. I will tell you a small story that explained why I was mad against 3.10 process. One guy that is in network/web sent a fix and I thought as a 3.9 integrator that I would integrate it. Then bert reviewed the fix and said that this was bogus so it was not integrated in 3.9. In 3.10 there was little communication about bugs and I raised this concerned to the squeakfoundation board. Because if experts do not have access fast to what is happening then they will not look at it then your overall quality will decrease. This is why I really want the new recentMessage browser because it is gorgeous and I want to use it daily especially when others are doing integrations ( we want to open the process ). > Everyone won't look at the code of these fixes, interested people are already looking at them so you > won't gain anything. No this is where you are wrong. People are not. I have to add lukas in the bug entry manually .... I have to ask personnally people to look at specific issue. > And it's iterative process after all: you make > changes, people look at the code of these changes doing their job in > Pharo, and if they're unhappy with these changes you'll know about it > :) No because when you have time you do not look at other code. You hack your own great stuff. > But important changes still need to be reviewed by experienced > community members, no doubts here. > >> Now what we can do to please some of you so far 4, we could create a mailing-list where such mails would be sent. >> But let us see so far who is really against. > > Don't get me wrong, I'm not extremely against this change. I just > think that this is not the best way to achieve your goals. Thanks for sharing that with us. We will create a separated mailing-list to see how it works. > > My apologies for the long mail. > > George >

Nov. 18, 2010