December 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] pharo headless on windows, one problem and one question
by Esteban Lorenzano Dec. 23, 2009

Dec. 23, 2009

Hi, I'm trying to run an application on windows (aggggg), which is a seaside application, but I'm running it as a "desktop application", using xulrunner. This is a migration from an application who was already running, but on squeak (i'm slowly migrating all my squeak applications to pharo, he). I have an "Application executer class", called CDIRunner, who understands #startUp: method. This method is properly registered by doing Smalltalk addToStartupList: CDIRunner. This is the problem: if I run @start Pharo.exe -headless the #startUp: method is not executed! (if I run Pharo in usual way, the method is executed normally). And the question: I would like to hide the pharo try icon... is this possible without recompile the vm? Thanks, Esteban

2 2

[Pharo-project] Fwd: about allCallOn -> AllReferTo : issue 261
by StÃ©phane Ducasse Dec. 23, 2009

Dec. 23, 2009

> > Alex > > I integrated your changes but apparently some tests are broken. > Can you have a look? > > Tx > > Stef > > >

2 3

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser
by Frederic Pluquet Dec. 23, 2009

Dec. 23, 2009

Cool :) It is added in the last version. Thank you for your participation at NewInspector ! I think the best way to preview a form is to show it in the right side of the NewInspector in place of the description panel, but it is a really big challenge: NewInspector is unaware about the composants of the frame (everything is done by model). I must found a way to achieve this :) FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet On Mon, Dec 21, 2009 at 4:57 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi Frederic. Henrik Sperre Johansen created this method: > > Form >> asNINode > ^ (super asNINode) > addAction: > (NIAction labeled: 'Preview' > shortcut: $p > target: > [ :aForm | > | anOffset aFrame | > anOffset := aForm width @ aForm height / -2. > aFrame := LayoutFrame fractions: (0.5 @ 0.5 > corner: 0.5 @ 0.5) offsets: (anOffset corner: anOffset). > (SystemWindow labelled: 'Form preview') > addMorph: (ImageMorph new image: aForm) > fullFrame: aFrame; > openInWorldExtent: (aForm extent max: 267 @ > 0) ] > actionSelector: #value: > withArgs: {self} > category: 'Preview'); > yourself > > > > It let you see the image of something. Example, inspect a form ( ThemeIcons > infoIcon ), right-click the Form > node, and select preview. > > In addition, he told me this: > > "For inclusion in the NewInspector package on SqueakSource, I would at > least change the magic number 267 first, to one computed based on the width > of the Window label, 267 is merely what is needed to display it fully with > the standard window font in PharoDev :) > Feel free to do so, and ask Frederique Pluquet to to include it there." > > So....can you take care of this and include it ? would be very useful!!! > > Thank you very much. > > Mariano > > > ---------- Forwarded message ---------- > From: Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> > Date: Thu, Dec 17, 2009 at 10:12 PM > Subject: Re: [Pharo-project] [ANN] MagmaBrowser > To: pharo-project(a)lists.gforge.inria.fr > > > On 16.12.2009 11:29, Mariano Martinez Peck wrote: > > This is an excellent job. Congratulations HernÃ¡n. > > > > I have a question....how could you draw the photo instead of the array > > of bytes on the browser? I really hate when developing with seaside > > and I have some pictures in my filelibrary class and when I browse > > them I see the array of bits...but I want to see the picture!!! > > > > Thanks > > > > Mariano > For a proof of concept of what is possible using the NewInspector, > install this method: > Form>>asNINode > ^ (super asNINode) > addAction: > (NIAction labeled: 'Preview' > shortcut: $p > target: > [ :aForm | > aForm depth < 32 ifTrue: [ Display > getCanvas image: aForm at: 10 @ 10 ] > ifFalse: [ Display getCanvas > translucentImage: aForm at: 10 @ 10 ] ] > actionSelector: #value: > withArgs: {self} > category: 'Preview'); > yourself > > then inspect a form (Say, ThemeIcons infoIcons ), right-click the Form > node, and select preview. > > Ideally it'd be nice to add an extra "Preview" item to the subnodes of > Forms in the NI, which when clicked would show the form on the right > side, but I don't (easily) see how you can temporarily replace the > TextMorph on the right side with something capable of displaying Forms > > With some more work on the closure it should be possible to open the > preview in a separate window though :) > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

5 12

[Pharo-project] Call for companies using pharo to get a payed INRIA engineer
by StÃ©phane Ducasse Dec. 23, 2009

Dec. 23, 2009

Hi guys we are writing a proposal to get an engineer for pharo from INRIA (nothing is clear but we should at least try). I learned this morning that we could apply. Some meetings are better than others :) So I have a small list but I'm sure that we have much more companies around using pharo. Stef

6 11

[Pharo-project] Issue 1658: EncoderForV3PlusClosures(EncoderForV3)>>genPushLiteral: doesNotUnderstand: #<
by Stan Shepherd Dec. 22, 2009

Dec. 22, 2009

