- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12253
by Marcus Denker Nov. 24, 2010

Nov. 24, 2010

12253 ----- Issue 3280: Focus indicator for pluggable text morphs not correctly drawn -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3280 in pharo: Focus indicator for pluggable text morphs not correctly drawn
by pharo＠googlecode.com Nov. 24, 2010

Nov. 24, 2010

Status: New Owner: gazzaguru2 CC: marcus.denker New issue 3280 by gazzaguru2: Focus indicator for pluggable text morphs not correctly drawn http://code.google.com/p/pharo/issues/detail?id=3280 Fix below... TextMorphForEditView keyboardFocusChange: aBoolean "rr 3/21/2004 22:55 : removed the #ifFalse: branch, which was responsible of the deselection of text when the paragraph lost focus. This way selection works in a more standard way, and this permits the menu keyboard control to be really effective. Changed to update focus indication." paragraph ifNotNil: [paragraph focused: aBoolean]. aBoolean ifTrue: ["A hand is wanting to send us characters..." self hasFocus ifFalse: [self editor "Forces editor install"]. self editor focused: true. self useFindReplaceSelection ifTrue: [self selectionChanged]. Editor blinkingCursor ifTrue: [self startBlinking]] ifFalse:[editor ifNotNil: [editor focused: false]. self stopBlinking]. self editView ifNil: [self focusChanged] ifNotNil: [self editView focusChanged]

1 10

Re: [Pharo-project] Fwd: [Pharo-users] TestMock: a full featured mock testing framework now available in SqueakSource
by StÃ©phane Ducasse Nov. 24, 2010

Nov. 24, 2010

PharoCore should be really small at the end. Why a testing framework should be in the core when you can load it and load the tests? Stef > I'm lost ... actually tests are in PharoCore. It is planned to remove them ? > > Laurent > > On Wed, Nov 24, 2010 at 2:29 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Nothing should be in the core (not even the tests) > in the core we should have a way to load package from a distribution server. > > Now if this is in Pharo-dev this is another story :) > We can get tests and mock and mock framework. > > Stef > > > > I agree with you Dennis. TDD practices are far ahead in Ruby / Java / Python world. > > > > BUT IMHO can be a real cool neaty great platform for TDD because we have: dynamic development. > > > > What I think we miss: > > - put a Mock framework in PharoCore - Mocks should be a standard tool even for low-level stuff > > - introduce pragmas to declare tests / setUp / tearDown methods so I can write > > > > AddressBookWithLaurentAndDennis>>createAddressBook > > <setUpTest> > > bla bla > > > > AddressBookWithLaurentAndDennis>>shouldHaveNumberOfContactsAnswersTwo > > <test> > > blabla > > > > AddressBookWithLaurentAndDennis>>ifDennisRemovedNumberOfContactsShouldAnswersOne > > <test> > > bla bla > > > > > > > > - (harder) interface to / creation of an executable requirements / BDD framework like Cucumber http://cukes.info/ > > > > Laurent > > > > > > On Wed, Nov 24, 2010 at 4:31 AM, Dennis Schetinin <chaetal(a)gmail.com> wrote: > > As for me, I'm simply unable to establish smooth test-driven process without Mocks. I think it does not depend on language at all. > > > > Without mocks I have to divide the task I have into smaller independent parts. It's actually an up-front design. I can make a mistake (I usually do); even worse it's often just impossible to accomplish because too many subcomponents usually interact thoroughly and I simply don't know which one to implement first :). So, without mocks I have to code bottom-up, from details to general. This is unnatural and error-prone. > > > > With mocks I can start directly from the task I have. I get a use case and write a test for the one. Creating the test I detect subcomponents needed, understand how they should interact and document that in the same test. As those subcomponents do not exist yet, I have to specify them and their behavior right in the test (if I don't want to break the process I've just started). That's why I really need mocks. Then I can take another use case or implement one of the mocks I used as a real object and so on. Thus, mocks allow me to go top-down and implement only the things I really need, not the things I think I'll need. > > > > Are there other, maybe better, approaches? > > > > Concerning TDD popularityâ¦ I'm not sure TDD plays the role it should in Smalltalk community. > > > > Messing with Smalltalk for about 7â8 years, I can't say I often see real TDD code. About 50â70% (depending on Smalltalk dialect) of frameworks I use have no tests at all. The rest often looks being tested a posteriori. Perhaps, Pharo is the only exclusionâ¦ > > > > And if TDD is really popular and widely used, why do we have so much regression bugs even in core subsystems even in commercial Smalltalks? > > > > Please, correct me if I'm wrong. > > > > 2010/11/23 laurent laffont <laurent.laffont(a)gmail.com> > > > > On Tue, Nov 23, 2010 at 5:39 PM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > Hi Dennis, > > > > Yes, TDD is highly popular and encouraged in the Smalltalk community. > > And mocks are not necessary in most cases. > > > > > > Hi Luc, > > > > why Mocks are less necessary in Smalltalk than in other (Ruby/Python/whatever...) languages ? Do you have some examples / link ? > > > > Sometimes I think a mocking library should be in PharoCore so I don't need to write my own mocks..... > > > > > > Cheers, > > > > Laurent > > > > > > > > > > #Luc > > > > > > 2010/11/23 Dennis Schetinin <chaetal(a)gmail.com> > > > > How is it compared to Mocketry (http://www.squeaksource.com/Mocketry.html)? SMock? > > > > BTW, isn't TDD without mocks a bit incomplete? And is TDD popular among smalltalkers actually? > > > > 2010/11/22 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > > This is cool Anindya. I don't need mocks right now, but I will keep it in mind! > > > > I cc'ed Pharo-dev mailing list. > > > > Cheers > > > > Mariano > > > > ---------- Forwarded message ---------- > > From: Anindya Haldar <anindya_haldar(a)yahoo.com> > > Date: Mon, Nov 22, 2010 at 10:11 AM > > Subject: [Pharo-users] TestMock: a full featured mock testing framework now available in SqueakSource > > To: pharo-users(a)lists.gforge.inria.fr > > > > > > Dear Pharoers, > > > > TestMcok is a full featured mock based test framework that I am very glad to contribute to the community. It is in squeaksource under the project name TestMock. Please feel free to try it, and feedback will be greatly appreciated. The wiki section includes a brief how-to guide with code examples. > > > > Regards, > > Anindya Haldar > > > > > > > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > > > > > > > > -- > > Dennis Schetinin > > > > > > > > > > > > -- > > Dennis Schetinin > > > > >

