- Pharo-dev - lists.pharo.org

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

by Santiago Bragagnolo

wow. is amazing. 2014-12-02 14:46 GMT+01:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > > all shells are not named *sh > for example, I really would love to have Xiki ( > http://xiki.org/screencasts/) in Pharo ;-) > > #Luc > > 2014-12-02 14:17 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > On Tue, Dec 2, 2014 at 1:47 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> > Am 02.12.2014 um 13:31 schrieb Ben Coman <btc(a)openinworld.com>: >>> > >>> > phil(a)highoctane.be wrote: >>> >> 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 >>> > >>> > >>> > > We named the command we needed scale, because scales are in shells, >>> > > it sounded nice. >>> > >>> > Nice lateral thinking, but it seems like a stretch :) >>> > >>> > For making a shell, why not something simple in the tradition of sh, >>> bash, csh, ksh, psh? e.g. pharosh or phsh? >>> > >>> +1 >>> >> >> Scale is what it was. There is also Coral, so, well, marine names are >> staying. >> >> If we want a 'sh', what about: >> >> phish >> phash >> phosh >> >> psh is not too bad after all. >> pharosh looks cool too. >> >> With "phish" we can say, "I am phishing" in the same vein as "I am >> bashing". >> >> Phil >> >> >> >>> >>> Norbert >>> >>> >>> >> >

Dec. 2, 2014

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

by Luc Fabresse

all shells are not named *sh for example, I really would love to have Xiki (http://xiki.org/screencasts/) in Pharo ;-) #Luc 2014-12-02 14:17 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > On Tue, Dec 2, 2014 at 1:47 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> > Am 02.12.2014 um 13:31 schrieb Ben Coman <btc(a)openinworld.com>: >> > >> > phil(a)highoctane.be wrote: >> >> 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 >> > >> > >> > > We named the command we needed scale, because scales are in shells, >> > > it sounded nice. >> > >> > Nice lateral thinking, but it seems like a stretch :) >> > >> > For making a shell, why not something simple in the tradition of sh, >> bash, csh, ksh, psh? e.g. pharosh or phsh? >> > >> +1 >> > > Scale is what it was. There is also Coral, so, well, marine names are > staying. > > If we want a 'sh', what about: > > phish > phash > phosh > > psh is not too bad after all. > pharosh looks cool too. > > With "phish" we can say, "I am phishing" in the same vein as "I am > bashing". > > Phil > > > >> >> Norbert >> >> >> >

Dec. 2, 2014

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

by phil＠highoctane.be

On Tue, Dec 2, 2014 at 1:47 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 02.12.2014 um 13:31 schrieb Ben Coman <btc(a)openinworld.com>: > > > > phil(a)highoctane.be wrote: > >> 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 > > > > > > > We named the command we needed scale, because scales are in shells, > > > it sounded nice. > > > > Nice lateral thinking, but it seems like a stretch :) > > > > For making a shell, why not something simple in the tradition of sh, > bash, csh, ksh, psh? e.g. pharosh or phsh? > > > +1 > Scale is what it was. There is also Coral, so, well, marine names are staying. If we want a 'sh', what about: phish phash phosh psh is not too bad after all. pharosh looks cool too. With "phish" we can say, "I am phishing" in the same vein as "I am bashing". Phil > > Norbert > > >

Dec. 2, 2014

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

by CÃ©drick BÃ©ler

Thanks Santiago, I think this is a decent comparison. I also found these bits of information regarding the question: https://groups.google.com/forum/#!topic/meteor-core/BNfHzNFGAHQ <https://groups.google.com/forum/#!topic/meteor-core/BNfHzNFGAHQ> Now time to try out :) Cheers, CÃ©drick > Le 2 dÃ©c. 2014 Ã 00:44, Ben Coman <btc(a)openInWorld.com> a Ã©crit : > > 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

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

by Nicolai Hess

2014-12-02 13:36 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Esteban, > > Did you look/read what Juraj Kubelka did ? > > Like this issue, but there are others too: > > https://pharo.fogbugz.com/f/cases/13967 > https://pharo.fogbugz.com/default.asp?14048#110249 and cleanupForRelease reinitialize the font providers. > > I vaguely remember he found something wrt initialization, maybe Marcus > remembers. > > Sven > > > On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > â¦ and I lost fonts again :( > > I made an integration and fonts got lostâ¦ Iâm reviving issue, and > working on it :( > > > > Esteban > > > >> On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >>> > >>> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> > >>>> > >>>> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >>>> > >>>> > >>>>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>>>> > >>>>> There is no Source Code Sans :). There is only "Source Sans Pro" or > "Source Code Pro". > >>>> > >>>> Yes, right now in the latest 4.0. > >>>> > >>>> But there used to be a different one, that is the one I am using, see > screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't > remember where I got it from (Igor is the author), but I have been using it > for months. > >>> > >>> no, it was me the authorâ¦ and it was a mistake I made first time > thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ > I was even thinking on create a âFont Repositoryâ where put different > fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts > which is a cool repo, but does not works completely along our versionâ¦ we > will need to merge :P) > >> > >> Maybe it would be even better if there was code in the image to make > these embedded fonts yourself (or a comment). > >> > >>>> My question was, why choose one above the other ? > >>> > >>> I replaced it with the Source Sans Pro because same family fonts works > better together (Source * Pro) > >> > >> OK. It seems to have a smaller width, we'll see. > >> > >>> cheers, > >>> Esteban > >>> > >>>> > >>>> <Screen Shot 2014-12-02 at 11.57.13.png> > >>>> > >>>>> > >>>>> Doru > >>>>> > >>>>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >>>>> What is the difference between 'Open Sans' and 'Source Code Sans' ? > >>>>> > >>>>> I am using the former in my 3.0 image, and I like it a bit more, it > seems a bit wider. > >>>>> > >>>>>> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>>>>> > >>>>>> Great! > >>>>>> > >>>>>> Doru > >>>>>> > >>>>>> p.s. Finally :) > >>>>>> > >>>>>> > >>>>>> On Tue, Dec 2, 2014 at 9:48 AM, 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 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> www.tudorgirba.com > >>>>>> > >>>>>> "Every thing has its own flow" > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> www.tudorgirba.com > >>>>> > >>>>> "Every thing has its own flow" > > > > >

Dec. 2, 2014

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

by Norbert Hartl

> Am 02.12.2014 um 13:31 schrieb Ben Coman <btc(a)openinworld.com>: > > phil(a)highoctane.be wrote: >> 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 > > > > We named the command we needed scale, because scales are in shells, > > it sounded nice. > > Nice lateral thinking, but it seems like a stretch :) > > For making a shell, why not something simple in the tradition of sh, bash, csh, ksh, psh? e.g. pharosh or phsh? > +1 Norbert

