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

Re: [Pharo-dev] Units package access

by Marcus Denker

On 15 Dec 2013, at 16:51, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Hi all, > I want to commit some modifications to Units package: > http://smalltalkhub.com/#!/~MarcusDenker/Units > > Could someone provide me access to the repository ? > My ID: SergeStinckwich > Done! Marcus

Dec. 15, 2013

Re: [Pharo-dev] Units package access

by StÃ©phane Ducasse

On Dec 15, 2013, at 4:50 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Hi all, > I want to commit some modifications to Units package: > http://smalltalkhub.com/#!/~MarcusDenker/Units > > Could someone provide me access to the repository ? > My ID: SergeStinckwich marcus should do it because I'm just a contributor. > > Thank you. > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

Dec. 15, 2013

Re: [Pharo-dev] Is it possible to load and display pdfs inside pharo ?

by StÃ©phane Ducasse

> Is there any plan to display Pier files inside Pharo via Athens or Spec/Morphic ? In fact yes but no time. Igor did a markdown displayer using Athens (no idea where it is) but we could reuse it and it would be great > > > On Fri, Dec 13, 2013 at 5:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > So far I do not think so but I know that the open-source library of pdf developed by christian Haider on VW > can do it. > > Stef > > >> I was wondering if there is a library to load and display or at least parse pdf files for pharo. >> > >

Dec. 15, 2013

Re: [Pharo-dev] strange bug when opening the morph menu

by StÃ©phane Ducasse

On Dec 14, 2013, at 10:26 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > If you press and hold the mousebutton the menu is visible. > If you just click the mousebutton the menu flashes for a short time > and the window is in "grab" mode. I tried to understand your actions but I could not. I clicked and press long on different part of the workspace but I could not see a problem > Actually the grab-menu item is selected, because the menu > is such wide, that it does not open beneath the mouse pointer, > and so the mouse pointer is always over some menu item. > (at leas with on windows) > > If you have a normal workspace title bar, the menu stays on even if > you just click the mousebutton. > > nicolai > > > > 2013/12/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > >> Hi, >> >> Try this: >> >> 1. Execute >> Workspace open >> 2. Try to get the menu of the window >> ==> it opens just fine >> >> 1. Execute >> Workspace open label: (1 to: 100) asOrderedCollection asString >> 2. Try to get the menu of the window >> ==> it does not open properly (it opens large and it closes quickly) and the mouse remains in dragging mode > > I do not get this problem. > When I want to edit the title it just takes the complete screen width. > >> >> I opened a bug report: >> https://pharo.fogbugz.com/f/cases/12426/Morph-menu-has-strange-behavior-whe… >> >> Does anyone have any idea of why it happens? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow." > >

Dec. 15, 2013

Re: [Pharo-dev] Another thought about globals

by StÃ©phane Ducasse

