Re: [Pharo-dev] [Moose-dev] [ann] moose 4.8
On Fri, Sep 13, 2013 at 8:11 AM, Ben Coman b...@openinworld.com wrote: ** Great news. Well done all the Moose Team. I've been on a bit of a hiatus until recently and can't wait to get more stuck into Roassal on Athens. Are there any videos on the different GTdebugger workflows? Right now there is just one video with a short introduction: http://scg.unibe.ch/research/moldabledebugger More will come :)
[Pharo-dev] The Moldable Debugger Framework
Hi, I'd like to announce the first version of the Moldable Debugger. It is a framework for creating and working with domain specific debuggers. It's integrated into Moose and it currently comes with three debuggers: one for announcements, one for PetitParser and one for Glamour. More information can be found here: * http://scg.unibe.ch/research/moldabledebugger* A video introducing the framework is here: *https://vimeo.com/73980431* (more are on the way) Cheers, Andrei
[Pharo-dev] The future of SqueakSource
Hi all, We will shut down the SqueakSource image at the end of next week (30 August 2013). The current system will be replaced by a simple view of the file system containing just the publicly visible projects. As meta-data, each project will have it's overview page attached (showing the licence and its author). Please forward this email to other mailing lists. Cheers, The SCG Team
Re: [Pharo-dev] opal bug with the old debugger
Done. https://pharo.fogbugz.com/default.asp?11210 On Sat, Jul 20, 2013 at 11:09 AM, Marcus Denker marcus.den...@inria.frwrote: On Jul 19, 2013, at 5:10 PM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Just noticed that the second bug also appears in the new debugger. To reproduce execute (with either debugger) while debugging add a message send to a method that does not exist, step into that message send and then choose to create the method. After you created you'll get: UndefinedObject(Object) doesNotUnderstand: #debugHighlightRange Can you add a bug tracker entry? Marcus
Re: [Pharo-dev] opal bug with the old debugger
Just noticed that the second bug also appears in the new debugger. To reproduce execute (with either debugger) while debugging add a message send to a method that does not exist, step into that message send and then choose to create the method. After you created you'll get: UndefinedObject(Object) doesNotUnderstand: #debugHighlightRange Andrei On Mon, Jul 15, 2013 at 9:37 AM, Clément Bera bera.clem...@gmail.comwrote: Hi, Actually I saw the bug, tried in the new debugger, it worked. So I didn't fix it because the new debugger will be integrated before the release. 2013/7/14 Andrei Vasile Chis chisvasileand...@gmail.com Hi, Executing '1 haba' in a workspace and then choosing create method from the pre debug window leads to this exception: UndefinedObject(Object)doesNotUnderstand: #methodOrBlockNode If instead I choose to debug, select the top context of the stack and the press the 'Creare method' button a different exception is thrown: UndefinedObject(Object)doesNotUnderstand: #debugHighlightRange In both cases the method is created. So known or unknown issue? Also it doesn't seem to happen with the new debugger. Not sure why :) Andrei
Re: [Pharo-dev] Spec delete method
You can add this to the initialize method of your widget, and in the close method unregister all announcers self whenWindowChanged: [:w | w whenClosedDo: [ self close ] ]. Andrei On Wed, Jul 17, 2013 at 3:42 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: Ok :) Then there is a hook in Morph for that I think :) (and an announcement in Spec when a widget is built) Ben On Jul 17, 2013, at 3:37 PM, Tudor Girba tu...@tudorgirba.com wrote: I guess what Stef means is that he would like to know if there is a way specify custom behavior when a window closes, and then use this for his purpose of unregistering from some announcer. Cheers, Doru On Wed, Jul 17, 2013 at 2:36 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: I do not think it's a UI framework concern to handle model behaviour (like registration to announcement) Ben On Jul 17, 2013, at 9:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi ben I would like to unsubscribe announcement when the window is closed. Is there a hook for that in Spec? Stef -- www.tudorgirba.com Every thing has its own flow
[Pharo-dev] buttons for browsing in the debugger
Hi, If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons. Do you use this feature? Do we want it in the new debugger? Andrei
Re: [Pharo-dev] buttons for browsing in the debugger
-1 but i don't like it in form of extra buttons row, which makes debugger UI too bloated. They will be accessible from the context menu of the stack. Andrei -- Best regards, Igor Stasenko.
Re: [Pharo-dev] buttons for browsing in the debugger
In general what I learned: You find an obscure, not useful, not used feature in the code base that complexities everything. option 1) Ask the list. Result: 5 people will suddenly realize that they can not live without that strange feature they never heard about before. option 2) Just kill it. Result: the World is a happier place. ;-) But seriously I used that Strategy 2) a lot in the past :-) Sounds like a good plan :)
[Pharo-dev] opal bug with the old debugger
Hi, Executing '1 haba' in a workspace and then choosing create method from the pre debug window leads to this exception: UndefinedObject(Object)doesNotUnderstand: #methodOrBlockNode If instead I choose to debug, select the top context of the stack and the press the 'Creare method' button a different exception is thrown: UndefinedObject(Object)doesNotUnderstand: #debugHighlightRange In both cases the method is created. So known or unknown issue? Also it doesn't seem to happen with the new debugger. Not sure why :) Andrei
Re: [Pharo-dev] about WidgetAbstractWrapper
I start to create it, what would you like to get in ? for the moment there is nothing because i focused on something different No problem. I just wanted to know if there is already something more concrete.
[Pharo-dev] about WidgetAbstractWrapper
Hi Erwan, I've heard you are working on a WidgetAbstractWrapper for dealing with dynamic widgets :) Is it still a work in progress or there's already something concrete? Cheers, Andrei
Re: [Pharo-dev] Some Spec questions
Actually Erwan Douaille is doing WidgetAbstractWrapper to solve this problem (I've just learnt that a few minutes ago). You may discuss with him about that. Super. Thanks for all the help and the info Andrei
Re: [Pharo-dev] Some Spec questions
Hi folks, while working on the new debugger, I've come up with some questions... *is there any other implementation for dynamic widgets other that the current one? I do not get your question ... This is related to my previous question about dynamic spec, if it's possible to define the layout of a widget on the object side. *right now the toolbar is a static widget, and I would like to have a dynamic one to filter out the actions that should not be available (which are a subset of the default ones). Would it make sense to regenerate the toolbar everytime the selection changes? Is there any other approach I should consider? It may make sense to dynamically regenerate the toolbar (or at least remove only what needs to be removed, add only what needs to be added). Then you should also think in term of user experience. Having things changing may be disturbing and counter productive :) Right now our use case are post mortem contexts (that do not have a process attached). In there case only few actions make sense. The current debugger sets the toolbar at the creation of the debugger. If the context turns post mortem during debugging the actions should also change. Now the question would be if this is actually possible?
[Pharo-dev] MessageNotUnderstood: ZdcSocketStreamposition
Hi, I get this error with Zinc only when I'm behind a proxy, if from the Monticello Browser I try to see the changes of a certain package: 'Could not load FileSystem-Core-MarcusDenker.99.mcz: MessageNotUnderstood: ZdcSocketStreamposition' Is this a knows issues? If not I can provide more details. I noticed this on the latest Pharo 3 image. Cheers, Andrei
Re: [Pharo-dev] MessageNotUnderstood: ZdcSocketStreamposition
Is this a knows issues? Yes, and it is already fixed: === Name: Zinc-HTTP-SvenVanCaekenberghe.372 Author: SvenVanCaekenberghe Time: 30 June 2013, 9:06:10.101049 pm UUID: 98ea090f-27d4-498e-8111-95e954d010a9 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.371 Fixed a typo in ZnStringEntity#readFrom: (thanks Paul DeBruicker for reporting the issue) === Basically, #position was sent to the socket stream while it should have been sent to a string stream which is properly positionable. The #position / #position: interface makes little to no sense for streams that do not have their whole content in memory. Then again, certain parser seem to need it. Super. Thanks for the info. Cheers, Andrei
[Pharo-dev] FileReference(Object)doesNotUnderstand: #other
Hi, This code fails in both Pharo 2 and Pharo 3: 'FileSystem disk root children sorted' It throws this exception: FileReference(Object)doesNotUnderstand: #other Andrei
Re: [Pharo-dev] FileReference(Object)doesNotUnderstand: #other
Done: https://pharo.fogbugz.com/default.asp?11147 On Sat, Jul 6, 2013 at 7:39 PM, Stéphane Ducasse stephane.duca...@inria.frwrote: thanks for the report! Can you open a bug entry and a test (it would be lovely). BTW andrei I think that we forgot to book an hotel for your visit :) Can you tell me again when you are coming that we try to fix this little point :) Hi, This code fails in both Pharo 2 and Pharo 3: 'FileSystem disk root children sorted' It throws this exception: FileReference(Object)doesNotUnderstand: #other Andrei
Re: [Pharo-dev] [update 3.0] #30221
Also it would be good to sync with the content from the Debugger repository as it contains some bug fixes. What can I do to make this easy or you? (I can merge the version from pharo with the one from the Debugger repository; should I also create a slice?) Yeah please merge it and make a slice and a bug report in fogbugz. It will be integrated the day after you create the slice and put the bug in bugtracker to status 'fix review needed'. Will do it by tomorrow. Andrei I have a question. On the old debugger when I right click on the stack I have a lot of features (as return value, browse class, ..). On the new debugger with Spec UI and your model I don't have all these features. Are they implemented in the model and not in the spec UI ? Are they not implemented because no one requested :) ?Could you add them ? They are not implemented because at beginning I didn't needed them :). They will be added soon (https://pharo.fogbugz.com/default.asp?10952) Also I've created some more issues with the things that should be done in order for the new debugger to be ready for integration. I'd be online Friday afternoon during the sprint working on those issues. Andrei
Re: [Pharo-dev] zeroconf --headless/-headless
On Sat, Jun 1, 2013 at 12:51 AM, Camillo Bruni camillobr...@gmail.comwrote: fixed it: http://get.pharo.org/vmLatest works now under linux additionally I added a small CLI introduction to http://get.pharo.org ;) Thanks. I just committed another small change. Andrei
[Pharo-dev] zeroconf --headless/-headless
Hi, If I try to execute './pharo Pharo.image' after downloading the latest Pharo Vm with the zero conf script it fails with the error: unknown option: -headless. If I download the stable one it works. Cheers, Andrei
Re: [Pharo-dev] zeroconf --headless/-headless
Hi, Yes now the arguments are with --. Just that the zero conf scripts still use -. It can be easily fix, but then the stable vm will not work any more as it needs -. So the zero conf should use - for the stable vm and -- for the latest vm. On Fri, May 31, 2013 at 5:48 PM, Clément Bera bera.clem...@gmail.comwrote: Hey, Now the argument are with: - - no ? It should be --headless ? I'm not sure. Camillo has probably already fixed it reading your mail anyway 2013/5/31 Andrei Vasile Chis chisvasileand...@gmail.com Hi, If I try to execute './pharo Pharo.image' after downloading the latest Pharo Vm with the zero conf script it fails with the error: unknown option: -headless. If I download the stable one it works. Cheers, Andrei -- Clément Béra Mate Virtual Machine Engineer Bâtiment B 40, avenue Halley 59650 *Villeneuve d'Ascq*
