January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.2] #12297

by Igor Stasenko

On 14 January 2011 12:33, Douglas Brebner <squeaklists(a)fang.demon.co.uk> wrote: > On 13/01/2011 22:04, Tudor Girba wrote: >> >> That is a good point. I actually used the Sim Daltonism application (for >> Mac) to check the color blindness issues, but it looks like I overlooked >> Monochromacy (however, this is pretty rare). I will try to look into that. >> >> Cheers, >> Doru > > It's not just the colour blind that are affected (though they have it > worst). Even people with perfect vision can find it difficult to distinguish > adjacent areas of similar contrast. > > e.g. If you look at the save changes window that appears when quitting an > image you'll notice the buttons almost disappear into the background. > > Still, it's good that someone is working on this :) > yeah.. if you not cleaning your house, do not expect guests to come :) > -- Best regards, Igor Stasenko AKA sig.

Jan. 14, 2011

Re: [Pharo-project] Socket question (Was Re: Xtreams up to date)

by Schwab,Wilhelm K

I am really bothered by the timeout on the accept, so much so that I think it has no place in the tests. Of course, one needs a way to clean up after a failure, but that should be done by another thread that waits for a "long" time and then cleans up anything that is left behind after the failure. Servers should be started and stopped and in between, they should wait for and accept connections. Clients should try to connect until told otherwise; timeouts can be reasonable options there, but should not be forced by the sockets system. Only the calling threads should be blocked, of course. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of mkobetic(a)gmail.com [mkobetic(a)gmail.com] Sent: Friday, January 14, 2011 1:12 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Socket question (Was Re: Xtreams up to date) BTW, would this snippet be useful as a basic Socket smoke test ? Or is that already covered somewhere ? | input output listener process sync | sync := Semaphore new. listener := Socket newTCP. listener listenOn: 9999 backlogSize: 10. process := [ [ input := listener waitForAcceptFor: 10. sync signal ] ensure: [ listener close ] ] fork. output := Socket newTCP. output connectTo: #[127 0 0 1] port: 9999. sync wait. [ #( 64 1024 2048 4096 8192 ) do: [:dataSize || data | data := ByteArray new: dataSize. 1 to: data size do: [:i | data at: i put: (i - 1) \\ 256]. 1 to: 10 do: [:each | output sendData: data]. 1 to: 10 do: [ :each || result index | index := 1. result := ByteArray new: dataSize. [ index := index + (input receiveDataInto: result startingAt: index). index > dataSize ] whileFalse. result = data ifFalse: [ result halt]]] ] ensure: [ output close. input close ]

Jan. 14, 2011

[Pharo-project] Some browser UI refining

by Igor Stasenko

get rid of annoying 1-pixel height while line between buttons bar and text field. added padding at bottom of button bar, so it looks symmetric -- Best regards, Igor Stasenko AKA sig.

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by Douglas Brebner

On 13/01/2011 22:04, Tudor Girba wrote: > That is a good point. I actually used the Sim Daltonism application (for Mac) to check the color blindness issues, but it looks like I overlooked Monochromacy (however, this is pretty rare). I will try to look into that. > > Cheers, > Doru It's not just the colour blind that are affected (though they have it worst). Even people with perfect vision can find it difficult to distinguish adjacent areas of similar contrast. e.g. If you look at the save changes window that appears when quitting an image you'll notice the buttons almost disappear into the background. Still, it's good that someone is working on this :)

Jan. 14, 2011

[Pharo-project] ScrollBar needs a cleanup

by Igor Stasenko

Class vars: UpArrow UpArrow8Bit UpArrow used in: initialize "ScrollBar initialize" UpArrow := Form extent: 6 @ 3 fromArray: #(805306368 2013265920 4227858432 ) offset: 0 @ 0. "" self initializeImagesCache upArrow8Bit "convert to 8-bit and convert white to transparent to avoid gratuitous conversion every time we put one in an ImageMorph" ^UpArrow8Bit ifNil: [ UpArrow8Bit := (ColorForm mappingWhiteToTransparentFrom: UpArrow) asFormOfDepth: 8 ] and UpArrow8Bit used just here: upArrow8Bit "convert to 8-bit and convert white to transparent to avoid gratuitous conversion every time we put one in an ImageMorph" ^UpArrow8Bit ifNil: [ UpArrow8Bit := (ColorForm mappingWhiteToTransparentFrom: UpArrow) asFormOfDepth: 8 ] and guess what? upArrow8Bit not used anywhere (there is no senders of it). That is really weird piece of code.. If there is an up arrow, then i expect to see down arrow, left and right as well.. but only up one... The cleanup in cs -- Best regards, Igor Stasenko AKA sig.

Jan. 14, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by Denis Kudriashov

Sorry, I meen DateAndTime now millisecond and DateAndTime now nanoSecond. As I write in last mail. I found cuis fix of this in Pharo issues 2011/1/14 Adrian Lienhard <adi(a)netstyle.ch> > Hi Denis, > > There's no method milliseconds (at least in my Pharo 1.1.1 image). Can you > be more specific? > > I assume you want to get the milli seconds of a timestamp, rather than the > millisecond clock (DateAndTime millisecondClockValue). > > When you create a new timestamp (TimeStamp now) the milli/nano seconds are > indeed 0. The reason is that the timestamp is initialized from "Time > totalSeconds". > > So I consider this not as a bug but something that could be improved. > > Cheers, > Adrian > > BTW, I remember having seen a fix on Mantis (= Squeak bug tracker) which > asserts that TimeStamp now < TimeStamp now. > > > On Jan 14, 2011, at 10:20 , Denis Kudriashov wrote: > > > Hello. > > > > How I can get current time milliseconds parameter? > > > > I try DateAndTime millisecond. But it always zero. > > And DateAndTime nanoSecond is always zero too. > > > > Is it bug? > > > > I use Pharo1.1 > > >

Jan. 14, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by Adrian Lienhard

Hi Denis, There's no method milliseconds (at least in my Pharo 1.1.1 image). Can you be more specific? I assume you want to get the milli seconds of a timestamp, rather than the millisecond clock (DateAndTime millisecondClockValue). When you create a new timestamp (TimeStamp now) the milli/nano seconds are indeed 0. The reason is that the timestamp is initialized from "Time totalSeconds". So I consider this not as a bug but something that could be improved. Cheers, Adrian BTW, I remember having seen a fix on Mantis (= Squeak bug tracker) which asserts that TimeStamp now < TimeStamp now. On Jan 14, 2011, at 10:20 , Denis Kudriashov wrote: > Hello. > > How I can get current time milliseconds parameter? > > I try DateAndTime millisecond. But it always zero. > And DateAndTime nanoSecond is always zero too. > > Is it bug? > > I use Pharo1.1

Jan. 14, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by Denis Kudriashov

I think it's solved by Issue 3236<http://code.google.com/p/pharo/issues/detail?id=3236>: Cuis DateAndTime Enhancement 2011/1/14 Denis Kudriashov <dionisiydk(a)gmail.com> > I investigate squeak code. Its all work right with milli/nano seconds. > And implementation of DateAndTime very different. It has class variables > LastTicks and more. And #now method use it. > > Is it new implementation that should be integrated to pharo? > Or pharo drop this implementation? Why? > > 2011/1/14 Denis Kudriashov <dionisiydk(a)gmail.com> > > Hello. >> >> How I can get current time milliseconds parameter? >> >> I try DateAndTime millisecond. But it always zero. >> And DateAndTime nanoSecond is always zero too. >> >> Is it bug? >> >> I use Pharo1.1 >> > >

Jan. 14, 2011

Re: [Pharo-project] DateAndTime millisecond is always 0

by Denis Kudriashov

I investigate squeak code. Its all work right with milli/nano seconds. And implementation of DateAndTime very different. It has class variables LastTicks and more. And #now method use it. Is it new implementation that should be integrated to pharo? Or pharo drop this implementation? Why? 2011/1/14 Denis Kudriashov <dionisiydk(a)gmail.com> > Hello. > > How I can get current time milliseconds parameter? > > I try DateAndTime millisecond. But it always zero. > And DateAndTime nanoSecond is always zero too. > > Is it bug? > > I use Pharo1.1 >

Jan. 14, 2011

[Pharo-project] DateAndTime millisecond is always 0

by Denis Kudriashov

Hello. How I can get current time milliseconds parameter? I try DateAndTime millisecond. But it always zero. And DateAndTime nanoSecond is always zero too. Is it bug? I use Pharo1.1

Jan. 14, 2011