- Pharo-dev - lists.pharo.org

[update 3.0] #30180
by Marcus Denker June 5, 2013

June 5, 2013

30180 ----- 10844 Calling deprecated method triggerEvent:with:ifNotHandled: twice when running regressionTests https://pharo.fogbugz.com/f/cases/10844 10786 Semantic analysis not working for instance variables https://pharo.fogbugz.com/f/cases/10786 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.549.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/SmartSuggestions-MarcusDenker…

1 0

Release Artefact 1.0, the PDF framework
by Guillaume Larcheveque June 5, 2013

June 5, 2013

We are proud to announce that Artefact is available in 1.0 version. You can download it from: http://smalltalkhub.com/#!/~RMoD/Artefact Artefact is a framework to generate PDF documents. It is fully written in Smalltalk and doesn't require any native library. Artefact is light, platform independant and offer to users a high level of abstraction in order to easily creating PDF documents. * completely written in Smalltalk (and only Smalltalk), * complete freedom about the order of creation for pages, elements... (no need to follow the document order) * multi format and orientation for pages * page composition based on reusables PDF elements, * extensibility by offering a composition standard to create your own high level elements * styleSheet that can be reused in many documents and avoid wasting time and place with duplication * image support with the JPEG format * pre-defined high level elements like datagrid * support PDF compression to produce compact files A basic documentation is available in the help browser. Many examples are implemented in the PDFDemos class. -- *Olivier Auverlot and Guillaume Larcheveque*

9 13

Amber's new stepping debugger
by Nicolas Petton June 4, 2013

June 4, 2013

Hi guys! Today I was able to debug Amber code with a stepping debugger for the first time! The debugger is based on an AST interpreter with a small stack implementation. Here's a short video of the debugger in action: https://www.dropbox.com/s/43mli1wwbdwj5kx/amber-debugging.mov While it's an early version, it is already usable :) cheers, nico

7 7

ImageMorph initialize
by StÃ©phane Ducasse June 4, 2013

June 4, 2013

initialize "ImageMorph initialize" | h p d | DefaultForm := (Form extent: 80@40 depth: 16). h := DefaultForm height // 2. 0 to: h - 1 do: [:i | p := (i * 2)@i. d := i asFloat / h asFloat. DefaultForm fill: (p corner: DefaultForm extent - p) fillColor: (Color r: d g: 0.5 b: 1.0 - d)]. I wonder why I get a transparent morph DefaultForm asMorph openInWorld Stef

1 0

Scrolling without clicking in lists
by Sven Van Caekenberghe June 4, 2013

June 4, 2013

Hi, In 2.0 you can scroll (using a scroll wheel or the track pad 2-finger swipe) in any list (of a browser for example) just by moving the mouse pointer over it, _without_ clicking in it, thus _without_ moving the focus. In 3.0 this seems to be broken: no matter where you are with the mouse pointer, you scroll the view with focus. As far as I can tell, this is not how it should be, and it brakes my workflow ;-) Sven

4 4

Issue with ZnMimeType>>#=
by Andy Kellens June 4, 2013

June 4, 2013

Hi, Yesterday, I stumbled across a bug when using the Zinc Seaside adaptor that resulted in that the post fields of a request were not present in the WARequest. I found out that the problem occurred when converting a Zinc request into a WARequest. More particular: ZnZincServerAdaptor>>requestFieldsFor: aZincRequest | fields | fields := WARequestFields new. (aZincRequest method = #POST and: [ aZincRequest hasEntity ]) ifTrue: [ aZincRequest entity contentType = ZnMimeType applicationFormUrlEncoded ifTrue: [ fields addAll: aZincRequest entity fields ]. aZincRequest entity contentType = ZnMimeType multiPartFormData ifTrue: [ fields addAll: (self convertMultipart: aZincRequest entity) ] ]. ^ fields This method checks if the Mime Type is either applicationFormUrlEncoded or multiPartFormData in order to extract the post fields. Recently, ZnMimeType>>= got changed from: ZnMimeType>>= other ^ (self class == other class) and: [ self main = other main and: [ self sub = other sub ] ] to: ZnMimeType>>= other ^ (self class == other class) and: [ self main = other main and: [ self sub = other sub and: [ self hasParameters not & other hasParameters not or: [ self parameters = other parameters ] ] ] ] As my request had an additional parameter charset=utf-8, the equality with ZnMimeType applicationFormUrlEncoded failed and hence the fields were not extract. While I assume that the comparison of the Mime type parameters in #= is there for a good reason, and the best way to fix this problem is to change the #requestFieldsFor: method in order to match the Mime type differently, I wanted to briefly check with the mailing list before opening an issue + submitting a patch. Kind regards, Andy

2 11

Rubric: playing with selection
by plantec June 4, 2013

June 4, 2013

Hi all, I've tried to manage the selection as a Morph. I was curious to see if it was enough efficient. and yes it is :) http://vimeo.com/67516363 Cheers Alain

4 3

Trait exclusions
by Frank Shearar June 4, 2013

June 4, 2013

I have a Trait TGroup that requires #*, #identity and #inverse. I want to construct a TField by composing TGroup with itself. One TGroup will form the operations #*, #one, and #reciprocal while the other will form #+, #zero and #negated. I don't want #identity or #inverse, because these apply to one operation, and it makes TField's API ambiguous. That's what TraitExclusion is for. I had thought I could say (TGroup @ {#identity->#zero. #* -> #+. #inverse->#negated} + TGroup @ {#identity->#one. #inverse->#reciprocal}) - {#identity. #inverse} but TraitComposition >> #- says that exclusion binds tighter than +. So in effect the above composition is the same as TGroup @ {#identity->#zero. #* -> #+. #inverse->#negated} + (TGroup @ {#identity->#one. #inverse->#reciprocal} - {#identity. #inverse}) In short, to remove the undesirable #identity and #inverse I have to exclude from both sides of the composition: TGroup @ {#identity->#zero. #* -> #+. #inverse->#negated} - {#identity. #inverse} + TGroup @ {#identity->#one. #inverse->#reciprocal} - {#identity. #inverse} My question is this: what is the reason for - binding more tightly than +? Why is it _not_ desirable to have - distribute over +? frank

5 10

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 4, 2013

June 4, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 1 regressions found. FileSystem.Tests.Disk.FileHandleTest.testTruncate

1 0

MetacelloRepository
by Hilaire Fernandes June 4, 2013

June 4, 2013

Hello, To build DrGeo I use the squeaksource MetacelloRepository (example bellow). I can not find it in SmalltalkHub? I can see in PahroExtra/XMLParser ConfigurationOfXMLParser, is it the same as ConfigurationOfXMLSupport. Can I find equivalent of ConfigurationOfXMLSupport matching the exact same XML source version? Unhelpful, I did not find how to browse the source form Smalltalkhub to explore online the ConfigurationOf... code. Thanks Hilaire baseline1012: spec <version: '10.12-baseline'> spec for: #pharo do: [ spec blessing: #baseline. spec project: 'XML Parser' with: [ spec className: 'ConfigurationOfXMLSupport'; version: '1.0.1'; loads: #('default'); file: 'ConfigurationOfXMLSupport'; repository: 'http://www.squeaksource.com/MetacelloRepository']. spec package: 'DrGeoII-Core' with: [ spec requires: 'XML Parser']] -- Dr. Geo - http://drgeo.eu

3 4