- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Idea for playground

by stepharo

Once we have the path it means that we can reapply it to all the elements of a collection for example :) Le 28/4/15 19:53, Andrei Chis a Ã©crit : > It's coming :) > > We implemented a while back a prototype for recording/replaying all > the steps in an inspection session, but because of the > current design of glamour it was quite difficult to get it working > correctly. > > > Cheers, > Andrei > > > On Tue, Apr 28, 2015 at 7:16 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com > <mailto:yuriy.tymchuk@me.com>> wrote: > > Hi, > > sometimes when I play in playground in order to achieve something > I can go 10 levels deep or even more. Maybe we can implement an > option to somehow construct one script from all executed parts, so > then this script can be turned into a method or so on. > > > Uko > >

April 28, 2015

Re: [Pharo-dev] Idea for playground

by Pablo Estefo

Nice ;) On 28 April 2015 at 14:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Indeed, this one important direction we will take in the near future :) > > Cheers, > Doru > > > On Tue, Apr 28, 2015 at 7:53 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> It's coming :) >> >> We implemented a while back a prototype for recording/replaying all the >> steps in an inspection session, but because of the >> current design of glamour it was quite difficult to get it working >> correctly. >> >> >> Cheers, >> Andrei >> >> >> On Tue, Apr 28, 2015 at 7:16 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >>> Hi, >>> >>> sometimes when I play in playground in order to achieve something I can >>> go 10 levels deep or even more. Maybe we can implement an option to somehow >>> construct one script from all executed parts, so then this script can be >>> turned into a method or so on. >>> >>> >>> Uko >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

April 28, 2015

Re: [Pharo-dev] Idea for playground

by Tudor Girba

Indeed, this one important direction we will take in the near future :) Cheers, Doru On Tue, Apr 28, 2015 at 7:53 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > It's coming :) > > We implemented a while back a prototype for recording/replaying all the > steps in an inspection session, but because of the > current design of glamour it was quite difficult to get it working > correctly. > > > Cheers, > Andrei > > > On Tue, Apr 28, 2015 at 7:16 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> Hi, >> >> sometimes when I play in playground in order to achieve something I can >> go 10 levels deep or even more. Maybe we can implement an option to somehow >> construct one script from all executed parts, so then this script can be >> turned into a method or so on. >> >> >> Uko >> > > -- www.tudorgirba.com "Every thing has its own flow"

April 28, 2015

Re: [Pharo-dev] [Issue tracker] what about old issues?

by Sven Van Caekenberghe

> On 28 Apr 2015, at 19:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 28 Apr 2015, at 18:19, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> 666 open issues >> The tracker is telling us that old issues are evil. :) >> > :-) > >> -> automatically put them on âclosed, timeoutâ >> -> send a mail to the original submitter AND pharo-dev >> Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it. > > it would be easier to automateâ¦. > > Marcus Yes, it should be automated (saving people's time is very important). And yes, issue that are too old for anyone to care about should be deactivated.

April 28, 2015

Re: [Pharo-dev] [Issue tracker] what about old issues?

by Marcus Denker

> On 28 Apr 2015, at 18:19, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > 666 open issues > The tracker is telling us that old issues are evil. :) > :-) > -> automatically put them on âclosed, timeoutâ > -> send a mail to the original submitter AND pharo-dev > Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it. it would be easier to automateâ¦. Marcus

April 28, 2015

Re: [Pharo-dev] Idea for playground

by Andrei Chis

It's coming :) We implemented a while back a prototype for recording/replaying all the steps in an inspection session, but because of the current design of glamour it was quite difficult to get it working correctly. Cheers, Andrei On Tue, Apr 28, 2015 at 7:16 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi, > > sometimes when I play in playground in order to achieve something I can go > 10 levels deep or even more. Maybe we can implement an option to somehow > construct one script from all executed parts, so then this script can be > turned into a method or so on. > > > Uko >

April 28, 2015

Re: [Pharo-dev] Pharo 50 has old Rubric Repo

by Andrei Chis

We didn't do any integration of rubric into Pharo 5 yet so the old repo is still there. Cheers, Andrei On Tue, Apr 28, 2015 at 6:19 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Should be http://smalltalkhub.com/mc/Pharo/Rubric/main/, not Alain's > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Pharo-50-has-old-Rubric-Repo-tp4822586.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 28, 2015

Re: [Pharo-dev] Pharo 50 has old Rubric Repo

by Sean P. DeNigris

Andrei Chis wrote > We didn't do any integration of rubric into Pharo 5 yet so the old repo is > still there. Yes, but we want new packages to go into the new repo so it should be there! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-50-has-old-Rubric-Repo-tp4822586p4822604.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2015

Cherry Picking Doesn't Dirty MC Packages

by Sean P. DeNigris

I was merging a slice in order to leave out some unwanted changes that got in accidentally. In the merge tool for each of those changes I chose to keep the current version, did the merge, recommitted the slice, and... All the unwanted changes were still there! Apparently, when cherry picking, the packages aren't marked dirty in MC, so they were not saved again with the slice. Only by browsing changes for each package via the working copy browser was I able to get them all marked dirty and commit the new versions. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Cherry-Picking-Doesn-t-Dirty-MC-Packages-tp4822602.ht… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2015

Re: [Pharo-dev] Idea for playground

by Pablo Estefo

+1 I got the same idea some days ago, then we can shrink levels and got wide perspective of what we are doing. On 28 April 2015 at 13:16, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi, > > sometimes when I play in playground in order to achieve something I can go > 10 levels deep or even more. Maybe we can implement an option to somehow > construct one script from all executed parts, so then this script can be > turned into a method or so on. > > > Uko >

April 28, 2015