March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Smalltalkhub & API
by Stephan Eggermont March 27, 2014

March 27, 2014

Hi Phil, Did you take a look at a smalltalkhub image https://ci.inria.fr/pharo-contribution/job/SmalltalkHub/ The Hub package provides a starting point. Stephan

4 3

Re: [Pharo-dev] DateAndTime>>#= slow?
by Stephan Eggermont March 27, 2014

March 27, 2014

Esteban wrote >How do I test it? >Do I have to download a whole new 3.0 image? Normal way to test is to download latest 3.0 image and run it (on latest vm). Open monticello, open Pharo30Inbox, Type the issue number to find the slice and merge it to see changes. Stephan

2 1

Re: [Pharo-dev] DateAndTime>>#= slow?
by Stephan Eggermont March 27, 2014

March 27, 2014

Sven wrote: >PS2: I am not sure I am allowed to fix this so close to release, is it a feature or a bug fix ? ;-) Donât worry, if you look at the slope of our issue burndown chart you might notice that we need to change directions to get closer to releaseâ¦ Stephan

1 0

Redraw suggestion for Athens
by J.F. Rick March 27, 2014

March 27, 2014

I've been using Athens to render my applications and I've thought a bit about how the #changed mechanism might change when BitBlt rendering is replaced by Athens rendering. First, you must realize that a lot of the rendering in Morphic is highly specialized to deal with the slowness of BitBlt rendering. So, a morph that has changed in appearance (by moving, etc.) calls the #changed message on itself. This tells morphic that it needs to get rerendered when the screen is next being updated. The full bounds of the morph are then added to the damage recorder. When the UI loop gets around to it, the damage areas are rerendered in a relatively smart fashion. For instance, if a morph is opaque, none of the morphs behind it get rendered. Only the damage rectangles are copied to the canvas, which is then updated. With Athens, this strategy is problematic. Because Athens allows for arbitrary rotation and scaling, it is much more difficult to determine the bounds of a specific morph. Athens also can use local positioning as opposed to the global positioning currently used in Morphic. Igor argues that it is best not to try to figure this out but just to render everything when anything has changed. In my experience, that is a reasonable proposition. Athens rendering is fast enough that even full animation could be done reasonably. That would also simplify the #changed code and could pretty much eliminate the damage recorder. OK. That's enough setup. Now for the suggestion. One problem I still have with Athens rendering is that there is still a visual artifact that has to do with the screen refresh not being in sync with the UI loop. Half the screen renders the previous frame and the other half renders the current frame. While it only is noticeable when moving something fast, it still isn't nice. So, here's the suggestion. Have two Athens surfaces in memory that switch between being the one next to be rendered and the active one. When the screen refresh comes along, send it to the last one rendered (i.e., the active one). When a change happens, render the surface on the inactive one. When that is done, make it the active one. Thus, the screen update always has an accurate form. It also would mean less copying around of forms (i.e., cacheing). I'm not sure if this implementation is viable, but it seems like a fairly efficient strategy that Athens could enable. Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

2 2

Streaming problem in case of errors
by Damien Cassou March 27, 2014

March 27, 2014

P Hi guys, when PharoDebug.log can't be created (e.g., when the image is in a non writeable directory like /usr/share), the errors are sent to the Transcript in the hope that they will be redirected to stdout or stderr. However, ContextPart>>errorReportOn: is called when an exception is signaled and this method assumes that the stream is positionable (which is not the case for transscript, stdin and stderr). I was planing on rewriting ContextPart>>errorReportOn: to make it independent of #position. What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

2 5

Re: [Pharo-dev] DateAndTime>>#= slow?
by Esteban A. Maringolo March 27, 2014

March 27, 2014

2014-03-27 12:21 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > On 27 Mar 2014, at 12:14, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> On 27 Mar 2014, at 15:46, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> Will the fix be available for Pharo 2 builds as well? >> >> I knew you were going to ask that, but I don't know. The whole Chronology package was changed quite a lot going from 2.0 -> 3.0 >> >> On the other hand, my changes are pretty comprehensible (a couple of methods), somebody could certainly try to backport them - but no guarantees they will work though. > > pharo3 is at the corner to be out. > we are not integrating/backporting changes to pharo2 since... well, like 6 months. > so no, it will not be there and it will not be integrated. What is the support strategy for stable versions? Pharo 3 is still beta/release-candidate, so... strictly speaking Pharo 2 is the official stable version. Shouldn't it get support as such? If resource scarcity rules here, I'll understand. > said so... anyone can do their own backport and put it for others in a meta repo :) It will be so. :) Esteban A. Maringolo

1 0

[Job] netstyle.ch is hiring! (v2)
by Christoph Wysseier March 27, 2014

March 27, 2014

Hi all We are still looking for web application developers (Smalltalk/Seaside). Because of the lack of applications so far we reduced our primary restrictions: - German is not a must anymore, we accept applications from any experienced Smalltalk developers but we expect applicants to speak English fluently. - Citizenship does not matter anymore, we are going to take care of your work permit, if necessary. - No freelancer applications please, this is a permanent position located in Berne, Switzerland! [ Job Description ] netstyle.ch is looking for a Seaside web application developer. We are a small, agile and harmonious team located in Berne (Switzerland). With Cmsbox we have developed an award winning Content Management System with hundreds of installations so far. We also develop sophisticated web applications for longterm clients. The successful candidate must have excellent skills in OO software development with a dynamic programming language and fit in a team of young, ambitious engineers. For questions and applications please contact me at info(a)netstyle.ch. -- Christoph Wysseier netstyle.ch GmbH, CEO

1 0

[Help needed] Issuer tracker TODO Pharo3
by Marcus Denker March 27, 2014

March 27, 2014

Hi, There are 23 issues open for Pharo3 https://pharo.fogbugz.com/f/filters/64/3-0-TODO In general, it would be nice if more people would care about -> testing and reviewing proposed fixes -> just keeping the issue tracker healthy Marcus

2 1

Help needed with Pharo3 ChangeLog
by Marcus Denker March 27, 2014

March 27, 2014

Hi, If people have time, it would be nice to help a bit with the ChangeLog: https://pharo.fogbugz.com/default.asp?W64 e.g. make sure that *your* contribution is listed! Marcus

2 4

MOOSEDay@UPMC website online
by Serge Stinckwich March 27, 2014

March 27, 2014

Dear all, The MOOSEDay@UPMC 2014 will be organized in Paris, June 5th. The day will be followed by a Pharo Sprint (June 6th) at the same place. A first draft of the MOOSEDay@UPMC is online here: http://www.doesnotunderstand.org/MOOSEDayUPMC/ I need you help : - if you want to propose a talk, send me title, a short summary (3-4 lines), the name and a picture of the speaker. - if you want to sponsor the event, just ask me :-) - if you want to attend, just send me your name and affiliation. I will add you on the webpage. - if you have some graphic abilities, you can send me a better cover picture (maybe with some MOOSE pictures). The webpage is managed on github, if you want to modify the page, just send me a pull request on github: https://github.com/SergeStinckwich/MOOSEDayUPMC Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1