- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Mouse handler on a morph

by StÃ©phane Ducasse

Erwan I guess that you should get the mouse position and the window corner and compute the coordinates by yourself. World activeHand position Stef > Hi. > > I would like to know if it's possible to add a mouse handler on a specific morph ? > I have a window and i would like to know the position of my mouse only in this window. > > For exemple i also use : > > self on: #mouseDown send: #captureMouse: to: self. > > But it give me the mouse position in pharo environment and not only in my window. > > > Thanks :) > > -- > Douaille Erwan <douaille.erwan(a)gmail.com>

May 2, 2012

Re: [Pharo-project] Pharo 2.0: Just need a recompileAll or a real problem in background?

by Eliot Miranda

Hi Mariano, On Wed, May 2, 2012 at 1:27 AM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > > > On Tue, May 1, 2012 at 10:17 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Tue, May 1, 2012 at 10:05 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> On 1 May 2012 21:45, Mariano Martinez Peck <marianopeck(a)gmail.com> >>> wrote: >>> > >>> > >>> > On Tue, May 1, 2012 at 9:22 PM, Francisco Garau < >>> francisco.garau(a)gmail.com> >>> > wrote: >>> >> >>> >> Your code snippet is comparing the associations. The below one >>> evaluates >>> >> to true: >>> >> >>> >> (Smalltalk globals associationAt: #ScriptLoader) value >>> >> == >>> >> ((SmalltalkImage >> #shrinkToCore) literalAt: 4) value >>> >> >>> > >>> > Yes, but the literals of CompiledMethod that refer to classes should >>> have >>> > the SAME association as Smalltalk globals. In fact, that's the reason >>> why we >>> > have: >>> > >>> indeed. >>> The question is what leads to creation of multiple associations >>> pointing to same global? >>> >> >> >> Exactly. I can easily fix it with a Compiler recompileAll. But the main >> question is if we have a bug or something that could let us in that state. >> >> > > Ok, I wrote an ugly test and I noticed that the ONLY method with this > problem in the image is > > > | behaviorAssociations broken | > behaviorAssociations := Smalltalk globals associations select: [:each | > each value isBehavior or: [each value isTrait]]. > broken := OrderedCollection new. > (CompiledMethod allInstances select: [:each | each isInstalled]) > do: [:aMethod | aMethod literals > do: [:aLiteral | aLiteral isVariableBinding > ifTrue: [ ((behaviorAssociations > includes: aLiteral) > and: > [(behaviorAssociations identityIncludes: aLiteral) not]) > ifTrue: [broken > add: (aMethod -> aLiteral)] > ] > ] > ]. > broken inspect > This doesn't look for unbound class variables. I just wrote something that handles this in Squeak trunk: methodsWithUnboundGlobals "Get all methods that use undeclared global objects that are not listed in Undeclared. For a clean image the result should be empty." "SystemNavigation new methodsWithUnboundGlobals" ^self allSelect: [:m| m literals anySatisfy: [:l| l isVariableBinding and: [l key isSymbol "avoid class-side methodClass literals" and: [(m methodClass bindingOf: l key) isNil and: [(Undeclared associationAt: l key ifAbsent: []) ~~ l]]]]] so the test would be self assert: SystemNavigation new methodsWithUnboundGlobals isEmpty > And I have 6 methods from the classes SmalltalkImage and ScriptLoader and > all the 6 literals are pointing to ScriptLoader. So something weird > happened with this class. > Any idea? > > For the moment I will update the test and do a Compiler recompileAll. > > > > >> >>> > Association >> #literalEqual: otherLiteral >>> > "Answer true if the receiver and otherLiteral represent the same >>> > literal. >>> > Variable bindings are literally equals only if identical. >>> > This is how variable sharing works, by preserving identity and >>> changing >>> > only the value." >>> > ^self == otherLiteral >>> > >>> > instead of the Object implementation. >>> > >>> > >>> >> >>> >> On 1 May 2012 17:52, Mariano Martinez Peck <marianopeck(a)gmail.com> >>> wrote: >>> >>> >>> >>> (Smalltalk globals associationAt: #ScriptLoader) == ((SmalltalkImage >>> >> >>> >>> #shrinkToCore) literalAt: 4) >>> >>> gives false when it should be true. If I do a Compiler recompileAll >>> it >>> >>> gets fixed. So, my question is, is that normal? how could that >>> happen? >>> >>> is there any real problem behind? >>> >>> >>> >>> anyway, can we do a recompileAll for the moment? >>> >>> >>> >>> thanks! >>> >>> >>> >>> -- >>> >>> Mariano >>> >>> http://marianopeck.wordpress.com >>> >>> >>> >> >>> > >>> > >>> > >>> > -- >>> > Mariano >>> > http://marianopeck.wordpress.com >>> > >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- best, Eliot

May 2, 2012

Re: [Pharo-project] [update 2.0] #20039

by StÃ©phane Ducasse

> Issue 5724: integrate Spotlight in Pharo 2.0 > http://code.google.com/p/pharo/issues/detail?id=5724 Hi guys we should pay attention not to add to much stuff in 2.0. Is there a configuration for Spotlight? I would really like to see if we can have a process where we can always unload Nautilus Shout ECompletionâ¦. and do not have dandling references. Stef

May 2, 2012

Re: [Pharo-project] [update 2.0] #20038

by StÃ©phane Ducasse

On May 2, 2012, at 2:12 PM, Marcus Denker wrote: > Issue 5738: do allow the same ivar in the hierarchy > http://code.google.com/p/pharo/issues/detail?id=5738 Do we really want to let the user define instance variables duplicated in the class hierarchy? I think that this is not really a good move. But I did not browse the issue because I do not have internet. Stef

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by Nicolas Cellier

2012/5/2 Christian Haider <Christian.Haider(a)smalltalked-visuals.com>: >> Von: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project- >> bounces(a)lists.gforge.inria.fr] Im Auftrag von Nicolas Cellier >> >> What are we speaking of exactly ? >> Here are two different features of different level : > > I'll answer for PDF4Smalltalk > >> 1) the composition : >> - 1a) compose a document with a given structure and a style sheet >> Â Â For the structure, think of section / subsection etc... > No (use Report4PDF) >> Â Â For the style sheet, think of LaTeX article, book or report.sty > No >> Â Â For the composition, think of page layout (when to insert page break, >> compose on several columns, wrap text around figures etc...). > No (use Report4PDF) >> Â Â High level composition rules for example might forbid to begin a sub- >> section at the bottom of a page. > No (use Report4PDF) >> - 1b) compose a document from a sequence of lower level graphics (including >> composed paragraph). >> Â Â The composition rule might be very simple, just compose one item over >> the other, insert page break if it does not fit on page. > No (use Report4PDF) >> Â Â For composed text, page break can occur at any composed line or only at a >> carriage return. > No (use Report4PDF) >> Â Â A good example was VisualWorks Document class. >> 2) the fileout of the composition in pdf format >> - 2a) including PDF document structuring conventions (DSC) if ever they exist >> at Smalltalk level. > Fully supported >> - 2b) without DSC, but only low level graphics > Fully supported >> >> Composing the paragraph also means having all the font metrics available >> plus eventually all the kerning rules, plus rules for inter-word spacing (non >> speaking of alignment and tabulation options which should be part of >> paragraph spec). > No, but Type-1 fonts and OpenType(PS) fonts are implemented so that this information is available. >> >> Which PDF library is doing what exactly ? >> Are the low level Graphics >> - entirely PDF library dependent (which would mean no preview via Smalltalk >> graphics), > Yes >> - entirely dialect dependent (using exclusively >> VisualPart/Wrapper/GraphicsContext or Morph/Form/Canvas) > No >> - mixed (transformation of PDF graphics into Smalltalk graphics for preview >> and/or translation of Smalltak graphics to PDF graphics) In the last two cases, >> porting VW <->Squeak/Pharo might not be immediate ;) > No, there is now viewing - just PDF objects > > Think of PDF4Smalltalk as a backend for graphics programs which do layout and such. With TrueType fonts and bitmap graphics, it should be easy to hook it up as GraphicsContext for VW or as Canvas(?) for Squeak/Pharo. > > Christian > OK, thanks, I think it's clearer now for this framework. Here is how I understand it: An intermediate level library could render a VisualWorks Document into a PDF file thru a PDFGraphicsContext. The PDFGraphicsContext would use PDF4Smalltalk. As a Document is low level, there would be no DSC at this intermediate level. Technically, each font specification has to be mapped to a concrete PDF font, and each Paragraph has to be recomposed with these PDF fonts metrics, as it's already the case with the PostscriptGraphicsContext. An upper level library would compose the document from a structure and style sheet specifications, and could eventually produce DSC information thanks to PDF4Smalltalk support. With DSC, the document would be editable in 3rd party PDF editor (PDF writer ...). Report4PDF package already implements some of above features, and use PDF4Smalltalk as backend. >From the blog, it looks a bit like the VisualWorks Document API, but certainly much more capable (can handle tables and all kinds of layouts). It's not yet clear if higher level structures are available. Since Report4PDF is published on Cincom public store, we can dig further... Knowing that the PostscriptGraphicsContext just streams out graphics primitives to the file, without needing any intermediate reification of Postscript objects (except fonts), what was the point of such implementation choice in PDF4Smalltalk? Nicolas >> >> What about composition? >> >> Nicolas >> >> 2012/5/2 Yanni Chiu <yanni(a)rogers.com>: >> > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: >> >> >> >> >> >> Stephan Eggermont wrote >> >>> >> >>> >> >>> Don't you think it would be much less work to port Christian >> >>> Haider's work to Pharo? >> >> >> >> >> >> I was thinking the same thing. The usual Smalltalk duplication of >> >> effort seems to have been taken to new heights with PDF libs ;-) >> > >> > >> > I've loaded Artefact, browsed the code, tried the demos. >> > >> > I've not seen the code for PDF4Smalltalk, because I can't figure out >> > how to browse it without VW. However, looking at the examples at: >> > Â https://gitorious.org/pdf4smalltalk/pages/Examples >> > I get the (possibly mistaken) impression that the two frameworks do >> > slightly different things, but the final result is a PDF in both cases. >> > >> > Looking at the PDFDemos of Artefact, it's clear how text and tables >> > can be written. However, looking at the PDF4Smalltalk examples, it >> > looks like you have to position the text and tables in your own code. >> > Of course, I may be completely wrong about PDF4Smalltalk, since I've >> > not seen the full code base. >> > >> > >> >> > >

