December 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] MQTT for Pharo
by Sean P. DeNigris Dec. 23, 2016

Dec. 23, 2016

timrowledge wrote > Hi Sven, > yes, the code in SqueakSource/MQTT is very early stuff. It's improving > quickly though. I'd be happy to get together to work on an as common as > possible versions for both Squeak and Pharo. ----- Cheers, Sean -- View this message in context: http://forum.world.st/MQTT-for-Pharo-tp4927759p4928045.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Do you think VersionBrowser is counterintuitive?
by Denis Kudriashov Dec. 23, 2016

Dec. 23, 2016

Hi. I always catch myself that I am completely lost in method versions (and feel pain :)). There is no clue what at the left pane and what at the right pane. Now I realize that VersionBrowser is trying to compare selected version versus next version (according to list order). So right pane shows selected version and left pane shows next one. For me all of these is super non intuitive but maybe it is only my problem. So here I want to ask about your experience. Do you feel same? I would prefer if VersionBrowser will always compare selected version versus current version in image with actual image version on the left and selected version on the right. What you think? Best regards, Denis

6 12

MQTT for Pharo
by Sven Van Caekenberghe Dec. 22, 2016

Dec. 22, 2016

Hi, MQTT is a light-weight publish/subscribe messaging protocol, originally created around 1998. It is now an official open industry ISO standard. It is perfect for large-scale Internet of Things applications and high performance mobile messaging. The publish/subscribe messaging pattern requires a message broker. The broker is responsible for distributing messages to interested clients based on the topic of a message. Parties communicating with each other over MQTT would all be clients in different roles, like producers and consumers, using the broker as middleware. Many client libraries for different programming languages and multiple brokers/servers are available. Facebook Messenger and Amazon AWS IOT are two users, among many others. A good client library for Pharo was not yet available. I started a new MQTT project and I am looking for collaborators to help me finish it. The official specification is quite readable and there is a lot of information available (see the References/Links section at the end). Right now, a first version of the following features is available: - reading & writing of all 14 binary packet types - an experimental client with support for connection open/close, ping, subscribe/unsubscribe, QoS levels 0 (at most once), 1 (at least once) and 2 (exactly once) for application (publish) messages in both directions, message/package IDs and keep alive (heartbeat) - unit tests, for packet reading/writing and for clients against 3 publicly available sandbox/test brokers Basically, the code works but needs polishing and maturing. Also, it might be useful to experiment with alternative client API design. Not all features are yet implemented. It would also be nice to implement an actual server/broker, not to replace production quality servers, but as a proof of concept and tools during development. Code http://smalltalkhub.com/#!/~SvenVanCaekenberghe/MQTT/ Right now, documentation is limited, but there are class comments and the most important public API methods are commented too. There is no Metacello configuration yet, just load the 3 packages. References/Links - http://mqtt.org - https://en.wikipedia.org/wiki/MQTT - http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html - https://github.com/mqtt/mqtt.github.io/wiki/software - http://mosquitto.org - https://github.com/emqtt/emqttd - http://kamilfb.github.io/mqtt-spy/ - https://github.com/eclipse/paho.mqtt-spy/wiki - https://eclipse.org/paho/ - https://eclipse.org/paho/clients/c/embedded/ - http://www.rabbitmq.com/mqtt.html - https://vernemq.com - https://www.ibm.com/developerworks/community/blogs/c565c720-fe84-4f63-873f-… Sandbox/test Servers/Brokers iot.eclipse.org:1883 test.mosquitto.org:1883 broker.mqtt-dashboard.com:1883 Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

4 13

Pharo on Raspberry, how? Who?
by Igor Stasenko Dec. 22, 2016

Dec. 22, 2016

Hi there, i have this cute device on my hands, and wanna show my colleges how cool Pharo is.. i remember Pavel shown us once, that it works and possible, and i would like to try as well.. since i hate python, and i would much more prefer to run humane-friendly language, such as our beloved smalltalk rather than prehistoric-era scripting language :) -- Best regards, Igor Stasenko.

2 6

Berlin 2016-12-19
by Sven Van Caekenberghe Dec. 22, 2016

Dec. 22, 2016

https://en.wikipedia.org/wiki/2016_Berlin_attack It is really sad that these things happen, that so many innocent people are killed and hurt. It makes me even more sad that I seem to be getting used to this, that should not be the case, at all. Sven

10 15

[pharo-project/pharo-core]
by GitHub Dec. 21, 2016

Dec. 21, 2016

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

1 0

[pharo-project/pharo-core] 420e59: 60334
by GitHub Dec. 21, 2016

