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

Please vote on Dr. Geo news

by Hilaire

http://www.fsdaily.com/EndUser/Dr_Geo_14_07 Do you know of other places where it is appropriate to post news about Dr. Geo? Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://launchpad.net/istoa

July 22, 2014

Re: [Pharo-dev] WhatsUp from: 2014-07-21 until: 2014-07-31

by Esteban A. Maringolo

2014-07-21 2:00 GMT-03:00 <seaside(a)rmod.lille.inria.fr>: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS Successfully integrated FullCalendar <http://arshaw.com/fullcalendar/> within Pharo/Seaside application, with tons of JS callbacks. > ### What's next, until 2014-07-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION Clean out code and release FullCalendar integration with Seaside as open source. Eventually (aka "when I have time"). Lots of other "internal" refactorings in our ongoing Pharo based software. Esteban A. Maringolo

July 22, 2014

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by kilon alios

Yeah !!! I did it !!! :D Apparently I was doing it wrong , by returning the message in doesNotUnderstand , this is why the next MNU was returned by Object instead of my parser class. Say bye bye to ugly nil syntax , Ephestos now supports normal pharo messaging. This ugly thing EphParser bpy:nil data:nil objects:'[ "Cube" ]' location: '=(0.0,0.0,0.0)' . has turned to this EphCParser bpy ; data ; objects:'["Cube"]' location:'=(0.0,0.0,0.0)' ; e. or this EphCParser bpy data objects:'["Cube"]' location:'=(0.0,0.0,0.0)'; e. or you can use parentheses . You can send all keywords as single message as I do in the example or separate them with parentheses to different messages , it does not matter because the parser unites them into a single string anyway. Message e, formulates the python string and marks the end of pharo command. Means that now I offer full python support with no weird pharo syntax :) New parser is called EphCParser if you want to give it a try, I am still working on it to make sure it works well in all scenarios. this is an example of using python globals for making the code shorter EphCParser x:'=1.0' ; e. EphCParser cube:'=bpy.data.objects["Cube"]';e. EphCParser cube ; location:'=(x,0.0,0.0)' ; e. You may wonder , "why not use pharo variables instead ?" . Well you can do that too ;) cube := EphCParser bpy data objects:'["Cube"]'. cube location:'=(x,0.0,0.0)' ; e. I will try to test the new parser a bit more and I will work on 1) receiving data from Blender 2) python errors triggering the pharo debugger and 3) buffer together multiple lines of python code for complex stuff like class and function definition etc 4) support BGE . On Sun, Jul 20, 2014 at 10:06 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Sun, Jul 20, 2014 at 7:34 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > With the help of Damien I was successful in creating a parser for pharo > to > > python syntax. Using pharo messages you can now construct automagically > > python strings and pass it to blender . This way you no longer need to > type > > in python syntax to do python stuff. So a big thanks to Damien. Note this > > method of course is slower because of parsing and heavy usage of regex > > string matching. > > > are you sure you need to pass 'nil' everywhere? In > #doesNotUnderstand:, you could check for the number of arguments and > generate something appropriate based on that. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

July 21, 2014

Re: [Pharo-dev] Suspending a Process

by Nicolai Hess

