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

Re: [Pharo-project] [ VM ]Smalltalk getSystemAttribute:

by Esteban Lorenzano

Hi, ok, I will answer argv[0], then :) Esteban El 03/01/2012, a las 3:00p.m., Eliot Miranda escribiÃ³: > Hi Esteban, > > you'll find that my Mac VMs as of r2519 do "the right thing", agreeing with the linux VM. See > > http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/Mac%20OS/vm/sqMac… > > --- platforms/Mac OS/vm/sqMacUnixCommandLineInterface.c (revision 2515) > +++ platforms/Mac OS/vm/sqMacUnixCommandLineInterface.c (revision 2522) > @@ -63,14 +63,14 @@ > char *unixArgcInterfaceGetParm(int n) { > int actual; > > - if (n < 0) > + if (n < 0) { > actual = -n; > - else > + return actual < vmArgCnt ? vmArgVec[actual] : nil; > + } > + else { > actual = n - 2; > - > - if (actual < squeakArgCnt) > - return squeakArgVec[actual]; > - return nil; > + return actual < squeakArgCnt ? squeakArgVec[actual] : nil; > + } > } > > And e.g. > > $ oscogvm/macbuild/Fast.app/Contents/MacOS/Croquet -headless startreader.image foo bar baz > squeak> (0 to: -3 by: -1) collect: [:i| Smalltalk getSystemAttribute: i]! > #('oscogvm/macbuild/Fast.app/Contents/MacOS/Croquet' '-headless' 'startreader.image' nil) > squeak> (0 to: 5) collect: [:i| Smalltalk getSystemAttribute: i]! > #('oscogvm/macbuild/Fast.app/Contents/MacOS/Croquet' '/Users/eliot/Cog/startreader.image' 'foo' 'bar' 'baz' nil) > squeak> Smalltalk quit! > $ > On Mon, Jan 2, 2012 at 8:04 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > I was trying to fix this, but seems to be a problem (besides the "'-psn_0_528513'", which is an error). > According SmalltalkImage>>#getSystemAttribute: comment, getSystemAttribute: 0 shouldn't answer the executable name, but the VM path: > > 0 the full path name for currently executing VM > (or, on some platforms, just the path name of the VM's directory) > > ...so... getSystemAttribute: 0 is answering fine... and -1 should answer nil (or the vm parameters, if present), not the executable name. Real problem then is: > > we don't have a way to get the executable name > > or > > getSystemAttribute: comment is wrong :) > > what's the audience opinion? > > cheers, > Esteban > > > El 31/12/2011, a las 9:11p.m., Sean P. DeNigris escribiÃ³: > > > The latest blessed cocoa build from Jenkins (12/11/11 #10) + 1.3-rc returns: > > > > SmalltalkImage current getSystemAttribute: -1."'-psn_0_528513'" > > SmalltalkImage current getSystemAttribute: 0 "'/Applications'" > > > > There does not seem to be a way to get the vm executable name. > > > > Sean > > > > -- > > View this message in context: http://forum.world.st/VM-Smalltalk-getSystemAttribute-tp4122708p4249718.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > -- > best, > Eliot >

Jan. 3, 2012

Re: [Pharo-project] [ VM ]Smalltalk getSystemAttribute:

by Eliot Miranda