Dec. 21, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 420e59ef1f9acba9c16c30c9ec56d47efb47872e https://github.com/pharo-project/pharo-core/commit/420e59ef1f9acba9c16c30c9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-21 (Wed, 21 Dec 2016) Changed paths: M GeneralRules.package/GRVariableAssignedLiteralRule.class/instance/accessing/name.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60333.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60334.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60333.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60334.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/initialization/setTextModelForTransformationRule_.st A Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/private/diffSeparator.st A Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/private/diffTextForChange_.st Log Message: ----------- 60334 19479 Typo in name attribute of GRVariableAssignedLiteralRule https://pharo.fogbugz.com/f/cases/19479 19478 Criticsbrowser shows a refactoring class name instead of the text diff https://pharo.fogbugz.com/f/cases/19478 19438 Widen tolerance for DelayScheduler timing tests https://pharo.fogbugz.com/f/cases/19438 http://files.pharo.org/image/60/60334.zip

1 0

[pharo-project/pharo-core] 258c2c: 60333
by GitHub Dec. 21, 2016

Dec. 21, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 258c2c569dd82ba6184a5bd6facfd13aa0d172da https://github.com/pharo-project/pharo-core/commit/258c2c569dd82ba6184a5bd6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-21 (Wed, 21 Dec 2016) Changed paths: M BaselineOfMorphic.package/BaselineOfMorphic.class/instance/actions/postload_package_.st A Monticello.package/MonticelloBootstrap.class/README.md A Monticello.package/MonticelloBootstrap.class/class/instance-creation/bootstrapDefault.st A Monticello.package/MonticelloBootstrap.class/class/instance-creation/inDirectory_.st A Monticello.package/MonticelloBootstrap.class/definition.st A Monticello.package/MonticelloBootstrap.class/instance/accessing/directory_.st A Monticello.package/MonticelloBootstrap.class/instance/accessing/localRepository.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/bootstrap.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/createWorkingCopies.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadBootstrapPackageNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadBootstrapPackages.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadBootstrapPackagesNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadPackageNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadPackageVersion_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadPackagesNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/versions/bootstrapVersionsExcept_.st A Monticello.package/MonticelloBootstrap.class/instance/versions/bootstrapVersionsSatisfying_.st A Monticello.package/MonticelloBootstrap.class/instance/versions/fileNameForPackageNamed_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60332.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60333.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60332.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60333.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60333 19484 BaselineOfMorphic references unexisting class https://pharo.fogbugz.com/f/cases/19484 19483 Add bootstrap specific code in Monticello https://pharo.fogbugz.com/f/cases/19483 http://files.pharo.org/image/60/60333.zip

1 0

[pharo-project/pharo-core]
by GitHub Dec. 21, 2016

Dec. 21, 2016

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

1 0

a request to change the meaning of <example> pragma
by Tudor Girba Dec. 21, 2016

Dec. 21, 2016

Hi, As you might know, a while ago we created GTExamples, a framework that supports both example-based live documentation and testing: http://gtoolkit.org/doc/Examples/examples.html GTExamples was part of the GTInspector for a while, but as it evolved, we pulled it out in a separate project. This separate project is not in Pharo anymore but it is part of the full GToolkit configuration (Pharo only ships the core of GToolkit). The idea of taking GTExamples out was to allow the community to have a more elaborate discussion about the role of examples in our environment. I have invited you to join that conversation, but it did not take off. I understand that perhaps the topic does not look appealing at this moment. We will certainly continue to evolve GTExamples both on the semantics level of the dependency constructs and on the integration with tools. Our goal is to enable a new practice that I would like to call Example-Guilded Development (or Example-Driven Development), and position Pharo to be the only platform on which someone can do that. But, that is our goal, and does not have to be the same with other peopleâs goal. Right now, GTExamples relies on the <gtExample> pragma to denote a method that returns an object that exemplifies something. Executing this method as an example should have no side-effects (either because the method itself does not have a side-effect, or because the example method defines how the cleanup should happen using the mechanism provided by GTExamples). This meaning is different from the meaning of the <example> pragma used through Pharo. There are currently 55 places that use this pragma inside Pharo and most of them come from FastTable. As things will progress and more libraries might use GTExamples, the situation can become confusing. To make things less confusing in the future, I would like to define the meaning of the <example> to denote a method that returns an object without having side effects. Would you agree with this? If yes, I would suggest the name of the new pragma that would replace the existing one to include âscriptâ in the name. For example, <sampleScript>. What do you think? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

9 19