- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Mac like editing?

by Chris Muller

Hi, I used eclipse for about 5 years, and liked many aspects of its editor and keyboard shortcuts. However, there are a couple of things about Pharo's ParagraphEditor that correlate to what you want: > cmd + -> : go to end of line END key > cmd + <- : go to beginning of line HOME key > alt + -> : go to end of the current word Control+[right-arrow], left-arrow > alt + -> : go to beginning of current word You mean alt + <- ?? Control+[left-arrow] > alt + arrow up : switch the line above with the current line (current line > has line number -1, line above has line number +1) In Pharo, you can swap any two _selections_, not just lines. This is much more useful since often expressions span multiple lines. To use: 1) select the first selection 2) select the second selection (the first becomes unselected) 3) press Command+e, to "exchange" them. > alt + arrow down : switch the line below with the current line > cmd + l : delete line (I know this shortcut is used to cancel changes at the > moment. Still, I haven't found a shortcut yet that deletes a single line) I'm not sure how useful it would be for a Smalltalk editor to start putting in "line"-oriented commands but... I've always preferred disabling: wordStyleCursorMovement and then you can delete an "line" easily with the keyboard with the following key-sequence: Shift+Home, Shift+End, Delete > I'd LOVE to see this in Pharo, or at least be able to configure the > shortcuts myself. I think, being able to change the shortcuts is important > anyway because each developer has an own style. > I'd try to come up with a solution myself but I just don't have the time at > the moment. > Thanks for listening to my yapping :) > Max > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 2, 2010

[Pharo-project] libGLU.so.1: cannot open shared object file: No such file or directory

by StÃ©phane Ducasse

I'm using Pharo for the first time as a beginner. My O/S is $ uname -a Linux shevek 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux which is OpenSuSE 11.2 I downloaded and unzipped Pharo-1.1-OneClick.app with this result: $ pwd /home/greg/Play/Lang/Special/Pharo/Pharo-1.1-OneClick.app $ ./pharo.sh libGLU.so.1: cannot open shared object file: No such file or directory could not find module vm-display-X11 Aborted However, the module does seem to exist: $ find . -name '*vm-display-X11*' ./Contents/Linux/so.vm-display-X11 I look forward to running Pharo and sharing it with my friends when it comes up reliably for newbies like me on Gnu/Linux - something which Squeak has not yet achieved! Thanks, _Greg J. Greg Davidson Read moreâ¦

Aug. 2, 2010

[Pharo-project] ProgressDisplay package features

by Ralph Boland

Cool Can you tell us some of the added features? Stef > I recently released the first draft of my package ProgressDisplay to > SqueakSource. > It is like SystemProgressMorph et. al. but with a lot of bells and > whistles added. > It is not a suitable replacement for SystemProgressMorph though because it is > too large and specific for that. Well you asked for it: 1) You can pass an applyBlock rather than a duringBlock. The progressDisplay then applies the apply block to each element to each of the users values updating the display as it does so. The users values can be the values min..max or the values of a stream. 2) You can set a jump value k such that the display is updated once for each k times a display update request is sent. The minimum time that must pass before the display is updated is settable (it is fixed with SystemProgressMorph). Finally, a check is made that a display request update will actually modify the progressBar before the modification is performed. These changes were made because with SystemProgressMoprh, in some circumstances, the progressBar could take excessive amounts of time. However the last of these changes was probably all that was needed. 3) You can set the progressDisplay to catch user interrupts. Unfortunately this doesn't work correctly currently. The interrupt is caught but not processed until the progressBar closes. :-( I don't know how to fix this so suggestions or a fix most welcome. 4) You can set the start point to be other than at the beginning. If you start not at the beginning then you can set the progressDisplay to wrap once the end is reached. This is a weird feature but I need it for when I run a large collection of tests (not SUnit tests but similar). Say I run 1000 tests and the 900th test fails. I fix the problem and rerun the tests. I don't want to start at test one, I want to start at test 900, run tests 900-1000 and then run tests 1-899. The ProgressDisplay supports this and is the main reason I created it. 5) I have added an exception EarlyCompletionExit. This exception will be caught by progressDisplay if generated and result in the current progressBar being closed cleanly. If there is only one progressBar the entire display is closed. 6) If you want you can display the current value being processed and the total. The current value can be the user's value, the count of processed values, count of the number of user values remaining to be processed, the estimate of the amount of time remaining, or the time remaining estimate alternating with one of user value, count, countDown. The current value and total can be labelled if desired. The start poin, if not the beginning, can also be labelled. 7) The display does not flicker as much as SystemProgressMorph though this could still be improved. 8) Anything else I have forgotten. There are large number of examples in class RunnProgressMorphExample which is a subclass of ExampleCase. In my image ExampleCase is an subclass of CodeCase and TestCase is also a subclass of CodeCase. Someday I hope to have TestCase refactored to have CodeCase as a superclass in Squeak/Pharo. The examples use a number of utility classes which will eventually be moved to other packages. Some of them are: 1) ArrayPermutationsStream. Generates the permutations of a SequenceableCollection in a stream. Iteration, not recursion, is used. Ordering is not Lexicographic. 2) RangeList. Stores a sorted list of values where consecutive values are stored by listing them as an Interval. Example: 1,5-9,12,15,31-90 Example: $a,$c,$k-$t,$z This class is not complete. There are two subclasses: NumberRangeList and PositiveNumberRangeList also not complete. 3) NumberRangeListStream. Stream version of NumberRangeList. 4) NumericMultiplicityPartitionStream. For a given integer n, generates all numeric partitions of n (sums of positive numbers that add up to n) in lexicographic order. This can be combined with method SequenceableCollection>>multisetPermutationsDo: to generate arrays of size n containing combinations of the elements of 1..n with replacement (i.e. duplicates allowed). In another package I plan to use this for generating large numbers of test cases. There are also a scattering of useful methods in places like Object, Nil, and SequenceableCollection. Hope this helps. Ralph Boland

Aug. 2, 2010

Re: [Pharo-project] Test Runner 'File out results' button

by laurent laffont

On Mon, Aug 2, 2010 at 4:30 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Recently the button 'File out results' was added to the test runner. > > I find this button extremely annoying because it is something i don't > use daily and it doesn't fit into the group of run-action like all the > other buttons. I keep on accidentally clicking it. > > Why wasn't this action added to the context menu on the test results > that already has related items like 'History', 'Store results', 'Show > progress'? > Because the issue was "Button in TestRunner to fileout the test results" :) http://code.google.com/p/pharo/issues/detail?id=1281 For myself, I don't really care. Anyone for context menu ? Laurent > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 2, 2010

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by laurent laffont

On Mon, Aug 2, 2010 at 12:11 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > TestResult when: TestCaseStarts do: [:event | do some stuff ]. > > > > TestResult when: TestCaseEnds do: [:event | do some stuff ]. > > Currently, the announcer is stored in TestCase. For me, it looks more > intuitive to do > MyTestCase announcer on: TestCaseAnnouncement do: [:ann | ... ]. > > than dealing with TestResult. > > I am okay to move the announcer in TestResult, but that's look a bit to me. > Don't you feel? > I'm currently playing with annoucements in TestResult. Indeed what I want to set in the TestCaseEnded: - is the test has #pass, #failure or #error - for failure and error, store the Exception so we can now why. But until I propose something, keep the implementation which fits your needs :). Laurent > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 2, 2010

Re: [Pharo-project] about ToolBuilder

by Lukas Renggli

