March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Pharo4Stef

I would like to have a basic mode without class and all instvars because they get in my way. Stef > I went back to compare the explorer in 2.0, the only visible (not behaviour) difference that I see is the class field, it would probably be better to lose that: > > <Screen Shot 2014-03-13 at 20.28.45.png> > > <Screen Shot 2014-03-13 at 20.29.10.png> > > But I hate the 'all inst vars' field, who uses that and for what ?? > > On 13 Mar 2014, at 20:16, phil(a)highoctane.be wrote: > >> I agree with that. >> >> I was inspecting a ZnResponse yesterday and it was very hard to see the contents etc. >> >> A general pain. I was clicking on the "inspect" option to see what the real content was. I was cursing a lot. >> >> Phil >> >> >> >> >> >> On Thu, Mar 13, 2014 at 12:51 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> I'm glad we're re-inventing the tools! And, I'm struggling with this tool in >> its current form... >> >> As others have mentioned, the "class" pseudo-variable is confusing, but here >> are some that I find worse: >> - The receiver does not change with the selection. For me, this was a key >> feature of the explorer. >> - It does not properly update e.g. if you are inspecting a class containing >> a dictionary and add an item to the dictionary, collapsing and expanding the >> dictionary node does not show the added item. It seems you must open an >> entirely new inspector. >> - If you toggle from EyeTreeInspector to EyeInspector, your code in the >> bottom pane is lost >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> >

March 13, 2014

Re: [Pharo-dev] Is there a Smalltalk way to lock a file?

by David T. Lewis

> Hi Mariano, > > It is supported directly in OSProcess. See the unit test for examples. > > Dave Sorry, I should have been more clear about this. The classes in the OSProcess package are OSFileLock and OSFileRegionLock, as well as the methods in category 'file locking' of class UnixOSProcessAccessor. You can look at the unit tests to see how these are used, but you will not be able to actually run any of the tests that depend on #forkSqueak because these rely on a feature not present in Cog. So look at the tests as examples, but do not expect them to run. The actual file locking support should work fine on Pharo (but let me know if that is not true). HTH, Dave > >> Hi guys, >> >> Do we have a method to lock a file at the OS level? I searched in image >> but >> I cannot find anything. If it would work in gemstone too that would be >> nice. >> >> Thanks! >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by phil＠highoctane.be

> > I see that you haven't clicked on a 17K long string that opens a 17K items > long tree of characters with nice icons and makes your image bloat to > 200+MB in size. > --> 223 162 288 bytes for XXXX.image Look: (in 2.0 the explorer just shows a piece of text) [image: Inline image 1] > > . > > > > But I hate the 'all inst vars' field, who uses that and for what ?? > > On 13 Mar 2014, at 20:16, phil(a)highoctane.be wrote: > > I agree with that. > > I was inspecting a ZnResponse yesterday and it was very hard to see the > contents etc. > > A general pain. I was clicking on the "inspect" option to see what the > real content was. I was cursing a lot. > > Phil > > > > > > On Thu, Mar 13, 2014 at 12:51 PM, Sean P. DeNigris <sean(a)clipperadams.com > > wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool > in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but > here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding > the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > >

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Sebastian Sastre

yeah, and saw what happens when you use the keyboard? try this: 1. selecting in a workspace 2. cmd+shift+i 3. when it opens, press 3 ro 4 times the right arrow you navigate the class instead of the instace not great I miss the old explorer On Mar 13, 2014, at 4:30 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I went back to compare the explorer in 2.0, the only visible (not behaviour) difference that I see is the class field, it would probably be better to lose that: > > <Screen Shot 2014-03-13 at 20.28.45.png> > > <Screen Shot 2014-03-13 at 20.29.10.png> > > But I hate the 'all inst vars' field, who uses that and for what ?? > > On 13 Mar 2014, at 20:16, phil(a)highoctane.be wrote: > >> I agree with that. >> >> I was inspecting a ZnResponse yesterday and it was very hard to see the contents etc. >> >> A general pain. I was clicking on the "inspect" option to see what the real content was. I was cursing a lot. >> >> Phil >> >> >> >> >> >> On Thu, Mar 13, 2014 at 12:51 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> I'm glad we're re-inventing the tools! And, I'm struggling with this tool in >> its current form... >> >> As others have mentioned, the "class" pseudo-variable is confusing, but here >> are some that I find worse: >> - The receiver does not change with the selection. For me, this was a key >> feature of the explorer. >> - It does not properly update e.g. if you are inspecting a class containing >> a dictionary and add an item to the dictionary, collapsing and expanding the >> dictionary node does not show the added item. It seems you must open an >> entirely new inspector. >> - If you toggle from EyeTreeInspector to EyeInspector, your code in the >> bottom pane is lost >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> >