2 1

[Pharo-project] Issue 3286 in pharo: SmalltalkImage>>#removeSelector: and Behavior>>#removeSelector:
by pharo＠googlecode.com Nov. 24, 2010

Nov. 24, 2010

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3286 by Benjamin.VanRyseghem.Pharo: SmalltalkImage>>#removeSelector: and Behavior>>#removeSelector: http://code.google.com/p/pharo/issues/detail?id=3286 Which method should be used ? Which one should have comment modified ?

1 2

[Pharo-project] Issue 3285 in pharo: Obsolete ConfigurationOfRFB
by pharo＠googlecode.com Nov. 24, 2010

Nov. 24, 2010

Status: New Owner: ---- New issue 3285 by gaston.dalloglio: Obsolete ConfigurationOfRFB http://code.google.com/p/pharo/issues/detail?id=3285 Pharo image: Pharo-core Pharo core version: Pharo1.2a I have installed RFBServer following this guide http://book.pharo-project.org/book/TipsAndTricks/RemoteDevelopment/ But when I connect an external VNC client I get a DNU: SmallInteger(Object)>>doesNotUnderstand: #'@-' I've fixed this by simply changing the code "-1@-1" to "-1 @ -1" in the method RFBSesion>>initServer:socket:reverse:, and then the server run fine. But when I look at ConfigurationOfRFB I see this definition is obsolete, this load RFB-lr.31, and the last is RFB-lr.33. In this other book http://book.seaside.st/book/advanced/deployment/maintaining/vnc say that this package is not more soported in Pharo. Its true?

1 2

[Pharo-project] Update for Coral
by Olivier Auverlot Nov. 24, 2010

Nov. 24, 2010

New methods for displaying in a UNIX console : * Console>>displayAttributes: * Console>>eraseScreen * Console>>esc: * Console>>locate: * Console>>plot: * Console>>resetAllAttributes Two examples: * scriptCarpet.cst * scriptHappyFace.cst Best regards Olivier www.auverlot.fr

