Pharo-dev

By thread

pharo-dev@lists.pharo.org

April 2013

97 participants
1636 messages

Re: [Pharo-project] [Moose-dev] Re: Big thanks for the organization of the Pharo Conf and MooseDay

by Stephan Eggermont

On 5 apr 2013, at 12:16, Tudor Girba wrote: > I would also want to thank the participants! The atmosphere was nice and the presentation was interesting. > > I for one learnt quite a bit. > > The sessions were recorded, and once Stephan Eggermont will convert them, they will be posted. And for some ideas on when that will be: I just got back from Diego with 72 GB of video files. This weekend I might find some time to proces them, but the whole week I'm at Accu2013 in Bristol. So what's not posted on monday, will take at least a week more. If anyone has other material (sheets, screencasts, other video) please let me know I'll keep you posted. Stephan

April 5, 2013

Re: [Pharo-project] [update 3.0] #30022

by Camillo Bruni

indeed strange... To me it looks like the pragma collector spends a lot of time fetching stuff. And I would even say it happens twice per menu popup? On 2013-04-05, at 17:53, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > One question: why is the debugged menu (right click thing) taking so long > to show up where the world menu pops almost immediately? > > I wonder. > > > 2013/4/5 Camillo Bruni <camillobruni(a)gmail.com> > >> >> On 2013-04-05, at 17:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 05 Apr 2013, at 17:18, Martin Dias <tinchodias(a)gmail.com> wrote: >>> >>>> Sounds great. No idea how to notice the difference, but I tried the >> "Fuel out stack" option and it works. >>> >>> Indeed, sounds very promising but what does it mean ? >>> There does not seem to be any description in the issue tracker either, >> or maybe I missed it. >> >> >> AFAIK that's a "very" old feature no? >> => open debugger => right click => last entry/second last entry => Fuel >> out stack >> >> It will just serialize the whole stack and put it in a file next to the >> image. >>

April 5, 2013

Re: [Pharo-project] [update 3.0] #30022

by phil＠highoctane.be

One question: why is the debugged menu (right click thing) taking so long to show up where the world menu pops almost immediately? I wonder. 2013/4/5 Camillo Bruni <camillobruni(a)gmail.com> > > On 2013-04-05, at 17:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > On 05 Apr 2013, at 17:18, Martin Dias <tinchodias(a)gmail.com> wrote: > > > >> Sounds great. No idea how to notice the difference, but I tried the > "Fuel out stack" option and it works. > > > > Indeed, sounds very promising but what does it mean ? > > There does not seem to be any description in the issue tracker either, > or maybe I missed it. > > > AFAIK that's a "very" old feature no? > => open debugger => right click => last entry/second last entry => Fuel > out stack > > It will just serialize the whole stack and put it in a file next to the > image. >

April 5, 2013

Re: [Pharo-project] [update 3.0] #30022

by Camillo Bruni

On 2013-04-05, at 17:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 05 Apr 2013, at 17:18, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Sounds great. No idea how to notice the difference, but I tried the "Fuel out stack" option and it works. > > Indeed, sounds very promising but what does it mean ? > There does not seem to be any description in the issue tracker either, or maybe I missed it. AFAIK that's a "very" old feature no? => open debugger => right click => last entry/second last entry => Fuel out stack It will just serialize the whole stack and put it in a file next to the image.

April 5, 2013

Re: [Pharo-project] [update 3.0] #30022

by Sven Van Caekenberghe

On 05 Apr 2013, at 17:18, Martin Dias <tinchodias(a)gmail.com> wrote: > Sounds great. No idea how to notice the difference, but I tried the "Fuel out stack" option and it works. Indeed, sounds very promising but what does it mean ? There does not seem to be any description in the issue tracker either, or maybe I missed it. > On Fri, Apr 5, 2013 at 1:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 30022 > ----- > > 10032 Integrate new debugger > https://pharo.fogbugz.com/f/cases/10032 > > Diff information: > http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/DebuggerModel-EstebanLorenza… > http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Debugger-EstebanLorenza…

April 5, 2013

Re: [Pharo-project] [update 3.0] #30022

by Martin Dias

Sounds great. No idea how to notice the difference, but I tried the "Fuel out stack" option and it works. On Fri, Apr 5, 2013 at 1:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > 30022 > ----- > > 10032 Integrate new debugger > https://pharo.fogbugz.com/f/cases/10032 > > Diff information: > > http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/DebuggerModel-EstebanLorenza… > > http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Debugger-EstebanLorenza… > > >

April 5, 2013

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by Martin Dias

