June 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Mugs 'n' stuff

by ClÃ©ment Bera

I have to agree. I would love to have a Pharo T-shirt. And I think I know some other people that would be interested :) Perhaps we could also get Pharo ecocups that we can provide for the sprints as an environment-friendly alternative of plastic glasses. 2013/6/8 Jeff Gray <jeff(a)rogerthedog.com> > ok so I need to be writing code in Pharo whilst drinking coffee from a > Pharo > branded coffee mug. Am I right? Yes of course I am. > I'll start 3 discussions: > 1. What mechanism for the store front. > 2. What images and message do we want to convey. > 3. What products do we most want. > Then, depending on what comes out of that I'll follow up to get something > in > place that will at least please some of the people some of the time. > Pharo is hot! We need to celebrate it. > > > > -- > View this message in context: > http://forum.world.st/Mugs-n-stuff-tp4692368.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 8, 2013

Mugs 'n' stuff - Mechanism

by Jeff Gray

How are we going to run the logistics of the Pharo merchandising? I have run a small business selling domain specific t-shirts, hats etc and I had a small online store running on a web server. That's nice from the point of view that it's sole purpose is the domain, but on the down side then it is a business with someone looking after stock and mailing etc. CafePress is an alternative. It seems pretty good at first glance. You can create your own designs and they do all the manufacture and shipping. The prices look ok and they are global. On te down side you are part of a massive base of products. I haven't looked in depth yet. There may be pitfalls. Anybody have any experience of them or any other suggestions? -- View this message in context: http://forum.world.st/Mugs-n-stuff-Mechanism-tp4692369.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 8, 2013

Mugs 'n' stuff

by Jeff Gray

ok so I need to be writing code in Pharo whilst drinking coffee from a Pharo branded coffee mug. Am I right? Yes of course I am. I'll start 3 discussions: 1. What mechanism for the store front. 2. What images and message do we want to convey. 3. What products do we most want. Then, depending on what comes out of that I'll follow up to get something in place that will at least please some of the people some of the time. Pharo is hot! We need to celebrate it. -- View this message in context: http://forum.world.st/Mugs-n-stuff-tp4692368.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 8, 2013

Blog Entry About Pharo

by Bahman Movaqar

Hi all, I wrote a blog entry[1] about Pharo and would appreciate your opinions and possible corrections. PS: Anonymous comments are enabled on my website. I had to disable user creation to fight spam. However if you'd like a user, I'll be pleased to create one for you. [1] http://www.bahmanm.com/blogs/a-new-platform-for-business-app-development -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation, Deployment Consultant

June 8, 2013

Re: [Pharo-users] DateAndTime>>asTime

by StÃ©phane Ducasse

