July 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Problem with announcements in Seaside when using Pharo 1.3
by Andrei Vasile Chis July 18, 2011

July 18, 2011

Hi all, In have a simple case: in an ajax callback I trigger an announcement and in the callback associated with the announcement I try to render a Date object. When I do this I get a WARequestContextNotFound exception. To be more exact I have in a component this function to render the callback link: renderAnnouncementUpdate: html html anchor onClick: (html jQuery ajax script: [ :s | script := s. model announce: SGLLinkClickedAnnouncement new ]); with: 'Update Announcements' The model is initialized when I create the component in: initialize super initialize. model := SGLVerySimplePresentation new. model on: SGLLinkClickedAnnouncement do: [:ann| self onClick: ann]. When the announcement is called it will trigger the onclick: method which will do the rendering: onClick: ann self addScripts: script addScripts: s s << (s jQuery: #date1) html: [ :r | r render: Date today ]. s << (s jQuery: #time1) html: [ :r | r render: Time now ] However the html: method trigers an WARequestContextNotFound exception. I'v tried this on Pharo 1.3 (running on CogVM) with the latest version of Seaside. The application can be found in the Moose Playground project from http://www.squeaksource.com in the package SGL-Seaside-Problem. Atfer you install the package and start a web server you have to execute "SGLTestComponentMin registerAsApplication: 'SGLTestComponentMin'." to register the application. Am I missing something? Cheers, Andrei

12 29

[Pharo-project] New 1.4 image on inria forge.
by StÃ©phane Ducasse July 18, 2011

July 18, 2011

https://gforge.inria.fr/frs/download.php/28785/Pharo-1.4-14048.zip Stef

2 2

[Pharo-project] [update 1.4] #14048
by StÃ©phane Ducasse July 18, 2011

July 18, 2011

14048 ----- - Issue 4528: Exception on:fork: enhancement. Thanks Igor Stasenko and Lukas Renggli for the idea and ... Stef

1 0

[Pharo-project] [update 1.4] #14048
by StÃ©phane Ducasse July 18, 2011

July 18, 2011

14048 ----- - Issue 4528: Exception on:fork: enhancement. Thanks Igor Stasenko and Lukas Renggli for the idea and ... Stef

1 0

[Pharo-project] ESUG 2011 Innovation Technology Awards reminder
by Jordi Delgado July 18, 2011

July 18, 2011

Hi, Just a reminder: ESUG 2011 Innovation Technology Awards (http://esug.org/Conferences/2011/InnovationTechnologyAwards) We are proud to announce the 8th Innovation Technology Awards. Have you written innovative Smalltalk? The developers of any Smalltalk-based software can enter by submitting a 3-5min video of their software. Entrants demo their systems in a session at the end of Monday August 22nd 2011, after which the conference attendees vote. (A vote consists in providing a sorted list of 3 preferred pieces of software.) The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros. The results are announced in the Awards ceremony that is held during the social event. Applicants should provide the following information on the conference registration server. Once you have registered your personal info, an "Awards" menu allows submitting your software. You can provide this information when you first register, or login again later and update your details. Info to provide: Name of the software Licence information (free, or shareware, or a commercial) Name of the Smalltalk dialect used Names, Affiliation and Country of developers URL for a video (3-5 min) showing a screencast / demo of the software URL for downloading the software or at least a runnable demo Deadline: 30th of july Any Smalltalker can apply (students, companies, ...). The presented piece of code/software should be written in Smalltalk or directly support Smalltalk (e.g. Smalltalk VM). All Smalltalk dialects are accepted. The applicant should own the copyright/copyleft of presented code or at least be the official representative of the copyright/copyleft owner. The software should be available on-line for evaluation (time-limited evaluation version, demo version, free for non-commercial use ...). Bests, Jordi

1 1

[Pharo-project] [update 1.4] #14047
by StÃ©phane Ducasse July 18, 2011

July 18, 2011

14047 ----- - Issue 4527: serialPort enh. Thanks Bill Schwab. - Fixing getPreamble:

1 0

[Pharo-project] [update 1.4] #14044
by StÃ©phane Ducasse July 18, 2011

July 18, 2011

14044 ----- - Issue 4530: Source enh. Thanks Veronica Uquillas-Gomez. - Issue 4529: Announcement delivery breaks if last subscriber is curtailed. Thanks Henrik Johanssen. Tx Stef

1 0

[Pharo-project] Sound on Linux
by Schwab,Wilhelm K July 18, 2011

July 18, 2011

To see if sound works on Linux, I grabbed Squeak 4.2 - it works, at least on Ubuntu Lucid. In Pharo 1.3, I can't enable the sound preference. I'm not sure if that's good or bad :) Any ideas?

2 1

[Pharo-project] Fancier Debugger
by Camillo Bruni July 18, 2011

July 18, 2011

Hi everyone, last friday I spent some 20mins on improving the debugging experience (at least for me) by doing to following: - removed many "core" message sends from the context stack in the debugger - automatically expand the context stack if the last stackframe is selected For the first task I added a method which filters out all message sends which IMO are mostly uninteresting when debugging (right now still a but dirty implemented..): - #ifTrue: #ifFalse.... and so forth - iteration internals on Collections: #do: - Message sends to Blocks / MethodContexts: #on:do: #value: ... - Basic accessors on dicts: #at: #at:put: .... at least for me this helps me incredibly with locating important pieces of code in the debugger e.g. reducing the noise.. So is there any interest in this to be added? (of course with a settings switch to turn it on/off... in case you work on the filtered messages) If so I will implement it a bit cleaner and add a decent settings entry... cami

4 3

[Pharo-project] problem in configuration of swazoo
by Tudor Girba July 17, 2011

July 17, 2011

Hi Janko, The latest version of the ConfigurationOfSwazoo has a problem. Specifically, version '2.3.0.0' was recently changed to point to the Swazoo package version 'Swazoo-2.3beta2.6'. However, in Monticello we only have 'Swazoo-janko.3beta2.6'. Could you fix it, or should I try to do it? Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

2 2