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

Re: [Pharo-dev] [ANN] Stamp, another STOMP implementation

by phil＠highoctane.be

superb! On Tuesday, August 13, 2013, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 13 Aug 2013, at 15:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Excellent! >> And with a lovely documentation (even if too short to my eyes :)). > > Indeed, although it is better than nothing, it is too short and the code itself can use more comments as well, but it is a pretty complex subject, especially if you are unfamiliar with messaging-oriented middleware and architecture. > > It will improve over time. Users are an important driver for improvements. > >> On Aug 13, 2013, at 3:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Hi, >>> >>> I am pleased to announce the public release of Stamp >>> >>> http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp >>> https://github.com/svenvc/docs/blob/master/neo/stamp.md >>> >>> Stamp is an implementation of STOMP, the Simple (or Streaming) Text Oriented Message Protocol, for Pharo, a protocol to interact with message-oriented middleware (MOM). >>> >>> More specifically, Stamp implements STOMP 1.2 and was tested against RabbitMQ 3.1. Other message-oriented middleware implementations accessible through STOMP include Apache ActiveMQ, Glassfish Open MQ and Fuse Message Broker based on Active MQ - but these have not yet been tested. >>> >>> Messaging middleware is an important technology for building scaleable and flexible enterprise software architectures. >>> >>> Stamp itself is still evolving. Any feedback is welcome. >>> >>> Sven >>> >>> PS: As noted in https://github.com/svenvc/docs/blob/master/neo/stamp.md#acknowledgementthere is a relation with GÃ¶ran Krampe's older http://www.squeaksource.com/StompProtocol.html >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >>> >> >> > > > -- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Featured on the Software Process and Measurement Cast http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

Aug. 13, 2013

[update 3.0] #30332

by StÃ©phane Ducasse

less broken tests soon green 30332 ----- - issue 11414 Fixing s1 change parsing https://pharo.fogbugz.com/default.asp?11414 - issue 11409 EyeInspector class-side slot #useAutoRefresh is missing https://pharo.fogbugz.com/default.asp?11409 - issue 11411 Cannot resize inspector window per inspector class https://pharo.fogbugz.com/default.asp?11411 - 11410 failing test (Polymorphism between classes and traits) https://pharo.fogbugz.com/default.asp?11410 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-StephaneDucass… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-StephaneD… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-StephaneDucasse.511.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/KernelTests-StephaneDucasse.5…

Aug. 13, 2013

Re: [Pharo-dev] [ANN] Stamp, another STOMP implementation

by Sven Van Caekenberghe

On 13 Aug 2013, at 15:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Excellent! > And with a lovely documentation (even if too short to my eyes :)). Indeed, although it is better than nothing, it is too short and the code itself can use more comments as well, but it is a pretty complex subject, especially if you are unfamiliar with messaging-oriented middleware and architecture. It will improve over time. Users are an important driver for improvements. > On Aug 13, 2013, at 3:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Hi, >> >> I am pleased to announce the public release of Stamp >> >> http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp >> https://github.com/svenvc/docs/blob/master/neo/stamp.md >> >> Stamp is an implementation of STOMP, the Simple (or Streaming) Text Oriented Message Protocol, for Pharo, a protocol to interact with message-oriented middleware (MOM). >> >> More specifically, Stamp implements STOMP 1.2 and was tested against RabbitMQ 3.1. Other message-oriented middleware implementations accessible through STOMP include Apache ActiveMQ, Glassfish Open MQ and Fuse Message Broker based on Active MQ - but these have not yet been tested. >> >> Messaging middleware is an important technology for building scaleable and flexible enterprise software architectures. >> >> Stamp itself is still evolving. Any feedback is welcome. >> >> Sven >> >> PS: As noted in https://github.com/svenvc/docs/blob/master/neo/stamp.md#acknowledgement there is a relation with GÃ¶ran Krampe's older http://www.squeaksource.com/StompProtocol.html >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> > >

