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

[Pharo-project] [dropped by admin]
by StÃ©phane Ducasse Sept. 19, 2012

Sept. 19, 2012

[dropped by admin]

5 6

Re: [Pharo-project] How to resurrect an unrepsonsive image?
by Marcus Denker Sept. 18, 2012

Sept. 18, 2012

On Dec 8, 2011, at 9:24 PM, Benoit St-Jean wrote: > I'm sure he is but Dolphin being a great environment, I don't mind when people remind (or inform) others of great ideas in other Smalltalk environments... As a Smalltalker, I don't mind seeing references to VAST, VW, ObjectStudion or even VSE here when something great/elegant/clever can be learned/imported/inspired from those... > But in *every* email? This is like when you switch job and in *every* conversation you say "But in my old company we did X". So What? Or even when you are in another country to remind everyone that "in $MyHomeCountry this is better". Yes, even if you are right, after the 49th time it gets idiotic. Especially, if it's just *talk* and not *do*. Marcus -- Marcus Denker -- http://marcusdenker.de

3 3

[Pharo-project] Who broke UTF8TextConverter?
by Igor Stasenko Sept. 7, 2012

Sept. 7, 2012

or it was like that from the birth?? arrrrgghhhh... | stream | stream := WriteStream on: (ByteArray new: 100). UTF8TextConverter new nextPut: (Character value: 129 ) toStream: stream. stream contents #[129] This is WRONG! RTFM, about utf8 encoding, please! :) --------- nextPut: aCharacter toStream: aStream | leadingChar nBytes mask shift ucs2code | aStream isBinary ifTrue: [^aCharacter storeBinaryOn: aStream]. in my case, stream is binary, so it goes directly to #storeBinaryOn: storeBinaryOn: aStream "Store the receiver on a binary (file) stream" value < 256 ifTrue:[aStream basicNextPut: value] ifFalse:[aStream nextInt32Put: value]. This is not even close to UTF8. If character code is less than 256, it will store a single byte (wtf?), and if more than that, it will store 32-bit integer value in big-endian order (wtf raisedToPower: 2).. i wonder , for what purpose we actually having this code path? this stuff is completely useless. according to implementation of storeBinaryOn: there's no way how you can read the same character value back. because it can be 1 byte or 4 bytes.. but you simply cannot determine which one. this is one of the reasons we using utf8 encoding, btw ;) -- Best regards, Igor Stasenko.

7 9

[Pharo-project] Monkey can't find working copies?
by Sean P. DeNigris Sept. 6, 2012

Sept. 6, 2012

There are a few issues with "Error: Working copy for SLICE-Issue-Xxx not found". Is this a monkey problem? The slice for http://code.google.com/p/pharo/issues/detail?id=6560 at least seems to load fine in latest 2.0... Sean [1] http://code.google.com/p/pharo/issues/list?can=2&q=Error+%22Working+copy+fo… -- View this message in context: http://forum.world.st/Monkey-can-t-find-working-copies-tp4644829.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] latam mirror down?
by Dale Henrichs Sept. 5, 2012

Sept. 5, 2012

http://www.dsal.cl/squeaksource/ http://www.downforeveryoneorjustme.com/http://www.dsal.cl/squeaksource/

2 13

[Pharo-project] Pharo 2.0 + Travis = ?
by Frank Shearar Sept. 5, 2012

Sept. 5, 2012

Hi Dale, I'm getting a build failure against Pharo 2.0 [1] with the error "FileDoesNotExist: /home/travis/dalehenrich-builderCI-cd2facd/builds/travisCI/TravisTranscript.txt". I think that's because the before.st says "transcriptStream := ((Smalltalk at: #FileSystem) workingDirectory / transcriptFileName) readStream ]" and that file doesn't exist. Is there a convenient way of saying "please open a readStream on this file and, if it's not there, make one" ? (If one semi-replicates the build, by opening a Pharo 2.0 image, manually loading the ConfigurationOfControl, and running "ConfigurationOfControl loadDevelopment", one will see Control 1.1.dev running with a green light for Pharo 2.0!) frank [1] http://travis-ci.org/#!/frankshearar/Control/jobs/2282004

6 17

[Pharo-project] Zinc-HTTP-Deprecated
by Sven Van Caekenberghe Sept. 5, 2012

