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

Project Catalog getting out slowly :)

by StÃ©phane Ducasse

Hi guys I start to be able to generate such files for a Pharo project catalog I added some metadata to configuration files and it pays off. Stef

July 13, 2013

Re: [Pharo-dev] Some Spec questions

by Tudor Girba

Exciting times :) Doru On Jul 13, 2013, at 8:08 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Ok, then we will integrate it together when you come to Lille in 2 weeks. > > Good news. > > Cheers, > > > 2013/7/12 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > Hi ClÃ©ment, Hi Clara, > > > What about integrating the new debugger by default now ? I mean the new debugger is now in Pharo 3.0 alpha but the old debugger is still triggered by default, for example when you do Cmd+Maj+d or when you set the setting 'Always open full debugger'. We (Marcus and I) would like to integrate it now by default in Pharo 3.0 alpha, so we have enough time to stabilize it (in case of problems) and we can then remove the old debugger and old inspectors from Pharo. > > Now I want your point of view: > - What do you think about integrating the spec debugger by default next week ? > > In two weeks (22 July) I would visit you in Lille. That would be a good time to integrate. > > > - Is it currently stable enough ? > > All the features that are present at the moment are quite stable. > > > - Should I wait a little more so you can add extra features ? > > I've talked with Andrei and we've set a "milestone". By next week, we would like to have done issues > 10956 > 10952 > 10954 > 10953 > 10955 > > If at least the first three issues are done, then the new debugger will have most of the necessary features. > I'd also help with these and I hope we'll be done by the end of this month. > > > By next week I will have more time, since the semester will be finished. > > Having Andrei's debugger by default requires that it has the full stack menu ready before the Pharo 3.0 release (next spring), because if not people will blame all the Pharo team. > - Are you working on it ? > That's what I plan to do next week :) I'm working on it, but not full time. > > - Will it be ready before the next Pharo release ? > > If you think you need to improve the debugger before we integrate it by default, for example with Clara's GSoC work, please tell me when it will be ready so we can add it into the Pharo 3.0 integration planning. Then I guess you can add a slice with your improvements in the Pharo bug tracker, and I will add an extra slice with smalltalk tools change so the new debugger will be triggered by default. It would be nice if we can integrate it before the end of september. > > We'll surely be able to have all the missing features by the end of September. > They do not require so much work. > > > In any case I will be in case with both Andrei and you (if you don't mind) to get this done... > > Please do :) > > Cheers, > Andrei > > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

July 13, 2013

Re: [Pharo-dev] Athens + Amber progress

by Tudor Girba

Hi, Great work! Also, Matthias is describing the progress on a dedicated blog, so people can stay tuned: http://amber-athens.m-sp.org/ Cheers, Doru On Jul 12, 2013, at 5:51 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hi, i just wanna share news about progress on subject GSoC project. > > Matthew made quite decent progress on the subject. It is almost there, > just some glitches here and there, > but in overall, i am quite happy, and i think it is already in quite > useful state. > > To check it, just follow the link on your browser: > > http://matthias-springer.github.io/amber-athens/ > > (works best with chrome then firefox) > > For impatient: > > go to step 2, press doit, > then skip to step 32 and press doit again > > :) > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "What we can governs what we wish."

July 13, 2013

Re: [Pharo-dev] about WidgetAbstractWrapper

by Stephan Eggermont

Can it be named, please ;) Stephan

July 13, 2013

Re: [Pharo-dev] @lab at midday

by Damien Cassou

On Fri, Jul 12, 2013 at 4:13 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> > Ok, that seems to only work for non-native french speakers :) Although it is stupid to explain jokes this should be a proof of my capabilities of speaking french. If I would know how to speak it I probably would have written "Au revoir" insteadâ¦ :-D -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 13, 2013

Re: [Pharo-dev] Some Spec questions

by ClÃ©ment Bera

