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

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by stepharo

This is really cool! Keep pushing that part. Le 1/12/14 17:51, Ben Coman a Ã©crit : > seaside(a)rmod.lille.inria.fr wrote: >> Hi! We're sending this automatic email twice a month, to give the >> community an opportunity to easily know what's happening and to >> coordinate efforts. Just answer informally, and feel free to spawn >> discussions thereafter! >> >> ### Here's what I've been up to since the last WhatsUp: >> > > * Made my first contribution to the VM, adding <modifier> keypress > events for OSX. > > * Refactored class variables and class-side methods of Delay to > instance side of new DelayScheduler. > >> >> ### What's next, until 2014-12-14 (*): >> > > * Change Delays/DelayScheduler base from milliseconds to microseconds, > to fix the commandline issue with "super fast delay" > > * Factor out the mutex interthread synchronisation code and provide > some alternatives (e.g. Semaphore & Spinlock) > >> >> (*) we'll be expecting results by then ;) >> >> > > >

Dec. 2, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by stepharo

We will need a success story soon (well we have a nice baglog of success stories but ....) Le 1/12/14 15:01, phil(a)highoctane.be a Ã©crit : > On Mon, Dec 1, 2014 at 7:00 AM, <seaside(a)rmod.lille.inria.fr > <mailto:seaside@rmod.lille.inria.fr>> wrote: > > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to > coordinate efforts. Just answer informally, and feel free to > spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > > Two commercial installs of a Pharo/Seaside based solution. > Some tweets with the #pharo tag. > > > > ### What's next, until 2014-12-14 (*): > > > More installs. More deals. > Using Mongodb more extensively for one application. > Start of a new application module on business dashboarding. > Documentation of our system writing using Pillar. > CommandLineHandler based tool for console based administration of the > system. > > > > (*) we'll be expecting results by then ;) > >

Dec. 2, 2014

Re: [Pharo-dev] GetOpt

by Torsten Bergmann

>Combined with a small image, it would be a terrific tool. That was/is the goal of Coral. http://rmod.lille.inria.fr/coral/ Dont know about its current state. Thx T.

Dec. 2, 2014

Re: [Pharo-dev] Scale in 3.0 (kind of ANN)

by phil＠highoctane.be

On Tue, Dec 2, 2014 at 11:19 AM, stepharo <stepharo(a)free.fr> wrote: > Indeed and we should build on top of Scale (adding coral syntax). Just no > time for doing it. > Tx phil to port Scale and publish it. > Being forced to deploy and deal with Pharo on X-less servers makes me motivated. :-p Phil > In fact the commandline handler came for Camillo as a first step for Coral. > > Le 2/12/14 10:36, phil(a)highoctane.be a Ã©crit : > > Looks like dead and superseded by the .st handler. > > But this is not coral with classdefs etc. > > Phil > Le 2 dÃ©c. 2014 09:49, "Luc Fabresse" <luc.fabresse(a)gmail.com> a Ã©crit : > >> >> Nice but I would like to know the exact status of Coral because it would >> be bad to restart from scratch. >> >> #Luc >> >> 2014-12-02 8:38 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> >>> I've put Guille's Scale thing ( >>> http://guillep.github.io/blog/2014/01/23/replacing-bash-with-pharo/) >>> into Pharo 3.0 >>> >>> Details on how to use here: >>> >>> http://smalltalkhub.com/#!/~philippeback/Scale >>> >>> Enjoy, >>> Phil >>> >>> >>> >>> >> >

Dec. 2, 2014