Aug. 13, 2013

Re: [Pharo-dev] [ANN] Stamp, another STOMP implementation

by StÃ©phane Ducasse

Excellent! And with a lovely documentation (even if too short to my eyes :)). On Aug 13, 2013, at 3:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I am pleased to announce the public release of Stamp > > http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp > https://github.com/svenvc/docs/blob/master/neo/stamp.md > > Stamp is an implementation of STOMP, the Simple (or Streaming) Text Oriented Message Protocol, for Pharo, a protocol to interact with message-oriented middleware (MOM). > > More specifically, Stamp implements STOMP 1.2 and was tested against RabbitMQ 3.1. Other message-oriented middleware implementations accessible through STOMP include Apache ActiveMQ, Glassfish Open MQ and Fuse Message Broker based on Active MQ - but these have not yet been tested. > > Messaging middleware is an important technology for building scaleable and flexible enterprise software architectures. > > Stamp itself is still evolving. Any feedback is welcome. > > Sven > > PS: As noted in https://github.com/svenvc/docs/blob/master/neo/stamp.md#acknowledgement there is a relation with GÃ¶ran Krampe's older http://www.squeaksource.com/StompProtocol.html > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Aug. 13, 2013

The point of extending NativeBoost-Win32 more than neccessary?

by Igor Stasenko

Hi, Torsten, all i greatly appreciate your help and contribution, so don't take my critics as destructive , please :) The main reason for NativeBoost-Win32 package existence is to contain minimal necessary platform-dependent things, which would allow to support NativeBoost functionality. But you adding more and more things, which not strictly related to NB per se, but more like general accessibility to system etc. The test question what should and what should not belong to this package is: 'will NB run without it or not?'. So, try answering this question for classes and methods like: NBWin32Shell NBWin32Point etc. Please, do not misunderstand: i would certainty prefer such (and many other) things to be easily accessible, and working , when i need them. But to my thinking they are not belong to NB core, and should be moved to separate package (or project?). We should decide where, because if we keep going like that, eventually NativeBoost-Win32 will cover whole Win32 API and will make us responsible for maintaining it, something which i frankly don't have time nor resources to do. P.S. yes, i guilty that i started this by adding classes like NBWin32Window and couple more. But that was serving more as examples and minimal support for NBOpenGL to create offscreen window & opengl context. That was a mistake.. and we should not continue like that. -- Best regards, Igor Stasenko.

Aug. 13, 2013

[ANN] Stamp, another STOMP implementation

by Sven Van Caekenberghe

Hi, I am pleased to announce the public release of Stamp http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Stamp https://github.com/svenvc/docs/blob/master/neo/stamp.md Stamp is an implementation of STOMP, the Simple (or Streaming) Text Oriented Message Protocol, for Pharo, a protocol to interact with message-oriented middleware (MOM). More specifically, Stamp implements STOMP 1.2 and was tested against RabbitMQ 3.1. Other message-oriented middleware implementations accessible through STOMP include Apache ActiveMQ, Glassfish Open MQ and Fuse Message Broker based on Active MQ - but these have not yet been tested. Messaging middleware is an important technology for building scaleable and flexible enterprise software architectures. Stamp itself is still evolving. Any feedback is welcome. Sven PS: As noted in https://github.com/svenvc/docs/blob/master/neo/stamp.md#acknowledgement there is a relation with GÃ¶ran Krampe's older http://www.squeaksource.com/StompProtocol.html -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Aug. 13, 2013

Jenkins build is back to normal : Pharo-2.0-Tests Â» run 1,vm,win #267

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=win/2…>

Aug. 13, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=linux… 1 regressions found. FileSystem.Tests.Disk.FileHandleTest.testTruncate

Aug. 13, 2013

Jenkins build became unstable: Pharo-2.0-Tests Â» run 1,vm,linux #267

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=linux…>

Aug. 13, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/20619 Home: https://github.com/pharo-project/pharo-core

Aug. 13, 2013