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

Re: [Pharo-dev] untypeable key combination

by Nicolai Hess

Fogbugz issue 14936 and slice in inbox After loading this slice, there are still many references to the (now) obsolete class KMUntypeableSingleKeyCombination. I tried to remove these references with the following code : NECPreferences popupShowWithShortcut: nil. KMSingleKeyCombination reset. KMSpecialCharSingleKeyCombination reset. KMRepository reset. But they arent removed. Anyone knows how to re-init all users of KMUntypeableSingleKeyCombination ? nicolai 2014-12-08 15:05 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > I think (I just think because I didn't write that class ^^) that class is > the result of an unfinished refactor... > > On Mon, Dec 8, 2014 at 2:36 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> Le 7/12/14 12:21, Nicolai Hess a Ã©crit : >> >> We have a class KMUntypeableSingleKeyCombination >>> this is used for key kombinations with >>> tab >>> arrow >>> backspace .... >>> >>> This is useful for printing key kombinations like >>> Ctrl+TAB >>> >>> "space" does not use the KMUntypeableSingleKeyCombination class, >>> therefore >>> a short cut like >>> Character space shift asKeyCombination >>> looks like >>> " Shift + " >>> >>> shouldn't space use this class? >>> And I find the name a little bit misleading, what is a untypeable key? >>> The key is typeable, otherwise we couldn't use it. >>> Renaming the class to KMUnprintableSingleKeyCombination >>> isn't better, because we can print this keycombination. >>> >>> >> +1 >> >>> >>> nicolai >>> >>> >> >> >

Feb. 19, 2015

Re: [Pharo-dev] [Slots] Invisible Slots

by Marcus Denker

> > > I started to implement PropertySlot, this uses hidden slots, initialisation (to set the empty dictionary of the base slot), virtual slots > (the proper slots), reflectively changing the class both when adding and removing (to add the base slot and remove it as needed). > Next tiny step: 14914 #initializeSlots: should not skip hidden slots https://pharo.fogbugz.com/f/cases/14914/initializeSlots-should-not-skip-hid… Now the slots get correctly called when initialising an object. To test: Object subclass: #TT slots: { #tt => PropertySlot } classVariables: { } category: âPlayground' The slot will add an #initialize methods to the class when it gets installed. When you inspect TT new you can see just the tt slot (you can change it in the inspector). Adding an accessor for tt will show what the compiler does: 21 <20> pushConstant: #tt => PropertySlot 22 <70> self 23 <E1> send: read: 24 <7C> returnTop this means that it compiles a reflective read for that slot. next: -> remove the hidden slot when removing the last property slot -> add a GTInspector view that shows the *real* object layout -> when adding a propertySlot higher up in the hierarchy where there are already some down, we need to move the base slot up. -> generate better byte code, the reflective read is of course slow. Tiny stepsâ¦ Marcus

Feb. 19, 2015

Re: [Pharo-dev] Why was #asLegalSelector removed?

by stepharo

Because we were analysing the string API and trying to clean it. Now this analysis is publicly available on https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/StringCl… Now I'm quite sure that I do not want to get such behavior into string: why string is responsible to convert junk into a "selector" which cannot even accept the fact that it could need a : This code is bogus and shitty. Stef asLegalSelector "'234znak 43 ) 2' asLegalSelector2" | toUse | toUse := self select: [:char | char isAlphaNumeric]. (toUse size = 0 or: [ toUse first isLetter not ]) ifTrue: [ toUse := 'v', toUse ]. ^ toUse withFirstCharacterDownshifted > As mentioned in Stephan's recent comment in > https://pharo.fogbugz.com/default.asp?13754 , some of us were using it. What > was the rationale? Maybe removing methods warrants a discussion on the list? > How about deprecations? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Why-was-asLegalSelector-removed-tp4806427.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Feb. 19, 2015

Re: [Pharo-dev] something else than a stupi timestamp in pane of the glamour workspace.... please

by stepharo

Do I put 'Pane 1' instead of this timestamp and it took me around 15 s to do it. So I guess that this is possible to propose a simple fix, isn't Stef Le 18/2/15 21:27, Tudor Girba a Ã©crit : > That's because this part is not finished :). It should come, hopefully > before the feature freeze. Otherwise, we can treat it as a bug :D > > Doru > > On Wed, Feb 18, 2015 at 8:52 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > something else than a stupi timestamp in pane of the glamour > workspace.... please > please please please. > It gives this impression that pharo is not finished at all. > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Feb. 19, 2015