I am still struggling with it. Any ideas? 2014-07-09 11:19 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > > 2014-07-09 2:07 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Nicolai, >> >> >> On Tue, Jul 8, 2014 at 7:19 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> I want to create a process doing some work and call #changed on a Morph. >>> I want to start/suspend/resume or stop this process. >>> But sometimes, suspending the process locks the UI-Process, >>> and I don't know why. Did I miss something or do I have to care when to >>> call suspend? >>> >>> Wrapping the "morph changed" call in >>> UIManager default defer:[ morph changed]. >>> Does not change anything. >>> >>> Here is an example to reproduce it. >>> Create the process, >>> call resume, call supsend. It works, most of the time, >>> but sometimes, calling suspend locks the ui. >>> >>> p:=[[true] whileTrue:[ Transcript crShow: (DateAndTime now asString). 30 >>> milliSeconds asDelay wait]] newProcess. >>> >> p resume. >>> p suspend. >>> >> >> If you simply suspend this process at random form a user-priority process >> you'll never be able to damage the Delay machinery you're using, but >> chances are you'll suspend the process inside the critical section that >> Transcript uses to make itself thread-safe, and that'll lock up the >> Transcript. >> > > Thank you Eliot > yes I guessed it locks up the critical section, but I hoped with would not > happen if I the use UIManager defer call. > > > >> >> ThreadSafeTranscript>>nextPutAll: value >> accessSemaphore >> critical: [stream nextPutAll: value]. >> ^value >> >> So instead you need to use a semaphore. e.g. >> >> | p s wait | >> s := Semaphore new. >> p:=[[true] whileTrue:[wait ifTrue: [s wait]. Transcript crShow: >> (DateAndTime now asString). 30 milliSeconds asDelay wait]] newProcess. >> wait := true. >> 30 milliSeconds asDelay wait. >> wait := false. >> s signal >> >> etc... >> > > Is this a common pattern I can find in pharos classes. Or I need some help > understanding this. The semaphore > wait/signal is used instead of process resume/suspend? > > What I want is a process doing repeatly some computation, > calls or triggers an update on a morph, and I want to suspend and resume > this process. > > I would stop this discussion if someone tells me, "No your are doing it > wrong, go this way ..", BUT what strikes me: > in this example, that reproduces my problem more closely: > > |p m s running| > running:=false. > m:=Morph new color:Color red. > s:= StringMorph new. > m addMorphBack:s. > p:=[[true]whileTrue:[20 milliSeconds asDelay wait. s contents:(DateAndTime > now asString). m changed]] newProcess. > m on:#mouseUp send:#value to:[ > running ifTrue:[p suspend. m color:Color red.] > ifFalse:[p resume.m color:Color green.]. > running := running not]. > m extent:(300@50). > m openInWorld > > > clicking on the morph will stop or resume the process, if it locks up I > can still press alt+dot -> > - a Debugger opens but the UI is still not responsive. I can click with > the mouse on the debuggers close icon. > - nothing happens, as the UI is still blocked. > - pressing alt+Dot again, the mouse click on the close icon is processed > and the first debugger window closes > - maybe other debuggers open. > > Repeating this steps, at some time the system is *fully* responsive again! > And miraculously, it works after that without further blockages. > What's happening here? > > > Nicolai > > > >> >> HTH >> >> regards >>> Nicolai >>> >> >> >> >> -- >> best, >> Eliot >> > >

July 21, 2014

Re: [Pharo-dev] SciSmalltalk v0.12

by Nicolas Cellier