May 2, 2012

Re: [Pharo-project] Questionn

by StÃ©phane Ducasse

First class instance variables will bring a lot to the system: foundation for a lot of innovation - relationships support - meta description. - bitfields description ... Now we should really work to get from the prototype to a fully robust and tested version. Stef > Thanks Camilo - I've tried your image with the latest CogVM for Mac and it's usable. > > I understand this is work in progress, are you planning to change Object>>instVarAt: with a new primitive? or will that be handled on the image side? > > Apart from the change in the class declaration, do you think that any of the existing code will have to be changed? > > What's the biggest advantage of having slots? (and will we also have slots for temp vars?) > > Object subclass: #Rectangle > layout: PointerLayout > slots: { > #origin => Slot. > #corner => Slot. > } > classSlots: {} > globals: '' > category: #'Graphics-Primitives' > > Display boundingBox instVarAt: #origin > > > On 1 May 2012 09:51, Camillo Bruni <camillobruni(a)gmail.com> wrote: > and the working protoype (in 1.3 + Helvetia) is avail here: > > http://dl.dropbox.com/u/18184943/SlotImage.zip > > make sure to run the image in an older vm (squeak 5.XX) > > best > cami > > On 2012-04-30, at 22:59, Mariano Martinez Peck wrote: > > > All I can do is to recommend you to read this paper: http://rmod.lille.inria.fr/archives/papers/Verw11a-OOSPLA11-FlexibleObjectL… > > > > > > On Mon, Apr 30, 2012 at 8:36 PM, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > Hi all! I was chating with Guille, who's blaming me for make a refactor in sunit for pharo 1.4 instead of 2.0 and told me 'pharo 2.0 probably adds class layouts and slots'. Well, i'm with a concrete type inference project, i want to know what is made and who is in that part of the project to annoy and bore him with questions, 'cause probably i'll want to type the slots, but i need to understand the metaphor of the slots implementation. I want to understand too whats implication has the class layout over the types. > > > > Santiago. > > > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > >

May 2, 2012

Re: [Pharo-project] What about making the configuration browser more visible?

by StÃ©phane Ducasse

Let me repeat it again (reread the vision document) we will put in place a process that: - check all the configurations of a given repository (for each versions) so for example for MetaRepoForPharo1.4 and MetaRepoForPharo20â¦ - each configuration will be loaded, test runs, rules executed. - we will have inbox for each repository, - if a configuration does not pass, it will move the configurations into an outbox Then people will be able to load configurations that have been loaded and verified. Stef

May 2, 2012

Re: [Pharo-project] Block questions

by StÃ©phane Ducasse

> > > I mean the example is not a useful example because it doesn't show the problem "my" representation solves, which is to make closures independent of their enclosing activations if they outlive their dynamic extent. Yes I'm starting to finish the chapter explanation on explicit return and now I will go in "opening the trunk section" and study for real your implementation because I really want to fully understand it. Stef > > > (define (%apply proc largs) > (cond ((%primitive? proc) (%apply-internal proc largs)) > ((%closure? proc) (%apply-closure proc largs)) > (else (error "Bad ! Un-apply-able object !" proc)))) > > (define (%apply-closure proc largs) > ;; apply a closure: evaluate proc body in > ;; extended the closure environment with > ;; proc arguments and largs > (%eval (%closure-body proc) > (%extend-env (%closure-args proc) largs (%closure-env proc)))) > > (define (%eval-lambda expr env) > ;; lambda in Scheme captures the environment at compile time > ;; expr = ((x) (+ x 2)) > (%make-closure (car expr) (cadr expr) env)) > > > You need to consider how to implement this example: > > > > Object subclass: #AbstractSuperclass > > > > AbstractSuperclass>>computeV > > | v | > > v := 0. > > self maybeCapture: [v := v + 1. v]. > > ^self maybeBlock: v > > > > AbstractSuperclass subclass: #CaptureBlock > > instanceVariableNames: 'block' > > > > CaptureBlock>>maybeCapture: aBlock > > block := aBlock > > > > CaptureBlock>>maybeBlock: value > > ^block > > > > AbstractSubclass subclass: #DontCaptureBlock > > > > DontCaptureBlock>>maybeCapture: aBlock > > > > DontCaptureBlock>>maybeBlock: value > > ^value > > > > > > Then > > | thingOne thingTwo | > > thingOne := CaptureBlock computeV. > > thingTwo := DontCaptureBlock computeV. > > (1 to: 10) collect: [:ignore| { thingOne value. thingTwo value }] > > > > should answer > > #((1 0) (2 0) (3 0) ... (10 0)) > > if 0 value returns 0? yes. (it confused me for a while). > > > right? So where does the l-value for v in computeV live? Iy must be an l-value since it is assigned to in the block in computeV. It must outlive the activation of computeV since CaptureBlock>maybeCapture: captures the block and CaptureBlock>>maybeBlock: answers it and the doit evaluates it. If it lives on the stack of the activation of computeV then there is no problem in a Context VM, but in a VM that maps activations to stack frames something special (and slow) has to happen when returning from computeV. However, if the l-value lives in a separate Array (as it does in my VisualWorks and Squeak closure implementations, and as happens in some Lisp implementations), nothing special has to happen. The block refers to the Array, *not* to the activation of computeV. > > > > Make sense now? > > Yes you allocate on the heap closure binding to be orthogonal to activation context. > > > I will reread your blog now. > > Stef > > > > -- > best, > Eliot >

