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

Re: [Pharo-users] Try PharoBoids :)

by Igor Stasenko

On 21 January 2013 19:37, Peter H. Meadows <peter.h.meadows(a)googlemail.com> wrote: > I changed CairoLibraryLoader class getLibraryPath to ^ > '/usr/lib/i386-linux-gnu/libcairo.so' and it works now :) > > v.cool. > yeah.. one day we should think how to write a library search mechanism, so it will take a OS-specificness into account.. i'm not happy with hardcoding paths.. -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-users] Pharo 2.0 - System Error Handling Failed

by Sven Van Caekenberghe

On 23 Jan 2013, at 14:58, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Camillo Bruni-3 wrote >> Indeed! >> >>> So not HorribleErrorBlockingEverything but maybe >>> HorribleUXQualityBugScaringAwayNormalPeople as label ? >> >> => Pharo20QC ;) > > Since HorribleXxx is unqualified as to the release, why not simply > QualityControl? > > I've added it as a status to google code: "QualityControl = Leave a bad > impression for users, even if easy or silly to fix" Yeah, but the label should also convey some sense of urgency. I also think that UX is an element: it relates to what users (and we too BTW) encounter in the IDE, blocking them (us) from doing normal work. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Jan. 23, 2013

Re: [Pharo-users] Pharo 2.0 - System Error Handling Failed

by Sean P. DeNigris

Camillo Bruni-3 wrote > Indeed! > >> So not HorribleErrorBlockingEverything but maybe >> HorribleUXQualityBugScaringAwayNormalPeople as label ? > > => Pharo20QC ;) Since HorribleXxx is unqualified as to the release, why not simply QualityControl? I've added it as a status to google code: "QualityControl = Leave a bad impression for users, even if easy or silly to fix" -- View this message in context: http://forum.world.st/Pharo-2-0-System-Error-Handling-Failed-tp4664742p4664… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 23, 2013

Re: [Pharo-users] Try PharoBoids :)

by MartinW

StÃ©phane Ducasse wrote > use the accessors instead of fractions:offsets: ok, much nicer indeed (if that's what you were hinting at?): + fullFrame: (LayoutFrame identity topOffset: self toolbar minExtent y). - fullFrame: ( - LayoutFrame - fractions: (0@0 corner: 1@1) - offsets: (0@(self toolbar minExtent y) corner: 0@0)). If there was a possibility to get write access to the Pharo collaborActive book i could update the example, because that's where i got it from in the first place. Or should there be a different version of the book for every Pharo release? Martin. -- View this message in context: http://forum.world.st/Try-PharoBoids-tp4664291p4664849.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 23, 2013

Re: [Pharo-users] Pharo 2.0 - System Error Handling Failed

by StÃ©phane Ducasse

camillo may be this was because we had this bug in the method cache. So the extensions may be lost. Stef On Jan 22, 2013, at 10:43 PM, Camillo Bruni wrote: > that is/was a bug: > > https://code.google.com/p/pharo/issues/detail?id=6608 > > looks like it is still there in a newer image! > > On 2013-01-23, at 02:05, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: > >> I am running the Pharo 2.0 beta, and I am getting a lot of System Error >> Handling Failed events. Is this simply a product of the beta status, or >> have I somehow enabled some kind of debug switch? >> >> For example, in a workspace I execute a doit on: >> >> fd := FileDialogWindow new. >> fn := fd openInWorld. >> >> When I click OK in the dialog box, I get the System Error screen. On other >> occasions I get the screen, press space to continue, then I get the debug >> window, and when attempting to debug it bounces me back to the System Error >> screen. >> >> Normal behaviour for the beta, or operator error on my part? >> >> Cheers >> Andy > >

Jan. 23, 2013

Re: [Pharo-users] [Pharo-project] Pharo 2.0 - System Error Handling Failed

by Marcus Denker

On Jan 23, 2013, at 10:52 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I really think that for the process of polishing 2.0 from beta to release we need a new label for issues. > > Bugs like the one below are really important, they might be silly or easy to fix, but they leave a bad impression. We want as many people as possible to help, but UX failures like this will scare away many users, most won't be as helpful as Andy to even report the issue. We as developers know that 2.0 is OK because we use it every day, but occasional users who just try 2.0 for the first time can't know that. > > So not HorribleErrorBlockingEverything but maybe HorribleUXQualityBugScaringAwayNormalPeople as label ? > :-) yes. Marcus

Jan. 23, 2013

Re: [Pharo-users] Pharo 2.0 - System Error Handling Failed