As Fernando said, probably is better for you to substitute the obsolete class by a ring definition. Look here: http://ws.stfx.eu/OAVG8IXKWOYA Don't need to filein the workaround of my previous email. Martin On Fri, Apr 5, 2013 at 4:47 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi, > I'm sorry for my delay. I didn't stop to think a good solution. There were > interesting answers before mine. But if it's a prototype... maybe this > workaround helps you. I played with this code: > > http://ws.stfx.eu/HYWM1ZB9R45K > > (the first time I use the shared workspace :-) > > if you file in the attached file, it materializes the new A class. > > But this will be not useful for you, if either: > - you don't have the "original class" at materialization time > - you don't want to know if the class was obsolete at serialization time > > HTH > Martin > > > > On Tue, Apr 2, 2013 at 7:33 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > >> On 02/04/13 12:50 AM, roberto.minelli-BHDiRLqP7qo(a)**public.gmane.org<roberto.minelli-BHDiRLqP7qo(a)public.gmane.org>wrote: >> >>> >>> Is there any way to "browse" through such references to understand where >>> are they? >>> >> >> From an inspector, choose the "Explore pointers", making sure you've >> selected the object that you're trying to understand what is referencing it. >> >> It takes trial & error, and intuition on which pointers to follow. This >> method has often been unsuccessful for me. >> >> Another approach (my memory is fuzzy), was to put a halt at a suitable >> place during the Fuel serialization. Then explore the intermediate >> structures used by Fuel, to try to find out why Fuel thinks it needs to >> serialize that object. >> >> Yet another approach is to put a halt in the Fuel materialization, and >> explore the intermediate structures used by Fuel. You might even set up a >> mapping of the obsolete class to some temporary class, which allows Fuel to >> fully materialize the saved objects. You can then explore the Fuel >> intermediate structures, as well as the final de-serialized object >> structure. >> >> >> >

April 5, 2013

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by Martin Dias

Hi, I'm sorry for my delay. I didn't stop to think a good solution. There were interesting answers before mine. But if it's a prototype... maybe this workaround helps you. I played with this code: http://ws.stfx.eu/HYWM1ZB9R45K (the first time I use the shared workspace :-) if you file in the attached file, it materializes the new A class. But this will be not useful for you, if either: - you don't have the "original class" at materialization time - you don't want to know if the class was obsolete at serialization time HTH Martin On Tue, Apr 2, 2013 at 7:33 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > On 02/04/13 12:50 AM, roberto.minelli-BHDiRLqP7qo(a)**public.gmane.org<roberto.minelli-BHDiRLqP7qo(a)public.gmane.org>wrote: > >> >> Is there any way to "browse" through such references to understand where >> are they? >> > > From an inspector, choose the "Explore pointers", making sure you've > selected the object that you're trying to understand what is referencing it. > > It takes trial & error, and intuition on which pointers to follow. This > method has often been unsuccessful for me. > > Another approach (my memory is fuzzy), was to put a halt at a suitable > place during the Fuel serialization. Then explore the intermediate > structures used by Fuel, to try to find out why Fuel thinks it needs to > serialize that object. > > Yet another approach is to put a halt in the Fuel materialization, and > explore the intermediate structures used by Fuel. You might even set up a > mapping of the obsolete class to some temporary class, which allows Fuel to > fully materialize the saved objects. You can then explore the Fuel > intermediate structures, as well as the final de-serialized object > structure. > > >

April 5, 2013

Re: [Pharo-project] Pharo Theming: does anyone have some doc?

by Benjamin

On Apr 5, 2013, at 3:02 PM, phil(a)highoctane.be wrote: > Cool. > > Yes, my panes are gray too now. But at the end, I just redefined Color white to return something grayish... Too much things to change in too many places. And the Window color in the settings is absolutely not giving anything else than weird results (I tried with some kind of "Nuclear Green" and it really was "interesting". Yes indeed, that is why we have extracted that into class methods :) > I want to do a theme looking like Adobe Lightroom or the editor that Still uses (around 55:00) > > > Revision 2013 - Concept, Camera, Composition and Color > > > https://www.youtube.com/watch?v=TPaQUZF_KZI&list=PLF0E68A8AD5BB6140&index=13 > > Also, the STHStyler80 class coloring schemes are nice and well, but without an editor, good luck w/ the colors. That's an area where spec would come in handy. About that, I read that some paper would surface explaining spec a bit more. I updated the SVN but didn't saw anything conclusive. Is there something? > Also, I wonder what the relationship is with the color settings in the prefs. > We hadn't tried SH yet (I was presuming this part to be a pain ^^) What you could do is maybe subclass what we are doing we Nico, to have less entry points (but since it's still work in progress :S) Our plan was to push it into the system not too late (like in one month or something) so we can then all iterate over ^^ Ben > > > 2013/4/5 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > With Nicolas Petton we are currently working on a new Pharo theme too, and fixing hardcoded references from Morph along the way :) > We didn't find documentation either, but if you have questions, we will be glad to (try to) answer them :) > > Ben > > PS: I attach a screen of the new theme as it is right now (still a lot to fix), just to give you a glance :) So if you have ideas, feedback â¦ you're welcome :) > > > <NewPharoTheme_alpha.png> > > On Apr 4, 2013, at 3:26 PM, phil(a)highoctane.be wrote: > >> I am digging inside the UITheme and friends and wondered if there was any documentation about it. >> >> Googled already but not much turned up. >> >> I've got some success in the PharoTheme (fill-style) category and now have a decent grasp of how it works (it is strange to find a ton of glamorous-xxx methods in the private category of PharoTheme but well). >> >> I want to do a high contrast/dark theme for my own work as it would be better for accessibility. >> >> I find the Darcula theme pretty neat (http://www.jetbrains.com/idea/) and use it for work. Would be lovely to have some close thing for Pharo. >> >> TIA >> Phil > >

April 5, 2013

Re: [Pharo-project] Big thanks for the organization of the Pharo Conf and MooseDay

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > I am really waiting for the videos to be available to be able to watch > them to get what I missed :) (and spread this to the whole team ^^) +1. Huge thank you to everyone who is contributing to the videos. This is a huge benefit to our global community :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Big-thanks-for-the-organization-of-the-Pharo-Conf-and… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 5, 2013

Jump to page: