- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo - [ANN] SimpleDDS v1.0 released.

by Ben Coman

Santiago Bragagnolo wrote: > Hi guys, i am just releasing SimpleDDS. > > In order to connect into ROS world i had to implement a DDS support > (Publisher/subscriber). > > For achieving this i did MetaDDS, a library that defines basic objects, > announcements, event related mechanisms and data encoding formats, and > on top of it SimpleDDS, which is ROS based. > > SimpleDDS Has a package of examples highly commented for learning how to > use it. > > The comments are also in the Github wiki, as wiki pages: > > https://github.com/sbragagnolo/SimpleDDS/wiki > > Gofer it smalltalkhubUser: 'sbragagnolo' project: 'SimpleDDS'; > configuration; loadVersion: #stable > > > > Here some links about > > http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern > > http://en.wikipedia.org/wiki/Data_Distribution_Service > > > Thats it. Enjoy. > > Santiago > > > > I haven't heard of DDS, but this seems really significant! From wikipedia... "DDS addresses the needs of applications like financial trading, air-traffic control, smart grid management, and other Big data applications. The standard is used in applications such as smartphone operating systems,[1] transportation systems and vehicles,[2] software-defined radio, and by healthcare providers." This could be a nice lead into these application domains. If this got to a sufficient level of features, maybe Santiago could even be sponsored to attend an interoperability meeting? "DDS vendors participated in _Interoperability demonstrations_ at the Object Management Group (OMG) Spring Technical Meeting.[7] During the demo, each vendor publishes and subscribes to each other's topics using a test suite called the Shapes Demo." Such might be a good place to network and demo general use of Pharo. cheers -ben

Dec. 1, 2014

Re: [Pharo-dev] Pharo - [ANN] SimpleDDS v1.0 released.

by phil＠highoctane.be

Wow, impressive.â

Dec. 1, 2014

Re: [Pharo-dev] [To be merged] GT-InspectorExtensions-Core-SvenVanCaekenberghe.77

by Tudor Girba

Ugh. Sorry, I missed it. It's merged now. Cheers, Doru On Mon, Dec 1, 2014 at 11:28 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > http://www.smalltalkhub.com/#!/~Moose/GToolkit > > > On 01 Dec 2014, at 23:18, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Where do I find this one? > > > > Doru > > > > On Mon, Dec 1, 2014 at 10:04 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > In Moose/GToolkit: > > > > === > > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.77 > > Author: SvenVanCaekenberghe > > Time: 1 December 2014, 9:56:58.104994 pm > > UUID: 3da8544f-909e-49c6-88a5-f944a5f13b42 > > Ancestors: GT-InspectorExtensions-Core-TudorGirba.76 > > > > New version of Float>>#gtInspectorFloatIn: that shows the new binary > presentation available in Pharo 4. > > > > Tests on availability of #binaryLiteralString so that this change should > remain compatible with Pharo 3. > > > > Thx Kris Gybels for this contribution. > > === > > > > To be merged with higher versions (this was based on the version present > in Pharo 4 today). > > > > Sven > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 1, 2014

Re: [Pharo-dev] [To be merged] GT-InspectorExtensions-Core-SvenVanCaekenberghe.77

by Sven Van Caekenberghe

http://www.smalltalkhub.com/#!/~Moose/GToolkit > On 01 Dec 2014, at 23:18, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Where do I find this one? > > Doru > > On Mon, Dec 1, 2014 at 10:04 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > In Moose/GToolkit: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.77 > Author: SvenVanCaekenberghe > Time: 1 December 2014, 9:56:58.104994 pm > UUID: 3da8544f-909e-49c6-88a5-f944a5f13b42 > Ancestors: GT-InspectorExtensions-Core-TudorGirba.76 > > New version of Float>>#gtInspectorFloatIn: that shows the new binary presentation available in Pharo 4. > > Tests on availability of #binaryLiteralString so that this change should remain compatible with Pharo 3. > > Thx Kris Gybels for this contribution. > === > > To be merged with higher versions (this was based on the version present in Pharo 4 today). > > Sven > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 1, 2014

Re: [Pharo-dev] [To be merged] GT-InspectorExtensions-Core-SvenVanCaekenberghe.77

by Tudor Girba

Where do I find this one? Doru On Mon, Dec 1, 2014 at 10:04 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > In Moose/GToolkit: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.77 > Author: SvenVanCaekenberghe > Time: 1 December 2014, 9:56:58.104994 pm > UUID: 3da8544f-909e-49c6-88a5-f944a5f13b42 > Ancestors: GT-InspectorExtensions-Core-TudorGirba.76 > > New version of Float>>#gtInspectorFloatIn: that shows the new binary > presentation available in Pharo 4. > > Tests on availability of #binaryLiteralString so that this change should > remain compatible with Pharo 3. > > Thx Kris Gybels for this contribution. > === > > To be merged with higher versions (this was based on the version present > in Pharo 4 today). > > Sven > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 1, 2014

Pharo - [ANN] SimpleDDS v1.0 released.

by Santiago Bragagnolo

Hi guys, i am just releasing SimpleDDS. In order to connect into ROS world i had to implement a DDS support (Publisher/subscriber). For achieving this i did MetaDDS, a library that defines basic objects, announcements, event related mechanisms and data encoding formats, and on top of it SimpleDDS, which is ROS based. SimpleDDS Has a package of examples highly commented for learning how to use it. The comments are also in the Github wiki, as wiki pages: https://github.com/sbragagnolo/SimpleDDS/wiki Gofer it smalltalkhubUser: 'sbragagnolo' project: 'SimpleDDS'; configuration; loadVersion: #stable Here some links about http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern http://en.wikipedia.org/wiki/Data_Distribution_Service Thats it. Enjoy. Santiago

