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

[Pharo-project] Issue 3323 in pharo: [Kernel Dependencies] Model>>#initialExtent
by pharo＠googlecode.com March 12, 2011

March 12, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo Labels: Difficulty-Easy New issue 3323 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Model>>#initialExtent http://code.google.com/p/pharo/issues/detail?id=3323 Should be extended

1 4

[Pharo-project] Issue 3305 in pharo: [Kernel Dependencies] Integer Extension
by pharo＠googlecode.com March 12, 2011

March 12, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3305 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Integer Extension http://code.google.com/p/pharo/issues/detail?id=3305 Create UIManager extension for: verbosePrimesUpTo:Do:

1 3

[Pharo-project] Issue 3297 in pharo: [Kernel Dependencies] Object>>#notifyWithLabel:
by pharo＠googlecode.com March 12, 2011

March 12, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3297 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Object>>#notifyWithLabel: http://code.google.com/p/pharo/issues/detail?id=3297 Strange dependence to ToolSet

1 4

[Pharo-project] Issue 3299 in pharo: [Kernel Dependencies] Object Extension
by pharo＠googlecode.com March 12, 2011

March 12, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3299 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Object Extension http://code.google.com/p/pharo/issues/detail?id=3299 Create extension to UIManager confirm:Or:Cancel: inform: confirm: primitiveError:

1 4

[Pharo-project] Issue 3298 in pharo: [Kernel Dependencies] Object >> #cannotReturn
by pharo＠googlecode.com March 12, 2011

March 12, 2011

Status: Accepted Owner: Benjamin.VanRyseghem.Pharo New issue 3298 by Benjamin.VanRyseghem.Pharo: [Kernel Dependencies] Object >> #cannotReturn http://code.google.com/p/pharo/issues/detail?id=3298 Strange dependence to ToolSet

1 4

[Pharo-project] serializing a class
by StÃ©phane Ducasse March 7, 2011

March 7, 2011

Hi I would like to do a little experiment. I need to save a class (not the instances) in a binary format and I was wondering if somebody got experience with that. Stef

8 15

[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] Issue 3350 in pharo: Network Tests
by pharo＠googlecode.com Feb. 24, 2011

