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

Re: [Pharo-dev] buttons for browsing in the debugger

by Marcus Denker

On Jul 17, 2013, at 4:11 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > >> 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? > > I don't think so. 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 :-) Marcus

July 17, 2013

Re: [Pharo-dev] buttons for browsing in the debugger

by Marcus Denker

On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > 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? I don't think so. > Do we want it in the new debugger? I would not botherâ¦ things like that are to be removed to gain clarity. Marcus

July 17, 2013

Re: [Pharo-dev] buttons for browsing in the debugger

by Igor Stasenko

On 17 July 2013 15:57, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > 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? > +1 i want these things to be easily accessible from debugger -1 but i don't like it in form of extra buttons row, which makes debugger UI too bloated. > Andrei -- Best regards, Igor Stasenko.

July 17, 2013

buttons for browsing in the debugger

by Andrei Vasile Chis

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

July 17, 2013

Re: [Pharo-dev] CameraPlugin for (Pharo) VM

by Marcus Denker

On Jul 17, 2013, at 3:51 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 17 July 2013 15:30, Torsten Bergmann <astares(a)gmx.de> wrote: >> We once had a discussion already, to summarize: >> - the camera plugin from scratch worked according to Bernat Romagosa [1] >> - Stef checked the scratch license and said this license is not MIT so he do not want to see it in Pharo [2] [3] >> >> We didnt move on with this since we thought it is covered by Scratch license or since nobody really cared. >> >> But it looks like the Camera stuff is indeed released with MIT license (even before the discussion) >> I just found by accident this old issue: >> >> http://bugs.squeak.org/view.php?id=7654 >> >> <quotes> >> "two plugins that should be made available for standard VMs" >> >> "Per communication from Bert Freudenberg, source for CameraPlugin is >> now available under MIT license:" >> >> "Here is the CameraPlugin code under MIT license." >> </quote> >> >> Acccording to this issue the camera code was opened with MIT. The issue also includes the code. >> >> Can we check again - default support for camera would be a nice addition >> to our Pharo universe. >> > > If we include that plugin into VM, then there should be someone , who > will take responsibility for maintaining and improving it. > > And that means: > - making sure it works on all 3 major platforms (at least) and not > breaks with new version(s) releases > - updates the code, improves it etc > - keep image-side code in good shape covered by tests and updated > regularly , as Pharo make progress > - have a good documentation > > any volunteers? > I could, but i can't , because i already have multiple projects to > care about. And i am close to limits of personal physical capabilities > to keep things up. > > I didn't wanted to discourage anyone, but just wanted to remind that > 'including into pharo' means a lot more than 'copying files there', > otherwise it is not 'including', but planting timebomb which will > explode eventually. Yes, in addition I really don't like to ship the VM with lots of specialized Plugins. (Klatt Pluginâ¦ ) Wouldn't it be possible to use FFI instead? Than everything is in user land, no VM change needed. Marcus

July 17, 2013

Re: [Pharo-dev] CameraPlugin for (Pharo) VM

by Esteban Lorenzano

On Jul 17, 2013, at 3:51 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 17 July 2013 15:30, Torsten Bergmann <astares(a)gmx.de> wrote: >> We once had a discussion already, to summarize: >> - the camera plugin from scratch worked according to Bernat Romagosa [1] >> - Stef checked the scratch license and said this license is not MIT so he do not want to see it in Pharo [2] [3] >> >> We didnt move on with this since we thought it is covered by Scratch license or since nobody really cared. >> >> But it looks like the Camera stuff is indeed released with MIT license (even before the discussion) >> I just found by accident this old issue: >> >> http://bugs.squeak.org/view.php?id=7654 >> >> <quotes> >> "two plugins that should be made available for standard VMs" >> >> "Per communication from Bert Freudenberg, source for CameraPlugin is >> now available under MIT license:" >> >> "Here is the CameraPlugin code under MIT license." >> </quote> >> >> Acccording to this issue the camera code was opened with MIT. The issue also includes the code. >> >> Can we check again - default support for camera would be a nice addition >> to our Pharo universe. >> > > If we include that plugin into VM, then there should be someone , who > will take responsibility for maintaining and improving it. > > And that means: > - making sure it works on all 3 major platforms (at least) and not > breaks with new version(s) releases > - updates the code, improves it etc > - keep image-side code in good shape covered by tests and updated > regularly , as Pharo make progress > - have a good documentation > > any volunteers? > I could, but i can't , because i already have multiple projects to > care about. And i am close to limits of personal physical capabilities > to keep things up. > > I didn't wanted to discourage anyone, but just wanted to remind that > 'including into pharo' means a lot more than 'copying files there', > otherwise it is not 'including', but planting timebomb which will > explode eventually. amen > >> Thx >> T. >> >> >> [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051826.html >> [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051838.html >> [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051843.html >> > > > > -- > Best regards, > Igor Stasenko. >

July 17, 2013

Re: [Pharo-dev] Spec delete method

by Andrei Vasile Chis

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.pharo(a)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 <tudor(a)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.pharo(a)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.ducasse(a)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" > > >

July 17, 2013

Re: [Pharo-dev] CameraPlugin for (Pharo) VM

by Igor Stasenko

On 17 July 2013 15:30, Torsten Bergmann <astares(a)gmx.de> wrote: > We once had a discussion already, to summarize: > - the camera plugin from scratch worked according to Bernat Romagosa [1] > - Stef checked the scratch license and said this license is not MIT so he do not want to see it in Pharo [2] [3] > > We didnt move on with this since we thought it is covered by Scratch license or since nobody really cared. > > But it looks like the Camera stuff is indeed released with MIT license (even before the discussion) > I just found by accident this old issue: > > http://bugs.squeak.org/view.php?id=7654 > > <quotes> > "two plugins that should be made available for standard VMs" > > "Per communication from Bert Freudenberg, source for CameraPlugin is > now available under MIT license:" > > "Here is the CameraPlugin code under MIT license." > </quote> > > Acccording to this issue the camera code was opened with MIT. The issue also includes the code. > > Can we check again - default support for camera would be a nice addition > to our Pharo universe. > If we include that plugin into VM, then there should be someone , who will take responsibility for maintaining and improving it. And that means: - making sure it works on all 3 major platforms (at least) and not breaks with new version(s) releases - updates the code, improves it etc - keep image-side code in good shape covered by tests and updated regularly , as Pharo make progress - have a good documentation any volunteers? I could, but i can't , because i already have multiple projects to care about. And i am close to limits of personal physical capabilities to keep things up. I didn't wanted to discourage anyone, but just wanted to remind that 'including into pharo' means a lot more than 'copying files there', otherwise it is not 'including', but planting timebomb which will explode eventually. > Thx > T. > > > [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051826.html > [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051838.html > [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-July/051843.html > -- Best regards, Igor Stasenko.

July 17, 2013

Re: [Pharo-dev] Spec delete method

by Benjamin

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 <tudor(a)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.pharo(a)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.ducasse(a)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"

July 17, 2013

Re: [Pharo-dev] Spec delete method

by Tudor Girba

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.pharo(a)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.ducasse(a)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"

July 17, 2013