March 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Morphic operation in startUp sequence

by Hilaire Fernandes

I tried, it did not help. Hilaire Le 19/03/2012 02:07, Ricardo Moran a Ã©crit : > Hi, > > I'm just guessing here but have you tried wrapping your operation in a > deffered UI message? > > Something like the following: > > WorldState addDeferredUIMessage: ["Your stuff here"]. > > > Cheers, > Richo > > On Sun, Mar 18, 2012 at 5:19 AM, Hilaire Fernandes > <hilaire.fernandes(a)edu.ge.ch > <mailto:hilaire.fernandes@edu.ge.ch>> wrote: > > Hello, > > What is the proper way to do morphic operation when an image is loaded. > I am not sure it is safe to do in the startUp sequence. > > Thanks > > Hilaire > > > -- > Dr. Geo -- http://www.drgeo.eu > > > -- Dr. Geo -- http://www.drgeo.eu

March 19, 2012

Re: [Pharo-project] Any theme or settings that will speed up a Pharo 1.3 image?

by Stefan Marr

Hi: On 19 Mar 2012, at 18:08, Eliot Miranda wrote: > I noticed some absurd preference checking in standard images a while back, but turning this off made no noticeable different in optimized Cog. Look for uses of Preferences subPixelRenderFonts, e.g. installStrikeFont:foregroundColor:backgroundColor:. There's a non-local return in the default path on preference access. So not having subPixelRenderFonts a defined preference method creates lots on noise when doing VM debugging. In the Pharo 1.3 image, that does not look like a problem. #subPixelRenderFonts is only defined in StrikeFont class and does a quick ^ true. One thing I noticed is that the amount of open windows has a hugh impact on the speed. Camillo, profiling only told me that the RoarVM apparently does not support it ;) The same experiment on Cog didn't show anything interesting either. At least nothing obvious. You used your own images for Pinocchio, or was Pinocchio just fast enough for the standard images? Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

March 19, 2012

Re: [Pharo-project] Any theme or settings that will speed up a Pharo 1.3 image?

by Marcus Denker

On Mar 19, 2012, at 6:09 PM, Eliot Miranda wrote: > > > On Sun, Mar 18, 2012 at 4:57 AM, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > When trying to debug a Pharo image with a VM that is heavily instrumented with assertions and runs without any compiler optimizations turned on, it is crawlingly slow. > (The good old MVC based image is blazingly fast in comparison) > > Are there any tricks to reduce/disable all the possibly fancy things like transparency, code completion, syntax highlighting easily? > > I already disable the code completion, and syntax highlighting. > I also switched off things like animations, rounded corners, and switched to the Standard Squeak theme. > > Still, non of these cosmetic changes gave me the noticeable performance gain I had hoped for. > > Is there anything else I could try to reduce the amount of work the image is doing? > It blinks the cursor in a text field in the speed I would expect. > But as soon as I start typing, or try to interact with a window, it feels like I can go for a walk before the image is done. > > I noticed some absurd preference checking in standard images a while back, but turning this off made no noticeable different in optimized Cog. Look for uses of Preferences subPixelRenderFonts, e.g. installStrikeFont:foregroundColor:backgroundColor:. There's a non-local return in the default path on preference access. So not having subPixelRenderFonts a defined preference method creates lots on noise when doing VM debugging. > in Pharo Preferences are not anymore... #subPixelRenderFonts is send to StrikeFont and just returns true (the default of the Preference). I think the idea was to add a Setting later if someone requests it... and nobody ever did. So maybe we can simplify that method a bit. Marcus -- Marcus Denker -- http://marcusdenker.de

March 19, 2012

[Pharo-project] Small polymorph suggestion

by Schwab,Wilhelm K

Gary, I haven't figured out what they do yet, but I found #newSeparator, which creates a horizontal widget (name does not reflect this). Then I dug around and found #newVerticalSeparator. I suggest #newSeparatorHorizontal and #newSeparatorVertical, putting them together in the method list for easier discovery. Bill

March 19, 2012

Re: [Pharo-project] non-interactive compiling with feedback

by Milan Mimica