Feb. 24, 2011

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3350 by stephane.ducasse: Network Tests http://code.google.com/p/pharo/issues/detail?id=3350 Item was changed: ----- Method: Socket>>localAddress (in category 'accessing') ----- localAddress + + self isWaitingForConnection ifFalse: [ + self + waitForConnectionFor: Socket standardTimeout + ifTimedOut: [ ^ByteArray new: 4 ] ]. + ^self primSocketLocalAddress: socketHandle! - self isWaitingForConnection - ifFalse: [[self waitForConnectionFor: Socket standardTimeout] - on: ConnectionTimedOut - do: [:ex | ^ ByteArray new: 4]]. - ^ self primSocketLocalAddress: socketHandle! Item was changed: ----- Method: Socket>>localPort (in category 'accessing') ----- localPort + + self isWaitingForConnection ifFalse: [ + self + waitForConnectionFor: Socket standardTimeout + ifTimedOut: [ ^0] ]. - self isWaitingForConnection - ifFalse: [[self waitForConnectionFor: Socket standardTimeout] - on: ConnectionTimedOut - do: [:ex | ^ 0]]. ^ self primSocketLocalPort: socketHandle! Item was changed: ----- Method: Socket>>waitForAcceptFor: (in category 'waiting') ----- waitForAcceptFor: timeout "Wait and accept an incoming connection. Return nil if it falis" + self waitForConnectionFor: timeout ifTimedOut: [^ nil]. + ^ self isConnected - [self waitForConnectionFor: timeout] on: ConnectionTimedOut do: [:ex | ^nil]. - ^self isConnected ifTrue:[self accept] ! Item was changed: ----- Method: Socket>>waitForConnectionFor:ifTimedOut: (in category 'waiting') ----- waitForConnectionFor: timeout ifTimedOut: timeoutBlock "Wait up until the given deadline for a connection to be established. Return true if it is established by the deadline, false if not." + | startTime msecsDelta msecsEllapsed status | + startTime := Time millisecondClockValue. + msecsDelta := (timeout * 1000) truncated. - | status deadline | - deadline := Socket deadlineSecs: timeout. status := self primSocketConnectionStatus: socketHandle. + [(status = WaitingForConnection) and: [(msecsEllapsed := Time millisecondsSince: startTime) < msecsDelta]] - [(status = WaitingForConnection) and: [Time millisecondClockValue < deadline]] whileTrue: [ + semaphore waitTimeoutMSecs: msecsDelta - msecsEllapsed. - semaphore waitTimeoutMSecs: (deadline - Time millisecondClockValue). status := self primSocketConnectionStatus: socketHandle]. + status = Connected ifFalse: [^timeoutBlock value]. + ^ true! - status = Connected ifFalse: [^timeoutBlock value] - ! Item was changed: ----- Method: Socket>>waitForDataFor:ifClosed:ifTimedOut: (in category 'waiting') ----- waitForDataFor: timeout ifClosed: closedBlock ifTimedOut: timedOutBlock "Wait for the given nr of seconds for data to arrive." + + | startTime msecsDelta | + startTime := Time millisecondClockValue. + msecsDelta := (timeout * 1000) truncated. + [(Time millisecondsSince: startTime) < msecsDelta] whileTrue: [ + (self primSocketReceiveDataAvailable: socketHandle) + ifTrue: [^self]. + self isConnected + ifFalse: [^closedBlock value]. + self readSemaphore waitTimeoutMSecs: + (msecsDelta - (Time millisecondsSince: startTime) max: 0). + ]. - | deadline | - deadline := Socket deadlineSecs: timeout. - - [Time millisecondClockValue < deadline] - whileTrue: [ - (self primSocketReceiveDataAvailable: socketHandle) - ifTrue: [^self]. - self isConnected - ifFalse: [^closedBlock value]. - self readSemaphore waitTimeoutMSecs: (deadline - Time millisecondClockValue)]. - (self primSocketReceiveDataAvailable: socketHandle) ifFalse: [ self isConnected ifTrue: [^timedOutBlock value] + ifFalse: [^closedBlock value]].! - ifFalse: [^closedBlock value]]! Item was changed: ----- Method: Socket>>waitForDisconnectionFor: (in category 'waiting') ----- waitForDisconnectionFor: timeout "Wait for the given nr of seconds for the connection to be broken. Return true if it is broken by the deadline, false if not. The client should know the connection is really going to be closed (e.g., because he has called 'close' to send a close request to the other end) before calling this method." + | startTime msecsDelta status | + startTime := Time millisecondClockValue. + msecsDelta := (timeout * 1000) truncated. - | status deadline | status := self primSocketConnectionStatus: socketHandle. - deadline := Socket deadlineSecs: timeout. [((status == Connected) or: [(status == ThisEndClosed)]) and: + [(Time millisecondsSince: startTime) < msecsDelta]] whileTrue: [ - [Time millisecondClockValue < deadline]] whileTrue: [ self discardReceivedData. + self readSemaphore waitTimeoutMSecs: + (msecsDelta - (Time millisecondsSince: startTime) max: 0). - self readSemaphore waitTimeoutMSecs: (deadline - Time millisecondClockValue). status := self primSocketConnectionStatus: socketHandle]. + ^ status ~= Connected! - - ^ status ~= Connected - ! Item was changed: ----- Method: Socket>>waitForSendDoneFor: (in category 'waiting') ----- waitForSendDoneFor: timeout "Wait up until the given deadline for the current send operation to complete. Return true if it completes by the deadline, false if not." + | startTime msecsDelta msecsEllapsed sendDone | + startTime := Time millisecondClockValue. + msecsDelta := (timeout * 1000) truncated. + [(sendDone := self primSocketSendDone: socketHandle) not and: [ self isConnected - | sendDone deadline | - deadline := Socket deadlineSecs: timeout. - [self isConnected & (sendDone := self primSocketSendDone: socketHandle) not "Connection end and final data can happen fast, so test in this order" + and: [(msecsEllapsed := Time millisecondsSince: startTime) < msecsDelta]]] whileTrue: [ + self writeSemaphore waitTimeoutMSecs: msecsDelta - msecsEllapsed]. - and: [Time millisecondClockValue < deadline]] whileTrue: [ - self writeSemaphore waitTimeoutMSecs: (deadline - Time millisecondClockValue)]. ^ sendDone! Item was changed: ----- Method: SocksSocket>>connectTo:port: (in category 'connection open/close') ----- connectTo: hostAddress port: port self initializeNetwork. self shouldUseSocks ifFalse: [^super connectTo: hostAddress port: port]. super connectTo: socksIP port: socksPort. + self waitForConnectionFor: Socket standardTimeout. - self waitForConnectionUntil: Socket standardDeadline. dstIP := hostAddress. dstPort := port. vers = 4 ifTrue: [self connectSocks4] ifFalse: [self connectSocks5] ! Item was changed: ----- Method: SocksSocket>>connectToHostNamed:port: (in category 'connection open/close') ----- connectToHostNamed: hostName port: port super connectTo: socksIP port: socksPort. + self waitForConnectionFor: Socket standardTimeout. - self waitForConnectionUntil: Socket standardDeadline. dstName := hostName. dstPort := port. vers = 4 ifTrue: [self connectSocks4] ifFalse: [self connectSocks5] !