by Camillo Bruni

On 2013-01-23, at 10:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I really think that for the process of polishing 2.0 from beta to release we need a new label for issues. > > Bugs like the one below are really important, they might be silly or easy to fix, but they leave a bad impression. We want as many people as possible to help, but UX failures like this will scare away many users, most won't be as helpful as Andy to even report the issue. We as developers know that 2.0 is OK because we use it every day, but occasional users who just try 2.0 for the first time can't know that. Indeed! > So not HorribleErrorBlockingEverything but maybe HorribleUXQualityBugScaringAwayNormalPeople as label ? => Pharo20QC ;) > Sven > > On 23 Jan 2013, at 02:43, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> that is/was a bug: >> >> https://code.google.com/p/pharo/issues/detail?id=6608 >> >> looks like it is still there in a newer image! >> >> On 2013-01-23, at 02:05, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: >> >>> I am running the Pharo 2.0 beta, and I am getting a lot of System Error >>> Handling Failed events. Is this simply a product of the beta status, or >>> have I somehow enabled some kind of debug switch? >>> >>> For example, in a workspace I execute a doit on: >>> >>> fd := FileDialogWindow new. >>> fn := fd openInWorld. >>> >>> When I click OK in the dialog box, I get the System Error screen. On other >>> occasions I get the screen, press space to continue, then I get the debug >>> window, and when attempting to debug it bounces me back to the System Error >>> screen. >>> >>> Normal behaviour for the beta, or operator error on my part? >>> >>> Cheers >>> Andy > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Jan. 23, 2013

Re: [Pharo-users] Pharo 2.0 - System Error Handling Failed

by Sven Van Caekenberghe

I really think that for the process of polishing 2.0 from beta to release we need a new label for issues. Bugs like the one below are really important, they might be silly or easy to fix, but they leave a bad impression. We want as many people as possible to help, but UX failures like this will scare away many users, most won't be as helpful as Andy to even report the issue. We as developers know that 2.0 is OK because we use it every day, but occasional users who just try 2.0 for the first time can't know that. So not HorribleErrorBlockingEverything but maybe HorribleUXQualityBugScaringAwayNormalPeople as label ? Sven On 23 Jan 2013, at 02:43, Camillo Bruni <camillobruni(a)gmail.com> wrote: > that is/was a bug: > > https://code.google.com/p/pharo/issues/detail?id=6608 > > looks like it is still there in a newer image! > > On 2013-01-23, at 02:05, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: > >> I am running the Pharo 2.0 beta, and I am getting a lot of System Error >> Handling Failed events. Is this simply a product of the beta status, or >> have I somehow enabled some kind of debug switch? >> >> For example, in a workspace I execute a doit on: >> >> fd := FileDialogWindow new. >> fn := fd openInWorld. >> >> When I click OK in the dialog box, I get the System Error screen. On other >> occasions I get the screen, press space to continue, then I get the debug >> window, and when attempting to debug it bounces me back to the System Error >> screen. >> >> Normal behaviour for the beta, or operator error on my part? >> >> Cheers >> Andy -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Jan. 23, 2013

Re: [Pharo-users] Pharo 2.0 - System Error Handling Failed

by Camillo Bruni

that is/was a bug: https://code.google.com/p/pharo/issues/detail?id=6608 looks like it is still there in a newer image! On 2013-01-23, at 02:05, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: > I am running the Pharo 2.0 beta, and I am getting a lot of System Error > Handling Failed events. Is this simply a product of the beta status, or > have I somehow enabled some kind of debug switch? > > For example, in a workspace I execute a doit on: > > fd := FileDialogWindow new. > fn := fd openInWorld. > > When I click OK in the dialog box, I get the System Error screen. On other > occasions I get the screen, press space to continue, then I get the debug > window, and when attempting to debug it bounces me back to the System Error > screen. > > Normal behaviour for the beta, or operator error on my part? > > Cheers > Andy

Jan. 23, 2013

Pharo 2.0 - System Error Handling Failed

by Andy Burnett

I am running the Pharo 2.0 beta, and I am getting a lot of System Error Handling Failed events. Is this simply a product of the beta status, or have I somehow enabled some kind of debug switch? For example, in a workspace I execute a doit on: fd := FileDialogWindow new. fn := fd openInWorld. When I click OK in the dialog box, I get the System Error screen. On other occasions I get the screen, press space to continue, then I get the debug window, and when attempting to debug it bounces me back to the System Error screen. Normal behaviour for the beta, or operator error on my part? Cheers Andy

Jan. 23, 2013