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

Re: [Pharo-project] strange autocomplete behavior

by ClÃ©ment Bera

There was a discussion about that recently now the autocompletion is partially done with tab and partially with enter by default. In your case tab didn't work because it was necessary to use enter. You can change in the setting browser to your favorite setting. 2013/3/3 stephane ducasse <stephane.ducasse(a)free.fr> > Check the setting because there are many setting related to the > autocompletion. > > Stef > > On Mar 3, 2013, at 1:46 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> > wrote: > > Hi guys, > > I don't know if any of you experience this problem, but with last versions > of Pharo I have a strange behavior with code completion. > > The autocomplete list shows as I should, however after selecting an item > hitting tab does not always completes the code as it should. > > For example try something like while typing Configuration... > > Do someone have an idea why this happens? > > Cheers, > ciprian > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro > > >

March 3, 2013

[Pharo-project] Pastell is now migrated to SmalltalkHub and has a nice CI job

by StÃ©phane Ducasse

Hi guys Pastell is now migrated to SmalltalkHub and has a nice CI job https://ci.inria.fr/pharo-contribution/ Did I said that I love continuous integration :). So coooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooool

March 3, 2013

Re: [Pharo-project] strange autocomplete behavior

by Mariano Martinez Peck

On Sun, Mar 3, 2013 at 9:46 AM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com > wrote: > Hi guys, > > I don't know if any of you experience this problem, but with last versions > of Pharo I have a strange behavior with code completion. > > The autocomplete list shows as I should, however after selecting an item > hitting tab does not always completes the code as it should. > > Yes, it happened to me. What is more weird is that when tab does not work, doing an "enter" does indeed work! weird.... However, it is even worst because it is like if it forgets about what I already typed, and it paste the whole word again (so I have duplicated parts now) The problem is that it is difficult to reproduce... > For example try something like while typing Configuration... > > Do someone have an idea why this happens? > > Cheers, > ciprian > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro > -- Mariano http://marianopeck.wordpress.com

March 3, 2013

Re: [Pharo-project] about run tests from nautilus

by Stefan Marr

Hi Benjamin: On 03 Mar 2013, at 10:55, Benjamin wrote: > Because some one decided that methods starting with "should" are also tests I added that change, because I didn't see an easy and extensible way to do it differently. Please see https://code.google.com/p/pharo/issues/detail?id=7367 If you could provide me with a proper hook in Nautilus, or use the facilities in SUnit to determine whether a method is a test that would be much better and avoid Stephane's problems. Thanks Stefan > > Ben > > On Mar 3, 2013, at 10:38 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi ben >> >> I do not know if you saw this behavior but when I press the button on the class of a test methods that are not tests >> are also executed and reported as failures. >> For example I got >> >> XMLNodeTest>>should: aBlock enumerate: aCollection >> | enumerated | >> >> enumerated := OrderedCollection new. >> aBlock value: [:each | enumerated add: each]. >> self assert: enumerated = aCollection asOrderedCollection. >> >> executed while it is an helper. >> With the testrunner I get a class with 100% green tests now. >> but not with nautilus. >> >> Stef > -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

March 3, 2013

Re: [Pharo-project] strange autocomplete behavior

by stephane ducasse

Check the setting because there are many setting related to the autocompletion. Stef On Mar 3, 2013, at 1:46 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > Hi guys, > > I don't know if any of you experience this problem, but with last versions of Pharo I have a strange behavior with code completion. > > The autocomplete list shows as I should, however after selecting an item hitting tab does not always completes the code as it should. > > For example try something like while typing Configuration... > > Do someone have an idea why this happens? > > Cheers, > ciprian > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro

March 3, 2013

Re: [Pharo-project] about run tests from nautilus

by stephane ducasse

