- Pharo-dev - lists.pharo.org

Spec table problem

by ClÃ©ment Bera

This example I used to have does not work any more in the latest Pharo 3: tree := TreeModel new. tree openWithSpec. tree columns: (Array with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content second asString ]; headerLabel: 'Last Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content third asString ]; headerLabel: 'Age'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content fourth asString ]; headerLabel: 'Gender'; yourself)). tree roots: { {'Benjamin'.'Van Ryseghem'.'26'.'M'} . {'Pamela'.'Anderson'.'Far too much'.'F'} }. How can I have a similar behavior to what it used to do ? Thanks !

Dec. 3, 2013

Re: [Pharo-dev] Opal hook?

by StÃ©phane Ducasse

> Well if the class does not exists it calls the method on UndefinedObject (UndeclaredBinding). And you have: I will check and see if I can set up a hook because having classes subclasses of protoobject is not a good idea when loading broken code. > UndefinedObject>>subclass: nameOfClass > instanceVariableNames: instVarNames > classVariableNames: classVarNames > poolDictionaries: poolDictnames > category: category > "Calling this method is now considered an accident. If you really want to create a class with a nil superclass, then create the class and then set the superclass using #superclass:" > self traceCr: ('Attempt to create ', nameOfClass, ' as a subclass of nil. Possibly a class is being loaded before its superclass.'). > ^ProtoObject > subclass: nameOfClass > instanceVariableNames: instVarNames > classVariableNames: classVarNames > poolDictionaries: poolDictnames > category: category > > The best is to set manually the superclass after with #superclass: No because I have no idea what are the classes whose superclasses are not in the image. With a proper hook I could just say if the superclass is unknow please use the "StubRootClass" of my framework. else let the system handles it. Stef

Dec. 3, 2013

Re: [Pharo-dev] Versionner CI?

by ClÃ©ment Bera

The jobs's on Rmod: https://ci.inria.fr/rmod/job/Versionner/ 2013/12/3 Sean P. DeNigris <sean(a)clipperadams.com> > I was surprised there was no job on community contributions... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Versionner-CI-tp4726899.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by StÃ©phane Ducasse

You know what? It will not be integrated because apparently the monkey tagged it as invalid. I have no idea why. I hate this automatic down grading. May be we should have a different tags to make the difference between work needed = nothing was done or something but it was never in the state where we could think it should be integrated was integration ready = it was ready but something happen Stef > Igor Stasenko wrote >> if yes then i think we can finally close the bug entry). > > I updated the issue and made your packages into a slice: > https://pharo.fogbugz.com/default.asp?7542 > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 3, 2013

Re: [Pharo-dev] transcript is plain bad

by StÃ©phane Ducasse

On Dec 3, 2013, at 2:59 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/12/2 Sean P. DeNigris <sean(a)clipperadams.com>: >> EstebanLM wrote >>> yes, the transcript is ThreadSafeTranscript >> >> Does "ThreadSafe" mean I don't have to wrap all my debug logging in >> "WorldState addDeferredUIMessage: [ Transcript... ]? That would save a lot >> of time :) > > According to the implementation it means there is a Mutex stopping > multiple processes from doing operations (#nextPut:, #nextPutAll:) at > the same time. It is... who sends the message first will be received > happily, whoever is second will have to wait in a semaphore :D I did that because I was trying to write a chapter on concurrent programming and since the output could be in any order it was difficult to show anything reliably. Now the implementation can be bad and anybody willing to imporve it is more than welcome. > Funny outputs might happen if two different senders use #nextPut: intertwined. > (other frameworks only left "complete line" outputs to loggers What is is? In the new logger I'm writing we have log ***OBJECTS*** and not dead strings. > , to > avoid this kind of scenarios). > > Regards! >

Dec. 3, 2013

Re: [Pharo-dev] transcript is plain bad

by StÃ©phane Ducasse

On Dec 2, 2013, at 8:46 PM, phil(a)highoctane.be wrote: > And missing a ton of methods. > > Teh StackInterpreterSimulator is agreeing with this statement. send us the ones that are missing. Please note that we should kill the transcript in the future because this is a ^%$&*((^%$* outdated way to manage feedback: plain string, close the window data is lost, limited in length, no filteringâ¦.. bad bad bad does not scale horrible and so frustrating. I will not send you the current transcript I have because I deal with private code but this does not work. Stef > > > > > > On Mon, Dec 2, 2013 at 8:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes, the transcript is ThreadSafeTranscript > > > On Mon, Dec 2, 2013 at 8:00 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Buy the way, is absence of Transcript class - ok? > > I know how it all works now, but is it ok? :) > > uko > > > On 02 Dec 2013, at 19:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> yes, please :) >> >> >> On Mon, Dec 2, 2013 at 7:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> > The return of the toothpick is near. o/ >> >> No I will finish my logger :) >> >> Stef >> >> > > >