March 13, 2014

RPackage... not quite licked

by Sean P. DeNigris

We're getting there! But... Issue 13074: Renaming a package -> Wrong MC Tags https://pharo.fogbugz.com/default.asp?13074 ----- Cheers, Sean -- View this message in context: http://forum.world.st/RPackage-not-quite-licked-tp4749038.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Sven Van Caekenberghe

I went back to compare the explorer in 2.0, the only visible (not behaviour) difference that I see is the class field, it would probably be better to lose that: But I hate the 'all inst vars' field, who uses that and for what ?? On 13 Mar 2014, at 20:16, phil(a)highoctane.be wrote: > I agree with that. > > I was inspecting a ZnResponse yesterday and it was very hard to see the contents etc. > > A general pain. I was clicking on the "inspect" option to see what the real content was. I was cursing a lot. > > Phil > > > > > > On Thu, Mar 13, 2014 at 12:51 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

March 13, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by phil＠highoctane.be

I agree with that. I was inspecting a ZnResponse yesterday and it was very hard to see the contents etc. A general pain. I was clicking on the "inspect" option to see what the real content was. I was cursing a lot. Phil On Thu, Mar 13, 2014 at 12:51 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool > in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but > here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding > the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

March 13, 2014

Re: [Pharo-dev] [ANN] RenoirSt 1.0.0 Release for Pharo 3.0

by Denis Kudriashov

Cool. Do you try it on Amber? 2014-03-11 17:13 GMT+04:00 Gabriel Cotelli <g.cotelli(a)gmail.com>: > Hi, > > I'm announcing the first official release of RenoirSt, a DSL enabling > programmatic cascading style sheet generation for Pharo. > > For the impatient, you can load it in your 3.0 image evaluating: > > Gofer it > url: 'http://smalltalkhub.com/mc/gcotelli/RenoirSt/main'; > configurationOf: 'RenoirSt'; > loadStable > > or download a ready to use image from the Contribution CI Server<https://ci.inria.fr/pharo-contribution/job/RenoirSt/> ( > a ConfigurationBrowser option comming soon). > > Visit the project page <http://gcotelli.github.io/RenoirSt/> and GitHub > repository <https://github.com/gcotelli/RenoirSt> for more information on > the supported and planned features, and check-out the online tutorial.<https://github.com/gcotelli/RenoirSt/blob/stable/docs/tutorial/Tutorial%20-…> > > I hope you find it useful. Feel free to ask any questions, suggest ideas > and improvements, or report bugs (the issue tracker is in GitHub). > > Gabriel >

March 13, 2014

Re: [Pharo-dev] Is there a Smalltalk way to lock a file?

by David T. Lewis

Hi Mariano, It is supported directly in OSProcess. See the unit test for examples. Dave > Hi guys, > > Do we have a method to lock a file at the OS level? I searched in image > but > I cannot find anything. If it would work in gemstone too that would be > nice. > > Thanks! > > -- > Mariano > http://marianopeck.wordpress.com >

March 13, 2014

Re: [Pharo-dev] Is there a Smalltalk way to lock a file?

by Sebastian Sastre

On Mar 13, 2014, at 1:14 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys, > > Do we have a method to lock a file at the OS level? I searched in image but I cannot find anything. We couldnât have done airflowing without that feature (which enables horizontal scaling). Take a look at: https://github.com/sebastianconcept/OmniBase The locking tests will fail in a default linux installation until you mount your filesystem with the mandatory locking option: http://www.hackinglinuxexposed.com/articles/20030623.html sebastian o/

March 13, 2014