- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo VMs should be more Pharo-like

by GermÃ¡n Arduino

2011/11/29 Esteban Lorenzano <estebanlm(a)gmail.com> > pd: I'm the only one who does not likes One-Click versions? I would prefer > a different package for each platform (Is ugly to have a directory named > Pharo.app in linux or windows. Also, no need to have all those > duplicated-but-for-different-platform files) > > +1

Nov. 29, 2011

[Pharo-project] Pharo VMs should be more Pharo-like

by Esteban Lorenzano

Hi, Currently, we are linking official VMs for pharo taking directly from Jenkins a version and packaging for download (or for Pharo One-Click). I think this is a temporal solution, we need something better: 1) Pharo VMs should have Pharo Icons. 2) Pharo VMs should be named "pharo" or "pharovm" (better the fist), not "CogVM", which is an internal name. 3) We should include a PLUGINS.txt file with information about present plugins (internal and external) 4) We should include a LICENCE.txt file with all licence information. ... I think that's all :) I know... this is very dumb and clearly not mandatory, but it says a lot about the maturity of our Pharo :) All agree? Should I create a ticket? Cheers, Esteban pd: I'm the only one who does not likes One-Click versions? I would prefer a different package for each platform (Is ugly to have a directory named Pharo.app in linux or windows. Also, no need to have all those duplicated-but-for-different-platform files)

Nov. 29, 2011

Re: [Pharo-project] Problem with NonInteractiveUIManager

by Norbert Hartl

Am 29.11.2011 um 02:24 schrieb Igor Stasenko: > ok, seems like someone extended protocol without implementing analog > in non-interactive manager. > please file a bug report we will fix that. done. http://code.google.com/p/pharo/issues/detail?id=5040 Norbert

Nov. 29, 2011

[Pharo-project] 1.4 arch users of Smalltalk does not work anymore

by StÃ©phane Ducasse

Hi ben I cannot work with 1.4 to look for users for example of Smalltalk. Can you have a look because it is dead slow. May be something with the Class comments. Stef

Nov. 29, 2011

Re: [Pharo-project] Building 32-bit Cairo library on Macs

by StÃ©phane Ducasse

> > you shall install it from ports or homebrew. just make sure you build > either universal binaries > or 32-bit, because 64 bit ones won't work. Igor what is the exact invocation? Stef

Nov. 29, 2011

Re: [Pharo-project] RenameMethodRefactoring Comment

by Sean P. DeNigris

Sean P. DeNigris wrote > > permutation: (0 to: oldSelector numArgs). > should be: permutation: (1 to: oldSelector numArgs). -- View this message in context: http://forum.world.st/RenameMethodRefactoring-Comment-tp4117939p4117958.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 29, 2011

[Pharo-project] RenameMethodRefactoring Comment

by Sean P. DeNigris

Here's a free bonus class comment: I do just what my name says. Example Usage: refactoring := RenameMethodRefactoring renameMethod: oldSelector in: class to: newSelector permutation: (0 to: oldSelector numArgs). refactoring execute. A few things to keep in mind: - even though a class is specified, my action is system-wide. The only thing I do with the class is make sure it defines oldSelector - the permutation should be a collection that specifies what order the arguments from the oldSelector should appear in the newSelector. If the argument order doesn't change, you can just use the interval shortcut shown above in the example. Example when arguement order changes: oldSelector: arg1 with: arg2 with: arg3 newSelector: arg2 with: arg3 with: arg1 permutation := { 2. 3. 1 } -- View this message in context: http://forum.world.st/RenameMethodRefactoring-Comment-tp4117939p4117939.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 29, 2011

Re: [Pharo-project] Problem with NonInteractiveUIManager

by Igor Stasenko

On 28 November 2011 20:01, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 28.11.2011 um 18:53 schrieb Igor Stasenko: > > On 28 November 2011 17:44, Norbert Hartl <norbert(a)hartl.name> wrote: > > Ok, > > > this is the behaviour with an image #13320 and the newest cog vm. I don't > need to do anything because the NonInteractiveUIManager is set to default > automatically regardless if -nodisplay or -headless is specified. And in my > case this is broken. However if I hack away the noninteractive stuff by > doing > > > UIManager default: (UIManager default instVarAt: 1). > > > than it works. A debugger pops up in the image and can see the real > exception with VNC. So to me it seems that there is something broken. Igor, > can you add anything. I think Marcus is not available at the moment. > > > > a non-interactive manager takes ownership when you either: > - run image with -headless param > - during image startup (StartupUIManager). > > the default behavior of it, when any interaction with user is > requested, it signals ErrorNonInteractive error, > and default action for this error is to print stack trace to log file > and leave to OS. > signaling any other unhandled error leading to opening a debugger > window, which is considered a user interaction request, and > consequently bails out to OS as well by signaling ErrorNonInteractive. > > if you run headless and don't want to use this manager, > you can disable it, just by setting a morphic ui manager: > > UIManager default: MorphicUIManager new. > > Yes, that's the same as what I did with restoring the original manager. > Using the non-interactive manager does not output the stack trace of the > exception that occured but the exception that is triggered because > > openDebuggerOn:context:label:contents:fullView: > > is not implemented in NonInteractiveUIManager. And even if I impement the > method with > > ^ self nonInteractive > > I don't get the exception that originally ocurred. So you cannot see the > exception that caused the image to exit. Shouldn't that be different? > ok, seems like someone extended protocol without implementing analog in non-interactive manager. please file a bug report we will fix that. > Norbert > > > > -- Best regards, Igor Stasenko.

Nov. 29, 2011

Re: [Pharo-project] Problem with NonInteractiveUIManager

by Igor Stasenko

On 28 November 2011 23:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Igor Stasenko wrote >> >> the default behavior of it, when any interaction with user is >> requested, it signals ErrorNonInteractive error, >> and default action for this error is to print stack trace to log file >> and leave to OS. >> signaling any other unhandled error leading to opening a debugger >> window, which is considered a user interaction request, and >> consequently bails out to OS as well by signaling ErrorNonInteractive. >> > > Igor, I added your response to the class comment, but could you expand the > above paragraph (maybe some periods, lol). I don't understand it. > here what happens: [ some error signal ] -> attempt to open debugger -> [signal ErrorNonInteractive] -> leave to OS > -- > View this message in context: http://forum.world.st/Problem-with-NonInteractiveUIManager-tp4115412p411698… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

Nov. 29, 2011

Re: [Pharo-project] Problem with NonInteractiveUIManager

by Sean P. DeNigris

Igor Stasenko wrote > > the default behavior of it, when any interaction with user is > requested, it signals ErrorNonInteractive error, > and default action for this error is to print stack trace to log file > and leave to OS. > signaling any other unhandled error leading to opening a debugger > window, which is considered a user interaction request, and > consequently bails out to OS as well by signaling ErrorNonInteractive. > Igor, I added your response to the class comment, but could you expand the above paragraph (maybe some periods, lol). I don't understand it. -- View this message in context: http://forum.world.st/Problem-with-NonInteractiveUIManager-tp4115412p411698… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 28, 2011