Dec. 3, 2013

Re: [Pharo-dev] Roassal Bug related to Athens?

by StÃ©phane Ducasse

Igor I see that you are learning the pattern: Write a simple doc [point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it point people to it ] until: [They got it] It is a massive amount of energy saving :) Stef On Dec 2, 2013, at 10:12 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > http://code.google.com/p/nativeboost/wiki/SessionManagement > > > On 2 December 2013 22:02, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 2 December 2013 17:14, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > Hello Igor, > > Moose 5.0 is using Athens as default canvas for Roassal and we have bug with Roassal that seems to be related to Athens. > http://code.google.com/p/moose-technology/issues/detail?id=1019 > > I think it is related to the fact that we create a surface in the OS with Athens and once we quit the image, the surface is destroyed as well. So, when image is restarted with the visualization trying to use the surface, we get the error. > > right. > > Could you point to what possibly can be done to avoid this error? Merely checking the existence of an appropriate drawing surface in Athens every time visualization is drawn, would it suffice? > > yes.. i explained and given examples multiple times both for NB and Athens (and last time it was like couple weeks ago). > > http://lmgtfy.com/?q=nativeboost+session+aware&l=1 > > regards, > > Usman > > > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] Unifying Testing Ideas

by Attila Magyar

Sean P. DeNigris wrote > I understand the motivation. My question is how do we create appropriate > hooks so that we don't get into these conflicts? I don't know yet, I'm open for discussion. Sean P. DeNigris wrote > - anyArgument now inst var of BabyMockTestCase, similar to BmAnyMessage How do you use the anyArgument? The /with:/ is optional, so mock should receive: #a:b:c: accepts a:b:c: with any arguments by default, unless you restrict it with /with:and:and:/. Or did you want something like this? mock a: anyArgument b: exactArgument1 c: exactArgument2 This seems to be a valid need. Sean P. DeNigris wrote > - #does: now optionally takes arguments I rarely use /does/, as far as I remember it is not even documented. I don't know the code behind the test but based on the names it looks like an adapter like thing. (e.g. a thin wrapper above a 3rd party api with not too much logic inside). If this is the case, normally I would test it with integration tests, instead of mocks. -- View this message in context: http://forum.world.st/Unifying-Testing-Ideas-tp4726787p4726915.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 3, 2013

Re: [Pharo-dev] Responsible development

by StÃ©phane Ducasse

On Dec 2, 2013, at 8:37 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > On 02 Dec 2013, at 20:27, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >>>>> We try now to have responsive UIs in the sense the tools like Nautilus try to >>>>> run things in a separate thread. >>>>> >>>>> I will do an experiment and fork each Nautilus opening to see if it can save my ass :P >>>> :) >>>> >>>> personnally I would be really against because just forking is just a way to have a lot more mess in the future. >>> >>> Why ? >> >> Because you do not know when you invariants should hold. Normally you expect them to hold once the system is loaded. >> Because loading for example act as an atomic action when you modify the system. Now if your thread can see and modify >> different versions of the state be prepared to have really strange and difficult bugs to find. >> >> I prefer to have cache than to have forked processes around. > > Cache will not help you killing Nautilus when it freezes your image fork neither. > (why cache by the way ?) I thought the discussion was about speeding up nautilus when performing start up actions. > > Ben > >> >> Stef > >

Dec. 3, 2013

Re: [Pharo-dev] Opal hook?

by ClÃ©ment Bera

Well if the class does not exists it calls the method on UndefinedObject (UndeclaredBinding). And you have: UndefinedObject>>subclass: nameOfClass instanceVariableNames: instVarNames classVariableNames: classVarNames poolDictionaries: poolDictnames category: category "Calling this method is now considered an accident. If you really want to create a class with a nil superclass, then create the class and then set the superclass using #superclass:" self traceCr: ('Attempt to create ', nameOfClass, ' as a subclass of nil. Possibly a class is being loaded before its superclass.'). ^ProtoObject subclass: nameOfClass instanceVariableNames: instVarNames classVariableNames: classVarNames poolDictionaries: poolDictnames category: category The best is to set manually the superclass after with #superclass: 2013/12/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi > > when I load a class whose superclass is not in the image I have the > impression that the system create a subclass from ProtoObject > and I would like to be able to control the superclass. > > ProtoObject subclass: #Adaptor1Example > instanceVariableNames: 'customers accountID address name > phoneNumber' > classVariableNames: '' > poolDictionaries: '' > category: 'Examples-Cookbook' > > Any idea where to look? > > Stef >

Dec. 3, 2013