thanks :) This is less work for us and the process can automatically check the code and run the tests automatically. Stef On Jun 7, 2013, at 10:16 PM, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: > Ok, I will correct it tomorrow. > > Txs > > > > El 07/06/2013, a las 21:45, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > >> Jose >> >> normally we do not summit code in the pane of the bug tracker, we commit a slice (click + slice in the monticello browser) >> in the inbox folder. >> >> Stef >> >> On Jun 7, 2013, at 9:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >> >>> tx I will look at it. >>> >>> Stef >>> >>> On Jun 7, 2013, at 8:57 PM, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>> >>>> Done. >>>> >>>> I hope I have made it correctly. If not, please tell me. >>>> >>>> Regards >>>> >>>> 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> Here it is https://pharo.fogbugz.com/default.asp?10869 >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> On Jun 7, 2013, at 8:17 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >>>> >>>>> >>>>> >>>>>> Hi again. >>>>>> >>>>>> I have one first test for #readFrom:pattern:. What can I do now to send it, where, to whom?. >>>>> >>>>> I will create a bug entry for you and you create a slice with the test and the fix and you publish it in the pharo inbox. >>>>> >>>>> Stef >>>>> >>>>>> >>>>>> Regards >>>>>> >>>>>> 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>> >>>>>> On 07 Jun 2013, at 14:28, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>>>> >>>>>> > Answers in red. >>>>>> > >>>>>> > Regards >>>>>> > >>>>>> > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>> > >>>>>> > On 07 Jun 2013, at 13:26, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>>>> > >>>>>> > > Thank you Sven. >>>>>> > > >>>>>> > > I had made the fixes myself, creating a new class for dates (I don't need the complexity of Date just for determining if a date is past, I don't need date arithmetic either). I just wanted to inform, mainly because the bug seems to be still present in Pharo 3.0. >>>>>> > > >>>>>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although it does for 'd/m/yy'. >>>>>> > >>>>>> > Depends on what a single y means, right ? >>>>>> > >>>>>> > According to documentation, one y means ...year, no matter how many digits supplied... (my own words, not litteral). It means it will either accept ../../13 or ../../2013 >>>>>> >>>>>> Yes, that is how I understood it as well. My change adds 2000 only in the case of 2 y's unless I am mistaken. But I must admin I didn't test it. >>>>>> >>>>>> > > I could write the tests you suggest, if you think they are interesting. >>>>>> > >>>>>> > Yes, please do: with a good set of tests, we can discuss using concrete examples. >>>>>> > >>>>>> > >>>>>> > Sure I will. Will keep you informed! >>>>>> >>>>>> Super. >>>>>> >>>>>> > > Regards >>>>>> > > >>>>>> > > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>> > > Hi JosÃ©, >>>>>> > > >>>>>> > > On 07 Jun 2013, at 12:02, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>>>> > > >>>>>> > > > Hello everybody. >>>>>> > > > >>>>>> > > > I would like to add a new improvement to this thread. >>>>>> > > > >>>>>> > > > I have noticed that Date class has a bug, or at least something to improve in readFrom:pattern: method. The initial comment states that "A year given using only two decimals is considered to be >2000.". >>>>>> > > > >>>>>> > > > But this seems to be incorrect: if you evaluate >>>>>> > > > >>>>>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y' >>>>>> > > > >>>>>> > > > you get: >>>>>> > > > >>>>>> > > > 7 June 0013 instead of 7 June 2013. >>>>>> > > > >>>>>> > > > I am working with version #20605 >>>>>> > > >>>>>> > > The fix would be quite easy: >>>>>> > > >>>>>> > > year := (inputStream next: 2) asInteger >>>>>> > > >>>>>> > > should be >>>>>> > > >>>>>> > > year := 2000 + (inputStream next: 2) asInteger >>>>>> > > >>>>>> > > A more important problem is that there are no users of #readFrom:pattern: in the system, not even unit tests. If we want to keep the methods, someone should start by writing a couple of unit tests. >>>>>> > > >>>>>> > > Sven >>>>>> > > >>>>>> > > > Thank you all for your great work. >>>>>> > > > >>>>>> > > > Regards. >>>>>> > > > >>>>>> > > > >>>>>> > > > 2013/6/6 Camillo Bruni <camillobruni(a)gmail.com> >>>>>> > > > can you save an image with the inspector opened on both x and y, x asTime and y asTime >>>>>> > > > and provide a link to it? like that I can inspect it in all detail... >>>>>> > > > >>>>>> > > > On 2013-06-06, at 17:51, dmacq <dmacq(a)instantiations.com> wrote: >>>>>> > > > >>>>>> > > > > I tried it again this morning and still had the problem. >>>>>> > > > > >>>>>> > > > > This is interesting. >>>>>> > > > > >>>>>> > > > > | x y | >>>>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>>>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>>>>> > > > > x = y <------------------ True >>>>>> > > > > >>>>>> > > > > But >>>>>> > > > > | x y | >>>>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>>>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>>>>> > > > > x asTime = y asTime <------------- False >>>>>> > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> > > > > -- >>>>>> > > > > View this message in context: http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html >>>>>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>>>>> > > > > >>>>>> > > > >>>>>> > > > >>>>>> > > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > >>>>>> > >>>>>> > >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >>

June 7, 2013