1.Ran full test suite (7266 run, 7223 passes, 21 expected failures, 9 failures, 13 errors, 0 unexpected passes) 2.store result as progress measurement 3.EncoderForV3PlusClosures throws above error. walkback attached to issue. -- View this message in context: http://n2.nabble.com/Issue-1658-EncoderForV3PlusClosures-EncoderForV3-genPu… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] Issue 1657: Large test suites caused slow OB menu, fix attached.
by StÃ©phane Ducasse Dec. 22, 2009

Dec. 22, 2009

Issue 1657: Large test suites caused slow OB menu, fix attached. from aKuhn Thanks adrian.

1 0

[Pharo-project] ImageSegment vs SmartRefStream
by Mariano Martinez Peck Dec. 22, 2009

Dec. 22, 2009

Hi folks. I have been analyzing the code and trying to understand what ImageSegment does and how. After that, I came up to SmartRefStream and here is where I have some questions: 1) which is the difference between ImageSegment and SmartRefStream ? what does each of them do ? 2) Who uses who ? ImageSegment uses SmartRefStream or vice-versa? each one use the other? Thank you for any hints you can give me. Mariano

3 3

[Pharo-project] ISSUE #1647: TheTrunk-KernelTests-bs.121
by Alexandre Bergel Dec. 22, 2009

Dec. 22, 2009

Pharo image: Pharo-core Pharo core version: 11110 Virtual machine used: Squeak 4.2.1beta1U This email takes the fixes sent in the email having the subjet: - [squeak-dev] The Trunk: KernelTests-bs.121.mcz - [squeak-dev] The Trunk: Kernel-bs.330.mcz After loading the .cs, we have for MethodPropertiesTest: 11 run, 5 passes, 5 expected failures, 0 failures, 1 errors, 0 unexpected passes The error left is for testAnalogousCode, not related to this fix. Thanks to Andreas Raab for the fix. Note to the reviewer: I put a .cs file on google code. Is that okay with you? Or do you prefer a SLICE in the Inbox? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

Dec. 22, 2009

this is interesting. I had on my todo to look at the old implementation of andreas since years. Adrian it would be really interesting to check because having a smaller/with less impact traits implementation would be cool. Stef > > My experiments with a simpler traits implementation are starting to bear results. Attached a version of NanoTraits which is the smallest implementation of traits that I could come up with. Making it loadable inside a current trunk image has been a bit of a challenge since it needs to operate side-by-side with the existing traits during load (apologies for the various isKindOf:'s), but it seems to work fairly well now (fingers crossed). There are few differences to the Berne trait implementation including: > > - TraitDescription is a subclass of ClassDescription. This is the main simplification since it avoids creating a dual trait/class hierarchy. It comes at the "cost" of having potentially support for instance variables in traits (i.e., stateful traits) but since this isn't exposed there is very little actual overhead. > > - NanoClassTrait is the class of NanoTrait (i.e., the same meta structure that classes have). Since this models exactly the structure that classes have, it makes browser integration significantly simpler (NanoTraits would work fine in 3.8 for example without changing browsers etc) and allows us to remove the (now unecessary) additional tool support. > > - Methods used from other traits retain a "method home" reference so that for any method in a class you can tell whether it was defined locally or in some other trait. This makes several things *a lot* easier and will allow us to get rid of all the localSelectors stuff in ClassDescription in the next pass (Igor - this gives you the information where a method is from without poking in other places; just ask i.e., (ClassDescription>>#addSelectorSilently:withMethod:) methodHome ==> TAccessingMethodDictDescription) > > - Some previously invalid trait composition are now valid, in particular T - {#x} - {#y} (meaning T- {#x. #y}) as well as T @ {#x->#y} @ (#a -> #b} (meaning T @ { #x -> #y. #a -> #b}. > > - You can't mix Berne and Nano traits. If you try it, things will blow up (incompatible internals). > > - You can't mix Berne and Nano traits tests. I don't know why but if you run them at the same time things go wrong. > > To install NanoTraits: > * Load NanoTraits-Kernel.st > * Load NanoTraits-Tests.st > * Load NanoTraits-Extensions.cs > * Run the NanoTraits-Tests > * (assuming all tests are green) execute: NanoTraits install. > > This will make NanoTraits the default traits implementation and convert any existing traits. I've successfully played with Nile (the only other traits stuff I was aware about besides the class kernel which is a bit difficult to experiment with) but from what I can tell everything should work just fine. > > The one extra thing I'm seriously considering after our recent discussions is to change NanoTraits to actually use mixins to implement traits composition. What this would mean is that instead of adding trait methods to a class directly, they would be added to a (hidden) superclass. Composition rules would be unaffected by this change but it would solve the issue of trait methods messing up the methods *actually* defined in a class, showing a seven times when looking for implementors and more. > > Consider this my holiday gift to the community :-) > > Cheers, > - Andreas > > >

1 0

[Pharo-project] [update 1.1] #11111
by Marcus Denker Dec. 22, 2009

Dec. 22, 2009

11111 ----- Issue 1646: SLICE-PreferencesReferencesRemovalPart2 * remove all remaining Preferences references * also fix a DiffMorph bug introduced by previous SLICE-PreferencesReferencesRemovalPart1 (send of #setting instead of #settings) Thanks, Alain! Issue 1649: Workspace cannot print object whose class does not inherit from Behavior Thanks to Adrian Kuhn

2 2