Sept. 5, 2012

There is a class category called 'Zinc-HTTP-Deprecated'. It contains some old classes that were replaced/superceded by newer ones almost a year ago. I plan to actually delete these and their unit tests in a commit in the next couple of days. Specifically, the following classes will be removed: - ZnClientOld - ZnFixedClient - ZnExtendedFixedClient - ZnUserAgent - ZnHttpClient - ZnUserAgentSettings I hope nobody uses these anymore. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

2 1

[Pharo-project] What happens with Warning when running in headless image (2.0)?
by Dale Henrichs Sept. 3, 2012

Sept. 3, 2012

I'm running a headless pharo2.0 from a script and the vm disappears without a trace (no pharodebug.log info etc.) ... when I run the script in a gui, I see that a warning dialog box is popping up, so perhaps this is the source of the issue? ... or perhaps it's something else? Dale

4 10

[Pharo-project] [ANN] Nagare - a new flexible logger for Smalltalk
by Masashi UMEZAWA Sept. 2, 2012

Sept. 2, 2012

Hello all, I have recently developed a new logging library called Nagare. http://code.google.com/p/nagare-logger/ Nagare is designed to be simple and scalable. Contrary to other logging frameworks which provide rich set of log output methods (file, socket, DB, etc.), Nagare just connects to fluentd (http://fluentd.org) And Fluentd does the various log processing jobs. Features: - Simple log interfaces with reliable backend - Semi-structured logging (Not only String, you can store structured records in log) - Flexible - you can easily customise log-tags, log policy, etc. - Portable (runs on Squeak, Pharo, VisualWorks) Enjoy! -- [:masashi | ^umezawa]

2 2

[Pharo-project] An idea about visual feedback in Athens
by Igor Stasenko Sept. 2, 2012

Sept. 2, 2012

so, the problem is that all you see on screen consists from shapes, which are drawn by Athens. Now, since drawings can be quite complex and include various transformations, it will be hard to track them manually to use for mouse (or fat finger) pointer hits. A simplest example: i wanna draw a rectangle, rotated by 45 degrees. and i wanna change it's color when mouse is over it. If you look at the situation from global coordinate system perspective, in order to find whether some morph contains given point or not, you have to iterate over all it's parent morphs (because they also can have coordinate system transformations). But in a local coordinate system, things remain extremely simple: to test whether a point is inside of rectangle (most morphs usually is) is a piece of cake, isnt? I think i found an interesting approach for a coordinate system feedback, (so it can be used for 'hit tests' as well as many other things) So, lets consider a simple draw method: Morph>>drawOnAthensCanvas: aCanvas aCanvas setPaint: Color red; drawShape: self bounds now if we add a single line here: self registerShapeForEvents: self bounds canvas: aCanvas. Things getting very interesting: what this method should do, is to simply capture enough state from current canvas (like transformation matrix, clipping and the shape , of course), so later it can be used to test whether some point (like mouse cursor position) is over it or not. Why in drawing method , you might ask? Where else, i would answer.. A parent morphs branch can impose own clipping and transformation, which you can easily observe during drawing, but it becomes tedious once you leave outside of it: to get same amount of information you'll have to manually go over all morph's hierarchy and apply same transformation/clipping calculations once you get to the morph under the question. The drawing method responsible for visual representation of morph on display media, which means that it actually defines the shape(s) with which users will interact. So, by drawing a bunch of morphs on desktop using such approach, we can automatically capture all the geometry (as well as its relative hierarchy), which needs to be tested for mouse hits (or receiving a mouse events in general). And the hit test , which we need to perform every mouse move, boils down to simply iterating over that hierarchical list and testing the current hand position against each element. The morphs, which are not interested in receiving a mouse events (like hidden or parent morphs of various kinds), apparently can simply avoid publishing anything into that list, instead of implementing numerous #handlesMouseDown/#handlesMouseOver etcc... and like that saving cycles for being tested every time you touching the mouse, because some of their submorphs are actually interested in receiving such events. And of course a most interesting aspect of this approach is handling a complex geometry for morphs. Because with rectangles it is fairly simple to imagine a visual feedback system which based solely on morph's bounds (like the one which we currently using), but for morphs with complex geometry, things can become quite tedious. -- Best regards, Igor Stasenko.

2 6