- Pharo-dev - lists.pharo.org

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

by Tudor Girba

Exactly, Nicolai! Thanks for reproducing. I added your description to the issue. Essentially, I just wanted to get the halo menu in order to export a debugger window to png. Doru On Sat, 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. > 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." >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 15, 2013

Re: [Pharo-dev] Another thought about globals

by Norbert Hartl

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 ? Or package having a selector returning the list of package wide globals and a selector for each global to create the value for it? 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? 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

Re: [Pharo-dev] NBOpenGL commit permissions

by StÃ©phane Ducasse

done try and let me know. On Dec 15, 2013, at 12:35 AM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > Hello, > > I would like to request commit privileges to the PharoExtra/NBOpenGL smalltalk hub project, so that I can commit improvements made for Roassal 3D, but useful for anyone. > > My SmalltalkHub username is 'ronsaldo'. > > Greetings, > Ronie Salgado

Dec. 15, 2013

Re: [Pharo-dev] Another thought about globals

by Norbert Hartl

> Am 14.12.2013 um 20:38 schrieb Craig Latta <craig(a)netjam.org>: > > > 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. > > There's no need for a system dictionary. It was a profound and > long-lived mistake. > Sure. What I wrote before was implying exactly that. There are no globals except those few they are always there. The hard thing is always finding/composing stuff so it can be used. Not having a clever way to do this is preventing us from having namespaces. When this is solved I think it is not too hard to have more than one special objects array. This will bring us to object spaces within the same memory space. Norbert > > -C > > -- > Craig Latta > www.netjam.org/resume > +1 510 984 8117 > (Skype rings this until 31 January 2014) > >

Dec. 15, 2013

Re: [Pharo-dev] Athens: testing whether a point is within a path?

by Hilaire Fernandes

In the lists (-user or -devel), we had a thread on that topic a week ago. Hilaire Le 14/12/2013 20:46, Alexandre Bergel a Ã©crit : > Hi! > > I have seen that AthensPolygonTester may do the job somehow. > How can I test whether a point is included in a path? > > Cheers, > Alexandre > -- Dr. Geo http://drgeo.eu

Dec. 15, 2013

Re: [Pharo-dev] methodDict versus methodDictionary

by Marcus Denker

On 15 Dec 2013, at 09:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 14 Dec 2013, at 22:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi >> >> I do not understand why we deprecate methodDictionary and not methodDict (What a really bad name) >> I hate this inconsistent and lame name like methodDict and >> >> Marcus you mention on the bug entry >> >> nobody should access methodDict directly >> -> so why have a "nice" accessor for something not to be used? >> >> 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*!) > 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! > I actually thought about that. I did not move to #methodDictionary because - a lot of Smalltalk code used methodDict. Historically, e..g Squeak did not even have #methods on Classesâ¦ because that method was needed for fileIn backward compatibility with some ancient file out format. If you look, people use it a lot. You will not change that. So if we move the #methodDictionary, the system could use that in the 10 or so places where direct access is needed. But for externals, you would need to keep a non-deprecated #methodDict around (we can not remove it, no way). So therefore, just having #methodDict is better, I think. And then, itâs not that important. So going the way that take the least energy while being ok is the way to go here. (the only other alternative is to do nothing. Taking lots of pain just to have #methodDictionary instead of #methodDictâ¦ honestly, I think there are more important things to do) Marcus

Dec. 15, 2013

Re: [Pharo-dev] methodDict versus methodDictionary

by Marcus Denker

On 14 Dec 2013, at 22:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I do not understand why we deprecate methodDictionary and not methodDict (What a really bad name) > I hate this inconsistent and lame name like methodDict and > > Marcus you mention on the bug entry > > nobody should access methodDict directly > -> so why have a "nice" accessor for something not to be used? > > 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*!) 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. 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â¦). Marcus

Dec. 15, 2013

Re: [Pharo-dev] Are all SLICEs self-contained?

by HernÃ¡n Morales Durand

