Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Zooming in and out in a Moose panel
by Alexandre Bergel 04 Dec '15

04 Dec '15

Hi! Zoom - in and out does not work anymore in the moose panel. Anyone has a way to fix this? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 8

Finding in a roassal view
by Alexandre Bergel 04 Dec '15

04 Dec '15

Hi! I have worked on the actions available in Glamour during the last few days. I have just added a find icon (glasses icon): Clicking on it open a spotter to look for element in the view. Selecting it move the camera to focus on it. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 7

Improvement of Layout Builder
by Alexandre Bergel 04 Dec '15

04 Dec '15

Hi! I did some small improvement of the layout builder. For example: -=-=-=-=-=-=-=-= b := RTMondrian new. b nodes: (1 to: 100). b layout force; ifNotConnectedThen: RTGridLayout new. b edges connectTo: [ :v | v \\ 4 ]. b -=-=-=-=-=-=-=-= I have also introduced a null layout to move all elements at the same position. This is a simple way to discard elements. -=-=-=-=-=-=-=-= b := RTMondrian new. b nodes: (1 to: 100). b layout force; ifNotConnectedThen: RTNullLayout new. b edges connectTo: [ :v | v \\ 4 ]. b -=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

GTDebugger not draggable with latest VM
by Blondeau Vincent 04 Dec '15

04 Dec '15

Hi, I have a problem on the latest Moose6.0 image. I was not able to open a Roassal view, I had a NativeBoost Generic failure... So I updated the VM to last stable, and, now, the GTdebugger and the Moose panel are not draggable anymore... Can somebody is able to reproduce the problem? Thanks Cheers, Vincent ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

2 2

showing a diff on #assert:equals:
by Andrei Chis 04 Dec '15

04 Dec '15

Hi, I updated GTDebugger to automatically show a diff in the debugger when an #assert:equals: fails. For example if you execute '(GTSUnitExampleFailingTest selector: #testMultiValuedStreaming) debug.' you get the debugger below. Also works when running tests from Nautilus/TestRunner. The context from where #assert:equals: was called is also automatically selected. [image: Inline image 1] Let me know if you run into any issues. Cheers, Andrei

7 21

MacroRecorder available in Pharo
by Gustavo Santos 04 Dec '15

04 Dec '15

Hello guys, I would like to present you MacroRecorder, a tool to build custom source code transformations in Pharo. The tool is available in the Catalog for some weeks now. The current version runs in Pharo 5 and there is an old version running in Pharo 4. To show how this tool works, I prepared a quick demo video. Take a look: https://youtu.be/gW3l4O-WEGs Right now, I'm interested in usage data. That means, if you face a case of repetitive code transformation in practice, and I believe this happened to most of you, please: (i) show me the transformations you did, in case they already happened in the past, or (ii) consider using the tool to apply them automatically And, of course, feel free to ask questions, provide feedback, etc. Kind regards, -- Gustavo Santos http://gustavojss.github.io/

4 3

broken archives
by Peter Uhnak 04 Dec '15

04 Dec '15

Did the archive broke after the mailing list changed (sub)domain? It goes only up to mid October: https://www.list.inf.unibe.ch/pipermail/moose-dev/ -- Peter

1 0

Explanation how to use GT Debugger and GT SUnit Debugger with DarkThem in Pharo 4.0 [was] Using Re: Re: showing a diff on #assert:equals:
by Mariano Martinez Peck 04 Dec '15

04 Dec '15