2014-07-21 16:39 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > In fact it was a typo, this is an external package developed by > Nicolas Cellier : http://www.squeaksource.com/Smallapack.html > Sorry, not integrated with SciSmalltalk at the moment. > > Regards, > > On Mon, Jul 21, 2014 at 4:34 PM, Ben Coman <btc(a)openinworld.com> wrote: > > Serge Stinckwich wrote: > >> > >> Dear all, > >> > >> we are to happy to announce SciSmalltalk v0.12 > >> > >> SciSmalltalk is a new Smalltalk project, similar to existing > >> scientific libraries like NumPy, SciPy for Python or SciRuby for Ruby. > >> SciSmalltalk already provide the following basic functionalities: > >> > >> - complex and quaternions extensions, > >> - random number generators, > >> - fuzzy algorithms, > >> - LAPACK linear algebra package, > >> > > > > > > This is interesting. > > Googling "SciSmalltalk LAPACK" showed very little. > > Do you mean you have FFI bindings to Fortan libraries of... > > http://www.netlib.org/lapack/ ? > > > > Maybe using NativeBoost? > > cheers, Ben > > > > > Hi Ben, Smallapack would definitely have its place in SciSmalltalk. It's currently using FFI because that's what existed at the time of writing. But it would be interesting to rewrite the foreign call with NativeNoost. The bad news is that there are a lot of entry points! The good news is that most of the foreign calls were generated, so a slight adaptation of the generator for using NativeBoost instead of FFI should do the trick... Or we can attempt an automatic translation FFI->NativeBoost (the range types used in LAPACK is quite limited, so it seems feasible). Does it exist? The second point is that some LAPACK functions take more than 15 parameters, so a Compiler hack is necessary to transform these calls into a single parameter array at the Smalltalk level. The hack exists but is written for the Old Compiler. No problem in Pharo 3.0. For Pharo 4.0, it's possible to port the same principle to the New Compiler, but at first glance it's far less simple (many more classes to modify/derivate). Or in the interim, make the Old Compiler a separate package and declare a dependency on the Old Compiler... Nicolas > >> - Didier Besset's numerical methods, > >> - Ordinary Differential Equation (ODE) Solver). > >> > >> Everything is available here: > >> https://github.com/SergeStinckwich/SciSmalltalk > >> All the code is available under the MIT licence. > >> > >> We have more than 424 green unit tests and we run a CI job here: > >> https://ci.inria.fr/pharo-contribution/job/SciSmalltalk/ > >> > >> This version should work on Pharo 2.0/3.0/4.0 and also Squeak 4.5 (to > >> be confirmed). > >> > >> We are a small community, we are looking for more volunteers to > >> contribute code and documentation. Please join us at : > >> https://groups.google.com/forum/#!forum/scismalltalk > >> > >> Regards, > >> > > > > > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

July 21, 2014

Re: [Pharo-dev] Understanding ClassModifiedClassDefinition announcement

by Yuriy Tymchuk

Oh, thanks. This was useful! On 21 Jul 2014, at 21:02, Nicolai Hess <nicolaihess(a)web.de> wrote: > during > Object subclass: #SomeClass instanceVariableNames: 'one' > the announcement is send and your class var points to the old class definition. > after > Object subclass: #SomeClass instanceVariableNames: 'one' > is done, your class var points to the new class definition. > And yes, I think it is the wrong behavior. The announcement is not useful > if it announces this change before the class has changed. > > There is a bug report for this: > > 13020 ClassModifiedClassDefinition should be announced AFTER the class is changed > > > > > > > 2014-07-21 20:09 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, I did this small experiment > > class := Object subclass: #SomeClass. > SystemAnnouncer uniqueInstance > when: ClassModifiedClassDefinition > do: [ :ann | > Transcript cr; > crShow: class == ann oldClassDefinition; > crShow: class == ann newClassDefinition ]. > Transcript > crShow: class == (Object subclass: #SomeClass instanceVariableNames: 'one' ). > > and got > > true > false > true > > I could understand getting true, false, false, and so having a new object for a new class, or getting false, true, true e.i getting the same object and oldClassDefinition would be a mock that can be used for consistency. > > How is all this thing working? Because Iâm tracking classes and I need to switch to another object if itâs changed and evaluate some methods. But I canât evaluate them on newClassDefinition because itâs a different object, and I canât do it on oldClassDefinition because itâs oldâ¦ > > > I would be very grateful. > Uko >

July 21, 2014

Re: [Pharo-dev] Understanding ClassModifiedClassDefinition announcement

by Nicolai Hess

during Object subclass: #SomeClass instanceVariableNames: 'one' the announcement is send and your class var points to the old class definition. after Object subclass: #SomeClass instanceVariableNames: 'one' is done, your class var points to the new class definition. And yes, I think it is the wrong behavior. The announcement is not useful if it announces this change before the class has changed. There is a bug report for this: 13020 <https://pharo.fogbugz.com/default.asp?13020> ClassModifiedClassDefinition should be announced AFTER the class is changed 2014-07-21 20:09 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, I did this small experiment > > class := Object subclass: #SomeClass. > SystemAnnouncer uniqueInstance > when: ClassModifiedClassDefinition > do: [ :ann | > Transcript cr; > crShow: class == ann oldClassDefinition; > crShow: class == ann newClassDefinition ]. > Transcript > crShow: class == (Object subclass: #SomeClass > instanceVariableNames: 'one' ). > > and got > > true > false > true > > I could understand getting true, false, false, and so having a new object > for a new class, or getting false, true, true e.i getting the same object > and oldClassDefinition would be a mock that can be used for consistency. > > How is all this thing working? Because Iâm tracking classes and I need to > switch to another object if itâs changed and evaluate some methods. But I > canât evaluate them on newClassDefinition because itâs a different object, > and I canât do it on oldClassDefinition because itâs oldâ¦ > > > I would be very grateful. > Uko >