Dec. 1, 2014

Re: [Pharo-dev] Video Tutorial - Github for Pharo using Sourcetree

by Thierry Goubier

Le 01/12/2014 21:39, Esteban Lorenzano a Ã©crit : > > the goal is to not needing to install git command line to use it (is > a requirement: pharo needs to keep being as portable and independent > as always) :) from my point of view, Iâm quite happy with > gitfiletree. I will just intend to make it work without OSProcess. I can understand that intent. > but in other discussions. Yes, we will need to stabilise things in a > point. Iâm not happy with general status ofâ¦ well, a lot of things. > And not in status of stability (most of them work really well), but > Iâm working to try to ensure the maintainability in the long wayâ¦ and > that includes time to time needing to admit that we cannot maintain > everything (thus my push of (git)filetree and the use of git in > general) And I can only thank all the Pharo team for the impressive stability going from Pharo3 to Pharo4. Thierry > Esteban

Dec. 1, 2014

Re: [Pharo-dev] Video Tutorial - Github for Pharo using Sourcetree

by Thierry Goubier

Le 01/12/2014 21:53, Esteban Lorenzano a Ã©crit : > > Iâm also concerned about that (32bits only). But we are already > working on a solution. (and libgit2 support is already there, thanks > to Max). as I saidâ¦ our problem (not yours, but ours) is that we need > to keep pharo independent of installed tools. Soâ¦ libgit2. Otherwise > I would be pushing gitfiletree a lot more loud :) Yes. This is a strong point. I considered bundling a git along, to solve issues like Stephan's. Bundling libgit2 is a bit similar, in a way. Mind you. I do prefer the libgit2 + NativeBoost... but it was far too costly. And still not that portable (i.e. no git on the RaspberryPi, for example). And some of my internal arguments for libgit2 (being able to correctly propagate a Monticello merge into git) were wrong, but it took me time and the MergeDriver to understand why. Thierry

Dec. 1, 2014

[To be merged] GT-InspectorExtensions-Core-SvenVanCaekenberghe.77

by Sven Van Caekenberghe

In Moose/GToolkit: === Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.77 Author: SvenVanCaekenberghe Time: 1 December 2014, 9:56:58.104994 pm UUID: 3da8544f-909e-49c6-88a5-f944a5f13b42 Ancestors: GT-InspectorExtensions-Core-TudorGirba.76 New version of Float>>#gtInspectorFloatIn: that shows the new binary presentation available in Pharo 4. Tests on availability of #binaryLiteralString so that this change should remain compatible with Pharo 3. Thx Kris Gybels for this contribution. === To be merged with higher versions (this was based on the version present in Pharo 4 today). Sven

Dec. 1, 2014

Re: [Pharo-dev] Video Tutorial - Github for Pharo using Sourcetree

by Esteban Lorenzano

> On 01 Dec 2014, at 21:48, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 01/12/2014 21:04, Esteban Lorenzano a Ã©crit : >> >>> On 01 Dec 2014, at 20:25, Dale Henrichs >>> <dale.henrichs(a)gemtalksystems.com >>> <mailto:dale.henrichs@gemtalksystems.com>> wrote: >>> >>> >>> >>> On Mon, Dec 1, 2014 at 10:39 AM, Thierry Goubier >>> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >>> >>> Le 01/12/2014 19:21, Esteban Lorenzano a Ã©crit : >>> >>> >>> also, in a point (not now, but eventually)â¦ we will need to drop >>> something. The idea of keeping anything ad eternum just does >>> not scales. >>> >>> >>> But it's a good way of delaying git integration in the Pharo >>> platform by having to redesign the file format as well. >>> >>> >>> Thierry, >>> >>> Not sure if you are being sarcastic here:) >> >> he was, donât worry :) > > Maybe I was :) > >> and as an aswer: yes, Iâm not happy with filetree format, but I wouldnât >> spend changing it until we have ready other parts of the tooling I think >> is necessary (using libgit2 instead osprocess for me is a must, while >> changing filetree format is just an enhancement) > > When I considered libgit2 a while ago, I was like you: a must. Then I saw that: libgit2 was low-level => lot's of code in Pharo do do simple, basic stuff. libgit2 required changes in NativeBoost => what, NativeBoost isn't ready? Pharo is stuck in 32bits land=>No libgit2 by default on target OS. NativeBoost is x86 only? No libgit2 on ARM. Iâm also concerned about that (32bits only). But we are already working on a solution. (and libgit2 support is already there, thanks to Max). as I saidâ¦ our problem (not yours, but ours) is that we need to keep pharo independent of installed tools. Soâ¦ libgit2. Otherwise I would be pushing gitfiletree a lot more loud :) Esteban > > In short: I don't have the resources to do that. It's too expensive for the benefits. I'm impressed by Max and your dedication. > >> butâ¦ in the not so far future the metadata *needs* to change, Iâm sorry. >> Merging in complex project (more than one developer, in fact) can become >> a pain if we do not improve thatâ¦ even with mergetools from Thierry, is >> too complicated). > > The way you say it, I wonder if you understand what the MergeDriver is supposed to solve (and what it isn't). You'll have to say more ;) > > (especially the bit about the merge of large projects/multiple developers being too complicated...) > > Thierry > >> Esteban >> > >

Dec. 1, 2014