- Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by Igor Stasenko

On 14 January 2011 09:32, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > I agree that there should be only one, platform independent look-and-feel. I think the goal of such a theme would be to be slick and fast. > agreed. > Now, regarding the GLMOrangeTheme, the name is a bit confusing because the theme does a bit more than just setting a color. > agreed, usually if you look at other theme(s) for various UI frameworks they having a theme bundled with a number of presets, so the most elements of look and feel are the same, but colors are different. It is like subtheme in theme. That's why its good to support settings, so people could change them and save their own preset. So, users could pick a theme and then second level appears (if theme supports it), where they can pick a preset. > I like the idea of settings, and I will try to make the Glamorous Theme use it. > > Cheers, > Doru > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 14, 2011

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by Tudor Girba

Hi, I agree that there should be only one, platform independent look-and-feel. I think the goal of such a theme would be to be slick and fast. Now, regarding the GLMOrangeTheme, the name is a bit confusing because the theme does a bit more than just setting a color. I like the idea of settings, and I will try to make the Glamorous Theme use it. Cheers, Doru On 14 Jan 2011, at 00:58, Igor Stasenko wrote: > On 13 January 2011 21:57, Alain Plantec <alain.plantec(a)free.fr> wrote: >> Hi all, >> yes, I agree >> >> list selection and selection colors (and some others) can be changed from >> the setting browser. >> I think that in the core only the default theme should be present. >> The others should be packaged separately and loadable on-demand or >> when a package is loaded as it is for moose/glamour. > > +1 > i think we should get rid of all themes and leave only single default one. > > Actually today i was attempting to make sure that orange could be turned into > any other color of choice by picking a different color in settings. > Unfortunately its not so easy, because some widget do not honor / > using theme settings correctly. > > And theme by itself not always honors the settings. > > As a wish for future, i think we should fold all UI settings under a > per-theme settings, > so when user selects a concrete UI theme, then theme could control, > which UI Settings > it makes public and this allows to be modified, and which are not, and > should always use built-in (like window color or icons). > > Then theme could control whether it supports changing particular setting or not. > For instance i could use single color (orange) to define colors for > multiple things: > - Menu selection color > - Find replace selection color > ... others > > and to user show only 'Selection color' > > > >> Cheers >> Alain >> > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "Beauty is where we see it."

Jan. 14, 2011

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

by Tudor Girba

Done. Doru On 14 Jan 2011, at 09:06, StÃ©phane Ducasse wrote: > doru > could push a new version in the inbox? > > Stef > > On Jan 13, 2011, at 11:09 PM, Tudor Girba wrote: > >> I like the simple border around the windows. I adopted it in the Glamorous Theme :) >> >> Cheers, >> Doru >> >> >> On 13 Jan 2011, at 19:36, Igor Stasenko wrote: >> >>> here is updated version of it. >>> more consistent colors >>> (note the ">" button now not highlighted by default, >>> also added thin border for lists >>> and thin border for system windows, >>> and removed 1pixel-wide shadow for system window. >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> <GLMOrangeUITheme.st><GLMOrangeUITheme.png> >> >> -- >> www.tudorgirba.com >> >> "Relationships are of two kinds: those we choose and those that happen. They both matter." >> >> >> >> >> >> > > -- www.tudorgirba.com "Value is always contextual."

Jan. 14, 2011

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Comment #9 on issue 3522 by aplan...(a)gmail.com: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 SLICE-Issue-3522-wiki-like-help-contents in InBox Thanks a lot Torsten, I let you test it and tag this issue as fixed if its ok.

Jan. 14, 2011

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

by StÃ©phane Ducasse

doru could push a new version in the inbox? Stef On Jan 13, 2011, at 11:09 PM, Tudor Girba wrote: > I like the simple border around the windows. I adopted it in the Glamorous Theme :) > > Cheers, > Doru > > > On 13 Jan 2011, at 19:36, Igor Stasenko wrote: > >> here is updated version of it. >> more consistent colors >> (note the ">" button now not highlighted by default, >> also added thin border for lists >> and thin border for system windows, >> and removed 1pixel-wide shadow for system window. >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> <GLMOrangeUITheme.st><GLMOrangeUITheme.png> > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that happen. They both matter." > > > > > >

Jan. 14, 2011