Why was #asLegalSelector removed?

by Sean P. DeNigris

As mentioned in Stephan's recent comment in https://pharo.fogbugz.com/default.asp?13754 , some of us were using it. What was the rationale? Maybe removing methods warrants a discussion on the list? How about deprecations? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Why-was-asLegalSelector-removed-tp4806427.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 19, 2015

Re: [Pharo-dev] Ubunti 14.04 32bit install error

by bsselfridge＠gmail.com

Just tried installing "pharo-launcher" again and am getting the following error: Errors were encountered while processing: /var/cache/apt/archives/pharo-vm-core-i386_2014.11.29-16~ppa1~trusty1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ----- Brad Selfridge -- View this message in context: http://forum.world.st/Ubunti-14-04-32bit-install-error-tp4805391p4806426.ht… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 19, 2015

[FIX (Maybe ; ))]: Issue 14959: MC Hook for Default Credentials

by Sean P. DeNigris

Fix in inbox: SLICE-Issue-14959-MC-Hook-for-Default-Credentials-SeanDeNigris.1 When creating a repo in the MC Browser, it would be great to pre-populate the user and password fields. Thus, we declare a CredentialSource role collaborating with MCHttpRepository and subclasses. The in-kernel default is a no-op Null object, but users can install (via MCHttpRepository class>>#credentialSource:) any object that responds to #defaultUserFor: and #defaultPasswordFor: I'd like to apply this to Gofer, too, but I found a big switch statement in ZnUrl>>#mcRepositoryAsUser:withPassword: and now my head hurts ;) Anyway maybe this will spur discussion... ----- Cheers, Sean -- View this message in context: http://forum.world.st/FIX-Maybe-Issue-14959-MC-Hook-for-Default-Credentials… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 19, 2015

Re: [Pharo-dev] something else than a stupi timestamp in pane of the glamour workspace.... please

by Tudor Girba

That's because this part is not finished :). It should come, hopefully before the feature freeze. Otherwise, we can treat it as a bug :D Doru On Wed, Feb 18, 2015 at 8:52 PM, stepharo <stepharo(a)free.fr> wrote: > something else than a stupi timestamp in pane of the glamour workspace.... > please > please please please. > It gives this impression that pharo is not finished at all. > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 18, 2015

something else than a stupi timestamp in pane of the glamour workspace.... please

by stepharo

something else than a stupi timestamp in pane of the glamour workspace.... please please please please. It gives this impression that pharo is not finished at all.

Feb. 18, 2015

Re: [Pharo-dev] Super fast delay

by stepharo

would be so great to get that in pharo 40. Le 16/2/15 15:21, Ben Coman a Ã©crit : > This is the issue [1]. I did a fix a while ago, but its preload (see > issue) stops Delay processing while it loads, which locked up the UI > loop and Integration Tool. That was recently fixed by issue [2], but I > wanted to rebase the [1] on the latest Pharo - but first I should > strip out #newCodeEnabled: wrappers to make review of [1] easier. > There is a new issue [3] for that. > > Now if you tell me you are keen to review [3] and [1] when they are > ready, I'll bump them to the top of my queue. > > [1] https://pharo.fogbugz.com/default.asp?14669 "Delay refactoring > (part 2) - change from milliseconds to microseconds" > [2] https://pharo.fogbugz.com/default.asp?14669 "Delay refactoring > (part 2a) - avoid UI locking up when timer event loop is stopped" > [3] https://pharo.fogbugz.com/default.asp?14942 "Delay refactoring > (part 2b) - clean out newCodeEnabled wrappers" > > cheers -ben > > On Mon, Feb 16, 2015 at 4:01 PM, Holger Hans Peter Freyther > <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: > > On Thu, Oct 30, 2014 at 06:32:48PM -0400, stepharo wrote: > > Good Morning Ben, Stef, > > > We really need people to have a look at the code of Ben. > > I downloaded a Pharo-4 image today and executed: > > time pharo --nodisplay --headless ./Pharo-40490.image eval > "(Delay forSeconds: 5) wait" > a Delay(5000 msecs) > > real 0m1.254s > user 0m1.192s > sys 0m0.060s > > > So the first delay doesn't appear to wait the five seconds. I > would like to work on kqueue/epoll and remove polling and it > looks this involves code with Delay as well. I wonder if you > could provide an overview of what needs to be done and what is > done? > > thanks > holger > > > >

Feb. 18, 2015