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

[pharo-project/pharo-core] f3bc5a: 40395

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f3bc5a00b9026073cc5b13dee681a9b53b10da06 https://github.com/pharo-project/pharo-core/commit/f3bc5a00b9026073cc5b13de… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-02 (Tue, 02 Dec 2014) Changed paths: M EmbeddedFreeType-Tests.package/EmbeddedFreeTypeFontInstallerTest.class/instance/tests/testinstallAllFontsIn.st M FreeType.package/FreeTypeFontProvider.class/instance/loading and updating/updateEmbeddedFreeTypeFonts.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script395.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40395.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40395 14553 FreeType default fonts not correctly loaded when image initializes https://pharo.fogbugz.com/f/cases/14553 http://files.pharo.org/image/40/40395.zip

Dec. 2, 2014

[pharo-project/pharo-core]

by GitHub

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

Dec. 2, 2014

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

by Luc Fabresse

yes I know I will try to put a student on it but I must get a good one ;-) #Luc 2014-12-02 14:53 GMT+01:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com >: > 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] SmalltalkHub bugs & hangs :-(

by HernÃ¡n Morales Durand

2014-12-02 6:22 GMT-03:00 kilon alios <kilon.alios(a)gmail.com>: > "I prefer the Smalltalk environment." > > so do I > > "Sorry, if that would be true then Java or C# would be of extraordinary > quality. > Smalltalk has been there for more than 30 years and will probably another > 30 years. > Hypes come and go. Quantity for me seems more like the opposite of > quality." > > True ? Smalltalk cannot even begin to compete with the tools and library > support of these two behemoths programming languages. That does not mean > Java is not ugly or that some of the complain people have with it are not > valid and justified complains but still does not change the fact that > because of the size of the community it has produced a lot more top quality > libraries and tools than any programming language. The "quantity brings > quality" is not just a computer world rule its pretty much the fabric of > our cosmos that through failures and bad designs more elegant and beautiful > , sophisticate designs emerge. Its something that has been happening for > billions of years and I doubt will change any time soon. > > Developers in Smalltalk community have higher standards for quality. What is perceived as a quality product in Python, Java or C# is not perceived the same for seasoned Smalltalk developers. On the other side, you should measure and compare the ratio of created OSS in Java projects versus which of them are viewed as "quality" and by whom. Of course Java has hundreds of libraries but when you go down to details many of them are not really well designed (for example try to adapt just one quality library - cited by hundreds of scientific papers - made for processing human genomes to other organisms, try to extend with new visualizations as Alex is doing with Roassal). > "Why shouldn't they be able to die? > > products that can be used by everybody. Alas for your work needs their > operating systems get worse with every release. > Windows XP and Snow Leopard are being seen as the best versions by some... > > Nothing lasts forever so you can be sure that Windows and Mac OSX will die > some day." > > Win XP is the crappiest OS I ever used win 7 dances around it , its still > old crappy windows but way way better. Yosemite has its share of issues but > for me so far with the excepetion of problematic CUDAS drivers, had no > issues at all with it. I use also UBUNTU 14.04 it offers better support for > my system and works like a charm. I seriously dont see this "OS get worse > thing". Will one day those OS die ? sure but I doubt I will be alive so > there is no reason for me to worry about it. > > > "That's also possible in capitalism: you can ask very high prices so most > people and companies cannot (or will not) be able to affort it" > > I am not going to debate capitalism and its problems, of course I agree > that huge companies care only about making money and not for the well being > of the consumers. This is why I am here , this is why I support open source > and this is why I support Pharo but I cant just turn zealot and refuse the > usefulness and expertise of much commercial software out there. All I said > is that if there is demand there is going to be supply. Everybody wants to > make money and this is why when and if a software dies it gets replaced by > something else often better alternative. > > "For me Smalltalk is a system and not a simple language with some > arbitrary tools that can be replaced easily." > > Its not as hard as you may think to kinda emulate Smalltalk with other > programming languages. Actually Pharo has some fierce competition out there > as languages are more and more interested into live coding and creating an > enviroment for the developer. Smalltalk still has the edge on this because > it had an early start but if the example of Swift is any indication its > definetly a lesson that languages have not any issue catching up with the > Smalltalk world. > > The question is not if but when other languages come side by side with the > abilities of Pharo how you keep pharo developers with pharo ? I think the > only answer is by making sure Pharo remains fresh , modern and in sync with > modern technology. Git is just a small part of the equation. On the other > hand you need also , what Pharo already does to a great extend, innovation > to bring new more developers. So I think the right balance is "give > something new but also allow me to use my old familiar tools". I am very > glad that people behind Pharo realise and materialse this balance. > > On Mon, Dec 1, 2014 at 9:46 PM, Esteban A. Maringolo <emaringolo(a)gmail.com > > wrote: > >> >>> My comment was not about discussing the pros and cons of closed versus >>> open source software. My concerns are more about reliability. >>> For me it's totally Ok to use git for versioning IF the tools are there. >>> Squak and Pharo have decent versioning systems that suit their internal >>> needs. There is room for improvements, that's for sure. >>> For me Smalltalk is a system and not a simple language with some >>> arbitrary tools that can be replaced easily. >>> >>> >> The problem is whether the tools you choose for "commoditized" tasks >> (e.g. SCM) limit the amount of manpower that could contribute to your open >> source project. >> >> Forks and pull-requests are the way most open source projects fix bugs >> and integrates enhancements. You can't do branching with current tooling >> (read: Monticello) without suffering proportional to its complexity. >> >> No one said tools can be replaced easily, and that's the reason we still >> use Monticello, some of us backed by old mcz files, others already using >> some git behind it. >> >> Regards, >> >> >> >> > >

Dec. 2, 2014

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

by Juraj Kubelka

I am not sure if I follow the discussion, but next week I am planning to extract embedded fonts and make a new embedded provider. The current solution I have made recently is too tight, there are cyclic dependencies between free font type provider and embedded fonts and it causes problems. Cheers, Juraj > On Dec 2, 2014, at 9:36 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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 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