Re: [Pharo-users] DateAndTime>>asTime

by JosÃ© ComesaÃ±a

Ok, I will correct it tomorrow. Txs El 07/06/2013, a las 21:45, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > Jose > > normally we do not summit code in the pane of the bug tracker, we commit a slice (click + slice in the monticello browser) > in the inbox folder. > > Stef > > On Jun 7, 2013, at 9:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> tx I will look at it. >> >> Stef >> >> On Jun 7, 2013, at 8:57 PM, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >> >>> Done. >>> >>> I hope I have made it correctly. If not, please tell me. >>> >>> Regards >>> >>> 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> Here it is https://pharo.fogbugz.com/default.asp?10869 >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> On Jun 7, 2013, at 8:17 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >>>> >>>>> >>>>> >>>>>> Hi again. >>>>>> >>>>>> I have one first test for #readFrom:pattern:. What can I do now to send it, where, to whom?. >>>>> >>>>> I will create a bug entry for you and you create a slice with the test and the fix and you publish it in the pharo inbox. >>>>> >>>>> Stef >>>>> >>>>>> >>>>>> Regards >>>>>> >>>>>> 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>>> >>>>>>> On 07 Jun 2013, at 14:28, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>>>>> >>>>>>> > Answers in red. >>>>>>> > >>>>>>> > Regards >>>>>>> > >>>>>>> > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>>> > >>>>>>> > On 07 Jun 2013, at 13:26, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>>>>> > >>>>>>> > > Thank you Sven. >>>>>>> > > >>>>>>> > > I had made the fixes myself, creating a new class for dates (I don't need the complexity of Date just for determining if a date is past, I don't need date arithmetic either). I just wanted to inform, mainly because the bug seems to be still present in Pharo 3.0. >>>>>>> > > >>>>>>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although it does for 'd/m/yy'. >>>>>>> > >>>>>>> > Depends on what a single y means, right ? >>>>>>> > >>>>>>> > According to documentation, one y means ...year, no matter how many digits supplied... (my own words, not litteral). It means it will either accept ../../13 or ../../2013 >>>>>>> >>>>>>> Yes, that is how I understood it as well. My change adds 2000 only in the case of 2 y's unless I am mistaken. But I must admin I didn't test it. >>>>>>> >>>>>>> > > I could write the tests you suggest, if you think they are interesting. >>>>>>> > >>>>>>> > Yes, please do: with a good set of tests, we can discuss using concrete examples. >>>>>>> > >>>>>>> > >>>>>>> > Sure I will. Will keep you informed! >>>>>>> >>>>>>> Super. >>>>>>> >>>>>>> > > Regards >>>>>>> > > >>>>>>> > > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>>> > > Hi JosÃ©, >>>>>>> > > >>>>>>> > > On 07 Jun 2013, at 12:02, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>>>>> > > >>>>>>> > > > Hello everybody. >>>>>>> > > > >>>>>>> > > > I would like to add a new improvement to this thread. >>>>>>> > > > >>>>>>> > > > I have noticed that Date class has a bug, or at least something to improve in readFrom:pattern: method. The initial comment states that "A year given using only two decimals is considered to be >2000.". >>>>>>> > > > >>>>>>> > > > But this seems to be incorrect: if you evaluate >>>>>>> > > > >>>>>>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y' >>>>>>> > > > >>>>>>> > > > you get: >>>>>>> > > > >>>>>>> > > > 7 June 0013 instead of 7 June 2013. >>>>>>> > > > >>>>>>> > > > I am working with version #20605 >>>>>>> > > >>>>>>> > > The fix would be quite easy: >>>>>>> > > >>>>>>> > > year := (inputStream next: 2) asInteger >>>>>>> > > >>>>>>> > > should be >>>>>>> > > >>>>>>> > > year := 2000 + (inputStream next: 2) asInteger >>>>>>> > > >>>>>>> > > A more important problem is that there are no users of #readFrom:pattern: in the system, not even unit tests. If we want to keep the methods, someone should start by writing a couple of unit tests. >>>>>>> > > >>>>>>> > > Sven >>>>>>> > > >>>>>>> > > > Thank you all for your great work. >>>>>>> > > > >>>>>>> > > > Regards. >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > 2013/6/6 Camillo Bruni <camillobruni(a)gmail.com> >>>>>>> > > > can you save an image with the inspector opened on both x and y, x asTime and y asTime >>>>>>> > > > and provide a link to it? like that I can inspect it in all detail... >>>>>>> > > > >>>>>>> > > > On 2013-06-06, at 17:51, dmacq <dmacq(a)instantiations.com> wrote: >>>>>>> > > > >>>>>>> > > > > I tried it again this morning and still had the problem. >>>>>>> > > > > >>>>>>> > > > > This is interesting. >>>>>>> > > > > >>>>>>> > > > > | x y | >>>>>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>>>>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>>>>>> > > > > x = y <------------------ True >>>>>>> > > > > >>>>>>> > > > > But >>>>>>> > > > > | x y | >>>>>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>>>>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>>>>>> > > > > x asTime = y asTime <------------- False >>>>>>> > > > > >>>>>>> > > > > >>>>>>> > > > > >>>>>>> > > > > -- >>>>>>> > > > > View this message in context: http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html >>>>>>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>>>>>> > > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > >>>>>>> > >>>>>>> > >

June 7, 2013

Re: [Pharo-users] DateAndTime>>asTime

by StÃ©phane Ducasse

Jose normally we do not summit code in the pane of the bug tracker, we commit a slice (click + slice in the monticello browser) in the inbox folder. Stef On Jun 7, 2013, at 9:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > tx I will look at it. > > Stef > > On Jun 7, 2013, at 8:57 PM, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: > >> Done. >> >> I hope I have made it correctly. If not, please tell me. >> >> Regards >> >> 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Here it is https://pharo.fogbugz.com/default.asp?10869 >> >> Stef >> >> >> >> >> On Jun 7, 2013, at 8:17 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >> >>> >>> >>>> Hi again. >>>> >>>> I have one first test for #readFrom:pattern:. What can I do now to send it, where, to whom?. >>> >>> I will create a bug entry for you and you create a slice with the test and the fix and you publish it in the pharo inbox. >>> >>> Stef >>> >>>> >>>> Regards >>>> >>>> 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>> >>>> On 07 Jun 2013, at 14:28, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>> >>>> > Answers in red. >>>> > >>>> > Regards >>>> > >>>> > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>> > >>>> > On 07 Jun 2013, at 13:26, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>> > >>>> > > Thank you Sven. >>>> > > >>>> > > I had made the fixes myself, creating a new class for dates (I don't need the complexity of Date just for determining if a date is past, I don't need date arithmetic either). I just wanted to inform, mainly because the bug seems to be still present in Pharo 3.0. >>>> > > >>>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although it does for 'd/m/yy'. >>>> > >>>> > Depends on what a single y means, right ? >>>> > >>>> > According to documentation, one y means ...year, no matter how many digits supplied... (my own words, not litteral). It means it will either accept ../../13 or ../../2013 >>>> >>>> Yes, that is how I understood it as well. My change adds 2000 only in the case of 2 y's unless I am mistaken. But I must admin I didn't test it. >>>> >>>> > > I could write the tests you suggest, if you think they are interesting. >>>> > >>>> > Yes, please do: with a good set of tests, we can discuss using concrete examples. >>>> > >>>> > >>>> > Sure I will. Will keep you informed! >>>> >>>> Super. >>>> >>>> > > Regards >>>> > > >>>> > > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>>> > > Hi JosÃ©, >>>> > > >>>> > > On 07 Jun 2013, at 12:02, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>>> > > >>>> > > > Hello everybody. >>>> > > > >>>> > > > I would like to add a new improvement to this thread. >>>> > > > >>>> > > > I have noticed that Date class has a bug, or at least something to improve in readFrom:pattern: method. The initial comment states that "A year given using only two decimals is considered to be >2000.". >>>> > > > >>>> > > > But this seems to be incorrect: if you evaluate >>>> > > > >>>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y' >>>> > > > >>>> > > > you get: >>>> > > > >>>> > > > 7 June 0013 instead of 7 June 2013. >>>> > > > >>>> > > > I am working with version #20605 >>>> > > >>>> > > The fix would be quite easy: >>>> > > >>>> > > year := (inputStream next: 2) asInteger >>>> > > >>>> > > should be >>>> > > >>>> > > year := 2000 + (inputStream next: 2) asInteger >>>> > > >>>> > > A more important problem is that there are no users of #readFrom:pattern: in the system, not even unit tests. If we want to keep the methods, someone should start by writing a couple of unit tests. >>>> > > >>>> > > Sven >>>> > > >>>> > > > Thank you all for your great work. >>>> > > > >>>> > > > Regards. >>>> > > > >>>> > > > >>>> > > > 2013/6/6 Camillo Bruni <camillobruni(a)gmail.com> >>>> > > > can you save an image with the inspector opened on both x and y, x asTime and y asTime >>>> > > > and provide a link to it? like that I can inspect it in all detail... >>>> > > > >>>> > > > On 2013-06-06, at 17:51, dmacq <dmacq(a)instantiations.com> wrote: >>>> > > > >>>> > > > > I tried it again this morning and still had the problem. >>>> > > > > >>>> > > > > This is interesting. >>>> > > > > >>>> > > > > | x y | >>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>>> > > > > x = y <------------------ True >>>> > > > > >>>> > > > > But >>>> > > > > | x y | >>>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>>> > > > > x asTime = y asTime <------------- False >>>> > > > > >>>> > > > > >>>> > > > > >>>> > > > > -- >>>> > > > > View this message in context: http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html >>>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>>> > > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > >>>> > > >>>> > > >>>> > >>>> > >>>> > >>>> >>>> >>>> >>> >> >> >

