April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Lost in spec

by stepharo

Igor where is your code so that I can give a try? On 22/4/14 13:56, Igor Stasenko wrote: > i want to use different adaptor for TextModel, when opening my UI > so that when widget is built for it, it will be my own widget, > not PluggableTextMorph.. > > but i found it hard to do.. here what i tried: > > > I try to replace bindings, so at the stage when spec interpreted, it > uses my bindings: > > openWithSpec > > | old result | > old := SpecInterpreter bindings. > > SpecInterpreter bindings: TxAdapterBindings new. > > [ result := super openWithSpec ] > ensure: [ SpecInterpreter bindings: old ]. > ^ result > > > in TxAdapterBindings i initialize it same as morphic bindging, except > from text model binding: > #TextAdapter => #TxTextAdapter > > but it is never invoked nor used :( > > i understand the overall model, but it seems like not completely, > (else the above trick would work).. what do i miss? > > -- > Best regards, > Igor Stasenko.

April 22, 2014

Re: [Pharo-dev] updated documentation on magritte?

by stepharo

Not that I know. I started a chapter on the pharo for the entreprise (with the idea to base it on the seaside book) but I need help. If you start writing a draft I will do a pass. Stef On 22/4/14 09:28, Esteban Lorenzano wrote: > Hi, > > is there an updated documentation on magritte? where can I find it? > > cheers, > Esteban > >

April 22, 2014

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

by Sven Van Caekenberghe

TimeStamp is deprecated, because it creates too much confusion, you better use DateAndTime. On 22 Apr 2014, at 17:11, roberto.minelli(a)usi.ch wrote: > "TimeStamp now" rounds the timestamp, so #asNanoSeconds returns the seconds * 10e9. > > Doing âDateAndTime nowâ solves my issue, but this is a total non-sense. > > Cheers, > R > > On Apr 22, 2014, at 4:54 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Well, it has #asNanoSeconds, how finer can you go? >> >> Uko >> >> On 22 Apr 2014, at 17:13, roberto.minelli(a)usi.ch wrote: >> >>> Hi, >>> >>> I am wondering if there is the possibility to get milliseconds in a TimeStamp. >>> >>> I need to record fine-grained events and second-granularity is not enough. >>> >>> Cheers, >>> Roberto >> >> > >

April 22, 2014

Versionner screencast

by Christophe Demarey

Hello, I made a small screencast on Versionner to explain how to use it: https://www.youtube.com/watch?v=S5Dbmmln8tA Regards, Christophe.

April 22, 2014

Re: [Pharo-dev] Smalltalk Hub on Chrome

by Nicolas Petton

Sean P. DeNigris writes: > I noticed sometimes sthub hangs forever on Chrome (Version 34.0.1847.116 on > Mavericks), but if I open it alongside in Safari, it loads fine... Does the page load but stays without content, or is it another issue? Nico > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- Nicolas Petton http://nicolas-petton.fr

April 22, 2014

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

by roberto.minelli＠usi.ch

"TimeStamp now" rounds the timestamp, so #asNanoSeconds returns the seconds * 10e9. Doing âDateAndTime nowâ solves my issue, but this is a total non-sense. Cheers, R On Apr 22, 2014, at 4:54 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Well, it has #asNanoSeconds, how finer can you go? > > Uko > > On 22 Apr 2014, at 17:13, roberto.minelli(a)usi.ch wrote: > >> Hi, >> >> I am wondering if there is the possibility to get milliseconds in a TimeStamp. >> >> I need to record fine-grained events and second-granularity is not enough. >> >> Cheers, >> Roberto > >

April 22, 2014

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

by Stefan Marr

Hi Sean: First of all, I enabled public write access on the repository. While I am the admin on the project, I took it over from Niko and Adrian, and at this point, I would consider it âcommunity maintainedâ. The rest inline: On 22 Apr 2014, at 16:40, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > - change matcher #= to #equal: e.g. "1 should = 1" would now be written "1 > should equal: 1" > > Motivation: the #= magic made it impossible to store matchers in > dictionaries, and #hash was implemented to signal an error explaining as > much. Unfortunately, #= and #hash are deeply ingrained Smalltalk concepts, > and are assumed to work as expected. In Pharo 3.0, the debugger tried to put > matchers in a dictionary, causing an infinite error loop whenever a matcher > failed. I personally donât have a qualified opinion, in the sense that I do not actively use Phexample at the moment. Still, I will state it anyway: I donât like the change. So, just for the sake of argument, are there other ways? Are matchers reused, or are they one-shot things? If the later is true, perhaps, we could maintain the âcutenessâ of #= by making the matchers a little more cooperative? If they are one-shot objects, how about using their standard behavior only on the first access, and then switch their state so that #= and #hash respond normally? Thanks Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

April 22, 2014

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

by Yuriy Tymchuk

Well, it has #asNanoSeconds, how finer can you go? Uko On 22 Apr 2014, at 17:13, roberto.minelli(a)usi.ch wrote: > Hi, > > I am wondering if there is the possibility to get milliseconds in a TimeStamp. > > I need to record fine-grained events and second-granularity is not enough. > > Cheers, > Roberto

April 22, 2014

Smalltalk Hub on Chrome

by Sean P. DeNigris

I noticed sometimes sthub hangs forever on Chrome (Version 34.0.1847.116 on Mavericks), but if I open it alongside in Safari, it loads fine... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 22, 2014

Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

by Sean P. DeNigris

Reverting EyeInspector>>#updateList revealed the error when Phexample is used in latest Pharo 3.0... PhexMatcher uses #= as part of it's DSL e.g. "1 should = 1". Because it doesn't respond normally to #=, #hash is implemented to signal an error (self error: 'Don''t put a matcher into a dictionary. It does not behave ordinarily on ='). I guess the receiver inspector on the bottom left of the debugger keeps the items in a dictionary, so #hash gets called and everything blows up. The first thought that comes to my mind is that #= is "too cute" as a DSL. #= is too deep of a smalltalk concept to justify hijacking, AFAICT to avoid writing equals:. I removed #= and #hash from PhexMatcher, adding an #equals: with the former #= implementation, and everything seems to work. I don't have write access to http://smalltalkhub.com/mc/Phexample/Phexample/main/ and realize it's a big API change, so I committed the fix to http://smalltalkhub.com/mc/SeanDeNigris/SeansOutbox/main/ : Name: Phexample-SeanDeNigris.71 MAJOR API CHANGE: - change matcher #= to #equal: e.g. "1 should = 1" would now be written "1 should equal: 1" - update all code to use new API Motivation: the #= magic made it impossible to store matchers in dictionaries, and #hash was implemented to signal an error explaining as much. Unfortunately, #= and #hash are deeply ingrained Smalltalk concepts, and are assumed to work as expected. In Pharo 3.0, the debugger tried to put matchers in a dictionary, causing an infinite error loop whenever a matcher failed. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Phexample-API-Change-Proposal-was-Phexample-Image-Des… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 22, 2014