Dec. 2, 2014

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

by Sven Van Caekenberghe

Esteban, Did you look/read what Juraj Kubelka did ? Like this issue, but there are others too: https://pharo.fogbugz.com/f/cases/13967 I vaguely remember he found something wrt initialization, maybe Marcus remembers. Sven > On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > â¦ and I lost fonts again :( > I made an integration and fonts got lostâ¦ Iâm reviving issue, and working on it :( > > Esteban > >> On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> >>>> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> >>>>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". >>>> >>>> Yes, right now in the latest 4.0. >>>> >>>> But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't remember where I got it from (Igor is the author), but I have been using it for months. >>> >>> no, it was me the authorâ¦ and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our versionâ¦ we will need to merge :P) >> >> Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment). >> >>>> My question was, why choose one above the other ? >>> >>> I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) >> >> OK. It seems to have a smaller width, we'll see. >> >>> cheers, >>> Esteban >>> >>>> >>>> <Screen Shot 2014-12-02 at 11.57.13.png> >>>> >>>>> >>>>> Doru >>>>> >>>>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> What is the difference between 'Open Sans' and 'Source Code Sans' ? >>>>> >>>>> I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider. >>>>> >>>>>> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>>> >>>>>> Great! >>>>>> >>>>>> Doru >>>>>> >>>>>> p.s. Finally :) >>>>>> >>>>>> >>>>>> On Tue, Dec 2, 2014 at 9:48 AM, 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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Every thing has its own flow" >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >

Dec. 2, 2014

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

by Ben Coman

phil(a)highoctane.be wrote: > 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 > > > > We named the command we needed scale, because scales are in shells, > it sounded nice. Nice lateral thinking, but it seems like a stretch :) For making a shell, why not something simple in the tradition of sh, bash, csh, ksh, psh? e.g. pharosh or phsh?

Dec. 2, 2014

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

by Tudor Girba

Thanks, Esteban. This kind of work is too under appreciated. Cheers, Doru On Tue, Dec 2, 2014 at 1:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > â¦ and I lost fonts again :( > I made an integration and fonts got lostâ¦ Iâm reviving issue, and working > on it :( > > Esteban > > On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > There is no Source Code Sans :). There is only "Source Sans Pro" or > "Source Code Pro". > > > Yes, right now in the latest 4.0. > > But there used to be a different one, that is the one I am using, see > screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't > remember where I got it from (Igor is the author), but I have been using it > for months. > > > no, it was me the authorâ¦ and it was a mistake I made first time thatâs > why I removed it (but I can package it and put it somewhere anywayâ¦ I was > even thinking on create a âFont Repositoryâ where put different fonts, > until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is > a cool repo, but does not works completely along our versionâ¦ we will need > to merge :P) > > > Maybe it would be even better if there was code in the image to make these > embedded fonts yourself (or a comment). > > My question was, why choose one above the other ? > > > I replaced it with the Source Sans Pro because same family fonts works > better together (Source * Pro) > > > OK. It seems to have a smaller width, we'll see. > > cheers, > Esteban > > > <Screen Shot 2014-12-02 at 11.57.13.png> > > > Doru > > On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > What is the difference between 'Open Sans' and 'Source Code Sans' ? > > I am using the former in my 3.0 image, and I like it a bit more, it seems > a bit wider. > > On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Great! > > Doru > > p.s. Finally :) > > > On Tue, Dec 2, 2014 at 9:48 AM, 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 > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 2, 2014

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

by Esteban Lorenzano

â¦ and I lost fonts again :( I made an integration and fonts got lostâ¦ Iâm reviving issue, and working on it :( Esteban > On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> >>> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> >>>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". >>> >>> Yes, right now in the latest 4.0. >>> >>> But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't remember where I got it from (Igor is the author), but I have been using it for months. >> >> no, it was me the authorâ¦ and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our versionâ¦ we will need to merge :P) > > Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment). > >>> My question was, why choose one above the other ? >> >> I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) > > OK. It seems to have a smaller width, we'll see. > >> cheers, >> Esteban >> >>> >>> <Screen Shot 2014-12-02 at 11.57.13.png> >>> >>>> >>>> Doru >>>> >>>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> What is the difference between 'Open Sans' and 'Source Code Sans' ? >>>> >>>> I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider. >>>> >>>>> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Great! >>>>> >>>>> Doru >>>>> >>>>> p.s. Finally :) >>>>> >>>>> >>>>> On Tue, Dec 2, 2014 at 9:48 AM, 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 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow"

Dec. 2, 2014