May 2, 2012

Re: [Pharo-project] Pretty printing on Nautilus

by StÃ©phane Ducasse

Davide could you provide a description and screenshots for the website and success stories. Stef On Apr 30, 2012, at 7:57 AM, Davide Varvello wrote: > Thanks Mariano. > I've zero time now :-) I'm implementing a smalltalk web app for the Italian > market, if you can understand a little bit of Italian you can see a demo > video here: http://bit.ly/JVeWYe > Davide > > -- > View this message in context: http://forum.world.st/Pretty-printing-on-Nautilus-tp4596333p4597485.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 2, 2012

Re: [Pharo-project] Pretty printing on Nautilus

by StÃ©phane Ducasse

Why not using or enhancing the pretty printing of RB? Because lukas invested a lot of time into it. Stef On Apr 29, 2012, at 10:28 PM, Benjamin wrote: > I will implement a pretty print. > But the thing is since I am not the god of pretty print, I definitely want a mechanism to let every user to specify it's own way to pretty print. > Without that, it's useless for me :) > > Ben > > On Apr 29, 2012, at 2:59 PM, Davide Varvello wrote: > >> Hi, >> Today I have a lot of "cosmetic" questions :-) >> How can I enable pretty printing on Nautilus? Moreover, the old cmd-r does >> not work anymore, right? >> Thanks >> Davide >> >> -- >> View this message in context: http://forum.world.st/Pretty-printing-on-Nautilus-tp4596333p4596333.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

May 2, 2012