June 7, 2013

Re: [Pharo-users] DateAndTime>>asTime

by StÃ©phane Ducasse

tx I will look at it. Stef On Jun 7, 2013, at 8:57 PM, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: > Done. > > I hope I have made it correctly. If not, please tell me. > > Regards > > 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Here it is https://pharo.fogbugz.com/default.asp?10869 > > Stef > > > > > On Jun 7, 2013, at 8:17 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> >> >>> Hi again. >>> >>> I have one first test for #readFrom:pattern:. What can I do now to send it, where, to whom?. >> >> I will create a bug entry for you and you create a slice with the test and the fix and you publish it in the pharo inbox. >> >> Stef >> >>> >>> Regards >>> >>> 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>> >>> On 07 Jun 2013, at 14:28, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>> >>> > Answers in red. >>> > >>> > Regards >>> > >>> > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>> > >>> > On 07 Jun 2013, at 13:26, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>> > >>> > > Thank you Sven. >>> > > >>> > > I had made the fixes myself, creating a new class for dates (I don't need the complexity of Date just for determining if a date is past, I don't need date arithmetic either). I just wanted to inform, mainly because the bug seems to be still present in Pharo 3.0. >>> > > >>> > > Anyway, your solution does not work for the 'd/m/y' pattern, although it does for 'd/m/yy'. >>> > >>> > Depends on what a single y means, right ? >>> > >>> > According to documentation, one y means ...year, no matter how many digits supplied... (my own words, not litteral). It means it will either accept ../../13 or ../../2013 >>> >>> Yes, that is how I understood it as well. My change adds 2000 only in the case of 2 y's unless I am mistaken. But I must admin I didn't test it. >>> >>> > > I could write the tests you suggest, if you think they are interesting. >>> > >>> > Yes, please do: with a good set of tests, we can discuss using concrete examples. >>> > >>> > >>> > Sure I will. Will keep you informed! >>> >>> Super. >>> >>> > > Regards >>> > > >>> > > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >>> > > Hi JosÃ©, >>> > > >>> > > On 07 Jun 2013, at 12:02, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >>> > > >>> > > > Hello everybody. >>> > > > >>> > > > I would like to add a new improvement to this thread. >>> > > > >>> > > > I have noticed that Date class has a bug, or at least something to improve in readFrom:pattern: method. The initial comment states that "A year given using only two decimals is considered to be >2000.". >>> > > > >>> > > > But this seems to be incorrect: if you evaluate >>> > > > >>> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y' >>> > > > >>> > > > you get: >>> > > > >>> > > > 7 June 0013 instead of 7 June 2013. >>> > > > >>> > > > I am working with version #20605 >>> > > >>> > > The fix would be quite easy: >>> > > >>> > > year := (inputStream next: 2) asInteger >>> > > >>> > > should be >>> > > >>> > > year := 2000 + (inputStream next: 2) asInteger >>> > > >>> > > A more important problem is that there are no users of #readFrom:pattern: in the system, not even unit tests. If we want to keep the methods, someone should start by writing a couple of unit tests. >>> > > >>> > > Sven >>> > > >>> > > > Thank you all for your great work. >>> > > > >>> > > > Regards. >>> > > > >>> > > > >>> > > > 2013/6/6 Camillo Bruni <camillobruni(a)gmail.com> >>> > > > can you save an image with the inspector opened on both x and y, x asTime and y asTime >>> > > > and provide a link to it? like that I can inspect it in all detail... >>> > > > >>> > > > On 2013-06-06, at 17:51, dmacq <dmacq(a)instantiations.com> wrote: >>> > > > >>> > > > > I tried it again this morning and still had the problem. >>> > > > > >>> > > > > This is interesting. >>> > > > > >>> > > > > | x y | >>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>> > > > > x = y <------------------ True >>> > > > > >>> > > > > But >>> > > > > | x y | >>> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >>> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 second: 7. >>> > > > > x asTime = y asTime <------------- False >>> > > > > >>> > > > > >>> > > > > >>> > > > > -- >>> > > > > View this message in context: http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html >>> > > > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> > > > > >>> > > > >>> > > > >>> > > > >>> > > >>> > > >>> > > >>> > >>> > >>> > >>> >>> >>> >> > >