Hi Esteban, you'll find that my Mac VMs as of r2519 do "the right thing", agreeing with the linux VM. See http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/Mac%20OS/vm/sqMac… --- platforms/Mac OS/vm/sqMacUnixCommandLineInterface.c (revision 2515) +++ platforms/Mac OS/vm/sqMacUnixCommandLineInterface.c (revision 2522) @@ -63,14 +63,14 @@ char *unixArgcInterfaceGetParm(int n) { int actual; - if (n < 0) + if (n < 0) { actual = -n; - else + return actual < vmArgCnt ? vmArgVec[actual] : nil; + } + else { actual = n - 2; - - if (actual < squeakArgCnt) - return squeakArgVec[actual]; - return nil; + return actual < squeakArgCnt ? squeakArgVec[actual] : nil; + } } And e.g. $ oscogvm/macbuild/Fast.app/Contents/MacOS/Croquet -headless startreader.image foo bar baz squeak> (0 to: -3 by: -1) collect: [:i| Smalltalk getSystemAttribute: i]! #('oscogvm/macbuild/Fast.app/Contents/MacOS/Croquet' '-headless' 'startreader.image' nil) squeak> (0 to: 5) collect: [:i| Smalltalk getSystemAttribute: i]! #('oscogvm/macbuild/Fast.app/Contents/MacOS/Croquet' '/Users/eliot/Cog/startreader.image' 'foo' 'bar' 'baz' nil) squeak> Smalltalk quit! $ On Mon, Jan 2, 2012 at 8:04 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > I was trying to fix this, but seems to be a problem (besides the > "'-psn_0_528513'", which is an error). > According SmalltalkImage>>#getSystemAttribute: comment, > getSystemAttribute: 0 shouldn't answer the executable name, but the VM path: > > 0 the full path name for currently executing VM > (or, on some platforms, just the path name of the > VM's directory) > > ...so... getSystemAttribute: 0 is answering fine... and -1 should answer > nil (or the vm parameters, if present), not the executable name. Real > problem then is: > > we don't have a way to get the executable name > > or > > getSystemAttribute: comment is wrong :) > > what's the audience opinion? > > cheers, > Esteban > > > El 31/12/2011, a las 9:11p.m., Sean P. DeNigris escribiÃ³: > > > The latest blessed cocoa build from Jenkins (12/11/11 #10) + 1.3-rc > returns: > > > > SmalltalkImage current getSystemAttribute: -1."'-psn_0_528513'" > > SmalltalkImage current getSystemAttribute: 0 "'/Applications'" > > > > There does not seem to be a way to get the vm executable name. > > > > Sean > > > > -- > > View this message in context: > http://forum.world.st/VM-Smalltalk-getSystemAttribute-tp4122708p4249718.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > -- best, Eliot

Jan. 3, 2012

[Pharo-project] TWM warning while loading

by Sean P. DeNigris

In Pharo 1.4 update: #14261: (ConfigurationOfTilingWindowManager project version: #bleedingEdge) load This package depends on the following classes: OBBrowser You must resolve these dependencies before you will be able to load these definitions: patchworkUIThemeColor Select Proceed to continue, or close this window to cancel the operation. -- View this message in context: http://forum.world.st/TWM-warning-while-loading-tp4257854p4257854.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 3, 2012

Re: [Pharo-project] TWM Bug - different world menu

by Sean P. DeNigris

Bump -- View this message in context: http://forum.world.st/TWM-Bug-different-world-menu-tp4244649p4257635.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 3, 2012

Re: [Pharo-project] [ VM ]Smalltalk getSystemAttribute:

by Sean P. DeNigris

Sean P. DeNigris wrote > > Or with PetitParser: > But regex is much tighter for this simple case: bundlePath := '.*\.app' asRegex matchesPrefix: vmPath; subexpression: 1. -- View this message in context: http://forum.world.st/VM-Smalltalk-getSystemAttribute-tp4122708p4257445.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 3, 2012

Re: [Pharo-project] About announcements

by Igor Stasenko

