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

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

by Mariano Martinez Peck

On Tue, Jan 22, 2013 at 1:19 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > yeah, I declare my self guilty for having that incredibly ugly idea... :) > > heheheheh :) As you see (and I thanked in the email) Esteban has been helping me here. And then he will merge and integrate :) > On Jan 21, 2013, at 3:35 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > 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 > > > -- Mariano http://marianopeck.wordpress.com

Jan. 22, 2013

Re: [Pharo-project] [Issue Tracker] Status

by Sean P. DeNigris

FixToInclude: http://code.google.com/p/pharo/issues/detail?id=7207 -- View this message in context: http://forum.world.st/Issue-Tracker-Status-tp4664590p4664606.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 22, 2013

Re: [Pharo-project] Closing unresolved issues

by StÃ©phane Ducasse

Thanks for your feedback. Sean and I understand your frustration. The problem is what do we do if we have many bugs with nobody looking at them. > For example... > Issue 5656: Large fonts make tools slow > http://code.google.com/p/pharo/issues/detail?id=5656 > > This issue has not been resolved, but the issue was closed, leading to this > experience... > - I just upgraded a project to 2.0 > - I notice that the UI is very slow - a simple Spec dialog window with a few > text fields and buttons takes ~4 seconds to open > - I check the issue tracker because I remember I reported the bug already, > but I don't find it in the open issues > - I waste time because I think it must be something else > - I finally expand my search through the issues and find my report was > closed as invalid > > I'm not saying that this is wrong, just that I don't understand and want to > share another perspective and come to the best solution... What benefit are > we getting from closing these that is significant enough to justify this > kind of experience (I'm sure I'm not the only one). > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/Closing-unresolved-issues-tp4664420.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 22, 2013

Re: [Pharo-project] Fonts in Pharo By Example

by StÃ©phane Ducasse

On Jan 21, 2013, at 11:57 AM, Sean P. DeNigris wrote: > 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. If somebody explain it It would be great. I always wanted to read something on fonts but unfortunately I feel a bit alone on the writing side This is why I love the attitude of sven to produce doc. Stef > > 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. 22, 2013

Re: [Pharo-project] DocTest

by StÃ©phane Ducasse

it would be nice to introduce the same syntax than Sunit exp assert: exp2 [ exp ] shouldraise: Stef On Jan 21, 2013, at 4:41 AM, Benjamin wrote: > 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. 22, 2013

Re: [Pharo-project] Object>>#name

by Mariano Martinez Peck

Hi Sven. Yes, as far as I remember, Object>>name was safe to remove. Not likewise Class>>name but ok, it is less likely final users will need class side #name. So +1 to removing instance side #name. On Mon, Jan 21, 2013 at 3:43 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Many people have hit the fact that Object implements #name, which then > seems to conflict with some other class where one would really like to use > name as an instance variable and thus accessor. > > Turns out that it seems that Object>>#name is actually not used (anymore). > > I just put a halt in it and tried a couple of tools and everything seems > to work just fine. > > The comment talks about Inspector use, but there is > #defaultLabelForInspector for that. > > It is a small thing, but it confuses everybody for no good reason, > > Any comments ? > > Sven > > PS: it was also in the testing procotol ;-) > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > -- Mariano http://marianopeck.wordpress.com

Jan. 22, 2013

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

by Sean P. DeNigris

David T. Lewis wrote > I am trying to find a way to make OSProcess... work on Pharo 2.0, > Pharo1.x, and the various versions of Squeak and Cuis I've been thinking a lot about keeping OSP working well on all our favorite St platforms. Metacello was designed specifically to address this type of problem, which I'm sure will multiply as squeak and pharo evolve. I wonder if MetaC works with Cuis... If not, and for older versions of Squeak/Pharo, there could be a Gofer/Installer script like the one for FFI, or - easier for users but maybe a little more work - the multiple packages could be loaded in each supported platform and re-commited as a single platform-specific package e.g. OSProcessSqueak44, OSProcessPharo20; so development would be done w. MetaC, and users can simply download one package. This would also free us from the branching that currently exists to figure out which system we're on. Are you open to committing to the multiple-package path going forward and relying on MetaC to manage these incompatibilities? Sean -- View this message in context: http://forum.world.st/Must-OSPlatform-class-osVersion-be-deprecated-tp46643… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 22, 2013

Re: [Pharo-project] Object>>#name

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Many people have hit the fact that Object implements #name, which then > seems to conflict with some other class where one would really like to use > name as an instance variable and thus accessor. Yes, I've been bitten by this a few times. When developing through the debugger, it's confusing when the thing fails silently instead of prompting to create the method. Sven Van Caekenberghe-2 wrote > Turns out that it seems that Object>>#name is actually not used (anymore). There are lots of senders... I guess they're sending Class>>#name or another message. I say ditch it, but wait until 3.0... -- View this message in context: http://forum.world.st/Object-name-tp4664573p4664583.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 22, 2013

Re: [Pharo-project] a test :) yet another one.

by Marcus Denker

Hi, Yes, mailing lists where down and I on the train, so the ticket to supper was only send yesterday after office hoursâ¦ and today I spend some effort convincing the admins that no, it's not my mail client that is wrong configuredâ¦ Marcus On Jan 22, 2013, at 5:43 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >

Jan. 22, 2013

Re: [Pharo-project] zero conf build

by Tudor Girba

For example: curl http://pharo.gforge.inria.fr/ci/script/ciPharo20PharoVM.sh | sh ./vm.sh or: curl http://pharo.gforge.inria.fr/ci/script/ciPharo20CogVM.sh | bash. ./vm.sh Cheers, Doru On Mon, Jan 21, 2013 at 2:28 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > 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." > > > > > > > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 22, 2013