July 21, 2014

Understanding ClassModifiedClassDefinition announcement

by Yuriy Tymchuk

Hi, I did this small experiment class := Object subclass: #SomeClass. SystemAnnouncer uniqueInstance when: ClassModifiedClassDefinition do: [ :ann | Transcript cr; crShow: class == ann oldClassDefinition; crShow: class == ann newClassDefinition ]. Transcript crShow: class == (Object subclass: #SomeClass instanceVariableNames: 'one' ). and got true false true I could understand getting true, false, false, and so having a new object for a new class, or getting false, true, true e.i getting the same object and oldClassDefinition would be a mock that can be used for consistency. How is all this thing working? Because Iâm tracking classes and I need to switch to another object if itâs changed and evaluate some methods. But I canât evaluate them on newClassDefinition because itâs a different object, and I canât do it on oldClassDefinition because itâs oldâ¦ I would be very grateful. Uko

July 21, 2014

Re: [Pharo-dev] mistakenly committed in Pharo30

by stepharo

Thanks doru for the notice I has normally no impact since we only load versionned versions. Stef On 21/7/14 18:21, Tudor Girba wrote: > Hi. > > Just to let you know: > I committed by mistake Keymapping-Core-TudorGirba.185 directly in the > http://smalltalkhub.com/mc/Pharo/Pharo30/main repository. > > I logged in on SmalltalkHub, and I deleted the offending mcz now. > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Jan Vrany

