January 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Spec: Populating a playground with a particular content (was Re: Spec: Binding widgets how to)

by Johan Fabry

Hola, it looks like what you want here is covered by dynamic spec. Have a look at the dynamic spec section in the Spec booklet (work in progress) https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… I think that it will answer your question. > On Jan 7, 2016, at 22:36, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > > How can I initializeWidgets with some kind of conditions depending on the kind of selection I have done on the tree? ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Jan. 8, 2016

gtdebugger in pharo 5.0

by Tudor Girba

Hi, We are about to integrate in Pharo a new member of the Glamorous Toolkit: the GTDebugger. As this is a significant change that might affect your workflow, here is some background information to help you deal with the change. First, you should know that the change is not irreversible and it is easily possible to disabled the new debugger through a setting. However, please do take the time to provide us feedback if something does not work out for you. We want to know what can be improved and we try to react as fast as we can. A practical change comes from the fact that the variables are manipulated through a GTInspector, which makes it cheaper to maintain in the longer run. While the first thing that will capture the attention is the default generic interface, the real power comes from the moldable nature of the debugger. Like all other GT tools, GTDebugger is also moldable by design. This means that we can construct custom debuggers for specific libraries at small costs (often measured in a couple of hundred lines of code). For example, the core configuration includes also the SUnit and the bytecode debugger. These are around 150 lines of code. Here is how the bytecode debugger looks like: You can find more information in an introductory overview blog post that also includes some links for further reading: http://www.humane-assessment.com/blog/gtdebugger-in-pharo/ Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

Jan. 8, 2016

[ann] gtdebugger in pharo 5.0

by Tudor Girba

Hi, We are about to integrate in Pharo a new member of the Glamorous Toolkit: the GTDebugger. As this is a significant change that might affect your workflow, here is some background information to help you deal with the change. First, you should know that the change is not irreversible and it is easily possible to disabled the new debugger through a setting. However, please do take the time to provide us feedback if something does not work out for you. We want to know what can be improved and we try to react as fast as we can. A practical change comes from the fact that the variables are manipulated through a GTInspector, which makes it cheaper to maintain in the longer run. While the first thing that will capture the attention is the default generic interface, the real power comes from the moldable nature of the debugger. Like all other GT tools, GTDebugger is also moldable by design. This means that we can construct custom debuggers for specific libraries at small costs (often measured in a couple of hundred lines of code). Here is an introductory overview blog post that also includes some links for further reading: http://www.humane-assessment.com/blog/gtdebugger-in-pharo/ <http://www.humane-assessment.com/blog/gtdebugger-in-pharo/> Please let us know what you think. Cheers, Doru -- www.tudorgirba.com <http://www.tudorgirba.com/> www.feenk.com "Beauty is where we see it."

Jan. 8, 2016

Re: [Pharo-users] Pine64

by Ben Coman

I signed up for the PINE A64+ w/ 2GB SDRAM (March 2016). I'm interested in checking out the virtualization capabilities of the A53. cheers -ben On Fri, Jan 8, 2016 at 2:31 PM, John Pfersich <jpfersich(a)gmail.com> wrote: > I've pre-ordered a Pine64 SBC. The write up says it's got a "1.2 Ghz > Quad-Core ARM Cortex A53 64-Bit Processor. It has 64 and 32 Bit execution > states for scalable high performance power â including a NEON Multimedia > processing engine." > > Does anybody have an idea whether the vm for the raspberry pi will work with > this new computer? > > This is what the ARM site says about the A53 processor: > > As well as running 64-bit applications, the Cortex-A53 seamlessly and > efficiently runs legacy ARM 32-bit applications. It is highly scalable, from > a single multi-core CPU cluster, to a dual-cluster big.LITTLE CPU subsystem > in combination with the Cortex-A72or Cortex-A57 processor, to a > multi-cluster enterprise system connected through AMBAÂ® 5 CHI Coherent > Interconnecttechnology. Full ARMv8-A support in a small and highly > configurable package means that the Cortex-A53 is highly suited to a broad > range of mobile, consumer, general purpose, and enterprise applications. > > Sent from my iPad > > > Sent from my iPad