Ok, then we will integrate it together when you come to Lille in 2 weeks. Good news. Cheers, 2013/7/12 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > Hi ClÃ©ment, Hi Clara, > > > What about integrating the new debugger by default now ? I mean the new >>> debugger is now in Pharo 3.0 alpha but the old debugger is still triggered >>> by default, for example when you do Cmd+Maj+d or when you set the setting >>> 'Always open full debugger'. We (Marcus and I) would like to integrate it >>> now by default in Pharo 3.0 alpha, so we have enough time to stabilize it >>> (in case of problems) and we can then remove the old debugger and old >>> inspectors from Pharo. >>> >>> Now I want your point of view: >>> - What do you think about integrating the spec debugger by default next >>> week ? >>> >> > In two weeks (22 July) I would visit you in Lille. That would be a good > time to integrate. > > > >> - Is it currently stable enough ? >>> >> > All the features that are present at the moment are quite stable. > > > >> - Should I wait a little more so you can add extra features ? >>> >> >> I've talked with Andrei and we've set a "milestone". By next week, we >> would like to have done issues >> 10956 >> 10952 >> 10954 >> 10953 >> 10955 >> > > If at least the first three issues are done, then the new debugger will > have most of the necessary features. > I'd also help with these and I hope we'll be done by the end of this month. > > > >> By next week I will have more time, since the semester will be finished. >> >>> >>> >> Having Andrei's debugger by default requires that it has the full stack >>> menu ready before the Pharo 3.0 release (next spring), because if not >>> people will blame all the Pharo team. >>> - Are you working on it ? >>> >> That's what I plan to do next week :) I'm working on it, but not full >> time. >> >> >>> - Will it be ready before the next Pharo release ? >>> >> >>> If you think you need to improve the debugger before we integrate it by >>> default, for example with Clara's GSoC work, please tell me when it will be >>> ready so we can add it into the Pharo 3.0 integration planning. Then I >>> guess you can add a slice with your improvements in the Pharo bug tracker, >>> and I will add an extra slice with smalltalk tools change so the new >>> debugger will be triggered by default. It would be nice if we can integrate >>> it before the end of september. >>> >> > We'll surely be able to have all the missing features by the end of > September. > They do not require so much work. > > >> >> In any case I will be in case with both Andrei and you (if you don't >> mind) to get this done... >> >> Please do :) > > Cheers, > Andrei > > >

July 13, 2013

Re: [Pharo-dev] [NB]: Review & fixes & ideas

by Sean P. DeNigris

Thanks for all this work, Igor! But can we do a simple system call yet?! http://forum.world.st/NB-crash-boom-td4669980.html https://pharo.fogbugz.com/f/cases/7542/NB-system-examplerun: str Sean: run: str "self run: 'open http://www.google.com'." <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode > ^ self nbCall: #( int system (String str) ) module: NativeBoost CLibrary fails Cami: "Yes I would put that even on high-priority for NB, as it is the most important use-case that makes sense to me :D" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-NB-Review-fixes-ideas-tp4698514p4698563.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 13, 2013

Re: [Pharo-dev] about WidgetAbstractWrapper

by Erwan Douaille

I start to create it, what would you like to get in ? for the moment there is nothing because i focused on something different 2013/7/12 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > Hi Erwan, > > I've heard you are working on a WidgetAbstractWrapper for dealing with > dynamic widgets :) > Is it still a work in progress or there's already something concrete? > > Cheers, > Andrei > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

July 12, 2013

about WidgetAbstractWrapper

by Andrei Vasile Chis

Hi Erwan, I've heard you are working on a WidgetAbstractWrapper for dealing with dynamic widgets :) Is it still a work in progress or there's already something concrete? Cheers, Andrei

July 12, 2013

Re: [Pharo-dev] Some Spec questions

by Andrei Vasile Chis

Hi ClÃ©ment, Hi Clara, What about integrating the new debugger by default now ? I mean the new >> debugger is now in Pharo 3.0 alpha but the old debugger is still triggered >> by default, for example when you do Cmd+Maj+d or when you set the setting >> 'Always open full debugger'. We (Marcus and I) would like to integrate it >> now by default in Pharo 3.0 alpha, so we have enough time to stabilize it >> (in case of problems) and we can then remove the old debugger and old >> inspectors from Pharo. >> >> Now I want your point of view: >> - What do you think about integrating the spec debugger by default next >> week ? >> > In two weeks (22 July) I would visit you in Lille. That would be a good time to integrate. > - Is it currently stable enough ? >> > All the features that are present at the moment are quite stable. > - Should I wait a little more so you can add extra features ? >> > > I've talked with Andrei and we've set a "milestone". By next week, we > would like to have done issues > 10956 > 10952 > 10954 > 10953 > 10955 > If at least the first three issues are done, then the new debugger will have most of the necessary features. I'd also help with these and I hope we'll be done by the end of this month. > By next week I will have more time, since the semester will be finished. > >> >> > Having Andrei's debugger by default requires that it has the full stack >> menu ready before the Pharo 3.0 release (next spring), because if not >> people will blame all the Pharo team. >> - Are you working on it ? >> > That's what I plan to do next week :) I'm working on it, but not full time. > > >> - Will it be ready before the next Pharo release ? >> > >> If you think you need to improve the debugger before we integrate it by >> default, for example with Clara's GSoC work, please tell me when it will be >> ready so we can add it into the Pharo 3.0 integration planning. Then I >> guess you can add a slice with your improvements in the Pharo bug tracker, >> and I will add an extra slice with smalltalk tools change so the new >> debugger will be triggered by default. It would be nice if we can integrate >> it before the end of september. >> > We'll surely be able to have all the missing features by the end of September. They do not require so much work. > > In any case I will be in case with both Andrei and you (if you don't mind) > to get this done... > > Please do :) Cheers, Andrei

July 12, 2013