- Pharo-dev - lists.pharo.org

Re: [Pharo-project] RBNodes accept vs. visit

by Lukas Renggli

Legacy, and because it really doesn't matter of how you name your double-dispatch methods as long as you do it consistently within your realm. Lukas On 23 August 2011 15:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Indeed, this is really confusing :). I am not aware of any particular reason. > > Doru > > > On 23 Aug 2011, at 15:33, Camillo Bruni wrote: > >> Hi everyone, >> >> I just had a quick look at the RBNodes. Is there a particular reason why the visitor pattern methods are prefixed on both sides with 'accept'? >> >> eg. >> >> RBArrayNode >> acceptVisitor: aProgramNodeVisitor >> Â Â Â ^ aProgramNodeVisitor acceptArrayNode: self >> >> camillo > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 23, 2011

Re: [Pharo-project] RBNodes accept vs. visit

by Tudor Girba

Indeed, this is really confusing :). I am not aware of any particular reason. Doru On 23 Aug 2011, at 15:33, Camillo Bruni wrote: > Hi everyone, > > I just had a quick look at the RBNodes. Is there a particular reason why the visitor pattern methods are prefixed on both sides with 'accept'? > > eg. > > RBArrayNode >> acceptVisitor: aProgramNodeVisitor > ^ aProgramNodeVisitor acceptArrayNode: self > > camillo -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

Aug. 23, 2011

[Pharo-project] RBNodes accept vs. visit

by Camillo Bruni

Hi everyone, I just had a quick look at the RBNodes. Is there a particular reason why the visitor pattern methods are prefixed on both sides with 'accept'? eg. RBArrayNode >> acceptVisitor: aProgramNodeVisitor ^ aProgramNodeVisitor acceptArrayNode: self camillo

Aug. 23, 2011

[Pharo-project] [update 1.3] #13300

by Marcus Denker

13300 ----- Issue 4430: When copying a class, do not copy the methods it obtains from Traits http://code.google.com/p/pharo/issues/detail?id=4430 Issue 4642: FinderUI>>compileSource: aString notifying: aController http://code.google.com/p/pharo/issues/detail?id=4642 -- Marcus Denker -- http://marcusdenker.de

Aug. 23, 2011

[Pharo-project] 3 years postdoc position on dynamic language and security

by StÃ©phane Ducasse

We have a 3 year postdoc position on dynamic languages and security: http://rmod.lille.inria.fr/web/pier/blog/2011-08-19-2 Do not hesitate to apply Postdoc Position â¢ Duration: 3 years â¢ Starting date: end 2011 â¢ Where: RMOD team at INRIA Lille Nord Europe http://rmod.lille.inria.fr â¢ Salary: 55 Keuros net (before taxes) Keywords: dynamic languages, security, information flow, Smalltalk, Javascript The position will take place in the context of the Systematic Resilience project. We will focus on the following main tasks: â¢ Identification and understanding of security problems in Javascript and other dynamic languages â¢ Study and analyze existing approaches towards securing Javascript (Caja, isolates...) â¢ Comparison of different approaches to secure dynamic applications (Zope model, ZTK), Ruby â¢ Study of Mirrors/Capabilities as a basis for security in Javascript â¢ Proposition of an safe architecture for Resilience Please contact Stephane Ducasse (Stephane.Ducasse(a)inria.fr) for more information. Stef ------------------------ Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) INRIA - USTL - CNRS UMR 8022 stephane.ducasse(a)inria.fr http://stephane.ducasse.free.fr http://rmod.lille.inria.fr/ **NEW ***Tel 00 33 (0)3 20 43 42 56 - Fax 33 3 59 57 78 50 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.

Aug. 23, 2011

[Pharo-project] [update 1.4] #14109

by Marcus Denker

14109 ----- Issue 4678: AbstractTool modified again :) http://code.google.com/p/pharo/issues/detail?id=4678 Issue 4430: When copying a class, do not copy the methods it obtains from Traits http://code.google.com/p/pharo/issues/detail?id=4430 -- Marcus Denker -- http://marcusdenker.de

Aug. 23, 2011

Re: [Pharo-project] expanding text morph

by Tudor Girba

Thanks, Gary! And now the next question: If I place this one in a surrounding pane / expander / tab, how do I get the surrounding morph to resize when the text changes? Cheers, Doru On 22 Aug 2011, at 12:15, Gary Chambers wrote: > Hi Doru > > > |textMorph| > textMorph := UITheme builder newText: ''. > textMorph > hResizing: #spaceFill; > borderWidth: 1. > (UITheme builder newColumn: {textMorph}) openInWindow. > textMorph contentsWrapped: 'Some text here > > Get a halo and inspect the text morph > then use #contentsWrapped: to change text > > > and see the results! > > #rigid hResizing also works.' > > > > Have fun! > > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor(a)tudorgirba.com> > To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> > Sent: Sunday, August 21, 2011 11:57 PM > Subject: [Pharo-project] expanding text morph > > > Hi, > > I would like to create a Text Morph that wraps the text horizontally, and expands the height to fit the text. Thus, this morph would never offer scrolling. > > How could I do that? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > > > -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Aug. 23, 2011

Re: [Pharo-project] Some bugs