On Dec 15, 2013, at 11:22 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 14.12.2013 um 21:08 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >>> Hi Norbert-- >>> >>>> Class names are globals. A class is registered in a global namespace >>>> by its name. Names need to be looked up. How should it work in >>>> another way? >>> >>> Get rid of globals. Make the root classes elements of the special >>> objects array (Object already is), and look up classes through that. >>> Make everything else that used to be a global (like Transcript) the >>> responsibility of some class, and use them by sending messages. This >>> also makes the modularization straightforward. >> >> This is what we did with >> Smalltalk -> self environment. >> Smalltalk -> SmalltalkImage current >> >> Now I wonder if it really solves the problem that has igor (this is true that I would prefer to avoid to >> have specific declaration. >> Now what would be good is to have a protocol to systematically initialize such "global" even when they >> are attached to classes. >> > What speaks against Package>>#initialize ? You cannot easily build tools with this approach > Or package having a selector returning the list of package wide globals and a selector for each global to create the value for it? would be much better > What is the difference between a dependency to a package and the access to its globals? Shouldn't the package not having defined its dependencies and couldn't that mean the same information composes the "global" namespace for this package? I could not understand what you meant :) > > Norbert >>> There's no need for a system dictionary. It was a profound and >>> long-lived mistake. >> >> In the midterm I want to get rid of it (by splitting it and distributing into module) but it will take >> time. >

Dec. 15, 2013

Units package access

by Serge Stinckwich

Hi all, I want to commit some modifications to Units package: http://smalltalkhub.com/#!/~MarcusDenker/Units Could someone provide me access to the repository ? My ID: SergeStinckwich Thank you. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 15, 2013

Re: [Pharo-dev] methodDict versus methodDictionary

by StÃ©phane Ducasse

>> but I have 103 send of methodDict in my image >> > Yes, I am slowly removing them, but that takes time (I removed quite a lot over the last months! A *lot*!) Ok excellent I did not know that. > I even added a lint rule detecting calls to #methodDict. > >> So I do not get it and personally I would not deprecate methodDictionary and I would remove >> methodDict because it sucks! > > methodDict should *never* be used from the outside. Itâs far too easy to get problems because you modify the dictionary > without e.g. invalidating the VM cache or telling the system. > > And it gets *much* easier to read: > > methodDict values â> methods > methodDict keys â> selectors > methodDict size > 0 â> #hasMethods > and so onâ¦ itâs amazing how much more readable code gets. > > So why do we provide a âniceâ selector âmethodDictionaryâ if this is a private accessor for internal state? > If we do that it communicates âuse meâ! And you should not. If you want to use it, you know what you are doing > and you know #methodDict. I disagree here. In that case we should start using vv jyv jvzxxx. We should put the method in a private category and we should add a comment. > And if people use it, the #methodDict is so deep in the brain of people that they never used #methoDictionary > (there where maybe 5 sendersâ¦). Still I would rename it. Stef

Dec. 15, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 15, 2013

[pharo-project/pharo-core] ad29ad: 30645

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: ad29adb38aacff04fe1b5ab6e9b6a1854d744eca https://github.com/pharo-project/pharo-core/commit/ad29adb38aacff04fe1b5ab6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-15 (Sun, 15 Dec 2013) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script298.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30645.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Inspector.package/extension/SmallDictionary/class/inspectorClass.st R Spec-Inspector.package/extension/SmallDictionary/instance/inspectorClass.st A Transcript.package/ThreadSafeTranscript.class/class/declare/installThreadSafeAsSTranscript.st Log Message: ----------- 30645 12395 ThreadSafeTranscript examples do not work due to a missing method https://pharo.fogbugz.com/f/cases/12395 12428 Error while printing element https://pharo.fogbugz.com/f/cases/12428 http://files.pharo.org/image/30/30645.zip

Dec. 15, 2013

Re: [Pharo-dev] [ANN] traversal-enabled objects with DeepTraverser

by Tudor Girba

Hi, On Sat, Dec 14, 2013 at 3:44 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > > On Wed, Dec 11, 2013 at 12:21 PM, Tudor Girba <tudor(a)tudorgirba.com>wrote: > >> Hi, >> >> I put together a little implementation for traversals. It is inspired by >> an original implementation from Mariano. >> > > Wow... my memory is sooo bad I don't remember ;) > I asked once for something that can compute the size of an object, and you sent me a GraphTraverser class. I extended this concept and generalized it a bit. > > >> Using DeepTraverser, you can traverse arbitrary graphs by describing the >> traversal and by specifying the actions you want to perform on the nodes >> and relations. >> >> > Once (or even more times) we thought with Martin 2 things: > > 1) Reify the traversal in Fuel so that we could plug a different one. > 2) Use Fuel only for traversing and allowing user a hook to plug the what > to do with each node. > 3) Use the same traversal of 2) for deepCopying > 4) Use the same traversal of 2) to get an approximate memory consumption > of the transitive closure of an object > This would be great. > But as always happened we run out of time. > > Anyway...I think this is a nice area to explore. There are many uses for a > nice traverser. > Agreed. It would be great to build on DeepTraverser and make it more powerful. Also, did you see we wrote a Rossal extension to print the fuel traversal? > > http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.9/Documentation/… > Yes. That is cool :) Doru > The code is available in the Moose image as part of the MooseAlgos >> subproject, but can also be loaded separately in a Pharo image via: >> >> Gofer new >> url: 'http://www.smalltalkhub.com/mc/Moose/DeepTraverser/main'; >> package: âConfigurationOfDeepTraverserâ; >> load. >> (Smalltalk globals at: #ConfigurationOfDeepTraverser) loadDevelopment. >> >> >> Just to give you an idea, here are some representative examples: >> >> Number >> deep: #subclasses >> do: [:each | Transcript show: each; cr]. >> >> Number deepCollect: #subclasses. >> >> Number >> deep: #subclasses >> collect: #name. >> >> Number >> deep: #subclasses >> do: [:each | Transcript show: each; cr] >> relationDo: [ :from :to | Transcript show: from; show: ' <-- '; show: >> to; cr ]. >> >> >> >> More details about the usages and a little description of the >> implementation can be found here: >> http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects/ >> >> >> Cheers, >> Doru >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 15, 2013