On 21/07/14 17:46, Esteban Lorenzano wrote: > > On 21 Jul 2014, at 18:40, Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > >> > We should not get limited in spawning inspectors, I think. >> My question is... is there any legitimate reason to have opened >> hundreds of any type of window? Whether they are browser, debugger, >> inspector or anything else. At least to me that would seem like an error. > > is there any legitimate reason to forbid it? > placing artificial restrictions in base of âwhat we think it should beâ > is definitively a bad a idea. Both for programming and life. > (also, being able to restrict, filter, etc. in taskbar is a better idea, > and a non-restrictive one) > > Esteban What about a token bucket sort of mechanism? This protects well against window bomb and does not impose any artificial limit at the same time. Best. Jan > >> >> >> On Mon, Jul 21, 2014 at 6:30 PM, Esteban Lorenzano >> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> >> On 21 Jul 2014, at 18:26, Guillermo Polito >> <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >>> +1 to Doru. >> >> +1 >> >>> >>> In addition, if managed at the inspector level, you'll have the >>> same problem with the debuggers and any other easily-spawned window. >>> >>> >>> On Mon, Jul 21, 2014 at 6:24 PM, Tudor Girba >>> <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>> >>> I think the issue should be addressed at the level of the >>> TaskbarMorph. That should be the one that gets limited, for >>> example, by providing a "more windows" button. >>> >>> We should not get limited in spawning inspectors, I think. >>> >>> Cheers, >>> Doru >>> >>> >>> On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr >>> <mailto:stepharo@free.fr>> wrote: >>> >>> >>> On 21/7/14 10:29, Peter UhnÃ¡k wrote: >>>> Wouldn't it be easier to simply enforce fixed limit of >>>> Inspector/Debug instances (e.g. 10 or 20)? After >>>> reaching the limit creation of more would be simply >>>> ignored. Because as a victim I don't see much use of >>>> having vastly more windows than even fit on the screen >>>> especially since most of the erroneous windows are >>>> actually identical. >>> >>> yes this is a nice idea. >>> If somebody is ready for the challenge, please try and we >>> will integrate it. >>> >>> >>>> >>>> Peter >>>> >>>> >>>> On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be >>>> <mailto:phil@highoctane.be> <phil(a)highoctane.be >>>> <mailto:phil@highoctane.be>> wrote: >>>> >>>> It would be nice to have the toolbar have some kind >>>> of Win7 spinner to the right to solve this. >>>> >>>> Is there a way to know when a system window was opened? >>>> >>>> Who hasn't been a victim of the attack of the too >>>> many windows popping up all over? >>>> >>>> Phil >>>> >>>> Le 21 juil. 2014 02:12, "Ben Coman" >>>> <btc(a)openinworld.com <mailto:btc@openinworld.com>> a >>>> Ã©crit : >>>> >>>> kilon alios wrote: >>>>> I am afraid I could not do that, it seems that >>>>> when pharo has opened too many windows the >>>>> bottom bar takes all the space of the pharo >>>>> windows and because it has higher viewer >>>>> priority you cannot view any kind of window. >>>>> All you see is that bars that represent open >>>>> windows filling your screen. >>>> >>>> That is a problem. >>>> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >>>> >>>>> >>>>> So the solution for me was to reopen the image >>>>> , fetch most of my lost code from changes and >>>>> fortunately only add a few lines of code back >>>>> that were permanently lost. >>>>> >>>>> So a big thank you for changes , it saved me at >>>>> least hours of work and thank you for trying to >>>>> help me. >>>>> >>>>> >>>>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman >>>>> <btc(a)openinworld.com >>>>> <mailto:btc@openinworld.com>> wrote: >>>>> >>>>> As Peter said, you can execute any code in >>>>> an inspector window. Here is how you might >>>>> solve this yourself :) >>>>> There is a menu option >>>>> World > Windows > Delete unchanged windows. >>>>> Of course, you can't use that directly >>>>> since your background is covered with >>>>> windows. But you could open up another >>>>> image and then do this... >>>>> 1. Bring up the halos on that menu option >>>>> 2. Click the "Debug" spanner icon and >>>>> choose 'Inspect Morph' >>>>> 3. Scroll down to /target/ where you find >>>>> "[ World closeUnchangedWindows ]" >>>>> 4. Evaluate that back in the problem image >>>>> in any Inspector. >>>>> >>>>> I describe this process since until a >>>>> moment ago when I did that, I didn't know >>>>> about the existence of "closeUnchangedWindows." >>>>> cheers -ben >>>>> >>>>> >>>>> Peter UhnÃ¡k wrote: >>>>>> Maybe running something like this would work: >>>>>> ---- >>>>>> InspectorNavigator allInstancesDo: [ :each >>>>>> | each window close ]. >>>>>> ---- >>>>>> >>>>>> You can run arbitrary code from basically >>>>>> anywhere where you can enter text (and >>>>>> Inspector has couple of boxes where you >>>>>> can enter text). >>>>>> >>>>>> Also doesn't holding escape close it too? >>>>>> >>>>>> Peter >>>>>> >>>>>> >>>>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon >>>>>> alios <kilon.alios(a)gmail.com >>>>>> <mailto:kilon.alios@gmail.com>> wrote: >>>>>> >>>>>> Is there a shortcut to close all >>>>>> inspector windows ? and if not how I >>>>>> close the window of a selected inspector ? >>>>>> >>>>>> Basically I accidentally opened over >>>>>> 1000 inspector windows and i want to >>>>>> close them all now because they have >>>>>> occupied the entire GUI and I cant do >>>>>> anything other than closing them on by >>>>>> one. I cant open the world menu or >>>>>> open a new window because they take >>>>>> not only the entire window but also >>>>>> they are always on top. >>>>>> >>>>>> The tragedy is that I had plenty of >>>>>> code that I don't want to lose because >>>>>> I have not saved, please help :( >>>>>> >>>>>> Can't open a workspace to issue pharo >>>>>> commands or any other window :( >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> >>> "Every thing has its own flow" >>> >>> >> >> >

July 21, 2014