pfffff can we stop such kind of mess. I frankly do not see the value of self should not be = $a vs self assert: self = $a I looked and most of the tests in Moose do not gain anything to rely on phExample. And now such change break nautilus. Stef >> Because some one decided that methods starting with "should" are also tests > > we can be a bit more precise, > > (selector beginsWith: 'should') and: [ (selector at: 'should' size + 1) isUppercase ] > >> >> On Mar 3, 2013, at 10:38 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi ben >>> >>> I do not know if you saw this behavior but when I press the button on the class of a test methods that are not tests >>> are also executed and reported as failures. >>> For example I got >>> >>> XMLNodeTest>>should: aBlock enumerate: aCollection >>> | enumerated | >>> >>> enumerated := OrderedCollection new. >>> aBlock value: [:each | enumerated add: each]. >>> self assert: enumerated = aCollection asOrderedCollection. >>> >>> executed while it is an helper. >>> With the testrunner I get a class with 100% green tests now. >>> but not with nautilus. >>> >>> Stef >> > >

March 3, 2013

[Pharo-project] [ANN] Moose 4.7

by Tudor Girba

We are happy to announce the Moose Suite version 4.7: http://moosetechnology.org/download What is new: â¢ Integration of the Roassal visualization engine â¢ New PetitParser browser with integrated refactorings â¢ Improved Glamorous Toolkit for Pharo including the Glamorous Inspector and Debugger â¢ Several features in Glamour including Watcher support (similar to OS X preview) â¢ Significant improvements in FAMIX â¢ Improved external VerveineJ parser for Java â¢ Based on Pharo 1.4 A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Have fun, The Moose Team

March 3, 2013

[Pharo-project] strange autocomplete behavior

by Ciprian Teodorov

Hi guys, I don't know if any of you experience this problem, but with last versions of Pharo I have a strange behavior with code completion. The autocomplete list shows as I should, however after selecting an item hitting tab does not always completes the code as it should. For example try something like while typing Configuration... Do someone have an idea why this happens? Cheers, ciprian -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

March 3, 2013

Re: [Pharo-project] Spreadsheet widget

by Ben Coman

stephane ducasse wrote: > Hi ben > > I added you as contributor. > That worked. Thanks. > >>> >>> >> Thanks Stef. I've just signed up to Smalltalkhub. How do I contribute to the project? >> The following has been added to the attached mcz. >> * Pharo 1.4 does not have LayoutFrame>>identity. >> > > We should use 2.0 > I am in the middle of writing up my Masters project based on Pharo 1.4 (Moose 4.7). As soon as that is done I'll be moving it to Pharo 2.0. > >> * Allow external control of spreadsheet using SpreadsheetGridMorph>>cellStringAt:put: & cellStringAt: and added associated test. >> * Fixed error with SpreadsheetCell>>printOn: missing Integer>>printAsColumnRefOn: and added associated test. >> * To assist tracing/learning the code, added a few commented halt points. Worked around 'editedCell' instance variable losing its value while in debugger, which probably needs further review. >> > > cool :) > > >> cheers -ben >> >> <Spreadsheet-BenComan.3.mcz> >> > > > >

March 3, 2013

Re: [Pharo-project] about OrderedCollection new replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1

by Ben Coman

stephane ducasse wrote: > On Mar 3, 2013, at 10:23 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 03 Mar 2013, at 10:20, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >> >>> Hi sven >>> >>> yes I imagine now we should improve in trakcing such changes. >>> In addition I do not understand why >>> >>> XMLOrderedList new: 10 >>> >>> breaks the inspectorâ¦. >>> >> Yes, I once saw that as well, very strange, I guess that is what happens when you start making your own collection classesâ¦ >> > > Yes they said that the inspector class is OrderedCollectionInspector but it does not work so I changed it to get the system > debuggable right now. > Not sure if this is related, but back when I was using Squeak and just new to the system I was debugging through OrdereredCollection and got an MNU. OrderedCollectionInspector was somehow related but I don't quite remember the details, except that some of it is documented here... http://forum.world.st/OrderedCollection-gt-gt-size-fails-in-debugger-td3657… -ben > Stef > > >>> This is why all the important libraries should be covered by a jenkins job and tests. >>> So that right on the spot we can identify problems. >>> >>> Stef >>> >>> >>> >>>> These important changes were made intentionally, so we need to find the rationale of the change. >>>> Like is the new behavior covered by new tests ? >>>> >>>> On 03 Mar 2013, at 09:45, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> >>>> >>>>> On Mar 3, 2013, at 9:42 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>> >>>>> >>>>>> I could overwrite XMLOrderedList >>>>>> >>>>>> replaceFrom: aStartingIndex to: anEndingIndex with: aCollection startingAt: aReplacementStart >>>>>> >>>>>> >>>>>> collection >>>>>> replaceFrom: aStartingIndex >>>>>> to: anEndingIndex >>>>>> with: aCollection >>>>>> startingAt: aReplacementStart >>>>>> >>>>>> to make it grow? But I do not really know the impact on the XML library >>>>>> >>>>>> >>>>>>> self makeRoomFor: (anEndingIndex- self capacity). >>>>>>> >>>>>> any idea? >>>>>> >>>>> In fact it will not work since makeRoomFor: and others have been removed and I do not have the time to dive in >>>>> OrderedCollection growing logic. >>>>> >>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Mar 3, 2013, at 9:34 AM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >>>>>> >>>>>> >>>>>>> Hi guys >>>>>>> >>>>>>> in 1.2.1 >>>>>>> >>>>>>> OrderedCollection new replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1 >>>>>>> gave >>>>>>> an OrderedCollection(6 7 8 9 10) >>>>>>> >>>>>>> >>>>>>> while in 1.4 and 2.0 >>>>>>> OrderedCollection new replaceFrom: 1 to: 5 with: #(6 7 8 9 10) startingAt: 1 >>>>>>> raised an error >>>>>>> >>>>>>> Do you have an idea how I can handle that? Because XMLObservableList and XMLOrderedList implements >>>>>>> replaceFrom: to: with: startingAt: >>>>>>> >>>>>>> because there is no self makeRoomFor: (stop - self capacity) invocation. >>>>>>> >>>>>>> >>>>>>> in 1.4>> >>>>>>> replaceFrom: start to: stop with: replacement startingAt: repStart >>>>>>> "This destructively replaces elements from start to stop in the receiver >>>>>>> starting at index, repStart, in the sequenceable collection, >>>>>>> replacementCollection. Answer the receiver. No range checks are >>>>>>> performed." >>>>>>> >>>>>>> | index repOff | >>>>>>> repOff := repStart - start. >>>>>>> index := start - 1. >>>>>>> [(index := index + 1) <= stop] >>>>>>> whileTrue: [self at: index put: (replacement at: repOff + index)] >>>>>>> >>>>>>> at: anInteger put: anObject >>>>>>> "Put anObject at element index anInteger. at:put: cannot be used to >>>>>>> append, front or back, to an ordered collection; it is used by a >>>>>>> knowledgeable client to replace an element." >>>>>>> self ensureBoundsFrom: anInteger to: anInteger. >>>>>>> ^array at: anInteger + firstIndex - 1 put: anObject >>>>>>> >>>>>>> >>>>>>> in 1.2.1 >>>>>>> >>>>>>> replaceFrom: start to: stop with: replacement startingAt: repStart >>>>>>> "An ordered collection is growable, so a call to this can make the collection grow." >>>>>>> self makeRoomFor: (stop - self capacity). >>>>>>> array >>>>>>> replaceFrom: start + firstIndex - 1 >>>>>>> to: stop + firstIndex - 1 >>>>>>> with: replacement >>>>>>> startingAt: repStart. >>>>>>> lastIndex := lastIndex max: stop + firstIndex - 1. >>>>>>> >>>>>> >>>>> >>>> >>> >> > > > >

March 3, 2013