- Pharo-dev - lists.pharo.org

[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

Re: [Pharo-project] removeSelector:
by StÃ©phane Ducasse Nov. 24, 2010

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

Re: [Pharo-project] Symbol and Scanner
by StÃ©phane Ducasse Nov. 24, 2010

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

Re: [Pharo-project] removeSelector:
by StÃ©phane Ducasse Nov. 24, 2010

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

[Pharo-project] rename a method programatically
by Cyrille Delaunay Nov. 24, 2010

Nov. 24, 2010

Hello, I would like to know how I can rename a method programatically and safelly (without missing to raise any event that has to be raised)

5 13

[Pharo-project] removeSelector:
by Benjamin Nov. 24, 2010

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 ? Ben

2 1

[Pharo-project] Much better issues feed from Google
by Stephan Eggermont Nov. 23, 2010

Nov. 23, 2010

Would be to have it in a browser in the image. An early experiment with the current Moose daily build shows it can be done: http://www.squeaksource.com/GoogleIssuesFeed Stephan

2 1