- Pharo-dev - lists.pharo.org

[Pharo-project] A simple getenv primitive
by Damien Cassou May 3, 2012

May 3, 2012

Hi, I can't find any getenv primitive that would allow me to access environment an variable value from its name. This could be really helpful to get the HOME directory for example. Does one such primitive exist? If not, why? It looks trivial to implement for linux, and it is potentially also easy on Windows and Mac OS. I'm willing to try if necessary. Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

2 2

Re: [Pharo-project] Enable #alwaysOpenFullDebugger: and fastDragging:
by Marcus Denker May 3, 2012

May 3, 2012

On May 3, 2012, at 10:10 AM, Mariano Martinez Peck wrote: > Hi guys. There are 2 settings that I ALWAYS need to change and I think it would be nice to have them by default: > > 1) Always show debugger and avoid pre-debugger windows. It makes no sense for development. It takes you the double of time. What does the pre-debug brings you? nothing. If you want to proceed, then the debugger also has that option. If you want to abandon, you can just close the debugger. So, we should enable this. If someone wanst the pre-debugger fwindows for a reasons, then he should enable it. > > 2) Fast dragging. The normal dragging is slow in old machines and slow when there are lots of opened windows. The fast drag is much faster and nicer because since it is transparent you can even see what is below. > > Let's do a quick survey. We have 24 hrs. Do not vote if you didn't try it. > > I start: > > Debugger alwaysOpenFullDebugger: true. +1 > UITheme currentSettings fastDragging: true. +1 > Please do a doodle. We have already too many mails on the mailinglist. -- Marcus Denker -- http://marcusdenker.de

6 10

Re: [Pharo-project] Enable #alwaysOpenFullDebugger: and fastDragging:
by Marcus Denker May 3, 2012

May 3, 2012

On May 3, 2012, at 10:16 AM, Mariano Martinez Peck wrote: > > > On Thu, May 3, 2012 at 10:13 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On May 3, 2012, at 10:10 AM, Mariano Martinez Peck wrote: > > > Hi guys. There are 2 settings that I ALWAYS need to change and I think it would be nice to have them by default: > > > > 1) Always show debugger and avoid pre-debugger windows. It makes no sense for development. It takes you the double of time. What does the pre-debug brings you? nothing. If you want to proceed, then the debugger also has that option. If you want to abandon, you can just close the debugger. So, we should enable this. If someone wanst the pre-debugger fwindows for a reasons, then he should enable it. > > > > 2) Fast dragging. The normal dragging is slow in old machines and slow when there are lots of opened windows. The fast drag is much faster and nicer because since it is transparent you can even see what is below. > > > > Let's do a quick survey. We have 24 hrs. Do not vote if you didn't try it. > > > > I start: > > > > Debugger alwaysOpenFullDebugger: true. +1 > > UITheme currentSettings fastDragging: true. +1 > > > > Please do a doodle. We have already too many mails on the mailinglist. > > I was trying to be diplomatic. Ok: http://code.google.com/p/pharo/issues/detail?id=5787 > FixToInclude. No more emails ;) What I want to *not* have are 580 emails of people saying +1 or -1 There is for sure some website for doing a vote? I thought doodle added that? Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] grabbing morphs in 2.0
by Francisco Garau May 3, 2012

May 3, 2012

Hi - up until 1.4 doing ctrl-click on any morph would bring up a menu for the clicked morph. This is not happening any more in 2.0. Shall I open an issue for it? - Francisco

2 1

Re: [Pharo-project] Multiple desktops
by H. Hirzel May 3, 2012

May 3, 2012

How come? Maybe I should have chosen 'Multiple desktops' as the subject line. I just downloaded Pharo 1.4 a few days ago and with only one screen I feel quickly limited. How are people dealing with this? Having different desktops for a system is not a uncommon thing at all. --Hannes On 5/2/12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > I propose to just close the issue... having different words don't seems to > match with current pharo approach and future envisioned scenarios. > (I'm sorry if someone is expecting that) > > best, > Esteban > > On May 2, 2012, at 3:28 PM, Marcus Denker wrote: > >> >> On May 2, 2012, at 3:23 PM, H. Hirzel wrote: >> >>> Hello >>> >>> This issue >>> http://code.google.com/p/pharo/issues/detail?id=3545 >>> is about the feature of having multiple worlds. Status is 'Accepted'. >>> >> Accepted means accepted for thinking about, there is no commitment. >> >>> I assume it is now in Pharo 1.4. >>> >>> How can I use it. >>> >>> The code I found from Sean is >>> >>> "Add a world:" >>> WorldManager instance createOrSwitchToWorldNamed: 'JustAnotherWorld'. >>> >>> "Return to the default world:" >>> WorldManager instance createOrSwitchToWorldNamed: 'Pharo'. >>> >>> What are the proper instructions? >> >> >> It's a bug tracker entry. Not a package for users to use. >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > >

3 6

