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

[Pharo-project] [update 1.2] #12330

by Marcus Denker

12330 ----- Issue 3520: Workspaces do not recognize previously evaluated temps Issue 3643: TextMorph >> enableTextChange is missing -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #18 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 in 12330 TODO: 1.3

Feb. 2, 2011

Re: [Pharo-project] Issue 3643 in pharo: TextMorph >> enableTextChange is missing

by pharo＠googlecode.com

Comment #4 on issue 3643 by aplan...(a)gmail.com: TextMorph >> enableTextChange is missing http://code.google.com/p/pharo/issues/detail?id=3643 Here is a .cs Attachments: Issue-3643.1.cs 208 bytes

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #17 on issue 3520 by aplan...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 Here is the .cs Attachments: Issue-3520.1.cs 238 bytes

Feb. 2, 2011

Re: [Pharo-project] Issue 3609 in pharo: Integrate RPackage

by pharo＠googlecode.com

Comment #8 on issue 3609 by cy.delau...(a)gmail.com: Integrate RPackage http://code.google.com/p/pharo/issues/detail?id=3609 RPackage tests and Monticello tests should be green in a 1.3 core image with that: "load rpackage" Gofer new squeaksource: 'PharoTaskForces'; package: 'ConfigurationOfRPackage'; load. (Smalltalk globals at: #ConfigurationOfRPackage) loadDefault. "to be sure that the organizer is initialized before loading anything else:" (Smalltalk globals at: #RPackageOrganizer) initializeDefault. (Smalltalk globals at: #RPackageOrganizer ) removeMockPackagesFromOldOrganizer. Gofer new squeaksource: 'DelaunayTmpStuffs'; version: 'Monticello-cyrilledelaunay.511'; merge. Gofer new squeaksource: 'DelaunayTmpStuffs'; version: 'MonticelloGUI-cyrilledelaunay.88'; merge. Gofer new squeaksource: 'DelaunayTmpStuffs'; version: 'Tests-cyrilledelaunay.272'; merge.

Feb. 2, 2011

Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good

by pharo＠googlecode.com

Updates: Cc: marcus.denker stephane.ducasse guillermopolito Comment #6 on issue 3623 by Torsten....(a)astares.de: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 This is not fixed since "OCForOB-ul.5.mcz" is not in the dev image. Laurent changed the wrong version in ConfigurationOfOmniBrowser so it is not yet in 1.2. see http://lists.gforge.inria.fr/pipermail/pharo-project/2011-February/041184.h… for details. Is it possible to reopen this issue or should we open a new one?

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #16 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 No, I can not merge. Maybe we should go back to changesets for changes that are for both 1.2 and and 1.3?

Feb. 2, 2011

Re: [Pharo-project] Issue 3645 in pharo: Update Hudson One-Click build files for 1.2

by pharo＠googlecode.com

Comment #2 on issue 3645 by Torsten....(a)astares.de: Update Hudson One-Click build files for 1.2 http://code.google.com/p/pharo/issues/detail?id=3645 Does one click VM come with the standard VM or with Cog?

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #15 on issue 3520 by aplan...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 #bindingOf: have to be defined in TextMorphForEditView because it is passed as the requestor in SmalltalkEditor>>evaluateSelection. SLICE-Issue-3520-Workspaces-do-not-recognize-previously-evaluated-temps in InBox hope it is ok now.

Feb. 2, 2011

Re: [Pharo-project] 1.2: class var #Instance not allowed

by Igor Stasenko

2011/2/2 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: > Hi guys, > > One more problem: if some class have a class variable named #Instance, > it is not loadable anymore. > > It seems that problem is in Class>>bindingOf: method, where check is > done in a "declared environment", which happens to be a global > SystemDictionary, where a class Instance actually exists. > > This means that no class var with a name which collides with a name of > class is allowed? > > The bug is not in the #bindingOf: it just answers (correctly) that for given name there are already a binding exists in system. So, it should be allowed to declare the class variable with same name. But there are some nuances: - what to do if supeclass also defining binding for this name? - what if pool dicitonary in (super)class defines binding for given name? should we allow shadowing of these cases as well, or just for globals? > Class>>bindingOf: > > Â Â Â ... > Â Â Â Â "Next look in declared environment." > Â Â Â Â binding := self environment bindingOf: aSymbol. > Â Â Â Â binding ifNotNil:[^binding]. > Â Â Â ... > > Strack trace follows in next mail > > > > > -- > Janko MivÅ¡ek > AIDA/Web > Smalltalk Web Application Server > http://www.aidaweb.si > > -- Best regards, Igor Stasenko AKA sig.

Feb. 2, 2011