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

Re: [Pharo-project] [ANN] Zinc WebSockets

by Chris Cunningham

On Wed, Sep 12, 2012 at 2:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Thanks for trying and for giving feedback, Pavel. > > A live, connected socket cannot survive an image save, I think. ... > Sven I could have sworn there was code in the guts of the save/start code that could tell if the image was resuming from a cold start, or from a 'save but don't quite' start. If this still exists, then you could just leave the connection open during save, and if just doing a save, let it stay open (thus surviving the save), but from a cold start close/remove the socket, since it is definitely no longer around. Sorry for the vagueness. -Chris

Sept. 12, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 343 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 12, 2012

Re: [Pharo-project] [ANN] Zinc WebSockets

by phil＠highoctane.be

Cool stuff! 2012/9/12 Sven Van Caekenberghe <sven(a)stfx.eu> > Hi, > > I am pleased to announce the first public release of Zinc WebSockets, an > implementation of client and server RFC 6455 regular (ws://) and secure > (wss://) WebSockets on top of Zinc HTTP Components and Zodiac TLS/SSL > Streams. > > High level documentation can be found here: > > https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md > > The code can be found in the regular Zinc repositories, or can be loaded > using Metacello: > > ConfigurationOfZincHTTPComponents project latestVersion load: > 'WebSocket'. > > Three examples are included and explained in the high level documentation: > > 1. a trivial echo service > > - each incoming message is simply echoed back to the client > > 2. a simple chatroom > > - each client opens a web socket to the chatroom service running on the > server > - the server keeps track of all connected client web sockets > - when a message comes in from any client it is distributed to all clients > - each client shows all incoming messages > > 3. a simple, continously updated status view > > - a client connects and listens for incoming messages containing a status > report > - the server streams status reports to each connected client every second > - in the web browser you get to see the Smalltalk image's clock, memory > and process stats > > Tested and approved on 2.0 #281. Portability to 1.3 and 1.4 should be OK. > > The implementation of Zinc WebSockets was made possible in part through > financial backing by Andy Burnett of Knowinnovation Inc. and ESUG. Thanks! > > Questions, remarks, feedback ? Please use the Pharo Smalltalk mailing > lists. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > >

Sept. 12, 2012

Re: [Pharo-project] [ANN] Zinc WebSockets

by Sven Van Caekenberghe

Thanks for trying and for giving feedback, Pavel. A live, connected socket cannot survive an image save, I think. A listening server can, because it is stopped and restarted. But it shouldn't hang the image, of course. I will try to debug this later on and come back to you. I guess that you are on Linux, right ? Sven On 12 Sep 2012, at 22:51, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi Sven, > > Great! Thank you very much and supporters too. I'm currently doing > some experiments with it and XULRunner. I want to report one > problem... if I do in workspace: > > s := ZnServer startOn: 1701. > s logToTranscript. > s delegate > map: 'ws-test' > to: [ :request | ZnResponse ok: (ZnEntity html: > ZnWebSocketEchoHandler clientHtmlRemote) ]; > map: 'ws-test-local' > to: [ :request | ZnResponse ok: (ZnEntity html: > ZnWebSocketEchoHandler clientHtml) ]; > map: 'ws-echo' > to: (ZnWebSocketDelegate map: 'ws-echo' to: ZnWebSocketEchoHandler new); > map: 'ws-chatroom-client' > to: [ :request | ZnResponse ok: (ZnEntity html: > ZnWebSocketChatroomHandler clientHtml) ]; > map: 'ws-chatroom' > to: (ZnWebSocketDelegate map: 'ws-chatroom' to: > ZnWebSocketChatroomHandler new). > "s stopDefault." > > and then if I open a socket and save the image (without closing of the > socket), the image hangs. It is saved but it hangs during the wake-up. > > -- Pavel > > > On Wed, Sep 12, 2012 at 10:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Hi, >> >> I am pleased to announce the first public release of Zinc WebSockets, an implementation of client and server RFC 6455 regular (ws://) and secure (wss://) WebSockets on top of Zinc HTTP Components and Zodiac TLS/SSL Streams. >> >> High level documentation can be found here: >> >> https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md >> >> The code can be found in the regular Zinc repositories, or can be loaded using Metacello: >> >> ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. >> >> Three examples are included and explained in the high level documentation: >> >> 1. a trivial echo service >> >> - each incoming message is simply echoed back to the client >> >> 2. a simple chatroom >> >> - each client opens a web socket to the chatroom service running on the server >> - the server keeps track of all connected client web sockets >> - when a message comes in from any client it is distributed to all clients >> - each client shows all incoming messages >> >> 3. a simple, continously updated status view >> >> - a client connects and listens for incoming messages containing a status report >> - the server streams status reports to each connected client every second >> - in the web browser you get to see the Smalltalk image's clock, memory and process stats >> >> Tested and approved on 2.0 #281. Portability to 1.3 and 1.4 should be OK. >> >> The implementation of Zinc WebSockets was made possible in part through financial backing by Andy Burnett of Knowinnovation Inc. and ESUG. Thanks! >> >> Questions, remarks, feedback ? Please use the Pharo Smalltalk mailing lists. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> >

Sept. 12, 2012

Re: [Pharo-project] [ANN] Zinc WebSockets

by Pavel Krivanek

Hi Sven, Great! Thank you very much and supporters too. I'm currently doing some experiments with it and XULRunner. I want to report one problem... if I do in workspace: s := ZnServer startOn: 1701. s logToTranscript. s delegate map: 'ws-test' to: [ :request | ZnResponse ok: (ZnEntity html: ZnWebSocketEchoHandler clientHtmlRemote) ]; map: 'ws-test-local' to: [ :request | ZnResponse ok: (ZnEntity html: ZnWebSocketEchoHandler clientHtml) ]; map: 'ws-echo' to: (ZnWebSocketDelegate map: 'ws-echo' to: ZnWebSocketEchoHandler new); map: 'ws-chatroom-client' to: [ :request | ZnResponse ok: (ZnEntity html: ZnWebSocketChatroomHandler clientHtml) ]; map: 'ws-chatroom' to: (ZnWebSocketDelegate map: 'ws-chatroom' to: ZnWebSocketChatroomHandler new). "s stopDefault." and then if I open a socket and save the image (without closing of the socket), the image hangs. It is saved but it hangs during the wake-up. -- Pavel On Wed, Sep 12, 2012 at 10:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I am pleased to announce the first public release of Zinc WebSockets, an implementation of client and server RFC 6455 regular (ws://) and secure (wss://) WebSockets on top of Zinc HTTP Components and Zodiac TLS/SSL Streams. > > High level documentation can be found here: > > https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md > > The code can be found in the regular Zinc repositories, or can be loaded using Metacello: > > ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. > > Three examples are included and explained in the high level documentation: > > 1. a trivial echo service > > - each incoming message is simply echoed back to the client > > 2. a simple chatroom > > - each client opens a web socket to the chatroom service running on the server > - the server keeps track of all connected client web sockets > - when a message comes in from any client it is distributed to all clients > - each client shows all incoming messages > > 3. a simple, continously updated status view > > - a client connects and listens for incoming messages containing a status report > - the server streams status reports to each connected client every second > - in the web browser you get to see the Smalltalk image's clock, memory and process stats > > Tested and approved on 2.0 #281. Portability to 1.3 and 1.4 should be OK. > > The implementation of Zinc WebSockets was made possible in part through financial backing by Andy Burnett of Knowinnovation Inc. and ESUG. Thanks! > > Questions, remarks, feedback ? Please use the Pharo Smalltalk mailing lists. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > >

Sept. 12, 2012

Re: [Pharo-project] [Pharo-users] [ANN] Zinc WebSockets

by StÃ©phane Ducasse

Thank sven and andy and ESUG for the sponsoring. I like bounties because this is ground up from the needs to the code and green tests! Stef > Hi, > > I am pleased to announce the first public release of Zinc WebSockets, an implementation of client and server RFC 6455 regular (ws://) and secure (wss://) WebSockets on top of Zinc HTTP Components and Zodiac TLS/SSL Streams. > > High level documentation can be found here: > > https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md > > The code can be found in the regular Zinc repositories, or can be loaded using Metacello: > > ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. > > Three examples are included and explained in the high level documentation: > > 1. a trivial echo service > > - each incoming message is simply echoed back to the client > > 2. a simple chatroom > > - each client opens a web socket to the chatroom service running on the server > - the server keeps track of all connected client web sockets > - when a message comes in from any client it is distributed to all clients > - each client shows all incoming messages > > 3. a simple, continously updated status view > > - a client connects and listens for incoming messages containing a status report > - the server streams status reports to each connected client every second > - in the web browser you get to see the Smalltalk image's clock, memory and process stats > > Tested and approved on 2.0 #281. Portability to 1.3 and 1.4 should be OK. > > The implementation of Zinc WebSockets was made possible in part through financial backing by Andy Burnett of Knowinnovation Inc. and ESUG. Thanks! > > Questions, remarks, feedback ? Please use the Pharo Smalltalk mailing lists. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > >

Sept. 12, 2012

Re: [Pharo-project] 2.0 is back in "usable" state

by StÃ©phane Ducasse

+1 > Thanks a lot Esteban. It is nice to have an engineer when things start to look complicated :) > > On Wed, Sep 12, 2012 at 6:04 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi guys, > > I think Pharo 2.0 is back in an usable state :) > > Beware, that doesn't means that it is stable and bug free! > In particular, I think there are still some problems around RPackage and the new SystemAnnouncer, but you can resume using it and providing bug reports/fixes. > > Enjoy, > Esteban > > ps: That means tomorrow I will resume the integration of issues, etc. but the stability effort is still ongoing... > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Sept. 12, 2012

[Pharo-project] [ANN] Zinc WebSockets

by Sven Van Caekenberghe

Hi, I am pleased to announce the first public release of Zinc WebSockets, an implementation of client and server RFC 6455 regular (ws://) and secure (wss://) WebSockets on top of Zinc HTTP Components and Zodiac TLS/SSL Streams. High level documentation can be found here: https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md The code can be found in the regular Zinc repositories, or can be loaded using Metacello: ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. Three examples are included and explained in the high level documentation: 1. a trivial echo service - each incoming message is simply echoed back to the client 2. a simple chatroom - each client opens a web socket to the chatroom service running on the server - the server keeps track of all connected client web sockets - when a message comes in from any client it is distributed to all clients - each client shows all incoming messages 3. a simple, continously updated status view - a client connects and listens for incoming messages containing a status report - the server streams status reports to each connected client every second - in the web browser you get to see the Smalltalk image's clock, memory and process stats Tested and approved on 2.0 #281. Portability to 1.3 and 1.4 should be OK. The implementation of Zinc WebSockets was made possible in part through financial backing by Andy Burnett of Knowinnovation Inc. and ESUG. Thanks! Questions, remarks, feedback ? Please use the Pharo Smalltalk mailing lists. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 12, 2012

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

by StÃ©phane Ducasse

Thanks esteban So is it working? Stef On Sep 12, 2012, at 5:55 PM, Esteban Lorenzano wrote: > 20281 > ----- > > Issue 6654: Make one RPackage maps one PackageInfo > http://code.google.com/p/pharo/issues/detail?id=6654 > > (pass 3) > > - Monticello to use RPackageSet > > finish :) >

Sept. 12, 2012

[Pharo-project] [Screencast] StoryBoard

by laurent laffont

http://www.pharocasts.com/2012/09/getting-started-with-storyboard.html Storyboard is a multi-user agile planning board with drag and drop support. It shows how little code is needed to build a complete application with Deltawerken. It consists of 39 classes, of which 7 are announcements (very simple). It allows you to quickly enter stories, estimate and prioritize them. In addition to stories you can add issue, documentation and chore cards. The cards are colored based on their story state. More details can be entered/viewed by expanding the card. In the expanded view a change history is shown. Other users of Storyboard can be invited to participate. Deltawerken is a Seaside application level framework, allowing fast application development for medium-sized applications. We have used an earlier extended version of it to build a system with about 150 domain classes. Complexity was deliberately and systematically pushed from the application to the framework. It uses a declarative way to describe domain classes somewhat similar to Magritte or Mold. It uses Announcements, jQuery and jQueryUI. Storyboard was announced at ESUG2012 Thank you Stephan Eggermont! (Note: feel free to contact me if you want to publish on PharoCasts) Laurent

Sept. 12, 2012