1 5

[Pharo-project] Introducing smallUML: a little project to help us document :)
by Carla F. Griggio Jan. 30, 2011

Jan. 30, 2011

Hi everyone! Well, here I am announcing the resulting project of my GSoC experience during the [your] summer: smallUML, a project to help us building diagrams and sharing them with any package of code. My mentor was Stephane Ducasse and my co-mentor Geert Claes, so thanks to them for the guidance up to now, and also to Fernando Olivero who helped me a lot (hope to do some coding with you at ESUG! :P). You can gofer it: Gofer it > squeaksource: 'smallUML'; > package: 'ConfigurationOfSmallUML'; > load. > (Smalltalk at: #ConfigurationOfSmallUML) project latestVersion load. > And then open the Diagram Browser of the current little examples evaluating: DiagramDrawingDocumentation openDiagramBrowser . > This is beta and I'm still working on it, my work will continue after GSoC's deadline, so of course your welcome to give some feedback and think about what features would you like it to have and if you're confortable with the current features. It would be really nice if this helped to get all Pharo projects more documented, with visual diagrams that help understanding them at a glance. Talking about that... the current features are: - Open a *Diagram Browser* for an existing Category Diagrams Holder (this is a class ment to hold the created diagrams and there should be one per category, for now; you can browse DiagramDrawingDocumentation to see an example) - *Create and edit diagrams* programatically describing them with "diagram code" (the diagram code it's just a protocol of methods meant to describe diagrams, you can see some diagram code browsing DiagramDrawingDocumentation methods or each Class Box in the Diagram Browser) - Every diagram you build through the Diagram Browser it's saved as "diagram code", so you can *share it as code* that will reproduce your diagram :) That means that diagrams can 'travel' along it's package when you commit your changes with Monticello! And then they can be edited by anybody, they're not just a pretty picture. - You can *export* your diagram as a *PNG* picture or you can export it's "diagram code" as a *workspace*. - Only *Class Diagrams* can be built for now. - Class Boxes of a class diagram can be *dragged* to be easily positioned. Some details that are missing: - It's funny, but I can't center the class boxes title! :P - I tried adding some scrollbars to the "whiteboard" where you can view your diagrams in the Diagram Browser, but if I did that the drag & drop of the class boxes worked funny :( I'll ask about that to you later. On the way: - Tests and documentation, and a screencast showing every feature. - Lots of refactors: as I'm adding more kind of diagrams right now, so I'm doing a lot of refactors to make everything more flexible and improving all the messy code there. - A version of Minimal Connectors for anybody to use if they feel like connecting morphs for another project. - Some usability improvements. - Object diagrams - Sequence diagrams - Your feedback :D So I'd really appreciate if you can give it a try and tell me how you feel about it, I'd like it to be very usable. Cheers! Carla

7 14

[Pharo-project] CommandShell
by laurent laffont Jan. 28, 2011

Jan. 28, 2011

Hi, I'm trying to load CommandShell into Pharo. I have the error: This package depends on the following classes: PluggableTextController PluggableTextView You must resolve these dependencies before you will be able to load these definitions: ShellWindowView ...... Do you know where I can find PluggableTextController and PluggableTextView ? Or maybe we can use other classes to make it compatible with Pharo Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

5 12