Andrei... you rock!!! It works. I copy paste it here so that others can take advantage too. Look also the attached screenshot :) Doru...you were right..you THINK you don't need a any other tool, until someone comes with a little example as a debugger for test cases...wow... those are moldable tools!!!! The code I used (with the hack of the override) is this: http://ws.stfx.eu/ME85BCYIPSU8 (of course, I published the code via the playground hahahha) Thank you! On Thu, Dec 3, 2015 at 3:53 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Ahh. Wrong order for loading packages in my previous instructions. > You should load first DebuggerExtensions and then the debuggers. > > Cheers, > Andrei > > On Thu, Dec 3, 2015 at 7:39 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Thu, Dec 3, 2015 at 1:15 PM, Andrei Chis <chisvasileandrei(a)gmail.com> >> wrote: >> >>> Hi Mariano, >>> >>> To get it working in Pharo 4 you should: >>> >>> - load GT-Debugger-AndreiChis.249 from AndreiChis/GTDebuggerPharo4 >>> - load GT-SUnitDebugger-AndreiChis.18 from AndreiChis/GTDebuggerPharo4 >>> - load DebuggerExtensions-AndreiChis.9 from Pharo/Debugger >>> - register the debuggers: >>> - GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools. >>> - GTSUnitDebugger registerExtraToolsOn: Smalltalk tools >>> >>> Like this the spec debugger is still the default one and you still have >>> to start GTDebugger from the pre debug window. >>> You can register GTDebugger as the default one (GTGenericStackDebugger >>> registerToolsOn: Smalltalk tools) but it will not switch to the SUnit >>> extension automatically (that only works in Pharo 5). You'll need to switch >>> to it from the context menu of the stack. >>> >>> Let me know how it goes. >>> >>> >> Hi Andrei, >> >> I tried what you said with the following script in a virgin 4.0: >> >> Gofer it >> smalltalkhubUser: 'AndreiChis' project: 'GTDebuggerPharo4'; >> version: 'GT-Debugger-AndreiChis.250'; >> version: 'GT-SUnitDebugger-AndreiChis.19'; >> load. >> Gofer it >> smalltalkhubUser: 'Pharo' project: 'Debugger'; >> version: 'DebuggerExtensions-AndreiChis.9'; >> load. >> (Smalltalk at: #GTGenericStackDebugger) registerExtraToolsOn: Smalltalk >> tools. >> (Smalltalk at: #GTSUnitDebugger) registerExtraToolsOn: Smalltalk tools. >> >> >> However, as soon as I try to debug something I get the following error. >> It seems I am missing the class GTSUnitActivationPredicate. >> >> >> UndefinedObject(Object)>>doesNotUnderstand: #new >> GTSUnitDebugSession class>>activationPredicate >> GTSUnitDebugger class>>handlesContext: >> [ :aPair | aPair key handlesContext: aContext ] in >> PharoCommonTools(ToolRegistry)>>debuggersWithRanksForContext: in Block: [ >> :aPair | aPair key handlesContext: aContext ] >> OrderedCollection>>select: >> PharoCommonTools(ToolRegistry)>>debuggersWithRanksForContext: >> PharoCommonTools(ToolRegistry)>>debuggerDispatcherFor: >> GTTemporaryPreDebugChangeDebuggerAction>>executeAction >> GTTemporaryPreDebugChangeDebuggerAction(DebugAction)>>execute >> .... >> >> Any idea? >> >> Weird thing is that I am NOT opening a debugger of a SUnit.. but a >> regular debugger. >> Maybe the registration part of your script is wrong? >> >> Thanks in advance, >> >> >>> Cheers, >>> Andrei >>> >>> On Wed, Dec 2, 2015 at 5:37 PM, Mariano Martinez Peck < >>> marianopeck(a)gmail.com> wrote: >>> >>>> >>>> >>>> On Wed, Dec 2, 2015 at 1:31 PM, Andrei Chis <chisvasileandrei(a)gmail.com >>>> > wrote: >>>> >>>>> >>>>> >>>>> On Wed, Dec 2, 2015 at 5:24 PM, Mariano Martinez Peck < >>>>> marianopeck(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Dec 2, 2015 at 1:02 PM, Andrei Chis < >>>>>> chisvasileandrei(a)gmail.com> wrote: >>>>>> >>>>>>> I think it's not straightforward to get it to work in Pharo 4. >>>>>>> I'm not sure you can load the latest version of GTools into Pharo 4. >>>>>>> >>>>>>> >>>>>> That's what I was thinking :( >>>>>> >>>>>> >>>>>>> You can load just the packages for GT-Debugger, GT-SUnitDebugger and >>>>>>> DebuggerExtensions, however, it would not work by default as there were >>>>>>> some changes to the API of the debugger. You'll also need to backport >>>>>>> those changes, but that might be more work. >>>>>>> If you really want to use it I could make a version that uses the >>>>>>> old API. >>>>>>> >>>>>>> >>>>>> I don't want you loose much time if I am the only one wanting this. >>>>>> Personally, for my real client-paying job I won't be able to move to 5.0 >>>>>> until it's released. But then I can wait. >>>>>> >>>>> >>>>>> However, I would like to at least give it a quick try to the dirty >>>>>> solution. As you said, maybe loading those 3 packages and bringing some >>>>>> slices (the ones of the debugger api might work). mmmmm but I guess this >>>>>> will break the Spec Debugger right? Unless the slides also updates that.. >>>>>> Do you remember which were the debugger changes? >>>>>> >>>>> >>>>> There are 4 slices that you need to load >>>>> I tried loading the first one (https://pharo.fogbugz.com/f/cases/17069) >>>>> and my image hangs... >>>>> >>>>> I'll see tomorrow if I can make a quick and dirty refactoring to get >>>>> it to work just for Pharo 4. >>>>> >>>>> >>>> Super !!! Let us know! >>>> >>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> On Wed, Dec 2, 2015 at 4:07 PM, Mariano Martinez Peck < >>>>>>> marianopeck(a)gmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Dec 2, 2015 at 11:53 AM, Andrei Chis < >>>>>>>> chisvasileandrei(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> I splitted the code pane into two to also show the setUp/tearDown >>>>>>>>> code. >>>>>>>>> A button/checkbox to hide/show this pane could be next. >>>>>>>>> >>>>>>>>> >>>>>>>> Coool!!! >>>>>>>> Andrei, let me ask, would this work in Pharo 4.0? If true, then I >>>>>>>> should only load gt debugger or a new version of the whole GT suite ? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Andrei >>>>>>>>> >>>>>>>>> On Wed, Dec 2, 2015 at 1:09 PM, Mariano Martinez Peck < >>>>>>>>> marianopeck(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Dec 2, 2015 at 9:02 AM, Juraj Kubelka < >>>>>>>>>> juraj.kubelka(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> On Dec 1, 2015, at 17:47, Andrei Chis < >>>>>>>>>>> chisvasileandrei(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>> Hi Mariano >>>>>>>>>>> >>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 PM, Mariano Martinez Peck < >>>>>>>>>>> marianopeck(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Dec 1, 2015 at 7:31 AM, Andrei Chis < >>>>>>>>>>>> chisvasileandrei(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Dec 1, 2015 at 1:05 AM, Mariano Martinez Peck < >>>>>>>>>>>>> marianopeck(a)gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Uhhh that's very cool. Quick question, what happens if the >>>>>>>>>>>>>> textual representation of the actual vs expected is the same yet the >>>>>>>>>>>>>> objects are not #= ? >>>>>>>>>>>>>> It shows no diff and then I must go to see the inspector? >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> These textual representations can be customized per each >>>>>>>>>>>>> object type, however if they are the same now it just shows the diff pane >>>>>>>>>>>>> with no differences. >>>>>>>>>>>>> Another idea would be to also show two inspectors side-by-side >>>>>>>>>>>>> apart from the diff. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> A side-by-side inspector would be another really cool addition >>>>>>>>>>>> for when the string comparison won't work. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Then even if you see or not a difference in the textual diff, >>>>>>>>>>>>> you could use the inspector to look at differences between the state. >>>>>>>>>>>>> Also right now the diff is textual. Adding better diff widgets >>>>>>>>>>>>> for specific data types would help. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> Oh yes. But I think that adding a side-by-side inspector would >>>>>>>>>>>> be a great second step in which you know you can always fall back no matter >>>>>>>>>>>> which kind of object. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I added two side by side inspectors. I still need to >>>>>>>>>>> improve/disable navigation in these embedded inspectors >>>>>>>>>>> >>>>>>>>>>> <debugger.png> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> BTW...since we are near Christmas... it would be terrific to >>>>>>>>>>>> have a button somewhere to show/hide the #setUp method besides the code >>>>>>>>>>>> representing the piece of stack you clicked. Sometimes when I am debugging >>>>>>>>>>>> test failures that had a setup I always have to open another window with >>>>>>>>>>>> the setup because I don't remember everything I did there and that's useful >>>>>>>>>>>> information to understand what a test could have failed. There was a >>>>>>>>>>>> Nautilus plugin for that some time ago. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Sounds like an useful feature. I'll give a try implementing it. >>>>>>>>>>> Or if you are faster you can give it a try :) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I like the idea. Maybe having a ‘setUp tab; next to ‘Source’ tab >>>>>>>>>>> whenever we browse a test case object in debugger? Or it could be part of >>>>>>>>>>> the inspector the same way you did ‘Diff’ tab. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I think the MAIN point for me is to be able to see the setUp AT >>>>>>>>>> THE SAME time with the code of the failing error. If I have to click >>>>>>>>>> another tab to see the setup and then another click to go back to see my >>>>>>>>>> test, then I gain nothing. Maybe splitting (either vertically or >>>>>>>>>> horizontally) the area where now you see the method source (of the selected >>>>>>>>>> stack) in order to also see (fixed) the setUp ? Or .. maybe a new tab in >>>>>>>>>> the below (expected vs current, etc) called "setUp". That way, at least I >>>>>>>>>> can see the method and the setUp all together (Ok, I cannot see the >>>>>>>>>> expected vs current, but ok) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Juraj >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Andrei >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Moose-dev mailing list >>>>>>>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>>>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Moose-dev mailing list >>>>>>>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>>>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Mariano >>>>>>>>>> http://marianopeck.wordpress.com >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Moose-dev mailing list >>>>>>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Moose-dev mailing list >>>>>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Mariano >>>>>>>> http://marianopeck.wordpress.com >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Moose-dev mailing list >>>>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Moose-dev mailing list >>>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Mariano >>>>>> http://marianopeck.wordpress.com >>>>>> >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> Moose-dev(a)list.inf.unibe.ch >>>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)list.inf.unibe.ch >>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>> >>>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- Mariano http://marianopeck.wordpress.com

2 4

PhD in Chile
by Alexandre Bergel 03 Dec '15

03 Dec '15

Hi! We have national grant to do a PhD in Chile. Here are some information: http://www.conicyt.cl/becas-conicyt/2015/10/becas-doctorado-nacional-2016/ Deadline is approaching very soon. Let me know (privately) if you are interested. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

broken Roassal2Spec Adapter
by Peter Uhnák 03 Dec '15

03 Dec '15

Hi, apparently we broke MorphicRoassalAdapter when cleaning Spec, I attached a fix. However my question is - does anybody (except us) actually use the Roassal2Spec package? Because otherwise we could clean it a bit. For example I'm not sure of the use case of script:/lastEvent:. Peter

5 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev