January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Inspect it wrong shortcut
by Mariano Martinez Peck March 3, 2011

March 3, 2011

Hi! With latest pharo 304 in Linux the shortcut for inspect it (ctrl + i) doesn't work but alt + i. I have evaluated Preferences enable: #swapCOntrolAndAltKeys. Actually, all the other shortcuts (browse it, do it, explore it, and so on) works with ctrl + XXX but there is a problem with inspect it. Can someone confirm this ? Cheers, Mariano

7 15

[Pharo-project] Using Pharo from the command-line
by Stefan Marr Dec. 2, 2010

Dec. 2, 2010

Hello: I just try to get started with Pharo to experiment with some benchmarks and would be grateful for some basic hints, since the documentation on pharo-project.org is not to excessive. As far as I read in the documentation of the language shootout[1], I will need the OSProcess package. How can I load this package into the image downloaded from p-p.org? My second problem is to execute code from the command line. I tried a simple example file $ cat test.sq Transcript open; cr; show: 'Hello, world'. $ Squeak\ 4.2.1beta1U.app/Contents/MacOS/Squeak\ VM\ Opt pharo1.0-10418-BETAdev09.08.3.image test.sq But this only leads to a debugger popping up in installSourceFile saying "No content to install". Looks like aStream is nil which should have the data loaded from file:test.sq Any pointers to documentation which might discusses command line related features are very welcome. I actually just need a way to choose a benchmark to be executed from the commandline. The actual code could already be in the image. Many thanks and best regards Stefan [1] http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=squeak&la… -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525 -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

9 12

[Pharo-project] akuhn/SUnit: run faster tests first & step through tests
by Adrian Kuhn Oct. 23, 2010

Oct. 23, 2010

Hi Pharo list, The lastest akuhn/SUnit runs fasters tests first. When running your test suite for the second time, faster tests are run first. For the whole 9000 tests in the dev image, this means that the first 8000 tests are run in like 10 milliseconds. Also I fixed the menues in the test runner, you can now mark either all or single tests are expected defect. If you mark expected defects through the UI they are stored on the class side. The #expectedFailures method on the instance side is still taken into account for compatibility, but storing expected defects on the class side is the preferred way to do it now. I also cleared up the vocabulary. There are no more history on the class side, rather there are two histories one called "last run" and one called "expected defects" that both serve different purposes. The "last run" history is used to mark test results in the browser. The "expected defects" history is used to keep track of expected / unexpected defects. (As far I know, the icons in O2 show this as well.) Plus I added the ability to step through a failed tests. This stops right before the actual test method, rather than at the failed assertion. To step through a failed test, run your tests with the test runner and use the menu of test failures or errors. (OB and O2 might consider adding this option as well. In particular in combination with running fasters tests first a "run and debug/step-through first failure" might be interesting.) To load akuhn/SUnit gofer SystemChangeNotifier uniqueInstance noMoreNotificationsFor: TestCase. Gofer it disablePackageCache; squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load. Thank you all for the awesome feedback last time! More is welcome :) --AA

3 5

[Pharo-project] CLFramework-UIBuilder
by nullPointer July 1, 2010

July 1, 2010

i published the CLFramework package http://www.squeaksource.com/CLFramework.html Is totally alpha version, not valid for serious apps.The set of widgets of Polymoprh adapteds to designer is limited, and donÂ´t works with normal mechanism as MorphicModel, else with events. IÂ´m continue working in it, but I have arrived at crossroads, where i think is best create my own set of widgets, from zero, or perhaps be more ambitious and try use 3d... i dont know; my knowledges is limited. I added new features; can be viewed here: Inlaying a view into another http://www.youtube.com/watch?v=L0dSuunKbEM Adding external files (images only) for use in UIBuilder http://www.youtube.com/watch?v=UXvwieFA_4k Building a context menu http://www.youtube.com/watch?v=cilG97m4u2g For probe the designer only type view := CLUIBuilderMainForm new show. in a workspace. I want to be thankful to Jordi Delgado and Citilab for Smalltalk initiative and lessons, and future events ( ESUG 2010 :) ) Regards -- View this message in context: http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3594252.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 12

[Pharo-project] Keyboard Shortcuts in Pharo?
by Bart Gauquie June 7, 2010

June 7, 2010

Dear all, On my job I'm using Java; and Eclipse as an IDE. I'm discovering Pharo since a year now. I find it in almost every way superior. But not on the following way. I use keyboard shortcuts heavily in Eclipse. I use them to quickly select parts of code, extract methods, rename methods, fields, classes, switch browsing windows, delete a line of code, copy and move lines of code. I tend to miss these shortcuts in Pharo. There are actually a lot of shortcuts (http://news.squeak.org/2007/01/26/looking-for-a-shortcut/ - Andreas comment). But I still find that I have to leave the keyboard way to often and use the mouse to navigate to another window / or part of the browser I'm working in. Let me explain that a bit further. I will try to give some examples of behaviour I'm missing in Pharo. - If I'm editing a class and working in the source view. I'm done, I want to run the tests again I just ran. I have to take the mouse, navigate to the class and hit Alt-t. Or use the test runner. In Eclipse there is a global shortcut Alt-F11 which just runs the test (or even better: the suite of tests) which ran previously. It moreover runs it in the background and if everything is still ok, does not bother you again. It only pops up if something broke. This behaviour is very handy if you're refactoring. You can then with every small change run all relevant tests in matter seconds and continue. - If I'm editing in the source pane. I'm done editing, and I want to navigate for instance to another method. I have to take the mouse to navigate to the methods, scroll and click on the new method. Again had to take the mouse. In Eclipse, there is a Ctrl-O shortcut which brings up a list of all methods in this class. At the top there is an input field in which I can start typing; while typing the list is restricted. I can then using the arrow keys navigate to the method and hit Enter, and I'm in the method. - For switching between browser windows Eclipse also does have a handy mechanism. Eclipse keeps in memory a list of files you're editing ordered by latests usage. I can then quickly navigate through the list by hitting Ctrl-F6. Just hitting Ctrl-F6 navigates to the previous window visited. Hitting it again gets back. If you however hit Ctrl - F6, keep the Ctrl pressed in, and hit F6 again, you navigate the the second last window edited. I use this behaviour constantly to navigate back and forth between the test you're writing and the implementation. - Eclipse also has very keyboard shortcut integration to select/delete parts of the code. Ctrl D deletes the current line. Alt arrow up / down moves the current line (or selection) up or down (while keeping the clipboard selection). Alt-Shift-arrow up/down copies the current line (or selection) up or down (while keeping the clipboard selection). Alt Shift Left arrow / right arrow does a nifty code selection: if the code compiles properly, it will with every next hit on left arrow select a larger block of code. So if my cursor is on a message send, it will first select the message send, next the receiver and the message send, next: if this was a nested, select the part out of that, and so forth. This is very handy if you for instance want to do a extract method refactoring on some part of the code. Just quickly select it using this Alt-Shift selection and extract it. - Which brings me to the refactoring shortcuts, which I'm missing the most. * The most important one is rename. In Eclipse if I select a field, a temporary var, a message, a class, anything that can be renamed; I can always hit Alt-Shift-R to rename it. I don't have to go into a menu, refactor class, or refactor method, or refactor source with the mouse to select rename. Just click on it, hit the shortcut, type the new name and hit Enter. * The next one is Extract Method. After quickly selecting I just hit Alt-Shift-M, give a name (Eclipse guesses a name) and I extract. * Another very useful one is Extract Local Variable using Alt Shift L. I'm very well aware of the fact that in Smalltalk you typically only need half of the lines of code to achieve the same, but still I'm missing this kind of behaviour to quickly navigate, adapt code, run tests, ... All the tools are there in Pharo, but I just feel that they need a little better keyboard integration. How are experienced Smalltalkers feeling about this? Are there any solutions available already that I haven't found ? If not, I'm more than happy to implement some of these, but my knowledge of Morphic is still rather limited. Can anyone provide me with some pointers how to achieve that? Kind Regards, Bart -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein Gravitation is not responsible for people falling in love. - Albert Einstein

10 25

[Pharo-project] [ANN] Metacello configuration of OSProcess
by Miguel Enrique CobÃ¡ Martinez April 24, 2010

April 24, 2010

Hi all, I have published the ConfigurationOfOSProcess in the MetacelloRepository of squeaksource. With this you can load OSProcess and its tests in PharoCore. Just evaluate in a workspace: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOSProcess'; load. Then evaluate ((Smalltalk at: #ConfigurationOfOSProcess) project version: '4.3.11') load. to load just the OSProcess, or: ((Smalltalk at: #ConfigurationOfOSProcess) project version: '4.3.11') load: 'Tests'. to load OSProcess and their tests. Tested in PharoCore 10506 Enjoy! -- Miguel CobÃ¡ http://miguel.leugim.com.mx

4 5

[Pharo-project] SUnit
by Adrian Kuhn April 6, 2010

April 6, 2010

Niko and me are thinking about doing some work on SUnit. Background is that we are working on Phexample, which extends SUnit with test that expand on one another [1]. We got test dependencies working with the current SUnit, but had to do some quick ugly hacks. So we thought about cleaning the internals SUnit up, and then include test dependencies in the core. Things we would possible change (we will certainly identify more as we clean up SUnit...) - store test resources in a dynamic variable rather than a static one - refactor the assert: protocol to a trait, such that they can be used in setup and teardown of test resources as well (actually I already did that, you can find a version on my squeaksource account) - apply the fixes to test resources in Niall's slide deck that Lukas showed us - add expectations matchers as used in behavior-driven testing - break testcase into two classes, and to run the test and one to store the result (no more #cleanUpInstanceVariables hack to avoid memory leaks) - add test dependencies to test results, such that one test can extend on the return value of another test - fix expected failures such that they are a first-class result (no more #shouldPass with O(n^2) or worse behavior) So you see, the idea is twofold: first to clean up what is there, and second to add test dependencies as a new feature. For those that dont know test dependencies. They had first been proposed by Markus GÃ¤lli based on an analysis of all Squeak tests years ago. He found that most tests cover a superset of another test's coverage set. A prototype in Java as been implemented later by Lea HÃ¤nsenberger and me. We published a case study at XP 2008, which lead to PHP folks to include test dependencies in the latest PHPUnit. The idea of explicit test dependencies is to shift the burden of isolating test cases from the developers to the framework. You avoid duplicate test code and you get less red test cases per failure. Please refer to Niko's blog post for more details [2]. We got some more ideas (such as API baseline testing, search in test results, etc...) but they will not likely make it into a first clean up. One thing we do not know is how many folks are out there that depend on internal representation of SUnit. I talked to some folks and identified two requirements, first that legacy tests should keep running and second that contributions to other sunit forks should keep being mergeable. The first seems feasible, the second sounds like it boils down to not cleaning anything :) What do you think? cheers, AA [1]: http://www.squeaksource.com/phexample.html [2]: http://smalltalkthoughts.blogspot.com/2009/11/phexample-because-examples-ex…

15 65

[Pharo-project] New profiler for Pharo: tester wanted!
by Alexandre Bergel March 25, 2010

March 25, 2010

Dear List, Over the last few months I put some effort on a new profiler for Pharo. It has been used on a number of projects. Time has come to share it with you. To install it, just doit the following expression in a workspace (Mondrian will also be installed): -=-=-=-=-=-=-=-=-=-=-=-= Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSpy'; load. (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault -=-=-=-=-=-=-=-=-=-=-=-= To invoke the profiler, use the following template: ProfilingPackageSpy viewProfiling: [ "YOUR CODE" ] inPackage: 'YourPackageName' ProfilingPackageSpy viewProfiling: [ "YOUR CODE" ] inPackagesMatching: 'PackageName*' Replace "YOUR CODE" by an expression. Some examples are provided in the class ProfilingPackageSpy (method category 'example'). You can find profilings of Mondrian, Glamour, Moose/CAnalyzer, O2. The profiling of Mondrian looks like this: -=-=-=-=-=-=-=-=-=-=-=-= ProfilingPackageSpy viewProfiling: [ | view | view := MOViewRenderer new. view nodes: (1 to: 100) forEach: [:each | view nodes: (1 to: 100)]. view root applyLayout ] inPackage: 'Mondrian' -=-=-=-=-=-=-=-=-=-=-=-= There are two things you should keep in mind: - "YOUR CODE" will be executed twice. The first time with message Tally, then the second time with the full instrumentation. The second execution should not be impacted by the first execution. - You cannot instrument the whole image. I need more time to make this happens. Therefore, you cannot provide '*' to inPackagesMatching: How to read the picture: - big rectangle are classes - edges represent class inheritance - inner rectangles are methods: * height = total time that the method has been executed * width = number of time the method has been executed * color = number of different receiver: white = the method has been executed on 1 receiver. black = many receivers You can do a right-click on a method, and select viewInvocation. This opens a second view that show the execution flow. A different mapping of metrics is used: - rectangle = methods - edges = invocation (upper invokes below) - gray color = method that always return 'self'. It corresponds to void methods in Java or C++. It is therefore likely that the method performs a side effect - yellow color = method that always returns the same value for a particular object - width and height are as in the first visualization Keep in mind that you mind encounter a freeze of your image if you instrument sensitive methods. I would be sincerely delighted to have experience report on this. Regards, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

8 17

[Pharo-project] [update] 10472
by Adrian Lienhard March 20, 2010

March 20, 2010

Issue 1310: Make all tests green (not complete yet) - Remove class MethodHighlightingTests - ParseNode removeSelector: #addCommentToMorph: - Fix SelfEvaluatingObjectTest>>testArray ({1 + 0 . 1 @ 2 . 3}' prints '{1. 1@2. 3}) - Remove method CompiledMethod>>primitiveNode as it is not used anymore - Fix toolbuilder tests (sort of) - Fix Decompiler>>decompileBlock: (regression of closure fixes). This makes BlockContextTest>>testDecompile pass again - Make BlockContextTest>>testTrace run by commenting out broken part of code simulation Issue 1308: FixedIdentitySet = fails when compared with an integer ___________________ http://www.adrian-lienhard.ch/

6 8

[Pharo-project] For those who use Nabble ....
by Geert Claes March 11, 2010

March 11, 2010

I managed (with some assistance from Nabble support) to group several Smalltalk mailing lists on Nabble under the common category "Smalltalk" (http://n4.nabble.com/Smalltalk-f1294792.html) To get them all to appear together the Pharo forums had to move Pharo to the a common n4 server or something, so the links to the Pharo-Smalltalk and Pharo-Smalltalk-Users forums need to be updated on the Pharo website (although the old links will still work for some time) to: Pharo-Smalltalk: http://n4.nabble.com/Pharo-Smalltalk-f1294837.html Pharo-Smalltalk-Users: http://n4.nabble.com/Pharo-Smalltalk-Users-f1310670.html -- View this message in context: http://n4.nabble.com/For-those-who-use-Nabble-tp1310998p1310998.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

11 28