- Pharo-dev - lists.pharo.org

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

by Esteban Lorenzano

> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Great! > > Doru > > p.s. Finally :) yeah, it took far too much time :( > > > On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@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 <http://www.tudorgirba.com/> > > "Every thing has its own flow"

Dec. 2, 2014

Re: [Pharo-dev] GetOpt

by Esteban Lorenzano

> On 02 Dec 2014, at 11:24, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Combined with a small image, it would be a terrific tool. > > That was/is the goal of Coral. http://rmod.lille.inria.fr/coral/ <http://rmod.lille.inria.fr/coral/> afaik the goal of coral was/is what âscaleâ is trying also to doâ¦ the getopt library is just a command line parser :) Esteban > > Dont know about its current state. > > Thx > T. >

Dec. 2, 2014

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

by Tudor Girba

There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". 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] default fonts changed in Pharo 4.0

by Sven Van Caekenberghe

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"

Dec. 2, 2014

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

by Tudor Girba

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"

Dec. 2, 2014

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