by Michael Roberts

I think for the debugger, we all live with the bugs. I mean, we (I) unfortunately made the situation worse with the introduction of the closures around 1.0/1.1 and it has never been fixed. It is hard to fix too, this stuff is not simple. I contacted a few people quietly maybe a year ago to see if we all lived with it, because a few times i posted about the debugger and there was not a lot of response. I wondered if no one *actually* programmed in pharo. but no, we become masters of interpreting the debugger highlight... What can we do- 1) I have contacted Eliot (again). Historically he said it was fixed (or better) in teleplace images but I need him to send us any patches. He has also been helpful and highlighted the areas that need work like the decompiler and how we could write some tests to protect against unintended change 2) I have checked a recent Squeak, and it is bust there too. 3) I am writing some test cases. So that we can regression test the debugger highlighting, and building an analyser class (@esug) to make it easier to dig into the debugger. 4) carefully check Squeak class versions for merging changes into Pharo. this is not easy. 5) We have to rebuild the debugger model based on the new compiler / decompiler machinery. (This is a long term Pharo goal) I am just chipping away at the analysis, and i will share my code when i have something on the tracker. Also would be great in a separate thread if someone could explain to me the simulation guard primitive. i.e you can not step over process creation, but you can halt after it e.g. cheers, Mike

Aug. 23, 2011

[Pharo-project] Pharo mentioned in InfoQ article

by Carlo

Good to see Pharo and some of the related projects (PetitParser, tODE) mentioned in an article written by Werner Schuster on InfoQ. Take a look at http://www.infoq.com/news/2011/08/smalltalk-in-browser I'd like to thank everyone for all their hard work in making Pharo a better platform. On a rather random side note I see a contracting job to make a video game using squeak/smalltalk on the elance website. Might be of interest to someone See http://www.elance.com/j/video-game-developer/25782784/ Description: We are looking to build a video game for our clothing company. We prefer to build this on Java, Squeak, Smalltalk or Python however we are open for any suggestions. Cheers Carlo

Aug. 23, 2011

Re: [Pharo-project] Some bugs

by Adrian Lienhard

Yes, the issues Andrea reported are all from 1.2.2. That's the version we are currently using besides 1.1.2. Unfortunately, its not an option for us to move to new versions of Pharo too frequently. New Pharo versions can have unforeseen effects in production and hence can cause a lot of work for us and pain for our users (just an example is the semantic change of String>>asNumber). On the other hand, we are working 8 hours a day with Pharo and hence a good IDE is very important. If things like the debugger do not reliably work, this is not fun. Are other people just living with the issues? Are there any patches that could be backported? Cheers, Adrian On Aug 23, 2011, at 10:54 , Alexandre Bergel wrote: > These issues are for 1.2.2. Who is maintaining it by the way? > > Pharo 1.4 presents a significant number of improvements over Pharo 1.3. Whereas I found Pharo 1.3 almost unusable, I am quite happy with 1.4 > > Cheers, > Alexandre > > > On 23 Aug 2011, at 08:54, Andrea BrÃ¼hlmann wrote: > >> Hello, >> >> I reported some bugs on the issue tracker and hope you can help me with them! >> >> >> 4681: Accepting with the enter key does not work >> http://code.google.com/p/pharo/issues/detail?id=4681 >> >> 4682: Code completion makes strange cursor placements and too many spaces >> http://code.google.com/p/pharo/issues/detail?id=4682 >> >> 4683: Code completion breaks some search fields (errors during typing) >> http://code.google.com/p/pharo/issues/detail?id=4683 >> >> 4684: Missing ctrl+w (methodNamesContainingIt:) >> http://code.google.com/p/pharo/issues/detail?id=4684 >> >> 4685: Merge dialog: cannot resolve conflict with removed method >> http://code.google.com/p/pharo/issues/detail?id=4685 >> >> 4686: Method category change creates no new version >> http://code.google.com/p/pharo/issues/detail?id=4686 >> >> 4687: Errors during coding (MessageNotUnderstood: receiver of "morph" is nil) >> http://code.google.com/p/pharo/issues/detail?id=4687 >> >> 4688: Progress bar disappears on image save >> http://code.google.com/p/pharo/issues/detail?id=4688 >> >> 4689: MessageTally bug >> http://code.google.com/p/pharo/issues/detail?id=4689 >> >> 4690: Progress bar position >> http://code.google.com/p/pharo/issues/detail?id=4690 >> >> 4691: Bad line breaks in code until window is resized (because of bold text?) >> http://code.google.com/p/pharo/issues/detail?id=4691 >> >> 4692: Drop downs should select the default entry (topmost) instead of a middle one >> http://code.google.com/p/pharo/issues/detail?id=4692 >> >> 4693: Line breaks in tooltips are wrong >> http://code.google.com/p/pharo/issues/detail?id=4693 >> >> 4694: Debugger: stepping over an error can not open a new debugger until I hit cmd+. >> http://code.google.com/p/pharo/issues/detail?id=4694 >> >> 4695: Time asString prints nanos unrounded >> http://code.google.com/p/pharo/issues/detail?id=4695 >> >> >> -- >> Andrea BrÃ¼hlmann >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Aug. 23, 2011