Jan. 8, 2016

Pine64

by John Pfersich

I've pre-ordered a Pine64 SBC. The write up says it's got a "1.2 Ghz Quad-Core ARM Cortex A53 64-Bit Processor. It has 64 and 32 Bit execution states for scalable high performance power â including a NEON Multimedia processing engine." Does anybody have an idea whether the vm for the raspberry pi will work with this new computer? This is what the ARM site says about the A53 processor: As well as running 64-bit applications, the Cortex-A53 seamlessly and efficiently runs legacy ARM 32-bit applications. It is highly scalable, from a single multi-core CPU cluster, to a dual-cluster big.LITTLE CPU subsystem in combination with the Cortex-A72or Cortex-A57 processor, to a multi-cluster enterprise system connected through AMBAÂ® 5 CHI Coherent Interconnecttechnology. Full ARMv8-A support in a small and highly configurable package means that the Cortex-A53 is highly suited to a broad range of mobile, consumer, general purpose, and enterprise applications. Sent from my iPad Sent from my iPad

Jan. 8, 2016

Spec: Populating a playground with a particular content (was Re: Spec: Binding widgets how to)

by Offray Vladimir Luna CÃ¡rdenas

Hi, Thanks to NIcolai's help with his minimalist example I'm on track now and finally I have started to understand better the events in Spec. My problem was in the incorrect use of whenHighlightedItemChanged. Now the code its working fine and I can browse the tree and see the related contents on the respective UI panels (see attached screenshot and code at [*] at the end to see how was solved). Now I'm facing another issue: As you can see in the attached screenshot the UI has four parts: A tool bar above all, a tree with the node title (called node header) at left and a bigger panel at right with node contents (called node body). I would like to make the node body behave in a similar way as in my previous non-Spec interface, so it can react differently according to the node tags. If the node is tagged as code, it will become a playground with node contents inside such playground. If node is not tagged it will be a text like now (this is already working). So my questions are: 1) How can I populate a Spec-Glamour playground with a particular text code? 2) How can I initializeWidgets with some kind of conditions depending on the kind of selection I have done on the tree? At this moment my initializeWidgets look like this: ==[2a]=========== GrafoscopioGUI>>initializeWidgets "Buils graphical interface elements" windowMainMenu := self windowMainMenu. tree := self tree. nodeHeader := self newTextInput. nodeBody := tree selectedItem notNil ifTrue: [ self updateBody ] ifFalse: [nodeBody := self newText]. windowMainMenu applyTo: self. self focusOrder add: windowMainMenu; add: tree; add: nodeHeader; add: nodeBody. ================ and my updataBody (where I think that this conditional behavior could be looks like this: ==[2b]=========== GrafoscopioGUI>>updateBody "update the displayed content associated to the body of a node" (tree selectedItem content tags = 'cÃ³digo') ifTrue: [ ^ nodeBody text: 'I should be playground because I am tagged as ', tree selectedItem content tags ] ifFalse: [ ^ nodeBody text: tree selectedItem content body ] ================ So, more precisely, what I need to put in the ifTrue part of [2b] to make the interface to return a playground with pre-populated code? (is it the proper place?) Finally, here is the code that made the tree update properly, just for the curious ones. ==[*]============ GrafoscopioGUI>>tree | notebook | notebook := GrafoscopioNode new becomeDefaultTestTree. tree := TreeModel new. tree roots: notebook children; childrenBlock: [:node | node children]; displayBlock: [:node | node title ]. tree whenHighlightedItemChanged: [tree selectedItem notNil ifTrue: [ self updateHeader. self updateBody. ] ]. ^ tree ================ Cheers, Offray On 03/01/16 18:33, Offray Vladimir Luna CÃ¡rdenas wrote: > Thanks again Nicolai! I will start from here :-). > > Offray > > On 03/01/16 18:20, Nicolai Hess wrote: >> >> >> 2016-01-03 23:52 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas >> <offray(a)riseup.net>: >> >> Hi, >> >> On 03/01/16 08:45, Nicolai Hess wrote: >>> >>> >>> There is any way to run a minimal GUI with a tree using your >>> example? I'm still missing a key concept on how to use spec >>> and binding between widgets. >>> >>> >>> what is missing ? this is a minimal gui with a tree component. >> >> Ohh, what is missing is not in the example, but in my >> understanding on how to use/start it. I would expect for >> something like "example openWithSpec" to start deconstructing it, >> but I'm still lost about it. I will be working on it today and >> tomorrow to see if I can come with better questions. >> >> >> Ok, for this example you can just start it with: >> >> TreeDemo new openWithSpec >> >> It opens a window with two panes, the upper pane shows a tree with >> some nodes (subclasses of class Morph) >> The lower pane shows the text(name) of the selected node. You can >> change and accept (cmd+s) the text in the >> lower pane, which will update the name of the tree node. >> >> >> Cheers, >> >> Offray >> >> >