I see, thanks for explaining! Cheers, HernÃ¡n 2013/12/13 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 13 Dec 2013, at 08:19, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > As far as I know all mcz(s) are self contained. But slices for me are > still a big magic, so maybe there is something different. > > Any mcz can have required packages, dependencies that need to be loaded > with it, outside its own contents. > > A slice is an empty mcz, it has no contents of its own, but it does have a > set of required packages. So loading the slice loads the required packages. > When you make a slice, you select which dirty packages you want to add. > > This explain why sometimes a slice is empty: its required packages are > missing, either in specification, or in the repository. > > Sven > > > Uko > > > > > > On 13 Dec 2013, at 05:32, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > >> If not, how do I know if a SLICE depends on other SLICEs? > >> > >> For example loading > https://pharo.fogbugz.com/f/cases/edit/11282/Removal-DependentFields-refere… Monticello hangs the image and cannot interrupt with Alt+. Do I need > to load another SLICE before? > >> > >> Cheers, > >> > >> HernÃ¡n > >> > >> > > > > > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > >

Dec. 14, 2013

Re: [Pharo-dev] Similarity Matrix

by HernÃ¡n Morales Durand

Hi Alexandre, Just to provide you some feedback. My similarity matrices sometimes are calculated by other tools. However I want to display them using Roassal. For example this is a similarity matrix of 21 lines and 21 columns: ' a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 a12 a13 a14 a15 a16 a17 a18 a19 a20 a21 a1 1 0.130 0.132 0.130 0.158 0.189 0.130 0.022 1.000 0.062 0.083 0.061 0.080 0.059 0.149 1.000 0.098 0.161 0.109 1.000 0.000 a2 1 0.195 0.487 0.220 0.220 1.000 0.060 0.130 0.118 0.234 0.234 0.224 0.200 0.622 0.130 0.342 0.235 0.425 0.130 0.000 a3 1 0.195 0.464 0.464 0.195 0.073 0.132 0.116 0.114 0.256 0.109 0.085 0.133 0.132 0.105 0.320 0.171 0.132 0.000 a4 1 0.220 0.190 0.487 0.060 0.130 0.118 0.160 0.234 0.154 0.132 0.395 0.130 0.342 0.235 0.425 0.130 0.000 a5 1 0.500 0.220 0.071 0.158 0.195 0.220 0.389 0.209 0.182 0.156 0.158 0.162 0.417 0.225 0.158 0.000 a6 1 0.220 0.071 0.189 0.114 0.136 0.282 0.130 0.106 0.156 0.189 0.132 0.360 0.167 0.189 0.000 a7 1 0.060 0.130 0.118 0.234 0.234 0.224 0.200 0.622 0.130 0.342 0.235 0.425 0.130 0.000 a8 1 0.022 0.156 0.104 0.082 0.100 0.100 0.019 0.022 0.095 0.088 0.061 0.022 0.028 a9 1 0.062 0.083 0.061 0.080 0.059 0.149 1.000 0.098 0.161 0.109 1.000 0.000 a10 1 0.541 0.140 0.372 0.283 0.073 0.062 0.111 0.139 0.143 0.062 0.025 a11 1 0.160 0.714 0.579 0.176 0.083 0.133 0.200 0.163 0.083 0.024 a12 1 0.154 0.132 0.176 0.061 0.308 0.235 0.239 0.061 0.000 a13 1 0.676 0.170 0.080 0.128 0.189 0.157 0.080 0.023 a14 1 0.148 0.059 0.128 0.158 0.135 0.059 0.023 a15 1 0.149 0.262 0.158 0.341 0.149 0.000 a16 1 0.098 0.161 0.109 1.000 0.000 a17 1 0.207 0.316 0.098 0.000 a18 1 0.206 0.161 0.000 a19 1 0.109 0.000 a20 1 0.000 a21 1 ' lines collect: [ : line | line trimBoth findTokens: Character tab ] May be your Comparison class could be tailored to set manually rhs, lhs and similarity? What do you recommend for raw matrices? Cheers, HernÃ¡n 2013/11/29 Alexandre Bergel <alexandre.bergel(a)me.com> > Hi! > > I know some of you are working on DSM-kind of matrix. Oscar has been > working on a similarity matrix for Roassal. I just want to share a > self-explanble screenshot with you guys. > > > On this example, the methods of the subclasses of Set are compared between > themselves. > Black dot is a couple (m1, m2) that are very similar > > More on > https://www.facebook.com/media/set/?set=a.550677725018829.1073741833.340543… > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Dec. 14, 2013

NBOpenGL commit permissions

by Ronie Salgado

Hello, I would like to request commit privileges to the PharoExtra/NBOpenGL smalltalk hub project, so that I can commit improvements made for Roassal 3D, but useful for anyone. My SmalltalkHub username is 'ronsaldo'. Greetings, Ronie Salgado

Dec. 14, 2013