- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Nautilus

by Mariano Martinez Peck

On Sat, Apr 21, 2012 at 12:15 AM, blake <dsblakewatson(a)gmail.com> wrote: > Thanks, Mariano. > > It's nice! Does it do setter/getter generation? > > select a class -> right click -> refacoring -> class refactoring -> generate accessors cheers > On Fri, Apr 20, 2012 at 3:00 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > > > > > On Fri, Apr 20, 2012 at 11:58 PM, blake <dsblakewatson(a)gmail.com> wrote: > >> > >> Is there any documentation on Nautilus anywhere? > >> > >> I was trying to get it to create getters and setters but I don't see > >> if it does that. Also, there are these tantalizing letters on the side > >> (S, > > > > > > source code > > > >> > >> B, > > > > > > bytecodes > > > >> > >> D, > > > > > > decompiled string > > > >> > >> I, > > > > > > instance variables > > > >> > >> C) > > > > > > class variables > > > >> > >> and sometimes a yellow > > > > > > your method is a little bit long > > > >> > >> band appears on the > >> right--which I guess is a warning about length, > > > > > > you method is TOO long > > > >> > >> but what are the > >> numbers? > >> > > > > characters? > > > > Anyway, I agree we should document Nautilus somewhere :( > > > >> > >> Also, the category pane is now the package pane, and given my > >> confusion about the relationship between those, it'd be good to know > >> how Nautilus is different. > >> > >> ===Blake=== > >> > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > -- Mariano http://marianopeck.wordpress.com

April 20, 2012

Re: [Pharo-project] Nautilus

by blake

Thanks, Mariano. It's nice! Does it do setter/getter generation? On Fri, Apr 20, 2012 at 3:00 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Fri, Apr 20, 2012 at 11:58 PM, blake <dsblakewatson(a)gmail.com> wrote: >> >> Is there any documentation on Nautilus anywhere? >> >> I was trying to get it to create getters and setters but I don't see >> if it does that. Also, there are these tantalizing letters on the side >> (S, > > > source code > >> >> B, > > > bytecodes > >> >> D, > > > decompiled string > >> >> I, > > > instance variables > >> >> C) > > > class variables > >> >> and sometimes a yellow > > > your method is a little bit long > >> >> band appears on the >> right--which I guess is a warning about length, > > > you method is TOO long > >> >> but what are the >> numbers? >> > > characters? > > Anyway, I agree we should document Nautilus somewhere :( > >> >> Also, the category pane is now the package pane, and given my >> confusion about the relationship between those, it'd be good to know >> how Nautilus is different. >> >> ===Blake=== >> > > > > -- > Mariano > http://marianopeck.wordpress.com >

April 20, 2012

Re: [Pharo-project] strange logic

by Alain Rastoul

Bringing up the World menu ends up with more than 1000 'icon' messages in the Transcript 8-o "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> a Ã©crit dans le message de news: BAF0C354-2FD4-4AD0-B24E-EABE17ADE36D(a)inria.fr... Hi I added a simple transcript into the following method. icon "Answer the receiver's icon. Handle legacy case of wording-based mechanism." |state| Transcript show: 'icon'; cr. ^^^^^^^^^^^^^^^^^^^^^^ self getStateSelector ifNil: [^super icon]. state := (MessageSend receiver: self target selector: self getStateSelector) valueWithEnoughArguments: self arguments . (state = true or: [state isString and: [(state beginsWith: '<yes>') or: [state beginsWith: '<on>']]]) ifTrue: [^self onIcon]. (state = false or: [state isString and: [(state beginsWith: '<no>') or: [state beginsWith: '<off>']]]) ifTrue: [^self offIcon]. ^super icon Then I brought up the monticello menu which has 4 toggleMenus and I got a lot and a lot and a lot of processing in the transcript It looks to me that there is a wrong logic in the system Stef

April 20, 2012

Re: [Pharo-project] OSProcess - is process done?

by Sean P. DeNigris

Here's the OSProcess test results: * Pharo 1.3 * Mac Lion 10.7.3 * recent Cog VM from the Pharo CI server * latest version of OSProcess (the all-in-one package, not the broken up ones) 192 run, 110 passes, 0 expected failures, 79 failures, 3 errors, 0 unexpected passes Is that what you would expect?! 3 errors: #('AioEventHandlerTestCase>>#testPrimAioModuleName' 'UnixProcessAccessorTestCase>>#testDupTo' 'UnixProcessTestCase>>#testEightLeafSqueakTree') 79 failures: #('AioEventHandlerTestCase>>#testEnableHandleAndDisable' 'AioEventHandlerTestCase>>#testFileReadableEvent' 'AioEventHandlerTestCase>>#testFileWritableEvent' 'AioEventHandlerTestCase>>#testHandleForFile' 'AioEventHandlerTestCase>>#testHandleForSocket' 'AioEventHandlerTestCase>>#testPrimAioModuleVersionString' 'AioEventHandlerTestCase>>#testSocketReadableEvent' 'AioEventHandlerTestCase>>#testSuspendAioForSocketReadableEvent' 'UnixProcessAccessorTestCase>>#testRedirectStdOutTo' 'UnixProcessTestCase>>#testCatAFile' 'UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDo' 'UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDoThenQuit' 'UnixProcessTestCase>>#testClassForkSqueak' 'UnixProcessTestCase>>#testClassForkSqueakAndDo' 'UnixProcessTestCase>>#testClassForkSqueakAndDoThenQuit' 'UnixProcessTestCase>>#testForkHeadlessSqueakAndDo' 'UnixProcessTestCase>>#testForkHeadlessSqueakAndDoThenQuit' 'UnixProcessTestCase>>#testForkSqueak' 'UnixProcessTestCase>>#testForkSqueakAndDo' 'UnixProcessTestCase>>#testForkSqueakAndDoThenQuit' 'UnixProcessTestCase>>#testHeadlessChild' 'UnixProcessTestCase>>#testRunCommand' 'UnixProcessTestCase>>#testSpawnTenHeadlessChildren' 'UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses01' 'UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses02' 'UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses03' 'UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses04' 'UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses05' 'UnixProcessUnixFileLockingTestCase>>#testFailFileLockOnLockedFile' 'UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedOverlappedRegion' 'UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedRegion' 'UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedSupersetRegion' 'UnixProcessUnixFileLockingTestCase>>#testFailRegionLockOnLockedFile' 'UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite01' 'UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite02' 'UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite03' 'UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite04' 'UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite05' 'UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite06' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead01' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead02' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite01' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite02' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite03' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite04' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite05' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite06' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite07' 'UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite08' 'UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions' 'UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion' 'UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses01' 'UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses02' 'UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses03' 'UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses04' 'UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses05' 'UnixProcessWin32FileLockingTestCase>>#testFailFileLockOnLockedFile' 'UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedOverlappedRegion' 'UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedRegion' 'UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedSupersetRegion' 'UnixProcessWin32FileLockingTestCase>>#testFailRegionLockOnLockedFile' 'UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite01' 'UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite02' 'UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite03' 'UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite04' 'UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite05' 'UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite06' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead01' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead02' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite01' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite02' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite03' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite04' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite05' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite06' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite07' 'UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite08' 'UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions' 'UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion') -- View this message in context: http://forum.world.st/OSProcess-is-process-done-tp4569088p4575406.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2012

Re: [Pharo-project] Nautilus

by Mariano Martinez Peck

On Fri, Apr 20, 2012 at 11:58 PM, blake <dsblakewatson(a)gmail.com> wrote: > Is there any documentation on Nautilus anywhere? > > I was trying to get it to create getters and setters but I don't see > if it does that. Also, there are these tantalizing letters on the side > (S, source code > B, bytecodes > D, decompiled string > I, instance variables > C) class variables > and sometimes a yellow your method is a little bit long > band appears on the > right--which I guess is a warning about length, you method is TOO long > but what are the > numbers? > > characters? Anyway, I agree we should document Nautilus somewhere :( > Also, the category pane is now the package pane, and given my > confusion about the relationship between those, it'd be good to know > how Nautilus is different. > > ===Blake=== > > -- Mariano http://marianopeck.wordpress.com

April 20, 2012

[Pharo-project] [ANN] Physical Etoys 2.0 released!

by Ricardo Moran

Hi everybody (and sorry if you receive multiple copies), I would like to announce a new version of Physical Etoys, now with a lot of new features: 1. First of all, it's based on Etoys 5.0 so it incorporates all the bug-fixes and new features from the Etoys release. 2. We are now focusing on the two main hardware platforms: Arduino and Lego Mindstorms Nxt. For the rest, we will publish a set of "external modules" that you can install in your Physical Etoys version. 3. Also, we now support an argentinian version of Arduino, which is called DuinoBot and it's currently being used in a lot of argentinian schools. 4. We added new devices for arduino and now we also support the use of digital devices attached to analog pins. 5. We added two new objects that let you graph the input of a variable across time and save it to a csv file. 6. We added a new programming mode that lets you compile your scripts and have them running inside the robot, in contrast to running them in the computer and communicate with the robot via bluetooth or usb. We believe this opens a lot of new posibilities for the Physical Etoys users. 7. And finally, we fixed a lot of bugs that make the software a lot more stable (or so we hope :). I would like to use this opportunity to publicly thank all the people from the Etoys community for their work on Etoys 5, this latest version is much better than the last and I encourage you all to try it. And also, I would like to announce that Physical Etoys 2.0 is going to be installed by default on all the laptops of the "Conectar igualdad" program, which is kind of like the argentinian version of OLPC (but for older students). So we are *really* excited about this! Now that you're all as excited as we are :) you can download and try Physical Etoys 2.0 from our blog: http://tecnodacta.com.ar/gira/projects/physical-etoys/. Cheers, Richo

April 20, 2012

[Pharo-project] Nautilus

by blake

Is there any documentation on Nautilus anywhere? I was trying to get it to create getters and setters but I don't see if it does that. Also, there are these tantalizing letters on the side (S, B, D, I, C) and sometimes a yellow band appears on the right--which I guess is a warning about length, but what are the numbers? Also, the category pane is now the package pane, and given my confusion about the relationship between those, it'd be good to know how Nautilus is different. ===Blake===

April 20, 2012

Re: [Pharo-project] OSProcess - is process done?

by Sean P. DeNigris

David T. Lewis wrote > > PipeableOSProcess class>>waitForCommand: is just a loop... David, It doesn't seem like that's the problem because it's intermittent. I can run the exact same command with the same output and sometimes it recognizes that it's complete and sometimes not. I don't know if it's related, but when I do: p := PipeableOSProcess command: '/usr/bin/expect /path/to/expect.exp'. where expect.exp is a wrapper to supply login credentials to ssh, I get a similar problem... p next: 100. "This returns the welcome text from the server... ssh has successfully connected" p nextPutAll: 'ls', Character cr asString. "I send the ls command to the remote server" p atEnd. "Primitive failed <primitive: 'primitiveFileSetPosition' module: 'FilePlugin'> in AttachableFileStream(StandardFileStream)>>primSetPosition:to:" "weird, no?" p upToEnd. "This hangs, even though there is output in the pipe" p next: 5. "In fact, if I get the output a little at a time, I can see the result of the ls command" What do you think? Thanks. Sean -- View this message in context: http://forum.world.st/OSProcess-is-process-done-tp4569088p4575379.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2012

Re: [Pharo-project] One-click Windows comment

by blake

On Fri, Apr 20, 2012 at 12:32 PM, Ricardo Moran <richi.moran(a)gmail.com> wrote: > There is no need for a .Ink or .bat in Windows. You can just point to the > correct image in the .ini file so that users will only click on the .exe > (which should be renamed to Pharo.exe, BTW). > > If I remember correctly, older versions of Pharo did it this way, why did it > change? I would've sworn I recently downloaded a one-click that had a .LNK--that was where I got the idea to do it for this one. It even referenced the .LNK in the readme.bat. That said, I have the Pharo-1.3-13315-OneClick.zip file handy here, and it does just use an .INI file and tell Windows users to just click on the pharo.exe. So, I think all possible ways of starting Pharo have been explored at this point. :-) ===Blake===

April 20, 2012

Re: [Pharo-project] Pharo 1.4 on Reddit

by Marcus Denker

On Apr 20, 2012, at 8:55 AM, Geert Claes wrote: > I noticed the "toybox from mattel" comment, so its probably a good idea to > make sure the screenshots on the Pharo website at > http://www.pharo-project.org/about/screenshots reflect the current release. > The iPhone screenshot should also use a more recent iPhone to indicate Pharo > is on the ball. > I removed all the old screenshots. -- Marcus Denker -- http://marcusdenker.de

April 20, 2012