On 3 January 2012 16:24, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Igor Stasenko wrote >> >> as well as it could serve as a source of confusion, because you using >> same protocol for different purposes >> in two different frameworks. >> A medal always has two sides :) >> >>> Consistency makes frameworks easy to understand and use. >> > > I think having the two frameworks have the same API would be much easier > than if they were almost the same. And I don't think that similarity would > cause confusion - quite the opposite. When working with a different > framework, I've already shifted my context to the abstractions of that > framework. However, my fingers naturally want to > type/select-from-autocomplete/etc. the exact same things they've done > before, and I don't have to look at a browser to see "how was that selector > slightly different from the other one?" > exactly. just few days ago, we were hacking new events model with Stef. and i wrongly implemented #handleEvent: which is sent by InputEventFetcher and actually Sensor should just put an event into own queue, because this message were send in fetcher process. while event handling happens inside ui process. with announcements i had to rename #handles: to #handlesAnnouncement: first because if i would not do so, it would be not possible to migrate code (because handles: expect announcement class as argument, and if i change the sender, it will break it) or if i change all implementors of #handles: i will also break it because announcers are still sending this message with wrong argument. well, maybe it is not a big deal. and we could just use #handles: but imo #handlesAnnouncement: looks more explicit (now you have less chances to be confused with the role or receiver - an announcement filter and role of argument - an announced object) > -- > View this message in context: http://forum.world.st/About-announcements-tp4253255p4257251.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

Jan. 3, 2012

Re: [Pharo-project] [ VM ]Smalltalk getSystemAttribute:

by Sean P. DeNigris

Igor Stasenko wrote > > because you can always strip down unwanted information (just do regexp > like '.app/Contents'), > Or with PetitParser: | vmPath bundleExtension bundlePathParser bundlePath | vmPath := OSProcess programName. bundleExtension := '.app' asParser. bundlePathParser := (bundleExtension negate star, bundleExtension) flatten. bundlePath := bundlePathParser parse: vmPath. ^ FSFilesystem disk root resolve: bundlePath. -- View this message in context: http://forum.world.st/VM-Smalltalk-getSystemAttribute-tp4122708p4257314.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 3, 2012

Re: [Pharo-project] Bug Report: 6 of 6: Settings

by Nicolas Cellier

But the interface should bark instead of forgetting a change silently when we open/close a preference (Oups setting) node... Does it now ? Nicolas 2012/1/3 S Krish <krishnamachari.sudhakar(a)gmail.com>: > Thats already there.. > > it does show the highlighted background and also a tip on the text area > below to accept on cr. But as lazy as we are we do not notice hints obvious > in the face of habits. > > > On Tue, Jan 3, 2012 at 6:27 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >> Mariano Martinez Peck wrote: >>> >>> On Tue, Jan 3, 2012 at 1:11 PM, Alain Plantec >>> <alain.plantec(a)yahoo.com>wrote: >>> >>> >>>> >>>> Le 03/01/2012 11:57, S Krish a Ã©crit : >>>> >>>> Â This works... >>>> >>>>> >>>>> Guess I should have tried that.. >>>>> >>>>> >>>> >>>> thanks. >>>> but you are not the first one to forget to enter a cr. >>>> >>>> >>> >>> >>> Yes, I was the first one!!! I remember I have reported the same ;) >>> >>> >> >> A small thought - the field background might be made to change colour >> during entry until it is accepted by <cr>. >> >

Jan. 3, 2012

Re: [Pharo-project] About announcements

by Sean P. DeNigris

Igor Stasenko wrote > > as well as it could serve as a source of confusion, because you using > same protocol for different purposes > in two different frameworks. > A medal always has two sides :) > >> Consistency makes frameworks easy to understand and use. > I think having the two frameworks have the same API would be much easier than if they were almost the same. And I don't think that similarity would cause confusion - quite the opposite. When working with a different framework, I've already shifted my context to the abstractions of that framework. However, my fingers naturally want to type/select-from-autocomplete/etc. the exact same things they've done before, and I don't have to look at a browser to see "how was that selector slightly different from the other one?" -- View this message in context: http://forum.world.st/About-announcements-tp4253255p4257251.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 3, 2012

Re: [Pharo-project] Prematurely ending document on purpose with the SAXParser

by Sven Van Caekenberghe

On 03 Jan 2012, at 13:31, HernÃ¡n Morales Durand wrote: > I wonder what to do in this kind of situations. See > > 1) XML is one of the most important packages > 2) There is no mailng-list for xml ? > 3) Nobody replies and > 4) You want latest updates from that package > > Any suggestion? Maybe you could try to reach someone from the administrators/developers directly, there are quite a few on SS. Sven

Jan. 3, 2012