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

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

by Esteban Lorenzano

On 21 Jul 2014, at 18:40, Peter UhnÃ¡k <i.uhnak(a)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 > > > On Mon, Jul 21, 2014 at 6:30 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 21 Jul 2014, at 18:26, Guillermo Polito <guillermopolito(a)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> 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> 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 <phil(a)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> 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> 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> 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 >> >> "Every thing has its own flow" >> > >

July 21, 2014

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

by Peter UhnÃ¡k

> 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. On Mon, Jul 21, 2014 at 6:30 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 21 Jul 2014, at 18:26, Guillermo Polito <guillermopolito(a)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> 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> 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 <phil(a)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> 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> >>>>> 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> >>>>>> 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 >> >> "Every thing has its own flow" >> > > >

July 21, 2014

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

by Esteban Lorenzano

On 21 Jul 2014, at 18:26, Guillermo Polito <guillermopolito(a)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> 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> 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 <phil(a)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> 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> 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> 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 > > "Every thing has its own flow" >

July 21, 2014

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

by Guillermo Polito

+1 to Doru. 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> 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> 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 <phil(a)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> 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> 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> >>>>> 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 > > "Every thing has its own flow" >

July 21, 2014

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

by Tudor Girba

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> 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 <phil(a)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> 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> 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> >>>> 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 "Every thing has its own flow"

July 21, 2014

mistakenly committed in Pharo30

by Tudor Girba

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 "Every thing has its own flow"

July 21, 2014

Re: [Pharo-dev] [Pharo4] MetaLinks on Class Variables

by Marcus Denker

On 21 Jul 2014, at 15:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 21 Jul 2014, at 11:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hello, >> >> One of the questions with having meta objects for variables (Slots and Globals) is: For what is is good? >> >> Here is one exampleâ¦ in early stage but working. >> > > Now working: MetaLinks on Class Variables. > > |link | > link := MetaLink new > metaObject: Halt; > selector: #now. > > (TT classVariableNamed: #T) link: link. > > â¦ and any access of the class var will trigger a Halt. > > https://pharo.fogbugz.com/f/cases/13630/Links-on-Class-Variables > > next: Globals, this means > > Object binding link: link > > should trigger the link whenever the global Object is read anywhereâ¦ This now crashes your image as expectedâ¦ ;-) https://pharo.fogbugz.com/f/cases/13632/MetaLinks-for-Globals Marcus

July 21, 2014

Re: [Pharo-dev] SciSmalltalk v0.12

by Serge Stinckwich

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 > > >> - 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] SciSmalltalk v0.12

by Ben Coman

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 > - 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, >

July 21, 2014

SciSmalltalk v0.12

by Serge Stinckwich

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, - 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