- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Penelope - Fail to create account

by Carla F. Griggio

Not in my case, carlagriggio(a)gmail.com is a biologist from Brazil :P On Wed, Jul 17, 2013 at 3:40 AM, Clara Allende <clari.allende(a)gmail.com>wrote: > Just write your mail without dots, its the same for gmail (I've been there > already) > > Sent from Gmail for Android > On 17 Jul 2013 01:14, "Carla F. Griggio" <carla.griggio(a)gmail.com> wrote: > >> Me :( >> I could see the issues by entering each category listed in the home page, >> but still it was uncomfortable to feel that I should know before hand in >> which category the issue I was looking for could be listed. >> I wanted to register to post issues with my name and I couldn't (and in >> the login form there should be a link explaining how to register, not only >> for asking a lost password). >> >> Cheers, >> Carla >> >> >> On Wed, Jul 17, 2013 at 1:06 AM, Mariano Vicente <m.vicent(a)gmail.com>wrote: >> >>> Hi. >>> I tried create my user in penelope [1], so I can see the issues in >>> fogbugz. and this fails when i added the email, I think the problems are >>> the dots in my email adress. >>> >>> Anybody have had the same problem? >>> >>> [1] http://bugs.pharo.org/issues?_k=DBsCrRwP1TgaBEDb >>> >>> Regards, >>> Mariano >>> >> >>

July 17, 2013

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

by Andrei Vasile Chis

> > 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 :-) > > Sounds like a good plan :)

July 17, 2013

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

by Andrei Vasile Chis

-1 but i don't like it in form of extra buttons row, which makes > debugger UI too bloated. > They will be accessible from the context menu of the stack. > > > Andrei > > > > -- > Best regards, > Igor Stasenko. > >

July 17, 2013

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

by Frank Shearar

On 17 July 2013 15:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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 :-) It'll quickly flush out whether or not the feature really is important! frank > Marcus > > >

July 17, 2013

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