January 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] Fonts in Pharo By Example

by Sean P. DeNigris

It would be great to have a section in PBE2 about fonts. I find them very confusing - TrueType, FreeType, Logical, etc. Understanding how they're handled in Pharo requires background knowledge, and an overview and a few specific examples could really do some good. Cheers, Sean -- View this message in context: http://forum.world.st/Fonts-in-Pharo-By-Example-tp4664406.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 21, 2013

Re: [Pharo-project] [ANN] Headless support for Cog Cocoa VM

by Mariano Martinez Peck

On Sat, Jan 19, 2013 at 1:08 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Mariano Martinez Peck wrote > > thanks Square [i] International <http://www.square-i.net/> > > ... headless support will be included in the official Pharo > > VM and will be, therefore, accessible to everybody. > > Yes, thank you, thank you!! I've been using Pharo for Jenkins build > scripts, > and it was really disruptive to see the image pop up every time a job > started. > > As to the flag limitation, I think for now I'll have two copies of the VM - > a headful one, which will be the default on my Mac, and one with the > headless flag set, that gets explicitly launched by Jenkins... not perfect, > but a HUGE step!! > Yes, that's the easiest way. I spent *a lot* of time trying to find another way, but they all failed. There is one possibility that should work but it is too hacky for me: very at the beginning of the VM (before starting Cocoa) read the arguments. If "-headless" is present, then programmatically set/write the flag in the Info.plist. If it it not, do nothing (or set it to false). But modifying the file on startup looks hacky to me. I prefer the user to manually set it. > Cheers, > Sean > > > > -- > View this message in context: > http://forum.world.st/ANN-Headless-support-for-Cog-Cocoa-VM-tp4664137p46642… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Jan. 21, 2013

Re: [Pharo-project] [ANN] Headless support for Cog Cocoa VM

by Mariano Martinez Peck

On Sat, Jan 19, 2013 at 12:08 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sat, Jan 19, 2013 at 10:40 AM, Ciprian Teodorov < > ciprian.teodorov(a)gmail.com> wrote: > >> Hi Mariano, >> >> on MacOS 10.6.8 doing ./CogVM-release-noflash-noArgs.app/Contents/MacOS/CogVM >> Pier3.image does not work, I get Illegal instruction... >> the same with ./CogVM-release-noflash-noArgs.app/Contents/MacOS/CogVM >> --headless Pier3.image >> >> if i try using open CogVM-release-noflash-noArgs.app Pier3.image, it >> works but It's not headless, however when looking in the info.plist the key >> you have mentioned is there >> <key>LSBackgroundOnly</key> >> <true/> >> >> > Well, this one is weird ;) I think the problem is (as Mark pointed out) > the "open". When you do: > > open CogVM-release-noflash-noArgs.app Pier3.image > > I will (I think) do two things: > - open the CogVM-release-noflash-noArgs.app (which will popup the window > to choose an image) > - open the Pier3.image with the default app associated (that would be the > same as double clicking the .image from the finder) > > So, I think that what you need is to add the "-a": > > open -a CogVM-release-noflash-noArgs.app Pier3.image > > In this case, you should at least get the same behavior as: > > ./CogVM-release-noflash-noArgs.app/Contents/MacOS/CogVM Pier3.image > > that is, a ilegal instruction. Is it like this? > > Now...why the ilegal instruction?? I don't know. I will check. I could be > maybe what I said that I compiled with LLVM GCC. > We should compile this VM with GNU GCC...but so far I couldn't in 10.8.2 > :( > > Well, I have compiled a normal VM (without my headless changes) with LLVM GCC. Now, can you try this VM (CogVM-standard) please? If we get Ilegal Instruction, then it is the compiler. If we don't, and it works, then it is something related with my changes. https://www.dropbox.com/s/kpqnfycjpe76fo1/CogVM-standard.zip Thanks, > Thanks for the testing to everybody!!! > > >> >> On Sat, Jan 19, 2013 at 2:26 PM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> >>> >>> On Sat, Jan 19, 2013 at 7:24 AM, Stephan Eggermont <stephan(a)stack.nl>wrote: >>> >>>> This doesn't work >>>> >>>> >>>> open CogVM-release-noflash-noArgs.app Pier3.image & >>>> >>>> >>> Which OSX version are you using? >>> >>> >>> >>>> >>>> Jan 19 11:20:51 Stephan-Eggermonts-iMac >>>> [0x0-0x2f92f9].org.seaside-project[36832]: This interpreter (vers. 6502) >>>> cannot read image file (vers. 6505). >>>> Jan 19 11:20:51 Stephan-Eggermonts-iMac >>>> [0x0-0x2f92f9].org.seaside-project[36832]: Press CR to quit... >>>> Jan 19 11:20:52 Stephan-Eggermonts-iMac ReportCrash[36836]: Failed to >>>> create CSSymbolicatorRef for launchd >>>> Jan 19 11:20:52 Stephan-Eggermonts-iMac >>>> com.apple.launchd.peruser.501[207] >>>> ([0x0-0x2fa2fa].org.squeakfoundation.Squeak[36835]): Job appears to have >>>> crashed: Segmentation fault >>>> Jan 19 11:20:52 Stephan-Eggermonts-iMac ReportCrash[36836]: Saved crash >>>> report for launchd[36835] version ??? (???) to >>>> /Users/stephan/Library/Logs/DiagnosticReports/launchd_2013-01-19-112052_Stephan-Eggermonts-iMac.crash >>>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> >> >> >> -- >> Dr. Ciprian TEODOROV >> IngÃ©nieur DÃ©veloppement CAO >> >> tÃ©l : 06 08 54 73 48 >> mail : ciprian.teodorov(a)gmail.com >> www.teodorov.ro >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