Re: [Pharo-dev] SmalltalkHub bugs & hangs :-(

by stepharo

Thanks hilaire. May be we should try to find some time and love to ensure the next 5 years. Le 1/12/14 11:19, Hilaire a Ã©crit : > Hello, > > >From my experience point of view with SmalltlakHub, I found this tool > remarkably stable, useful, feature complete and quite well integrated > with Monticello. > I want to say thank you guys for the energy you spend to keep it running. > > Hilaire > > > > Le 27/11/2014 11:14, Noury Bouraqadi a Ã©crit : >> SmalltalkHub is slow, so donât click too fast :-( >> >> While Iâm grateful to developers of SmalltalkHub and previously >> SqueakSource, I believe as a small community, we cannot afford >> developing everything by ourselves. We donât have enough man-power. We >> can see the symptoms since SmalltalkHub is in beta stage since way too >> long... >> >> Itâs better to use some mainstream platform such as github. >> Weâll we have support for it in Pharo 4? >> >> It would be interesting also from the communication point of view to >> make the world a little bit more aware of Pharo. >> >> Noury >

Dec. 2, 2014

Re: [Pharo-dev] Scale in 3.0 (kind of ANN)

by stepharo

Indeed and we should build on top of Scale (adding coral syntax). Just no time for doing it. Tx phil to port Scale and publish it. In fact the commandline handler came for Camillo as a first step for Coral. Le 2/12/14 10:36, phil(a)highoctane.be a Ã©crit : > > Looks like dead and superseded by the .st handler. > > But this is not coral with classdefs etc. > > Phil > > Le 2 dÃ©c. 2014 09:49, "Luc Fabresse" <luc.fabresse(a)gmail.com > <mailto:luc.fabresse@gmail.com>> a Ã©crit : > > > Nice but I would like to know the exact status of Coral because it > would be bad to restart from scratch. > > #Luc > > 2014-12-02 8:38 GMT+01:00 phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>>: > > I've put Guille's Scale thing > (http://guillep.github.io/blog/2014/01/23/replacing-bash-with-pharo/) > into Pharo 3.0 > > Details on how to use here: > > http://smalltalkhub.com/#!/~philippeback/Scale > <http://smalltalkhub.com/#%21/%7Ephilippeback/Scale> > > Enjoy, > Phil > > > >

Dec. 2, 2014

Re: [Pharo-dev] GetOpt

by phil＠highoctane.be

Well, after looking at the command line handlers in the image for the way options are handled, I was of opinion that I wanted something like getopt. So, I looked around and found that implementation of Ian that I plugged into the CommandLineArguments in my activate methods. I like the dictionary + block approach I have quite a couple commands (like --create-user -u xxx -p xxx -e xxx -n xxx -g xxx) and it was a pain to write the options parsing. So, something like this in my XXToolsCommandLineHandler activate ... self activateCreateUser ... activateCreateUser GetOpt new at: $u put: [ :opt :arg | userName := arg ]; at: $p put: [ :opt :arg | ... ]; at: $e put: [ :opt :arg | ... ]; at: $n put: [ :opt :arg | ... ]. at: $g put: [ :opt :arg | ... ]; parse: self arguments. "wrapped in some error handling" XXTools makeUserNames: userName ... No more need to dig into a number of isXXXX methods and optionAt:... I think we should make this work with more integration etc but I have other fish to fry at the moment and this works well for me. We need more doc on the CommandLineHandlers but it is a fantastic piece of Pharo! Combined with a small image, it would be a terrific tool. I am investing some time on those CLI things as I need them for servers and even if Bash is cool for some things, Pharo is better in terms of cleanliness. One factor is the time taken for loading the image. Maybe should we look into something like a pharod, a daemon that would just run scripts and a lightweight CLI tool that would pass the scripts to it. Something like: http://www.martiansoftware.com/nailgun/ I think we could steal their C client right away/ Phil On Tue, Dec 2, 2014 at 10:17 AM, stepharo <stepharo(a)free.fr> wrote: > Can you just tell me a bit more :) > > Le 2/12/14 08:45, phil(a)highoctane.be a Ã©crit : > >> I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 >> >> See: >> >> http://www.smalltalkhub.com/#!/~philippeback/GetOpt < >> http://www.smalltalkhub.com/#%21/%7Ephilippeback/GetOpt> >> >> Nice tool even if we have some other support in CommandLineHandlers. >> But for a quick parameters setting in your own CommandLineHandler, it is >> fast to use and easy to debug. >> >> Phil >> >> >> >> > >

Dec. 2, 2014

Re: [Pharo-dev] GetOpt

by Christophe Demarey

See https://en.wikipedia.org/wiki/Getopt Le 2 dÃ©c. 2014 Ã 10:17, stepharo a Ã©crit : > Can you just tell me a bit more :) > > Le 2/12/14 08:45, phil(a)highoctane.be a Ã©crit : >> I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 >> >> See: >> >> http://www.smalltalkhub.com/#!/~philippeback/GetOpt <http://www.smalltalkhub.com/#%21/%7Ephilippeback/GetOpt> >> >> Nice tool even if we have some other support in CommandLineHandlers. >> But for a quick parameters setting in your own CommandLineHandler, it is fast to use and easy to debug. >> >> Phil >> >> >> > >

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by Santiago Bragagnolo

Great!! I am sooo happy, we are moving forward! 2014-12-02 10:41 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Cool > > > On 02 Dec 2014, at 09:48, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > Hi, > > > > We changed the default fonts in Pharo for the ones that are used > normally in Moose. > > They are: Source Sans Pro and Source Code Pro. > > We needed to do it for several reasons: > > > > 1) TxText (the new text model) is cairo based, and cairo just can work > with real fonts, so we need them as default (now we will be able to > integrate TxText and start the replace of old editors) > > 2) Current fonts takes too much space and do not scales fine (at least > that Iâve been told) > > > > So, well, thatâ¦ you will see âsomething differentâ when you download > latest image version :) > > > > cheers, > > Esteban > > > > > > >

Dec. 2, 2014

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

by Santiago Bragagnolo

Hi Cedric, thanks. As far as i know, (im not quite versed on DDP), DDP starts with the base that you have data distributed, and that you have kind of actors or RPC arhitecture. That means that you will call methods to remote servers, and that may cause changes. That changes will be notified to subscriptors, like this you can replicate the data or do what ever you want with the changes. In the design of an application, your services interact by sending messages, and everyone can be noticed by the notifications. In DDS you send, commonly, the output of your processing, hoping someone will use it for something. No one needs to understand anything about your implementation and the system keeps working with your process or without (meanwhile is not the master, weakpoint). A cool metaphor may be that DDP is like a ford assembly line, DDS is like a powerline or network. i hope it helps you 2014-12-02 10:31 GMT+01:00 CÃ©drick BÃ©ler <cdrick65(a)gmail.com>: > This is excellent :) > > I just wonder how it compare to DDP (Data Distribution Protocol) wich > seems > https://meteorhacks.com/introduction-to-ddp.html > http://en.wikipedia.org/wiki/Distributed_Data_Protocol > ruby client: https://github.com/tmeasday/ruby-ddp-client > > Thans by the way, Iâll try Simple DDS. > > Cheers, > > CÃ©drick > > Le 2 dÃ©c. 2014 Ã 09:16, Luc Fabresse <luc.fabresse(a)gmail.com> a Ã©crit : > > > This is great. > Fo info, DDS is a standardized MOM middleware heavily used in industrial > apps with multiple concrete implementations such as > http://www.prismtech.com/opensplice. > And one of these implementations will be the next backend of ROS and > therefore needed in PhaROS. > Thx Santiago! > > #Luc > > 2014-12-02 0:44 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > >> 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. 2, 2014