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

Re: [Pharo-dev] SLICE-Issue-12179-Nautilus-Add-package-filter-input-box

by Juraj Kubelka

OK. I will. Jura El 24-11-2013, a las 17:47, Marcus Denker <marcus.denker(a)inria.fr> escribiÃ³: > > On 24 Nov 2013, at 21:46, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > >> The slice SLICE-Issue-12179-Nautilus-Add-package-filter-input-box-JurajKubelka.3 >> already contains the fix. But whenever I try to merge with the image 30593, it says merge conflict. >> The solution is to say "Use incoming versionâ. I do not know how to do it better. > > As soon as an issue is integrated, it is better to submit a new change (new issue) based on the new > image. > Much easier to handle. > > Marcus > >

Nov. 24, 2013

Re: [Pharo-dev] Is there an up to date version of ConfigurationOfFuel?

by StÃ©phane Ducasse

> What do you mean by up to date? For 3.0 #development is current. I want to try to unload fuel and reload it. I guess that it will be easy since you maintain it. I want to do that to many parts (all) of the system. >> Is there an up to date version of ConfigurationOfFuel?

Nov. 24, 2013

about miniimage

by StÃ©phane Ducasse

Hi pavel may be I should start from your miniimage and start to making sure that the configurations can load then in a second step I can make sure that they can unload. What do you think? Stef

Nov. 24, 2013

MenuRegistration DNU enabledBlock:

by StÃ©phane Ducasse

Ben Do you have any idea? interpretRegistration: aRegistration | root | root := MenuRegistration owner: self. aRegistration items do: [:item || node | node := item group ifNil: [ root item: item item ] ifNotNil: [:grp | root group: grp ]. item with ifNotNil: [:block || old | old := aRegistration currentRoot. aRegistration currentRoot: node name. [ node with: block ] ensure: [ aRegistration currentRoot: old ]] ifNil: [ item action ifNil: [ node target: item target; arguments: item arguments; selector: item selector ] ifNotNil:[ node action: item action ]]. node keyText: item keyText; help: item help; icon: item icon; order: item order; parent: item parent. item enabled ifNil: [ node enabledBlock: item enabledBlock ] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I get something that say node does not understand enabledBlock: and I wonder why a MenuRegistration does not understand enableBlock: Stef

Nov. 24, 2013

Re: [Pharo-dev] Is there an up to date version of ConfigurationOfFuel?

by Max Leske

What do you mean by up to date? For 3.0 #development is current. On 24.11.2013, at 21:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Is there an up to date version of ConfigurationOfFuel? > > Stef >

Nov. 24, 2013

The Second Coming of Java article

by askoh

http://www.wired.com/wiredenterprise/2013/09/the-second-coming-of-java/ The article talks about Java Virtual Machine running dynamic languages like Scala and Clojure in addition to Java. What prevents the Smalltalk Virtual Machine from running Java, Scala, Clojure and other JVM languages? Is that something we can ride on to greater awareness and usage of Smalltalk Virtual Machine and Smalltalk? All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/The-Second-Coming-of-Java-article-tp4724932.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 24, 2013

allProtocols vs protocols

by StÃ©phane Ducasse

I have a question: why allProtocols returns an array and protocols a set? allProtocols ^ { allProtocol }, protocols asArray protocols ^ protocols protocolsNames ^ protocols collect: #name as: Array initialize super initialize. protocols := IdentitySet new. allProtocol := AllProtocol protocolOrganizer: self. to me it looks suspicious and it will be a source of bugs. Stef

Nov. 24, 2013

Re: [Pharo-dev] Browser does not work at all anymore... I fixed it but...

by StÃ©phane Ducasse

>>> >>>> well well well >>>> >>> >>> Code that is not used breaks. I do not know how to change that. I really do not. >>> >> >> I do not think that it is realistic to keep the old Browser alive. It will mean that we have >> to change it for everythingâ¦ Protocols already now. Later someone needs to change >> it to use RPackage instead of System Categoriesâ¦ this will be quite some workâ¦ >> > and how will we get that debugged if we donât use it? But we use it :) I need it. did you look at the methods I sent? Categorizer>>allMethodSelectors "give a list of all method selectors." ^^^^^^^^^^^^^ ^ elementArray copy sort ***A list is not a set*** ClassOrganization>>allMethodSelectors "Oops no commentsâ¦ no indication of types" ^ protocolOrganizer allMethods

Nov. 24, 2013

Re: [Pharo-dev] SLICE-Issue-12179-Nautilus-Add-package-filter-input-box

by StÃ©phane Ducasse

>> >> >>> I would like, but I have not found out how. I will take care of it and ask in mailing list. >>> >>> Anyway, I am not sure if it was well integrated. >> >> There was a conflict and I fully loaded your code. So I do not see how it could be different. >> But with computer science everything is possible. > > Why loading it if there was a conflict ? Do you really think that as an integrator we never chose which method to integrate and that we never handle conflicts? The version I selected is correct and working this is just an unused variable. Now if you want I can also stop looking at any bug entry and stop to integrate fix and focus on my own project. You will see if will take more time to get things integrated and do not believe that automatically validated means something when we are talking about certain aspects of the system. No need to rant that nobody take cares of integrating bugs. Living is taking action. Stef

Nov. 24, 2013

Re: [Pharo-dev] Browser does not work at all anymore... I fixed it but...

by StÃ©phane Ducasse

>> well well well >>> >> >> Code that is not used breaks. I do not know how to change that. I really do not. >> > > I do not think that it is realistic to keep the old Browser alive. It will mean that we have > to change it for everythingâ¦ Protocols already now. Later someone needs to change > it to use RPackage instead of System Categoriesâ¦ this will be quite some workâ¦ > > Marcus Marcus did you read my analysis until the end? Next time I will not post it. Did you see that this is not the Browser code the problem? but the fact that PluggableListMorph was confused because an invariant was violated. If protocols are not indexable then PluggableListMorph is fooled. Why Pluggable*****LIST*****Morph would have a work with Set? So it would be good that you do not systematically contradict what I'm saying because I changed a lot of things in this system and I will change many more. Right now I just got stuck on what I wanted to do. Stef

Nov. 24, 2013