- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [squeak-dev] Re: IdentitySet>>collect:

by Eliot Miranda

Hi Nicolai, On Nov 28, 2014, at 4:01 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-11-28 16:39 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >> >> On Fri, Nov 28, 2014 at 4:26 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> > On 28 Nov 2014, at 15:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> > >>> > >>> >> On 27 Nov 2014, at 08:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >> >>> >> >>> >>> On 26 Nov 2014, at 19:19, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>> >>> >>> Hi All, >>> >>> >>> >>> IdentitySet>>collect: answers a Set, not an IdentitySet. Anyone else agree this is a serious bug? Anyone else disagree? >>> >>> >>> >>> WTF?? >>> >>> >>> >>> (IdentitySet withAll: #(1 2 3 1.0 2.0 3.0)) collect: [:e| e] a Set(1.0 2 3) >>> >> >>> >> Yes, I would say so. I think we fixed some others like that already (not 100% sure) >>> >> >>> >> I added an issue tracker entry >>> >> >>> >> 14535 IdentitySet>>collect: answers a Set, not an IdentitySet. >>> >> https://pharo.fogbugz.com/f/cases/14535 >>> >> >>> > >>> > #collect: directly uses Set in Set>>#collect, I committed a fix (to the issue tracker, to be reviewed) >>> > to use âself speciesâ instead (plus the example from above as a test in IdentitySetTest). >>> > >>> > Marcus >>> >>> I think that is the most logical thing to do, it is what I would expect. >>> >>> I know others have cases where that is not really what you want (some of Set's subclasses are pretty special), but it is still a good default, while #collect:as: can be used for all other cases (and subclasses can override #species again if they want). >> >> Hmm... errors found by the test runner on that change. >> >> https://ci.inria.fr/pharo/job/Pharo-4.0-Issue-Validator/17683//artifact/val… >> >> So we will need to check... >> >> Marcus > > > In pharo, the problem is the OCKeyedSet, but the same happens in squeak with a KeyedSet. > Changing Set>>#collect: to use "self species new" the following code fails: > > k:=KeyedSet new keyBlock:[:e | e name]. > k addAll:{ Color red . Color blue . Color green}. > k collect:[:e | e ]. > --> MessageNotUnderstood: Color>>key And if you implement species in KeyedSet to answer Set (which should fix this one issue) does anything else break? Eliot (phone)

Nov. 29, 2014

Re: [Pharo-dev] SmalltalkHub bugs & hangs :-(

by volkert＠nivoba.de

Am 27.11.2014 um 11:46 schrieb Sven Van Caekenberghe: >> On 27 Nov 2014, at 11:14, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >> >> SmalltalkHub is slow, so donât click too fast :-( >> >> While Iâm grateful to developers of SmalltalkHub and previously SqueakSource, I believe as a small community, we cannot afford developing everything by ourselves. We donât have enough man-power. We can see the symptoms since SmalltalkHub is in beta stage since way too long... >> >> Itâs better to use some mainstream platform such as github. >> Weâll we have support for it in Pharo 4? >> >> It would be interesting also from the communication point of view to make the world a little bit more aware of Pharo. > I think it is important to have a serious online system written in Pharo and in daily use (you know, eat your own dog food). > > There is also a difference between the system itself and the way it is deployed/managed. > > Please do not underestimate how much work this is for something that is used so heavily, like StHub. > Yes, this is important for Pharo in some way. But such a the system have to be maintained and developed further/keept up to date, otherwise it has a bad impact. But i have the feeling in Pharo so many cool things started and then slowly waste away ... Why? The Community is to small, ... the cool guys move further. The PhD is finished ... Gaps hard to close. Would be sad, if this happens to SmalltalkHub. There should be only 2-3 public, open source key systems (or type of systems) where to put the focus on and give them a long term perspective & support from the association / consortium or other donators. And the systems and its building blocks should move with Pharo in the future. And the system should be in some obviously way special & exceptional ... and part of the "Pharo Masterplan". (a) Data Analysis & Visualization System => ?? MOOSE ?? => Key Building Blocks: f.e. Roassal2/3D, ZincHTTP, NeoCSV, NeoJSON, ... (b) Online/Web System => ?? SmalltalkHub ?? => Key Building Blocks: f.e. Amber, Seaside, ZincHTTP, NeoCSV, NeoJSON, ... (c) A Cool Game (would love it) => ??? => Key Building Blocks: ??? (d) ??? I know, it is easy to say. But the best promotion for Pharo are cool systems in Pharo. But maybe Pharo has not more potential than doing one type of systems right and ongoing, f.e. (a). I have no problems with it. I like Pharo for (a) as i like Erlang/OTP for (b) and Lua/Love2D for (c). The coolest would be a perspective for (a), (b), (c) and (d) in Pharo. But i do not see it ... But yes, it is better to do one or two things good, and not a five bad. My 2 cents, Volkert

Nov. 29, 2014

Re: [Pharo-dev] [squeak-dev] Re: IdentitySet>>collect:

by Nicolai Hess

2014-11-28 16:39 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On Fri, Nov 28, 2014 at 4:26 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> >> > On 28 Nov 2014, at 15:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> > >> > >> >> On 27 Nov 2014, at 08:21, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >> >> >> >> >>> On 26 Nov 2014, at 19:19, Eliot Miranda <eliot.miranda(a)gmail.com> >> wrote: >> >>> >> >>> Hi All, >> >>> >> >>> IdentitySet>>collect: answers a Set, not an IdentitySet. Anyone >> else agree this is a serious bug? Anyone else disagree? >> >>> >> >>> WTF?? >> >>> >> >>> (IdentitySet withAll: #(1 2 3 1.0 2.0 3.0)) collect: [:e| e] a >> Set(1.0 2 3) >> >> >> >> Yes, I would say so. I think we fixed some others like that already >> (not 100% sure) >> >> >> >> I added an issue tracker entry >> >> >> >> 14535 IdentitySet>>collect: answers a Set, not an IdentitySet. >> >> https://pharo.fogbugz.com/f/cases/14535 >> >> >> > >> > #collect: directly uses Set in Set>>#collect, I committed a fix (to the >> issue tracker, to be reviewed) >> > to use âself speciesâ instead (plus the example from above as a test in >> IdentitySetTest). >> > >> > Marcus >> >> I think that is the most logical thing to do, it is what I would expect. >> >> I know others have cases where that is not really what you want (some of >> Set's subclasses are pretty special), but it is still a good default, while >> #collect:as: can be used for all other cases (and subclasses can override >> #species again if they want). >> >> > Hmm... errors found by the test runner on that change. > > > https://ci.inria.fr/pharo/job/Pharo-4.0-Issue-Validator/17683//artifact/val… > > So we will need to check... > > Marcus > In pharo, the problem is the OCKeyedSet, but the same happens in squeak with a KeyedSet. Changing Set>>#collect: to use "self species new" the following code fails: k:=KeyedSet new keyBlock:[:e | e name]. k addAll:{ Color red . Color blue . Color green}. k collect:[:e | e ]. --> MessageNotUnderstood: Color>>key

Nov. 29, 2014

Re: [Pharo-dev] Compilation error of the PharoEnterprise book with luatex

by kilon alios

have you tried MacTex ? https://tug.org/mactex/ its what I use with my iMac and so far has been working for me without any issues. On Sat, Nov 29, 2014 at 12:02 AM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi All, > > I cannot compile the latest version in SquareBracketAssociates/ > EnterprisePharo.git > My problem is that the "FiraSans" cannot be found. > But in common.tex, the font path is correctly set up and the font is there. > > So on CI which version of luatex is used? > I did not find it in the Jenkins log. > > I am using LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_1) > (rev 4971) > > Cheers, > > #Luc >

Nov. 28, 2014

Re: [Pharo-dev] Compilation error of the PharoEnterprise book with luatex

by Ben Coman

Luc Fabresse wrote: > Hi All, > > I cannot compile the latest version in > SquareBracketAssociates/EnterprisePharo.git > My problem is that the "FiraSans" cannot be found. > But in common.tex, the font path is correctly set up and the font is there. > > So on CI which version of luatex is used? > I did not find it in the Jenkins log. > > I am using LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_1) > (rev 4971) > > Cheers, > > #Luc I don't know the answer, instead... its an interesting exercise to work out how to get a shell on the CI slaves https://wiki.inria.fr/ciportal/Slaves_Access_Tutorial Then you can check the version yourself :) Happy fishing... cheers -ben

Nov. 28, 2014

Compilation error of the PharoEnterprise book with luatex

by Luc Fabresse

Hi All, I cannot compile the latest version in SquareBracketAssociates/ EnterprisePharo.git My problem is that the "FiraSans" cannot be found. But in common.tex, the font path is correctly set up and the font is there. So on CI which version of luatex is used? I did not find it in the Jenkins log. I am using LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_1) (rev 4971) Cheers, #Luc

Nov. 28, 2014

Re: [Pharo-dev] Fix wikipedia article

by Sebastian Sastre

Ahh yeah. Youâre right, I read it too quick and in the wrong context and thought was talking about Purism in programming languages giving only functional as example. Never mind about that pageâ¦ And yet we could start one where we could talk about it. Here is an idea: LISP: "Everything is an Expressionâ Haskell and Miranda: "Everything is a Functionâ Self and Smalltalk: "Everything is an Object" could easily do a wikipedia page on âParadigmatic Programming Languagesâ or something like that Iâm not an academic but sounds like their beach and sounds to me it could be quite a reference > On Nov 28, 2014, at 2:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 28 Nov 2014, at 16:55, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> >> Hi guys, >> >> Just a heads upâ¦ >> >> This is asking for a fix: >> http://en.wikipedia.org/wiki/Pure_(programming_language) >> >> LISP and Self and Smalltalk people should add their voice there >> >> Unleash your nerd :) > > I don't understand, what do you mean ? > > The page describes some language called Pure that seems to be legit, so what is wrong with that (apart from the name being ambitious, pretentious) ? > > And there is http://en.wikipedia.org/wiki/Pharo which is OK but needs some love. > >

Nov. 28, 2014

[pharo-project/pharo-core] b0326f: 40390

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: b0326f5e79a6040644317b02654b5d1a5991261e https://github.com/pharo-project/pharo-core/commit/b0326f5e79a6040644317b02… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-28 (Fri, 28 Nov 2014) Changed paths: M Growl.package/GrowlMorph.class/class/settings/growlSettingsOn_.st R NautilusRefactoring.package/CodeCriticBrowser.class/README.md R NautilusRefactoring.package/CodeCriticBrowser.class/class/specs/defaultSpec.st R NautilusRefactoring.package/CodeCriticBrowser.class/class/specs/title.st R NautilusRefactoring.package/CodeCriticBrowser.class/class/specs/topSpec.st R NautilusRefactoring.package/CodeCriticBrowser.class/definition.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/environment.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/environment_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/listModel1.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/listModel1_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/listModel2.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/listModel2_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/listModel3.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/listModel3_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/process.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/process_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/status.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/status_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/textModel.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/accessing/textModel_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/initialization/initializePresenter.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/initialization/initializeWidgets.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/processing/basicSearch_.st R NautilusRefactoring.package/CodeCriticBrowser.class/instance/protocol/rules_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/class/removeClasses_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/option/selectVariableToMoveMethodTo_class_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-method/privateDeprecateMethodFor_.st R NautilusRefactoring.package/extension/TClassDescription/instance/renameMethodAllItem_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script390.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40390.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Traits.package/TClassDescription.class/instance/as yet unclassified/renameMethodAllItem_.st Log Message: ----------- 40390 14544 tiny code critique cleanup of NautilusRefactoring https://pharo.fogbugz.com/f/cases/14544 14543 Pharo4.0 settings do have Appearance and appearance (twice the entries that is) https://pharo.fogbugz.com/f/cases/14543 http://files.pharo.org/image/40/40390.zip

Nov. 28, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40390 Home: https://github.com/pharo-project/pharo-core

Nov. 28, 2014

Re: [Pharo-dev] 7350 window drag ghosting while progress bar is moving

by Esteban Lorenzano

this was happening because of morphic colliding with a process, so I think is safe to close it. Esteban > On 28 Nov 2014, at 17:05, Ben Coman <btc(a)openInWorld.com> wrote: > > > A while ago I logged an issue "window drag ghosting while progress bar is moving" [1] - but I haven't noticed this for a long time. Before I close it, has anyone had any similar problems with Pharo 4 ? > > [1] https://pharo.fogbugz.com/default.asp?7350 > > cheers -ben > > > <window+move+ghosting.png>

Nov. 28, 2014