June 7, 2013

Re: [Pharo-users] DateAndTime>>asTime

by JosÃ© ComesaÃ±a

Done. I hope I have made it correctly. If not, please tell me. Regards 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Here it is https://pharo.fogbugz.com/default.asp?10869 > > Stef > > > > > On Jun 7, 2013, at 8:17 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> > wrote: > > > > Hi again. > > I have one first test for #readFrom:pattern:. What can I do now to send > it, where, to whom?. > > > I will create a bug entry for you and you create a slice with the test and > the fix and you publish it in the pharo inbox. > > Stef > > > Regards > > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> > >> >> On 07 Jun 2013, at 14:28, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: >> >> > Answers in red. >> > >> > Regards >> > >> > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >> > >> > On 07 Jun 2013, at 13:26, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> >> wrote: >> > >> > > Thank you Sven. >> > > >> > > I had made the fixes myself, creating a new class for dates (I don't >> need the complexity of Date just for determining if a date is past, I don't >> need date arithmetic either). I just wanted to inform, mainly because the >> bug seems to be still present in Pharo 3.0. >> > > >> > > Anyway, your solution does not work for the 'd/m/y' pattern, although >> it does for 'd/m/yy'. >> > >> > Depends on what a single y means, right ? >> > >> > According to documentation, one y means ...year, no matter how many >> digits supplied... (my own words, not litteral). It means it will either >> accept ../../13 or ../../2013 >> >> Yes, that is how I understood it as well. My change adds 2000 only in the >> case of 2 y's unless I am mistaken. But I must admin I didn't test it. >> >> > > I could write the tests you suggest, if you think they are >> interesting. >> > >> > Yes, please do: with a good set of tests, we can discuss using concrete >> examples. >> > >> > >> > Sure I will. Will keep you informed! >> >> Super. >> >> > > Regards >> > > >> > > 2013/6/7 Sven Van Caekenberghe <sven(a)stfx.eu> >> > > Hi JosÃ©, >> > > >> > > On 07 Jun 2013, at 12:02, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> >> wrote: >> > > >> > > > Hello everybody. >> > > > >> > > > I would like to add a new improvement to this thread. >> > > > >> > > > I have noticed that Date class has a bug, or at least something to >> improve in readFrom:pattern: method. The initial comment states that "A >> year given using only two decimals is considered to be >2000.". >> > > > >> > > > But this seems to be incorrect: if you evaluate >> > > > >> > > > Date readFrom: '07/06/13' readStream pattern: 'd/m/y' >> > > > >> > > > you get: >> > > > >> > > > 7 June 0013 instead of 7 June 2013. >> > > > >> > > > I am working with version #20605 >> > > >> > > The fix would be quite easy: >> > > >> > > year := (inputStream next: 2) asInteger >> > > >> > > should be >> > > >> > > year := 2000 + (inputStream next: 2) asInteger >> > > >> > > A more important problem is that there are no users of >> #readFrom:pattern: in the system, not even unit tests. If we want to keep >> the methods, someone should start by writing a couple of unit tests. >> > > >> > > Sven >> > > >> > > > Thank you all for your great work. >> > > > >> > > > Regards. >> > > > >> > > > >> > > > 2013/6/6 Camillo Bruni <camillobruni(a)gmail.com> >> > > > can you save an image with the inspector opened on both x and y, x >> asTime and y asTime >> > > > and provide a link to it? like that I can inspect it in all >> detail... >> > > > >> > > > On 2013-06-06, at 17:51, dmacq <dmacq(a)instantiations.com> wrote: >> > > > >> > > > > I tried it again this morning and still had the problem. >> > > > > >> > > > > This is interesting. >> > > > > >> > > > > | x y | >> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 >> second: 7. >> > > > > x = y <------------------ True >> > > > > >> > > > > But >> > > > > | x y | >> > > > > x := DateAndTime year: 1991 day: 196 hour: 20 minute: 5 second: 7. >> > > > > y := DateAndTime year: 1991 month: 7 day: 15 hour: 20 minute: 5 >> second: 7. >> > > > > x asTime = y asTime <------------- False >> > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > View this message in context: >> http://forum.world.st/DateAndTime-asTime-tp4691870p4691988.html >> > > > > Sent from the Pharo Smalltalk Users mailing list archive at >> Nabble.com <http://nabble.com/>. >> > > > > >> > > > >> > > > >> > > > >> > > >> > > >> > > >> > >> > >> > >> >> >> > > >

