December 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] Using pharo-project@LISTS...
by StÃ©phane Ducasse Dec. 10, 2008

Dec. 10, 2008

Hi guys the guys maintaining the server changed the mailing-list names without telling us :( So you should not use pharo-rpoejct@gforge but Pharo-project(a)lists.gforge.inria.fr with the LISTS Sorry for their mess! Stef

2 1

Re: [Pharo-project] ODBC bugs
by Bill Schwab Dec. 10, 2008

Dec. 10, 2008

This sounds familiar on a couple of levels. In short, the ODBC package should probably define #printSqlOn: and/or #sqlString rather than altering the way everything else prints a time stamp. It even gets worse, because the DBMS sometimes affects what has to be written. Thanks for complaining and fixing! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 12/10/08 3:39 PM >>> On Dec 10, 2008, at 9:31 PM, Benoit St-Jean wrote: > Yes they were all green before loading the ODBC for Squeak package. > I have also verified with previous versions of Squeak (3.7 up to > 3.10) and they were also green for all Squeak versions BEFORE > loading the ODBC for "Squeak package". In other words, it's not a > Pharo related bug, it affects all versions of Squeak and it's caused > by the ODBC package... > > A very quick look at it shows that the ODBC package has changed the > way we print TimeStamp (an extra comma to separate the date from the > time) and that the #date method in class Time returns the receiver > #asDate, not the "plain" instance variable. Not rocket science to > fix but I wonder if it won't break everything on the ODBC side. > Besides, one might ask if it makes sense to convert a <Time> into a > TimeStamp (as I used to say to Smalltalk newcomers, "yes you can use > a chair as a table and vice-versa but does it really make > sense" ?). Well, that's what this method is trying to do. I would > have to take a closer look at the actual implication and effects of > possible fixes for this method and/or odbc-related methods. > > I will enter 3 bugs into the tracker, ODBC tests failing, the find > string tool and the email bug report in the debugger. > > I know, I complain all the time! ;) I do not feel it like that. And if you add and provide info and fixes this is even better :) > > > I should have been a QA tester!!! lol > > > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > Blog: lamneth.wordpress.com > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > > > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, December 10, 2008 3:01:23 PM > Subject: Re: [Pharo-project] ODBC package bugs > > Hi benoit > > > On Dec 10, 2008, at 8:53 PM, Benoit St-Jean wrote: > > > Hello everyone, > > > > Since I am not familiar with the Pharo process for reporting/fixing > > bugs, here's a quick email to let you know what I have found by > > loading (in order) FFI, ODBC and ODBCEnh packages from SqueakMap > > FYI : > > > > Loading the "ODBC for Squeak" package from SqueakMap into Pharo > > breaks 8 unit tests (4 failures, 4 errors), namely: > > Were these tests green before loading ODBC? > Then do you think that this is because ODBC extend/change TimeStamp? > > > 1) TimeStampTest>>#testPrint > > 2) TimeStampTest>>#testPrinting > > 3) TimeStampTest>>#testStoreOn > > 4) TimeTest>>#testTimeStamp > > 5) DateAndTimeLeapTest>>#testAsTimeStamp > > 6) TimeStampTest>>#testInstanceCreation > > 7) TimeStampTest>>#testReadFromA1 > > 8) TimespanTest>>#testAsTimeStamp > > > Thanks can you enter a bug entry on the bug tracker. > > > On a different topic, doing a string search in the code (menu item > > "method source with it") creates a walkback because : > > > > AbstractObjectsAsMethod(Object)>>doesNotUnderstand: > #getSourceFor:in: > > > > Also, I have noticed that if I want to mail a bug report from the > > debugger, the address the email would be sent to is squeak-dev(a)lists.squeakfoundation.org > > instead of a "Pharo" one. > > > > Hope this helps. > > Sure it does > > > > > > Thank you. > > > > ----------------- > > Benoit St-Jean > > Yahoo! Messenger: bstjean > > Blog: lamneth.wordpress.com > > A standpoint is an intellectual horizon of radius zero. > > (Albert Einstein) > > > > > > _______________________________________________ > > 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] ODBC bugs
by Benoit St-Jean Dec. 10, 2008

Dec. 10, 2008

Yes they were all green before loading the ODBC for Squeak package. I have also verified with previous versions of Squeak (3.7 up to 3.10) and they were also green for all Squeak versions BEFORE loading the ODBC for "Squeak package". In other words, it's not a Pharo related bug, it affects all versions of Squeak and it's caused by the ODBC package... A very quick look at it shows that the ODBC package has changed the way we print TimeStamp (an extra comma to separate the date from the time) and that the #date method in class Time returns the receiver #asDate, not the "plain" instance variable. Not rocket science to fix but I wonder if it won't break everything on the ODBC side. Besides, one might ask if it makes sense to convert a <Time> into a TimeStamp (as I used to say to Smalltalk newcomers, "yes you can use a chair as a table and vice-versa but does it really make sense" ?). Well, that's what this method is trying to do. I would have to take a closer look at the actual implication and effects of possible fixes for this method and/or odbc-related methods. I will enter 3 bugs into the tracker, ODBC tests failing, the find string tool and the email bug report in the debugger. I know, I complain all the time! ;) I should have been a QA tester!!! lol ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, December 10, 2008 3:01:23 PM Subject: Re: [Pharo-project] ODBC package bugs Hi benoit On Dec 10, 2008, at 8:53 PM, Benoit St-Jean wrote: > Hello everyone, > > Since I am not familiar with the Pharo process for reporting/fixing > bugs, here's a quick email to let you know what I have found by > loading (in order) FFI, ODBC and ODBCEnh packages from SqueakMap > FYI : > > Loading the "ODBC for Squeak" package from SqueakMap into Pharo > breaks 8 unit tests (4 failures, 4 errors), namely: Were these tests green before loading ODBC? Then do you think that this is because ODBC extend/change TimeStamp? > 1) TimeStampTest>>#testPrint > 2) TimeStampTest>>#testPrinting > 3) TimeStampTest>>#testStoreOn > 4) TimeTest>>#testTimeStamp > 5) DateAndTimeLeapTest>>#testAsTimeStamp > 6) TimeStampTest>>#testInstanceCreation > 7) TimeStampTest>>#testReadFromA1 > 8) TimespanTest>>#testAsTimeStamp > Thanks can you enter a bug entry on the bug tracker. > On a different topic, doing a string search in the code (menu item > "method source with it") creates a walkback because : > > AbstractObjectsAsMethod(Object)>>doesNotUnderstand: #getSourceFor:in: > > Also, I have noticed that if I want to mail a bug report from the > debugger, the address the email would be sent to is squeak-dev(a)lists.squeakfoundation.org > instead of a "Pharo" one. > > Hope this helps. Sure it does > > > Thank you. > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > Blog: lamneth.wordpress.com > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > > > _______________________________________________ > 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

2 1

[Pharo-project] IRC Channel
by Benoit St-Jean Dec. 10, 2008

Dec. 10, 2008

Hello again, I couldn't find the info on Google but is there a #pharo channel on IRC and if so, on what server? Thank you! ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

3 2

[Pharo-project] Reporting bugs
by Benoit St-Jean Dec. 10, 2008

Dec. 10, 2008

Where do I report Pharo bugs ? a) the Pharo tracker (http://gforge.inria.fr/tracker/?atid=4819&group_id=1299&func=browse) b) http://bugs.squeak.org ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

2 1

[Pharo-project] SmallFaces and Phantasia
by HernÃ¡n Morales Durand Dec. 10, 2008

Dec. 10, 2008

Hello list, Just to say now SmallFaces and Phantasia should load fine in the Pharo image. Cheers. HernÃ¡n PD: http://www.squeaksource.com/SmallFaces.html <http://www.squeaksource.com/Phantasia.html> http://www.squeaksource.com/Phantasia.html

1 0

[Pharo-project] ODBC package bugs
by Benoit St-Jean Dec. 10, 2008

Dec. 10, 2008

Hello everyone, Since I am not familiar with the Pharo process for reporting/fixing bugs, here's a quick email to let you know what I have found by loading (in order) FFI, ODBC and ODBCEnh packages from SqueakMap FYI : Loading the "ODBC for Squeak" package from SqueakMap into Pharo breaks 8 unit tests (4 failures, 4 errors), namely: 1) TimeStampTest>>#testPrintOn 2) TimeStampTest>>#testPrinting 3) TimeStampTest>>#testStoreOn 4) TimeTest>>#testTimeStamp 5) DateAndTimeLeapTest>>#testAsTimeStamp 6) TimeStampTest>>#testInstanceCreation 7) TimeStampTest>>#testReadFromA1 8) TimespanTest>>#testAsTimeStamp On a different topic, doing a string search in the code (menu item "method source with it") creates a walkback because : AbstractObjectsAsMethod(Object)>>doesNotUnderstand: #getSourceFor:in: Also, I have noticed that if I want to mail a bug report from the debugger, the address the email would be sent to is squeak-dev(a)lists.squeakfoundation.org instead of a "Pharo" one. Hope this helps. Thank you. ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

2 1

Dec. 10, 2008

Begin forwarded message: > From: "Gary Chambers" <gary(a)pinesoft.co.uk> > Date: December 10, 2008 5:53:07 PM CEST > To: Stephane Ducasse <stephane.ducasse(a)inria.fr> > Subject: RE: Issue 384: copy and paste does not work in MC diff view > > Polymorph-Widgets.gvc.23 (on SqueakSource) has the copy capability for > disabled TextEditorMorph (and subclasses). I've added a note to the > tracker. > > Regards, Gary. > >> -----Original Message----- >> From: Stephane Ducasse [mailto:stephane.ducasse@inria.fr] >> Sent: 10 December 2008 4:29 PM >> To: Gary Chambers >> Subject: Re: Issue 384: copy and paste does not work in MC diff view >> >> >> >> On Dec 10, 2008, at 5:22 PM, Gary Chambers wrote: >> >>> Managed it (copy from disabled TextEditorMorph) though reminded me >>> why I >>> hate Paragraph/TextMorphForEditView etc. so much. Really, really >>> horrible... >>> Given that MVC is gone in Pharo the whole thing could do with being >>> reworked >>> into less spaghetti. >> >> Excellent! >> Yes the goal of the first fat removal is to enable agility >> >> Stef >> >>> >>> >>> Reagrds, Gary. >>> >>>> -----Original Message----- >>>> From: Stephane Ducasse [mailto:stephane.ducasse@inria.fr] >>>> Sent: 10 December 2008 1:34 PM >>>> To: Gary Chambers >>>> Subject: Re: Issue 384: copy and paste does not work in MC diff >>>> view >>>> >>>> >>>> I understand I do not think we want paste but just copy >>>> >>>> Stef >>>> >>>> On Dec 10, 2008, at 2:26 PM, Gary Chambers wrote: >>>> >>>>> As indicated in the last email with attached email, MC does not >>>>> currently >>>>> support modification of changes/conflicts hence the text editors >>>>> are >>>>> disabled. I can see a case for "copy" but not paste. Unfortunately >>>>> keyboard >>>>> handling in Paragraph is somewhat convoluted, hence disablement >>>>> effectively >>>>> ignoring keyboard input totally. I guess I could separately >>>>> handle a >>>>> copy >>>>> opertation when disabled... >>>>> >>>>> Like I said though, I eventually envisage a third text pane >>>>> showing >>>>> the >>>>> composited method after taking the choices with the arrows with >>>>> the >>>>> ability >>>>> to manually modify before commiting, somehow! >>>>> >>>>> Regards, Gary >>>>> >>>>>> -----Original Message----- >>>>>> From: Stephane Ducasse [mailto:stephane.ducasse@inria.fr] >>>>>> Sent: 10 December 2008 1:05 PM >>>>>> To: Gary Chambers >>>>>> Subject: Issue 384: copy and paste does not work in MC diff view >>>>>> >>>>>> >>>>>> http://code.google.com/p/pharo/issues/detail?id=384&colspec=ID >>>>>> %20T >>>>>> ype%20Status%20Summary&start=100 >>>>>> >>>>> >>>>> >>>>> >>>>> Consider your responsibility to the environment - think before you >>>>> print! >>>>> >>>>> >>>> ****************************************************************** >>>> >> ************************************************************************ >>>>> This email is from Pinesoft Limited. Its contents are confidential >>>>> to the intended recipient(s) at the email address(es) to which it >>>>> has been addressed. It may not be disclosed to or used by anyone >>>>> other than the addressee(s), nor may it be copied in anyway. If >>>>> received in error, please contact the sender, then delete it from >>>>> your system. Although this email and attachments are believed to >>>>> be >>>>> free of virus, or any other defect which might affect any computer >>>>> or IT system into which they are received and opened, it is the >>>>> responsibility of the recipient to ensure that they are virus free >>>>> and no responsibility is accepted by Pinesoft for any loss or >>>>> damage >>>>> arising in any way from receipt or use thereof. >>>>> >>>> ****************************************************************** >>>> >> ************************************************************************* >>>>> >>>>> >>>>> Pinesoft Limited are registered in England, Registered number: >>>>> 2914825. Registered office: 266-268 High Street, Waltham Cross, >>>>> Herts, EN8 7EA >>>>> >>>> >>>> >>> >> >> >

1 0

Dec. 10, 2008

Begin forwarded message: > From: "Gary Chambers" <gary(a)pinesoft.co.uk> > Date: December 10, 2008 5:53:07 PM CEST > To: Stephane Ducasse <stephane.ducasse(a)inria.fr> > Subject: RE: Issue 384: copy and paste does not work in MC diff view > > Polymorph-Widgets.gvc.23 (on SqueakSource) has the copy capability for > disabled TextEditorMorph (and subclasses). I've added a note to the > tracker. > > Regards, Gary. > >> -----Original Message----- >> From: Stephane Ducasse [mailto:stephane.ducasse@inria.fr] >> Sent: 10 December 2008 4:29 PM >> To: Gary Chambers >> Subject: Re: Issue 384: copy and paste does not work in MC diff view >> >> >> >> On Dec 10, 2008, at 5:22 PM, Gary Chambers wrote: >> >>> Managed it (copy from disabled TextEditorMorph) though reminded me >>> why I >>> hate Paragraph/TextMorphForEditView etc. so much. Really, really >>> horrible... >>> Given that MVC is gone in Pharo the whole thing could do with being >>> reworked >>> into less spaghetti. >> >> Excellent! >> Yes the goal of the first fat removal is to enable agility >> >> Stef >> >>> >>> >>> Reagrds, Gary. >>> >>>> -----Original Message----- >>>> From: Stephane Ducasse [mailto:stephane.ducasse@inria.fr] >>>> Sent: 10 December 2008 1:34 PM >>>> To: Gary Chambers >>>> Subject: Re: Issue 384: copy and paste does not work in MC diff >>>> view >>>> >>>> >>>> I understand I do not think we want paste but just copy >>>> >>>> Stef >>>> >>>> On Dec 10, 2008, at 2:26 PM, Gary Chambers wrote: >>>> >>>>> As indicated in the last email with attached email, MC does not >>>>> currently >>>>> support modification of changes/conflicts hence the text editors >>>>> are >>>>> disabled. I can see a case for "copy" but not paste. Unfortunately >>>>> keyboard >>>>> handling in Paragraph is somewhat convoluted, hence disablement >>>>> effectively >>>>> ignoring keyboard input totally. I guess I could separately >>>>> handle a >>>>> copy >>>>> opertation when disabled... >>>>> >>>>> Like I said though, I eventually envisage a third text pane >>>>> showing >>>>> the >>>>> composited method after taking the choices with the arrows with >>>>> the >>>>> ability >>>>> to manually modify before commiting, somehow! >>>>> >>>>> Regards, Gary >>>>> >>>>>> -----Original Message----- >>>>>> From: Stephane Ducasse [mailto:stephane.ducasse@inria.fr] >>>>>> Sent: 10 December 2008 1:05 PM >>>>>> To: Gary Chambers >>>>>> Subject: Issue 384: copy and paste does not work in MC diff view >>>>>> >>>>>> >>>>>> http://code.google.com/p/pharo/issues/detail?id=384&colspec=ID >>>>>> %20T >>>>>> ype%20Status%20Summary&start=100 >>>>>> >>>>> >>>>> >>>>> >>>>> Consider your responsibility to the environment - think before you >>>>> print! >>>>> >>>>> >>>> ****************************************************************** >>>> >> ************************************************************************ >>>>> This email is from Pinesoft Limited. Its contents are confidential >>>>> to the intended recipient(s) at the email address(es) to which it >>>>> has been addressed. It may not be disclosed to or used by anyone >>>>> other than the addressee(s), nor may it be copied in anyway. If >>>>> received in error, please contact the sender, then delete it from >>>>> your system. Although this email and attachments are believed to >>>>> be >>>>> free of virus, or any other defect which might affect any computer >>>>> or IT system into which they are received and opened, it is the >>>>> responsibility of the recipient to ensure that they are virus free >>>>> and no responsibility is accepted by Pinesoft for any loss or >>>>> damage >>>>> arising in any way from receipt or use thereof. >>>>> >>>> ****************************************************************** >>>> >> ************************************************************************* >>>>> >>>>> >>>>> Pinesoft Limited are registered in England, Registered number: >>>>> 2914825. Registered office: 266-268 High Street, Waltham Cross, >>>>> Herts, EN8 7EA >>>>> >>>> >>>> >>> >> >> >

1 0

[Pharo-project] Redrawing bug ?
by Damien Pollet Dec. 10, 2008

Dec. 10, 2008

There is something funny with the latest pharo, apparently it is redrawing something in a loop. Counting Squeak + WindowServer this amounts to quite a lot of CPU (60-80%). Using QuartzDebug, it seems OB continually redraws the horizontal splitter between the columns and the status line above the buttons. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

1 0