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

Re: [Pharo-project] strange logic

by Alain Rastoul

Putting a haltOnce in the method shows : MenuMorph>>layoutItems ... self items do: [:item | item icon ifNotNil: [maxIconWidth := maxIconWidth max: item icon width]. item hasSubMenu ifTrue: [item subMenu layoutItems]]. too much layouting is going on (here submenu layout is done even if the submenu is not visible) ... But may be there are other calls Is there a package/tool that trace all message sends for particular methods with stack trace ? Spy ? "Alain Rastoul" <alr.dev(a)free.fr> a Ã©crit dans le message de news: jmsmjm$it8$1(a)dough.gmane.org... > 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] The video about Athens

by Mark Smith

+1 for the descriptive names. Too often I see strange contractions that aren't immediately obvious, and or otherwise inconsistent naming (not just in Smalltalk), and it ruins the illusion of having a consistent whole :). It bugs me a little ;). It would be really cool if we could agree as a community to follow a well-defined naming scheme. I'm rather fond of this book â Smalltalk With Style Any thoughts? Mark On 20 Apr 2012, at 08:47, Igor Stasenko wrote: > On 19 April 2012 18:27, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> It's so great stuff!!! :)) >> >> Is cairo used as athens backend for this demo? >> Is it should work with Bitblt backend? >> >> In demo I see many usage of angel parameter for transformations. Do you >> think about "angel unit objects" like "90 degrees" or "2 radians" instead of >> raw numbers ? >> > there are two methods - rotateByRadians: and rotateByDegrees: > It makes things more explicit, while if i just have > rotate: or rotateBy:, then it will be a bit ambiguous, whether > argument angle is in radians or degrees > (different frameworks assuming different things to be default) > >> How #scaledBy: works with Point argument (self extend) and Float like (frame >> / 100 sin abs) at the same time? What' logic? >> > for uniform scale, you provide a sole number, and for non-uniform - a point, > with x and y scale factors separately. > There is a scaleX:Y: method, while scaleBy: is more for convenience. > >> Best regards, >> Denis >> >> >> 2012/4/19 Igor Stasenko <siguctua(a)gmail.com> >>> >>> Hello, all >>> >>> I recorded a small introductory video about Athens. >>> Here it is: >>> >>> http://vimeo.com/40653315 >>> >>> (about 21 minutes). >>> >>> I explain some basic stuff like drawing things using Athens canvas, >>> building paths, use of transformation matrices etc. >>> >>> Please note, this is a first video i ever recorded in such context in >>> my life, so don't be too harsh :) >>> Also, note that the animations are jagged because of video recording >>> frame rate, not because it is that slow in reality. >>> >>> There are still a blog post pending about it.. which i plan to finish >>> when i will finish ;) >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> > > > > -- > Best regards, > Igor Stasenko. >

April 20, 2012

Re: [Pharo-project] Nautilus

by Sean P. DeNigris

Alain rastoul wrote > > Nautilus is really a cool browser , congrats Benjamin :-) > I especially like the Group view , very useful > Having a chasing senders/implementors browser like the refactoring browser > have would be top. > Having the annotation line telling in wich changeset the method is would > be > cool too. > > Each Pharo release gets better . > +1 to all of that!! Thanks Benjamin :) Also really cool are: * dirty packages show red in browser - really nice... * commit to MC right from browser - sweet! * contextual refactoring menus * resizable columns!!!!!!!!!!!!!!!!! Wish list item (why not): double clicking on column separator fits to contents width (like Mac Finder) Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-tp4575388p4575468.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2012

Re: [Pharo-project] Nautilus

by Alain Rastoul

Right clic on the class name, Refactoring> Class refactoring > Generate accessors . I guess it is what you are looking for (though I didn't do it yet). Nautilus is really a cool browser , congrats Benjamin :-) I especially like the Group view , very useful Having a chasing senders/implementors browser like the refactoring browser have would be top. Having the annotation line telling in wich changeset the method is would be cool too. Each Pharo release gets better . "blake" <dsblakewatson(a)gmail.com> a Ã©crit dans le message de news: CAJAnwP=CpXEJo4t8qY3L2Z8=n-FkeDCosAVxjKeS8wtBNwdrFA(a)mail.gmail.com... > 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] 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