I agree that it should be removed, but this means that many tools need to be rewritten in plain morphic. Lukas 2010/8/2 Richard Durr <richard.durr(a)googlemail.com>: > +1. > See Gilad's text about least common denominator in UI-widgetery > > On Fri, Jul 30, 2010 at 12:20 PM, stephane ducasse > <stephane.ducasse(a)free.fr> wrote: >> >> Hi guys >> >> during the sprint I discussed with Gary about ToolBuilder and we think >> that it would be better to remove it >> since a lot of new widgets are not covered so this means that we will be >> constantly limiting ourselves. >> Of course ToolBuilder is a nice idea (if we would have several UI >> framework). So far we got only one >> and we would have several we would have to take the smallest common >> denominator. >> Another idea would be to extend toolBuilder to support new widgets. >> So what do you think? >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Aug. 2, 2010

Re: [Pharo-project] about ToolBuilder

by Richard Durr

+1. See Gilad's text about least common denominator in UI-widgetery On Fri, Jul 30, 2010 at 12:20 PM, stephane ducasse <stephane.ducasse(a)free.fr > wrote: > Hi guys > > during the sprint I discussed with Gary about ToolBuilder and we think that > it would be better to remove it > since a lot of new widgets are not covered so this means that we will be > constantly limiting ourselves. > Of course ToolBuilder is a nice idea (if we would have several UI > framework). So far we got only one > and we would have several we would have to take the smallest common > denominator. > Another idea would be to extend toolBuilder to support new widgets. > So what do you think? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 2, 2010

Re: [Pharo-project] Pharo 1.1 host menu os x

by Mariano Martinez Peck

On Mon, Aug 2, 2010 at 3:53 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > shouldn't that be added as a package to the general images? otherwise > this will always be a potential error when pushing fixes? > > YESSSSSS!! PLEASEEEEE I already said this. We should add PharoTreatedInbox repository in standard PharoCore images. Can you open a ticket? > cheers, > Mike > > 2010/8/2 laurent laffont <laurent.laffont(a)gmail.com>: > > On Mon, Aug 2, 2010 at 2:43 PM, Michael Roberts <mike(a)mjr104.co.uk> > wrote: > >> > >> Hi, > >> i am trying to publish a fix, but I get MC error can't find > >> HostMenus-LaurentLaffont.53. It is the ancestor of > >> HostMenus-MarcusDenker.54 but does not seem to be in the /Pharo > >> package. Where did it go? > >> > > > > It's in PharoTreatedInbox at least as integrated fixes go there. > > http://www.squeaksource.com/PharoTreatedInbox > > Laurent. > > > >> > >> thanks, > >> Mike > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 2, 2010

[Pharo-project] Test Runner 'File out results' button

by Lukas Renggli

Recently the button 'File out results' was added to the test runner. I find this button extremely annoying because it is something i don't use daily and it doesn't fit into the group of run-action like all the other buttons. I keep on accidentally clicking it. Why wasn't this action added to the context menu on the test results that already has related items like 'History', 'Store results', 'Show progress'? Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 2, 2010

Re: [Pharo-project] Pharo 1.1 host menu os x

by laurent laffont

On Mon, Aug 2, 2010 at 3:53 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > shouldn't that be added as a package to the general images? otherwise > this will always be a potential error when pushing fixes? > That goes beyond my knowledge :) Stupid question, as there's HostMenus-MarcusDenker.54, why HostMenus-LaurentLaffont.53 is needed ? Laurent > > cheers, > Mike > > 2010/8/2 laurent laffont <laurent.laffont(a)gmail.com>: > > On Mon, Aug 2, 2010 at 2:43 PM, Michael Roberts <mike(a)mjr104.co.uk> > wrote: > >> > >> Hi, > >> i am trying to publish a fix, but I get MC error can't find > >> HostMenus-LaurentLaffont.53. It is the ancestor of > >> HostMenus-MarcusDenker.54 but does not seem to be in the /Pharo > >> package. Where did it go? > >> > > > > It's in PharoTreatedInbox at least as integrated fixes go there. > > http://www.squeaksource.com/PharoTreatedInbox > > Laurent. > > > >> > >> thanks, > >> Mike > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 2, 2010