Jan. 21, 2013

Re: [Pharo-project] zero conf build

by Camillo Bruni

which script did you use? so I can check locally. On 2013-01-21, at 08:24, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I am looking to setup a Moose job based on zero conf. > > However, when I execute the vm.sh on Ubuntu I get an error: > CogVM: /lib32/libc.so.6: version `GLIBC_2.15' not found > > I already installed lib32. What else should I do? > > Cheers, > Doru > > > On Oct 23, 2012, at 7:11 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Very cool ! >> >> Thanks a lot for all the work. >> >> On 23 Oct 2012, at 00:28, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> I finally managed to create a zero conf pharo image build setup: >>> >>> # =========================================================================== >>> curl http://pharo.gforge.inria.fr/ci/ciPharo20Cog.sh | sh >>> ./vm.sh Pharo.image save $JOB_NAME >>> >>> REPO=http://smalltalkhub.com/mc/dh83/nabujito/main >>> ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfNabujito --install=development >>> ./vm.sh $JOB_NAME.image test --junit-xml-output Nabujito >>> >>> zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes >>> # =========================================================================== >>> >>> ./ciPharo20Cog.sh --help >>> >>> This is an entry point script for any Pharo image CI >>> This script will download the latest Pharo 2.0 image and the latest VM >>> >>> Result in the current directory: >>> vm directory containing the VM >>> vm.sh script forwarding to the VM inside vm/ >>> Pharo.image The latest pharo image >>> Pharo.changes The corresponding pharo changes" >>> >>> # =========================================================================== >>> >>> have fun! >> >> > > -- > www.tudorgirba.com > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > >

Jan. 21, 2013

Re: [Pharo-project] [Ann] New version of Mocketry

by Esteban Lorenzano

Thanks Denis :) On Jan 20, 2013, at 7:08 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello. > > I upload new version of Mocketry 2.1 to smalltalkhub http://www.smalltalkhub.com/#!/~dionisiy/Mocketry . > > Changes: > > 1) All code now migrated to smalltalkhub repository. New configuration with version 2.1 implemented accordingly. > 2) State specs extracted to separate project "StateSpecs" with separate configuration. This project contains all object state specifications and validation stuff. Mocketry depends on it and only implements behaviour specs and mock objects. StateSpecs can be used in different projects. I use it in Presenty to describe data fields validness. > 3) Main new feature is stub behaviour. You can teach mock for stubs with: > mock stub someMessage willReturn: 'result' > And then mock can receive #someMessage everywhere anytimes. So you don't need scenario block if you only need stubs behaviour. > 4) Few state specs like > dictionary should include: item at: #key > > It will be cool if Mocketry become part of Pharo tools. What I can do for this? > Mock objects to me is main tool to design and implement flexible object systems. And Mocketry simplifies mock objects technique very much. > > Best regards, > Denis > >

Jan. 21, 2013

[Pharo-project] DocTest

by Benjamin

Hi guys, I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) Ben [1]http://docs.python.org/2/library/doctest.html

Jan. 21, 2013

Re: [Pharo-project] zero conf build

by Tudor Girba

Hi, I am looking to setup a Moose job based on zero conf. However, when I execute the vm.sh on Ubuntu I get an error: CogVM: /lib32/libc.so.6: version `GLIBC_2.15' not found I already installed lib32. What else should I do? Cheers, Doru On Oct 23, 2012, at 7:11 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Very cool ! > > Thanks a lot for all the work. > > On 23 Oct 2012, at 00:28, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> I finally managed to create a zero conf pharo image build setup: >> >> # =========================================================================== >> curl http://pharo.gforge.inria.fr/ci/ciPharo20Cog.sh | sh >> ./vm.sh Pharo.image save $JOB_NAME >> >> REPO=http://smalltalkhub.com/mc/dh83/nabujito/main >> ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfNabujito --install=development >> ./vm.sh $JOB_NAME.image test --junit-xml-output Nabujito >> >> zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes >> # =========================================================================== >> >> ./ciPharo20Cog.sh --help >> >> This is an entry point script for any Pharo image CI >> This script will download the latest Pharo 2.0 image and the latest VM >> >> Result in the current directory: >> vm directory containing the VM >> vm.sh script forwarding to the VM inside vm/ >> Pharo.image The latest pharo image >> Pharo.changes The corresponding pharo changes" >> >> # =========================================================================== >> >> have fun! > > -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Jan. 21, 2013