[Pharo-project] Fwd: [Pharo-bugtracker] Issue 5782 in pharo: Close ALL windows, no matter if they have unchanged changes
by Mariano Martinez Peck May 3, 2012

May 3, 2012

So do you like the issue? ---------- Forwarded message ---------- From: <pharo(a)googlecode.com> Date: Wed, May 2, 2012 at 11:54 PM Subject: [Pharo-bugtracker] Issue 5782 in pharo: Close ALL windows, no matter if they have unchanged changes To: pharo-bugtracker(a)lists.gforge.inria.fr Status: Accepted Owner: marianopeck Labels: Type-Bug New issue 5782 by marianopeck: Close ALL windows, no matter if they have unchanged changes http://code.google.com/p/**pharo/issues/detail?id=5782<http://code.google.com/p/pharo/issues/detail?id=5782> Hi guys. Lots of time I found in a situation where I want: 1) To close ALL type of windows (not necessary browsers) such as worksapces and transcripts. 2) To close all windows EVEN if they have unsaved changes. I have added a new entry in "World menu" -> "Windows" -> "Delete all windows discarding edits" that does exactly that. So...do you like it? if true, I can put it to review/integrate. ______________________________**_________________ Pharo-bugtracker mailing list Pharo-bugtracker@lists.gforge.**inria.fr<Pharo-bugtracker(a)lists.gforge.inria.fr> http://lists.gforge.inria.fr/**cgi-bin/mailman/listinfo/**pharo-bugtracker<http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker> -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] [update 2.0] #20042
by Marcus Denker May 3, 2012

May 3, 2012

20042 ----- Issue 5777: Test and workaround for methods with incorrect global literals http://code.google.com/p/pharo/issues/detail?id=5777 Issue 5781: Add nice diff morph to compare to current and compare to version... http://code.google.com/p/pharo/issues/detail?id=5781 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] multiple pharo images
by Marcus Denker May 3, 2012

May 3, 2012

On May 3, 2012, at 8:22 AM, Pavel Krivanek wrote: > Why not to have both :-) > yes, we should do that. > -- Pavel > > > > 3.5.2012 v 5:05, Serge Stinckwich <serge.stinckwich(a)gmail.com>: > >> When you download a lot of images every week, this is nice to have a >> build number in order to recognize them. >> Regards, >> >> On Thu, May 3, 2012 at 4:20 AM, Francisco Garau >> <francisco.garau(a)gmail.com> wrote: >>> >>> How about Jenkins putting a build suffix to the images? -- something like Pharo-2.0.build-20040.image >>> >>> At the moment, all the build generate files with the same name. >>> >>> https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/ >>> >>> 2.0 #20040 >>> >>> Pharo-2.0.changes 13069724 >>> Pharo-2.0.image 18732936 >>> Pharo-2.0-one-click.zip 19242637 >>> Pharo-2.0.zip 14962904 >> >> >> >> >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Every DSL ends up being Smalltalk >> http://doesnotunderstand.org/ >> > -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Jenkins status icons
by Sean P. DeNigris May 3, 2012

May 3, 2012

How do you get the icon to turn green on a successful build? Jenkins is picking up my test report and showing 0 failures, but the icon is blue instead of green. Thanks, Sean -- View this message in context: http://forum.world.st/Jenkins-status-icons-tp4604223.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 4

Re: [Pharo-project] PDF4Smalltalk (was: Artefact - a PDF framework)
by Christian Haider May 3, 2012

May 3, 2012

Done :-) : http://www.smallcharts.de/download/PDFSourcesV126.zip (I don't want to learn how to use git right now...) Version 1.2.6 filed out from VW 7.8.1 with the FileOut30 goodie in Squeak/Pharo format. See https://gitorious.org/pdf4smalltalk/pages/PackageStructure for the package structure. (Package "Fonts for Windows" could not be filed out... - only needed for the FontExplorer (UI for looking into font structures)) Happy browsing (the runtime code alone is 1.7 MB)... If you want to really get a look of it, you should definitely let it run, i.e. get VW and load it. Christian > -----UrsprÃ¼ngliche Nachricht----- > Von: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project- > bounces(a)lists.gforge.inria.fr] Im Auftrag von Yanni Chiu > Gesendet: Donnerstag, 3. Mai 2012 00:01 > An: pharo-project(a)lists.gforge.inria.fr > Betreff: [Pharo-project] PDF4Smalltalk (was: Artefact - a PDF framework) > > On 02/05/12 12:33 PM, Christian Haider wrote: > >> I've not seen the code for PDF4Smalltalk, because I can't figure >> out > how to browse it without VW. > > > > Unfortunately, you can't :-( > > Could you file out the source code (.st or xml) and post a zip file to the > gitorious site - or, maybe BobN could do it, since he's looking at a port to > GemStone. It's a bit of a hurdle to download, install, refresh/update VW skills > - just to evaluate some code. (When I first heard you'd decided on GIT, I > briefly thought that Dale's Montecello/GIT would let me browse the code > easily - maybe this will be true, at some future date). > > >

1 0