What does it do this code? a := 1. (undeclared 'a') On 19 March 2012 07:13, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>wrote: > If you have Grease loaded: > > Gofer new > squeaksource: 'CodeGenerator'; > package: 'CodeGenerator'; > load. > > [CGSmalltalk new > setSourceAsCode; > targetClass: Object; > compile: 'testMethod > ^ 42. ^ 32' ] > on: SyntaxErrorNotification " or Notification " > do: [: ex | ^ ex errorMessage ] > > > 2012/3/17 Milan Mimica <milan.mimica(a)gmail.com> > >> Hello, >> >> i want to add some scripting capabilities to my app, and I wand to use >> plain smalltalk for that. The only problem is that I still haven't found a >> way to generate a compiled which would return a string describing a problem >> in case a syntax errors. Can I get some help? >> >> >> -- >> Milan Mimica >> > > > > -- > HernÃ¡n Morales > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. > > -- Milan Mimica http://sparklet.sf.net

March 19, 2012

Re: [Pharo-project] non-interactive compiling with feedback

by Milan Mimica

On 18 March 2012 23:20, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hmm, you can compile a method with Behavior>>#compile:notifying: > > and send an observer implementing: > > #notify:at:in: > > and some other stuff like #selection #deselect... > > That way you can capture the errors... > This almost works. It doesn't raise errors for undeclared variables, instead it prompts for variable replacement. | method requestor | requestor := Mock new. (requestor stub: #selectionInterval) returns: (1 to: 2). requestor stub: #selectFrom:to:. (requestor stub: #bindingOf:) returns: nil. (requestor stub: #notify:at:in:) will: [ self halt ]. method := Compiler new compiledMethodFor: 'a:=1' in: nil to: nil notifying: requestor proxy ifFail: nil logged: false. method inspect I would like to catch the error. It is an error, right? -- Milan Mimica

March 19, 2012

[Pharo-project] Pharo Consortium Important Documents and Request for Feedback

by StÃ©phane Ducasse

Dear Pharo Friends and Supporters We worked a lot with INRIA lawyers and tried a lot of different scenarios. We arrived to a setup that make sense now we would like to get your input. Please have a look at the following powerpoint presentation and feel free to comment! We provide some sketches for the consortium fees and benefits for you. But we need your input! If you are not in the mailing-list: send us a mail to board(a)pharo-project.org. Remember that what we want to achieve is to be able to pay one (or more) full time engineer to help us improving our system and making that our future is bright. Since it may be difficult to follow closely our vision, dreams and current development efforts you can read the Pharo vision document. https://gforge.inria.fr/frs/download.php/30436/PHARO-ENG-V4.2.pdf https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf The Pharo Team Remember: The best way to predict the future is to invent it. A. Kay And we want to do it :)

March 19, 2012

Re: [Pharo-project] Extending SystemBrowser

by Ezequiel Lamonica

Thanks Stef. I didn't see it yet but I'll start to try nautilus in few weeks. It looks very nice. On 19 March 2012 14:29, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Did you try nautilus? > Because it is cool and it will get cooler. It will be the basic default > browser > and other people will be able to define new tools. > > > Stef > > > > Le 15/03/2012 22:46, StÃ©phane Ducasse a Ã©crit : > >> Use Glamour or Spec or OB but not systemBrowser. > >> Run away from SystemBrowser > >> > > > > What is the target window for the Pharo Browser? Are there any > > aggregating energy to get out a modern incarnation of a system browser > > for Pharo. Just wondering. > > > > Hilaire > > > > -- > > Dr. Geo -- http://www.drgeo.eu > > > > > > >

March 19, 2012

Re: [Pharo-project] Extending SystemBrowser

by StÃ©phane Ducasse

Did you try nautilus? Because it is cool and it will get cooler. It will be the basic default browser and other people will be able to define new tools. Stef > Le 15/03/2012 22:46, StÃ©phane Ducasse a Ã©crit : >> Use Glamour or Spec or OB but not systemBrowser. >> Run away from SystemBrowser >> > > What is the target window for the Pharo Browser? Are there any > aggregating energy to get out a modern incarnation of a system browser > for Pharo. Just wondering. > > Hilaire > > -- > Dr. Geo -- http://www.drgeo.eu > >

March 19, 2012

Re: [Pharo-project] Trying to make KomHttpServer load in 1.4

by StÃ©phane Ducasse

I fixed that too :) On Mar 17, 2012, at 6:00 PM, StÃ©phane Ducasse wrote: > Hi guys > > I saw that TranscriptStream is deprecated in 1.3 and I was looking at the logic of the Logger. > > I do not understand the use of isTranscriptStream especially since it is defined only on Stream ^ false > and the EmergencyEvaluator which is particularly not respecting the stream protocol. > > Any suggestion? > > Stef

March 19, 2012