1 0

Re: [Pharo-project] Waste of CPU Power by polling events?
by StÃ©phane Ducasse Nov. 24, 2010

Nov. 24, 2010

what I can tell you is that Pharo got some work to got forward on event and avoid polling but it was not fully finished. We will continue to work on that in the near future. On Nov 22, 2010, at 10:08 PM, Guido Stepken wrote: > I am just porting squeak/Etoys to Samsung-PAD and i noticed some strange things: > > In Pharo 1.1 network connections seemed to be limited to 4 connections: > > In the listenLoop backlogSize is set to 4. Means - Pharo is limited to max. of four simultaneous TCP Connections? > > But: Some MacIntel VM seem to run Squeak with additional worker thread for event processing. Maybe this limitation may not occur here? > > Carbon ports of Pharo use ioPeekKeystroke, ioGetKeystroke, ioMousePoint, ioGetButtonState instead of > kEventRawKeyModifiersChanged and kEventMouseMoved event > > Found in Pharo so far: > isDraggingEvent > isDropEvent > isEditEvent > isKbdEvent > isMorphicEvent > isNoteEvent > isTempoEvent > isWindowEvent > > > Hmmm ... quite a lot of events being polled: > > Need additional: > > isOnMouseOverEvent > isMouseGestureEvent > isTouchGestureEvent > isNetworkEvent > isUSBEvent > isSerialEvent > isParallelPortEvents > isCtrl-C-Event > ... > > I fear, that this costs a lot of wasted VM Power by polling. UNIX, especially Linux is changing towards a event machine, driven by interrupts. So - Interpreters should also migrated from polling to interrupt driven event-machines. > > I am missing that in Pharo. Pharo still has too much polling code/algorithm running, that slows down Pharo/Squeak/Etoys ... unneccessarily. > > Any ideas appreciated ... > > tnx, regards > > Guido Stepken > >

1 0

Nov. 24, 2010

We should check who uses it and remove it. Ben open a ticket please. BTW there is a pattern Move behavior close to data (and here methods are data so method touching them should be in Bhevaior and subclasses) Stef On Nov 24, 2010, at 8:13 AM, Noury Bouraqadi wrote: > No, it is an ill-named method. The argument is not a selector, but an array. First argument is a class and the second. > > Noury > On 23 nov. 2010, at 12:48, Benjamin wrote: > >> Hello guys, >> >> regarding that comment of SmalltalkImage>>#removeSelector: is >> >> "Safely remove a selector from a class (or metaclass). If the >> class or the method doesn't exist anymore, never mind and >> answer nil. >> This method should be used instead of 'Class removeSelector: >> #method' to omit global class references." >> >> maybe Behavior>>#removeSelector: sould be deprecated ? >> >> >> Ben > >

2 1

Nov. 24, 2010

I see well your problem. We want to have symbol without getting with it the parser and compiler. three questions - can we package isLiteralSymbol: with compiler? - what are the senders? - else do we have an alternate implementation not relying on scanner? Stef > Hello, > > I wonder why the method isLiteralSymbol: is in the Scanner methodDict instead of the Symbol (or maybe String) one ? > > Moreover there is no reference to self or variable in this method ... > > > And due to this method, there is a dependence between Symbol and Scanner (and then the Compiler) > > > > Thank you for answering another one of my noob questions ^^ > > > > Ben >

2 1

Nov. 24, 2010

>> >>> Hello guys, >>> >>> regarding that comment of SmalltalkImage>>#removeSelector: is >>> >>> "Safely remove a selector from a class (or metaclass). If the >>> class or the method doesn't exist anymore, never mind and >>> answer nil. >>> This method should be used instead of 'Class removeSelector: >>> #method' to omit global class references." >>> >>> maybe Behavior>>#removeSelector: sould be deprecated ? >> >> not really >> >> in fact the other one is a hack. I imagine that this is more to make sure you write >> Smalltalk removeSelector: #foo instead of MyClass removeSelector: #foo. >> >> I'm not sure that this is used in fact. >> Stef >> > > Ok, so maybe we should add a comment in Behavior>>#removeSelector: to precise we should now use SmalltalkImage>>#removeSelector: instead ? no we should not use the one of SmalltalkImage. Stef

1 0