Jan. 8, 2016

Re: [Pharo-users] Crash or locked VM

by Hilaire

What is really strange in the VM crash, is I can't even step in the recursive block. When stepping in the tree call (last line of the script bellow), the VM crash. | canvas tree angl angr fac| canvas := DrGeoCanvas new fullscreen. fac := (canvas freeValue: 2/3) hide. angl := (canvas freeValue: 2.8) hide. angr := (canvas freeValue: -2.8) hide. tree := [ ]. tree := [ :a :b :k | | ab m v bm lbc rbc lb rb mb | "construction of the tree" ab := canvas segment: a to: b. m := (canvas middleOf: ab) hide. v := (canvas vector: b to: m) hide. bm := (canvas scale: ab center: b factor: fac) hide. lbc := canvas rotate: bm center: b angle: angr. rbc := canvas rotate: bm center: b angle: angl. canvas translate: lbc vector: v. lb := (canvas rotate: m center: b angle: angr) . rb := (canvas rotate: m center: b angle: angl) . mb := (canvas translate: rb vector: v) . k > 0 ifTrue: [ tree value: m value: mb value: k - 1. tree value: b value: lb value: k - 1. tree value: b value: rb value: k - 1]]. tree value: 0@0 value: 0@6 value: 5 Crash dump: last object overwritten /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo pharo VM version: 3.9-7 #1 Sat Jun 14 17:26:13 CEST 2014 gcc 4.6.3 [Production ITHB VM] Built from: NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.20 uuid: cf2aeeee-897d-48fd-8251-6789dd21d958 Jun 14 2014 With: NBCogit NativeBoost-CogPlugin-EstebanLorenzano.20 uuid: cf2aeeee-897d-48fd-8251-6789dd21d958 Jun 14 2014 Revision: https://github.com/pharo-project/pharo-vm.git Commit: 0e8bbfbaeb03237fa6bb63ba834773fab18ca307 Date: 2014-06-14 12:20:21 -0300 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14833 Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux [default: /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/] C stack backtrace & registers: */home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo[0x809fc8c] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo(error+0x17)[0x809fe97] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo[0x8074a98] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo[0x8074bf0] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo(interpret+0x2de0)[0x8093640] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo(enterSmalltalkExecutiveImplementation+0x59)[0x8095d79] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo(interpret+0x1de)[0x8090a3e] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo(main+0x2b2)[0x805b842] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xf74dfa83] /home/hilaire/Travaux/Developpement/DrGeoII/trunk/build/tmp/DrGeo.appCrash/Contents/Linux/pharo[0x805bb61] [0x0] Smalltalk stack dump: 0xffcd7858 I EventManager class>actionMapFor: 0xb4cc1a40: a(n) EventManager class 0xffcd787c I DebugSession(Object)>actionMap 0xb65028a8: a(n) DebugSession 0xffcd78a0 I DebugSession(Object)>actionForEvent: 0xb65028a8: a(n) DebugSession 0xffcd78c4 I DebugSession(Object)>triggerEvent: 0xb65028a8: a(n) DebugSession 0xffcd78e8 I DebugSession>stepInto: 0xb65028a8: a(n) DebugSession 0xffcd7904 M StepIntoDebugAction>executeAction 0xb676297c: a(n) StepIntoDebugAction 0xffcd7924 I StepIntoDebugAction(DebugAction)>execute 0xb676297c: a(n) StepIntoDebugAction 0xffcd7940 M [] in SpecDebugActionButton>update 0xb6768a38: a(n) SpecDebugActionButton 0xffcd7960 I SpecDebugActionButton(ButtonModel)>performAction 0xb6768a38: a(n) SpecDebugActionButton 0xffcd797c M MorphicButtonAdapter>action 0xb677ed78: a(n) MorphicButtonAdapter 0xffcd799c I PluggableButtonMorph>performAction: 0xb677edac: a(n) PluggableButtonMorph 0xffcd6814 M [] in PluggableButtonMorph>mouseUp: 0xb677edac: a(n) PluggableButtonMorph 0xffcd6838 M Array(SequenceableCollection)>do: 0xb6834688: a(n) Array 0xffcd6858 M PluggableButtonMorph>mouseUp: 0xb677edac: a(n) PluggableButtonMorph 0xffcd6884 I PluggableButtonMorph(Morph)>handleMouseUp: 0xb677edac: a(n) PluggableButtonMorph 0xffcd68a0 M MouseButtonEvent>sentTo: 0xb6834660: a(n) MouseButtonEvent 0xffcd68bc M PluggableButtonMorph(Morph)>handleEvent: 0xb677edac: a(n) PluggableButtonMorph 0xffcd68d8 M PluggableButtonMorph(Morph)>handleFocusEvent: 0xb677edac: a(n) PluggableButtonMorph 0xffcd6900 M [] in HandMorph>sendFocusEvent:to:clear: 0xb4f45f38: a(n) HandMorph 0xffcd691c M BlockClosure>on:do: 0xb68345c8: a(n) BlockClosure 0xffcd6948 M WorldMorph(PasteUpMorph)>becomeActiveDuring: 0xb4f45e50: a(n) WorldMorph 0xffcd696c M HandMorph>sendFocusEvent:to:clear: 0xb4f45f38: a(n) HandMorph 0xffcd6994 M HandMorph>sendEvent:focus:clear: 0xb4f45f38: a(n) HandMorph 0xffcd985c M HandMorph>sendMouseEvent: 0xb4f45f38: a(n) HandMorph 0xffcd9888 M HandMorph>handleEvent: 0xb4f45f38: a(n) HandMorph 0xffcd98b4 M HandMorph>processEvents 0xb4f45f38: a(n) HandMorph 0xffcd98cc M [] in WorldState>doOneCycleNowFor: 0xb4f45e84: a(n) WorldState 0xffcd98f0 M Array(SequenceableCollection)>do: 0xb4f45fb4: a(n) Array 0xffcd990c M WorldState>handsDo: 0xb4f45e84: a(n) WorldState 0xffcd9928 M WorldState>doOneCycleNowFor: 0xb4f45e84: a(n) WorldState 0xffcd9944 M WorldState>doOneCycleFor: 0xb4f45e84: a(n) WorldState 0xffcd9960 M WorldMorph>doOneCycle 0xb4f45e50: a(n) WorldMorph 0xffcd9980 I [] in MorphicUIManager>spawnNewProcess 0xb4fff474: a(n) MorphicUIManager 0xffcd99a0 I [] in BlockClosure>newProcess 0xb648654c: a(n) BlockClosure Most recent primitives basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew @ @ basicNew truncated truncated @ truncated truncated @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew @ @ basicNew truncated truncated @ truncated truncated @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew basicNew @ @ basicNew @ @ @ basicNew @ @ basicNew truncated truncated @ truncated truncated @ basicNew @ @ basicNew @ @ basicNew @ @ perform: at: objectAt: new: at: stackp: at:put: at: stackp: at: stackp: at: stackp: objectAt: objectAt: basicNew: stackp: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: stackp: at:put: at: at: at: at: at: at: stackp: at:put: at: at: at: at: at: at: stackp: at:put: at: at: at: at: at: at: stackp: at:put: at: stack page bytes 4096 available headroom 3300 minimum unused headroom 3492 (last object overwritten) Abandon Le 05/01/2016 22:11, Hilaire a Ã©crit : > Hi, > > I have a situation with a recursive Dr. Geo script where the image crash > or get locked (Can't hold on the image). > I tried with latest VM as detailed in the joined crash dump. > > I did not get similar problem with other recursive script. So I may have > very special interaction between the objects, but I did not find out. > > It may also be related to Morph because when instantiating first the > canvas and its window (2nd line of the script), then the rest of the > script, it does not crash. > > The crashing image itself can be found there in case of usefulness > https://www.dropbox.com/s/rur8ayt8eon6mab/drgeo.image.zip?dl=0 > > When not crashing it outputs this cherry tree. > > Thanks > > Hilaire > -- Dr. Geo http://drgeo.eu

