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

Re: [Pharo-project] about DateAndTime =

by Henrik Johansen

On Apr 23, 2010, at 9:26 31PM, Brent Pinkney wrote: > On Friday 23 April 2010 21:12:03 StÃ©phane Ducasse wrote: >> Hi all >> >> I'm trying to fix some tests and I do not like the behavior of DateAndTime >> = Comparing aDateAndTime and a something tries to convert the something in >> a dateAndTime automagically. I find that not really good because it hides >> potential problem: manipulating string instead of objects. >> >> So I would like to have >> (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00' -> >> false (aDateAndTime offset: '0:12:00:00') asString = >> '1901-01-01T00:00:00+12:00' -> true. >> >> What do you think. > > Hi, > > I wrote that code, and it is needed to compare DateAndTimes with Timespans - eg Month, Year, Date... > Please tread carefully - lots of production code relies on that. > > Already my (DateAndTime now != DateAndTime now) have been removed :( > > Thanks > > Brent Because even if the resolution of a DateAndTime is nanoseconds, the clock available to derive now from has a resolution of milliseconds (microseconds using an updated VM on some platforms). (Not to mention the now method actually uses a second resolution...) Thus a test which states that asking for now two times in a row should always result in different DateAndTime values does not make sense. Cheers, Henry

April 23, 2010

Re: [Pharo-project] about DateAndTime =

by StÃ©phane Ducasse

On Apr 23, 2010, at 9:26 PM, Brent Pinkney wrote: > On Friday 23 April 2010 21:12:03 StÃ©phane Ducasse wrote: >> Hi all >> >> I'm trying to fix some tests and I do not like the behavior of DateAndTime >> = Comparing aDateAndTime and a something tries to convert the something in >> a dateAndTime automagically. I find that not really good because it hides >> potential problem: manipulating string instead of objects. >> >> So I would like to have >> (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00' -> >> false (aDateAndTime offset: '0:12:00:00') asString = >> '1901-01-01T00:00:00+12:00' -> true. >> >> What do you think. > > Hi, > > I wrote that code, and it is needed to compare DateAndTimes with Timespans - eg Month, Year, Date... > Please tread carefully - lots of production code relies on that. Thanks for the info. Now I think that strings are dead objects and we should not use them in place of real ones. > Already my (DateAndTime now != DateAndTime now) have been removed :( was it in 3.9? Stef > > Thanks > > Brent > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 23, 2010

Re: [Pharo-project] Serialization of font object

by StÃ©phane Ducasse

I was thinking more as a simple mechanism to serialize the info you gave than to serialize the objects since after you may not have the fonts in your system but should guess a substitution. Stef On Apr 23, 2010, at 9:22 PM, Henrik Johansen wrote: > > On Apr 23, 2010, at 7:37 33PM, StÃ©phane Ducasse wrote: > >> may be using the storeOn: aStream and readFrom: mechanism? >> > I doubt it would work for FreeType fonts, which hold external handles. > For StrikeFonts, it may, but even if it did, you'd probably end up importing a new Font instance (complete with an XX KB bitmap), for each Morph... > > Cheers, > Henry > >> >> On Apr 23, 2010, at 4:28 PM, Henrik Johansen wrote: >> >>> On Apr 23, 2010, at 4:01 48PM, nullPointer wrote: >>> >>>> >>>> >>>> Regards >>>> >>>> I see in Pharo a few ways for create a font, StrikeFont, LogicalFont... I >>>> need generate dinamically code in Smalltalk for build UIs, and my problem >>>> now is when I have serialize the font of a widget. Which could be the best >>>> way for do that? In other objects like arrays, points, associations is >>>> possible get that calling #printString method. Exists some equivalence for >>>> that in fonts, or is needed implement that mechanism of zero? >>>> >>>> Thanks for answers >>> >>> I would store the the name/boldness/size etc., then use (LogicalFont familyName: pointSize: stretchValue:weightValue: slantValue: ) realFont >>> to discover the closest font available when loading the morph into an image again. >>> >>> Cheers, >>> Henry >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 23, 2010

Re: [Pharo-project] about DateAndTime =

by Brent Pinkney

On Friday 23 April 2010 21:12:03 StÃ©phane Ducasse wrote: > Hi all > > I'm trying to fix some tests and I do not like the behavior of DateAndTime > = Comparing aDateAndTime and a something tries to convert the something in > a dateAndTime automagically. I find that not really good because it hides > potential problem: manipulating string instead of objects. > > So I would like to have > (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00' -> > false (aDateAndTime offset: '0:12:00:00') asString = > '1901-01-01T00:00:00+12:00' -> true. > > What do you think. Hi, I wrote that code, and it is needed to compare DateAndTimes with Timespans - eg Month, Year, Date... Please tread carefully - lots of production code relies on that. Already my (DateAndTime now != DateAndTime now) have been removed :( Thanks Brent

April 23, 2010

Re: [Pharo-project] Serialization of font object

by Henrik Johansen

On Apr 23, 2010, at 7:37 33PM, StÃ©phane Ducasse wrote: > may be using the storeOn: aStream and readFrom: mechanism? > I doubt it would work for FreeType fonts, which hold external handles. For StrikeFonts, it may, but even if it did, you'd probably end up importing a new Font instance (complete with an XX KB bitmap), for each Morph... Cheers, Henry > > On Apr 23, 2010, at 4:28 PM, Henrik Johansen wrote: > >> On Apr 23, 2010, at 4:01 48PM, nullPointer wrote: >> >>> >>> >>> Regards >>> >>> I see in Pharo a few ways for create a font, StrikeFont, LogicalFont... I >>> need generate dinamically code in Smalltalk for build UIs, and my problem >>> now is when I have serialize the font of a widget. Which could be the best >>> way for do that? In other objects like arrays, points, associations is >>> possible get that calling #printString method. Exists some equivalence for >>> that in fonts, or is needed implement that mechanism of zero? >>> >>> Thanks for answers >> >> I would store the the name/boldness/size etc., then use (LogicalFont familyName: pointSize: stretchValue:weightValue: slantValue: ) realFont >> to discover the closest font available when loading the morph into an image again. >> >> Cheers, >> Henry >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 23, 2010

[Pharo-project] about DateAndTime =

by StÃ©phane Ducasse

Hi all I'm trying to fix some tests and I do not like the behavior of DateAndTime = Comparing aDateAndTime and a something tries to convert the something in a dateAndTime automagically. I find that not really good because it hides potential problem: manipulating string instead of objects. So I would like to have (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00' -> false (aDateAndTime offset: '0:12:00:00') asString = '1901-01-01T00:00:00+12:00' -> true. What do you think. Stef

April 23, 2010

Re: [Pharo-project] starting to think about 1.1 freeze

by StÃ©phane Ducasse

Yes alien should be on the list. Thanks for the reminder. On Apr 23, 2010, at 8:30 PM, Schwab,Wilhelm K wrote: > Stef, > > I will soon reach a point of missing a way to do callbacks. Alien/FFI is listed among the goals, and I would very much like to see that happen, especially if callbacks are well supported as a result. > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: Friday, April 23, 2010 12:50 PM > To: Pharo Development > Subject: [Pharo-project] starting to think about 1.1 freeze > > Hi > > we started with the guys here to look at the tests that fail in 1.1. > We started to fix some of them. Now I would like to have a roadmap for freezing 1.1 > > - Green tests. > - No Preferences. > - What are the key other things that we want to get done in 1.1? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 23, 2010

Re: [Pharo-project] starting to think about 1.1 freeze

by Schwab,Wilhelm K

Stef, I will soon reach a point of missing a way to do callbacks. Alien/FFI is listed among the goals, and I would very much like to see that happen, especially if callbacks are well supported as a result. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Friday, April 23, 2010 12:50 PM To: Pharo Development Subject: [Pharo-project] starting to think about 1.1 freeze Hi we started with the guys here to look at the tests that fail in 1.1. We started to fix some of them. Now I would like to have a roadmap for freezing 1.1 - Green tests. - No Preferences. - What are the key other things that we want to get done in 1.1? Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 23, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Fix to OCompletion for Pharo 1.1

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > Pay attention FillInTheBlank does not exist anymore in 1.1 > Ha ha, yes that was kind of the point of the fix ;-) FillInTheBlankMorph works in 1.1-11317. Or, maybe you meant the comment '(The former has no request: initialAnswer:).' - since FillInTheBlank returns an UndefinedObject, then it does indeed not have that method, lol. Sean -- View this message in context: http://forum.world.st/Fwd-squeak-dev-Fix-to-OCompletion-for-Pharo-1-1-tp205… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 23, 2010

[Pharo-project] anyone interested for Pharo on this device?

by Hilaire Fernandes

I saw this cool tablette device when browsing the ARM Ltd web site. http://www.alwaysinnovating.com/touchbook/ Even PharoNOS will be cool Hilaire

April 23, 2010