[Pharo-project] Must OSPlatform class>>osVersion be deprecated?

by David T. Lewis

Why is OSPlatform class>>osVersion deprecated but OSPlatform class>>platformName is not? My suggestion would be to comment #osVersion as being a synonym for #version, but do not deprecate it. That would enable use of "Smalltalk os version", and it would also support "OSPlatform osVersion", both of which make logical sense. It would also maintain support for external packages that rely on #osVersion to figure out platform differences. The reason that I am asking is that I am trying to find a way to make OSProcess class>>osVersion work on Pharo 2.0, Pharo1.x, and the various versions of Squeak and Cuis. I quite honestly cannot figure out any way to add Pharo 2.0 without breaking one more more of the other supported images. If OSPlatform class>>osVersion did not raise a deprecation warning, then I could make it work. Thanks, Dave

Jan. 21, 2013

Re: [Pharo-project] where can I find the latest athens?

by Camillo Bruni

You should not even have to ask for it ;) https://ci.inria.fr/rmod/job/Athens/ On 2013-01-20, at 16:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Because I want to try boids. > > Stef >

Jan. 20, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Denis Kudriashov

I uploaded new version with refactored layout code and new tests. TxText tests now uses Mocketry framework. I very hope you will enjoy it. Mock objects to me is main tool to design and implement flexible object systems. And Mocketry simplifies mock objects technique very much. See announcement about new version of Mocketry. Best regards Denis 2013/1/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > This is really nice. > Tristan started to look at what you are doing because we proposed him to > enhance textModel as part of an internship with us. > > Stef > > On Jan 18, 2013, at 9:30 PM, Denis Kudriashov wrote: > > > Hello. > > > > I publish configuration at TxText repository based on proposed > repackaging. > > > > 2013/1/15 Camillo Bruni <camillobruni(a)gmail.com> > > > > On 2013-01-15, at 12:44, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > > > Yes. > > > I want to do it. But today I busy. Tomorrow I hope I can make it. > > > > no hurry :) I set up the jenkins build, it will trigger as soon as you > push the configuration :) > > > > > I actually want to split package to TxText-Model, TxText-Layout, > TxText-UI, > > > TxTextTests-Model, TxTextTests-Layout > > > > nice! > > > > >

Jan. 20, 2013