Jan. 7, 2016

Re: [Pharo-users] Halo Menu On Spec Tree Node

by stepharo

Thank you both... I'm getting burned from this Mooc. Reviewing slides all day long with Damien and Luc. Le 6/5/15 20:27, Nicolai Hess a Ã©crit : > > > 2015-05-06 13:47 GMT+02:00 Craig Johnson <craig(a)hivemind.net > <mailto:craig@hivemind.net>>: > > Hi All, > > I had an issue - when I opened a Halo on a Spec tree node in the > UI and select the menu Icon, I got a DNU message. However if I > selected a normal Morph, the menu Icon worked fine. > > I'm using Pharo 4.0 released version. > > Fixed this by changing TreeModel>>iconFor to: > iconFor: aNode > ^ iconBlock value cull: aNode content*s* cull: aNode > > > Hi, > > Thank you for the report (and the fix) > I made a bugtracker entry: > > 15500 <https://pharo.fogbugz.com/default.asp?15500> > SpecTreeNodeModel(Object)>>doesNotUnderstand: #content > > > > > Craig > > >

Jan. 6, 2016

Re: [Pharo-users] [ANN] The next Pharo Sprints (Lille)

by Marcus Denker

Very nice! I will put a news entry on pharo.org <http://pharo.org/> with the dates. Marcus > On 06 Jan 2016, at 15:24, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, > > thatâs great. We will organize Pharo Sprint in Santiago at the same time except of February (vacations). > > Cheers, > Juraj > > >> On Jan 6, 2016, at 04:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hello, >> >> We looked at the calendar and fixed the dates for all public sprints that we will do this >> year here locally. These are all Fridays: >> >> 29 Januar >> 26 Feb >> 25 March >> 29 April >> 27 May >> >> They will be at the Inria Lille, Building B, third floor (RMoD offices). >> Remotely, you can join us on Slack or the IRC channel #pharo on >> irc.freenode.net server. During the sprint, we will try to synchronize >> local and remote Pharo sprinters. >> >> One nice idea is to organise local sprints yourself. E.g. over the last >> sprints we had one in Chile at the same time. >> >> Marcus >> >> >> > >

Jan. 6, 2016

Re: [Pharo-users] [ANN] The next Pharo Sprints (Lille)

by Juraj Kubelka

Hi, thatâs great. We will organize Pharo Sprint in Santiago at the same time except of February (vacations). Cheers, Juraj > On Jan 6, 2016, at 04:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > We looked at the calendar and fixed the dates for all public sprints that we will do this > year here locally. These are all Fridays: > > 29 Januar > 26 Feb > 25 March > 29 April > 27 May > > They will be at the Inria Lille, Building B, third floor (RMoD offices). > Remotely, you can join us on Slack or the IRC channel #pharo on > irc.freenode.net server. During the sprint, we will try to synchronize > local and remote Pharo sprinters. > > One nice idea is to organise local sprints yourself. E.g. over the last > sprints we had one in Chile at the same time. > > Marcus > > >

Jan. 6, 2016