June 7, 2013

Re: [Pharo-users] Changes-File & caching

by Sven Van Caekenberghe

On 07 Jun 2013, at 19:45, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jun 7, 2013, at 11:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 07 Jun 2013, at 11:07, Markus Fritsche <fritsche.markus(a)gmail.com> wrote: >> >>> Hello Sven & List, >>> >>> On 07.06.2013 10:45, Sven Van Caekenberghe wrote: >>>> Yes, it is an important problem (but the trigger is a change in Ubuntu 13.04). I am not an Ubuntu desktop user, I can only hope that those who are will help. >>> Well, I have 13.04 on a few laptops (2GB Atom netbook, 8GB i7 dual core and 6GB AMD 4Core) with different file systems (ext4, btrfs) on them, so I have quite a few configurations at hand to test with. >> >> Great, we need more Linux Desktop users, the community it too Mac centric ;-) > > +1 > I'm waiting that mac gets totally evil to switch :) If you would switch and force a good UX, all Pharo users on Linux will thank you for it ;-) >>> The RemoteString-Error during updates has been fixed; as I see the files referenced by the download links have been replaced. The only "old" image left I found was the one titled "Pharo 2.0 image" on http://www.pharo-project.org/pharo-download which raises the error in ScriptLoaderupdate>>#20605 >> >> We need to fix that then. >> >> Thanks for the feedback. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> > >

June 7, 2013