February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ZTimestamp>>monthName spelling error

by Sven Van Caekenberghe

Sabine, On 01 Feb 2014, at 12:52, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Sven, > > could you change Februari into February please? Ah, terrible typo, it was all over the place. === Name: ZTimestamp-SvenVanCaekenberghe.32 Author: SvenVanCaekenberghe Time: 1 February 2014, 1:27:02.50151 pm UUID: 70fd3b88-e15e-4139-922c-9c602e3fc532 Ancestors: ZTimestamp-SvenVanCaekenberghe.31 The English spelling of the 2nd month name was consistently wrong: Februari instead of the correct February (thx Sabine KnÃ¶fel); Now use #monthIndex instead of the less consistent #month === Btw, did you know you can do: (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') german; format: Date today. => 'Samstag, 1 Februar, 2014' Regards, Sven > (I use http://mc.stfx.eu/Neo, this is the right place?) > > Regards > Sabine > > ZTimestamp>>monthName > "Return the English name of the month of the receiver, according to the > Gregorian calendar, a Symbol" > > ^ #(January Februari March April May June July August September October > November December) at: self monthIndex > > > > -- > View this message in context: http://forum.world.st/ZTimestamp-monthName-spelling-error-tp4740821.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Feb. 1, 2014

Re: [Pharo-dev] Yet another week of commits

by Norbert Hartl

Am 31.01.2014 um 20:21 schrieb blake <dsblakewatson(a)gmail.com>: > Websense categorizes "association.pharo.org" as "sex". > That should help attract new people :) Norbert > > On Fri, Jan 31, 2014 at 10:56 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Another week of improvements > > http://association.pharo.org/web/weekly/Commits-Jan-3 > > stef >

Feb. 1, 2014

Re: [Pharo-dev] Slides Pharo3 Fosdem

by Tudor Girba

Nice. Thanks Marcus for the advertising effort! Doru On Sat, Feb 1, 2014 at 1:10 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Hi, > > My slides for Fosdem are online (Pharo3, Pharo4 later) > > http://www.slideshare.net/MarcusDenker/pharo3-at-fosdem > http://marcusdenker.de/talks/14Fosdem/2014-FOSDEM-Pharo3.pdf > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 1, 2014

Slides Pharo3 Fosdem

by Marcus Denker

Hi, My slides for Fosdem are online (Pharo3, Pharo4 later) http://www.slideshare.net/MarcusDenker/pharo3-at-fosdem http://marcusdenker.de/talks/14Fosdem/2014-FOSDEM-Pharo3.pdf

Feb. 1, 2014

ZTimestamp>>monthName spelling error

by Sabine KnÃ¶fel

Hi Sven, could you change Februari into February please? (I use http://mc.stfx.eu/Neo, this is the right place?) Regards Sabine ZTimestamp>>monthName "Return the English name of the month of the receiver, according to the Gregorian calendar, a Symbol" ^ #(January Februari March April May June July August September October November December) at: self monthIndex -- View this message in context: http://forum.world.st/ZTimestamp-monthName-spelling-error-tp4740821.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 1, 2014

Re: [Pharo-dev] subscript out of bounds in protocol creation

by Andreas Wacknitz

Am 01.02.2014 um 12:02 schrieb Andreas Wacknitz <a.wacknitz(a)gmx.de>: > Hi Jordi and all, > > here is my detailed receipt with a freshly downloaded 30733.zip from Pharo files: > > 1. Open Nautilus > 2. Select an arbitrary package > 3. Select an arbitrary class from that package > 4. Right-click in the methods panel and select âAdd protocolâ¦â from the popup menu. Sorry, I was a little bit imprecise here: You need to right-click in the "method categoryâ (or method protocol, I donât know the correct term) panel to add a new protocolâ¦ > 5. Enter âprivateâ in the dialog without selecting any entry in the listbox on top. > 6. Hit âenterâ or press âOKâ with a left-click. > > -> Bummer! A cascade of 3 "SubscriptOutOfBounce: 1â pre-debuggers. > > Regards, > Andreas > > > > Am 01.02.2014 um 11:46 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > >> Hi, >> >> With a fresh image, I do that with a class randomly selected >> (obviously, with no class selected nothing happens) and the >> protocol gets added without problems. Then, I choose another class, >> again I pick a random one, and after doing exactly the same the >> error appears. Why? No clue. >> >> I said that the error is difficult to reproduce because sometimes >> it appears, and sometimes not. And I am not able to ascertain the >> circumstances under which it will pop up. >> >> Bests, >> >> Jordi >> >> >> >> >>> Hi, >>> >>> Am 31.01.2014 um 08:36 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: >>> >>>> Hi, >>>> >>>> I realized that sometimes, when creating new protocols, it appears an >>>> error "subscript out of bounds: 1". I have not been able -yet- >>>> to reproduce it from a clean image, but it happens often (at least >>>> to me). It seems to me that it has something to do with protocol >>>> creation before any method has been written, but I am still investigating. >>>> >>> I guess I can produce this easily :-) >>> Just hit âAdd protocolâ¦â in the popup menu of the method protocol pane. >>> Enter a name like âprivateâ in the dialog. And then press enter without selecting anything in the listbox above. >>> And voilÃ â¦ >>> >>> Regards, >>> Andreas >>> >>> >>> >> > >

Feb. 1, 2014

Re: [Pharo-dev] subscript out of bounds in protocol creation

by Andreas Wacknitz

Hi Jordi and all, here is my detailed receipt with a freshly downloaded 30733.zip from Pharo files: 1. Open Nautilus 2. Select an arbitrary package 3. Select an arbitrary class from that package 4. Right-click in the methods panel and select âAdd protocolâ¦â from the popup menu. 5. Enter âprivateâ in the dialog without selecting any entry in the listbox on top. 6. Hit âenterâ or press âOKâ with a left-click. -> Bummer! A cascade of 3 "SubscriptOutOfBounce: 1â pre-debuggers. Regards, Andreas Am 01.02.2014 um 11:46 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > Hi, > > With a fresh image, I do that with a class randomly selected > (obviously, with no class selected nothing happens) and the > protocol gets added without problems. Then, I choose another class, > again I pick a random one, and after doing exactly the same the > error appears. Why? No clue. > > I said that the error is difficult to reproduce because sometimes > it appears, and sometimes not. And I am not able to ascertain the > circumstances under which it will pop up. > > Bests, > > Jordi > > > > >> Hi, >> >> Am 31.01.2014 um 08:36 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: >> >>> Hi, >>> >>> I realized that sometimes, when creating new protocols, it appears an >>> error "subscript out of bounds: 1". I have not been able -yet- >>> to reproduce it from a clean image, but it happens often (at least >>> to me). It seems to me that it has something to do with protocol >>> creation before any method has been written, but I am still investigating. >>> >> I guess I can produce this easily :-) >> Just hit âAdd protocolâ¦â in the popup menu of the method protocol pane. >> Enter a name like âprivateâ in the dialog. And then press enter without selecting anything in the listbox above. >> And voilÃ â¦ >> >> Regards, >> Andreas >> >> >> >

Feb. 1, 2014

Re: [Pharo-dev] subscript out of bounds in protocol creation

by Jordi Delgado

Hi, With a fresh image, I do that with a class randomly selected (obviously, with no class selected nothing happens) and the protocol gets added without problems. Then, I choose another class, again I pick a random one, and after doing exactly the same the error appears. Why? No clue. I said that the error is difficult to reproduce because sometimes it appears, and sometimes not. And I am not able to ascertain the circumstances under which it will pop up. Bests, Jordi > Hi, > > Am 31.01.2014 um 08:36 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > > Hi, > > > > I realized that sometimes, when creating new protocols, it appears an > > error "subscript out of bounds: 1". I have not been able -yet- > > to reproduce it from a clean image, but it happens often (at least > > to me). It seems to me that it has something to do with protocol > > creation before any method has been written, but I am still investigating. > > > I guess I can produce this easily :-) > Just hit ÂAdd protocolÂÂ in the popup menu of the method protocol pane. > Enter a name like ÂprivateÂ in the dialog. And then press enter without selecting anything in the listbox above. > And voilÃ Â > > Regards, > Andreas > > >

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Andreas Wacknitz

Am 31.01.2014 um 20:50 schrieb Pharo4Stef <pharo4Stef(a)free.fr>: > > >>> Hi Torsten, >>> >>> I think it is a design decision / tradeoff, and therefore there is no fundamentally "right way" to do it. For me, it is the same case as the uses: message for Traits. It's not in the template by default because it is used very infrequently. So for language simplicity it should not be there. For me, simplicity is one of the core points of Smalltalk so this is why I feel strongly about it. >> >> I donât see how this change make Smalltalk (the language) simpler. For me this change looks more like an obfuscation than a simplification. > > How many lectures did you give? It is annoying to have to explain something that usually people do not need to know. I donât give any lectures to students but I often try to âteachâ Smalltalk to some of my colleagues and friends. And with that I have hard times. Typically âexperiencedâ software developers think about themselves as being experts in object orientation and programming languages, even if they have only experiences with C, C# and C++. âTeachingâ them about Smalltalkâs idea of object orientation is VERY hard, almost impossible because they already know everything (read: they are ignorant) and lazy. I guess there are some similarities to students. So, no I donât teach but have my own problems ;-) > >>> When I say "very infrequently", this is of course a fuzzy metric, I know. And I understand that you do not agree with this design decision. >>> >>> But on the other hand, I don't think that it is too hard to remember where to add the pooldictionaries: line if you need it, and the old message with this line still works, so all old examples still work. >> >> How should newcomers know how to enter pool dictionaries? I rarely use pool dictionaries and if I will need it I surely have forgotten about >> this change and expect irritation and frustration. > > Newcomers do not use pooldictionaries. In 10 years smalltalking I used them twice. Newcomers donât use a lot of things but that should not be a reason to hide them. In my experience newcomers need guidance and rules but âoldtimersâ need freedom. This is one of the reasons I really enjoy dynamic typing and Smalltalk. I donât like to obey to artificial rules that only put permanent burden to me in order to protect me from something I might do wrong sometimes. At the moment I am considering pool dictionaries for a solution of a problem at hand: I need to collect some information (warnings, errors, and reports) over lots of related and unrelated classes. For the moment I have parameters, but that is getting inconvenient with a growing number of things to collectâ¦ So, if you need something it should be there and not necessarily obscured and hidden! >> >> So, a -1 for this change from my side. > > We just need a full class template menu item. Yes, but itâs not there yet but this change already took away some power without giving me back something in exchange! I am able to ignore some parts of class creation message easily (I also donât use class variables that often) and I donât see why students shouldnât be able, too. Quite contrary I think if you hide these things from students they wonât see it, wonât get curious and in the end will only learn the boring parts of Smalltalkâ¦ Regards, Andreas

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by GOUBIER Thierry

Let's make Nautilus menu longer with a full class template ! -1, Honestly Shortening the default class description is also painfull when you port code, because it makes the class appear different (description with and without pool dictionaries) in the change sorter. I wrote a pac change reader to port SmaCC from Dolphin to Pharo, and, really, this kind of change makes that unusable. In short, make that change correctly: at the Nautilus level. It's a GUI issue, not a language issue. Just go your average GUI approach : a wizard for creating classes, with at least ten "Next" to go through for each class creation ;) As an aside: I suspect there are others low-levels Smalltalk langage features that we feel engaged to change or hack them because they appear straight through the GUI, instead of being mapped to whatever flavor of the day in the GUI. A list of recent changes which do belong to that: The all protocol. A special AST node type for #subclass:instanceVariables:... Some of RPackage features and requests (which, I think, have the nice side effect of making RPackage harder to implement) Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Pharo4Stef [pharo4Stef(a)free.fr] Date d'envoi : vendredi 31 janvier 2014 20:50 Ã : Pharo Development List Objet : Re: [Pharo-dev] poolDictionaries removal breaks my projects >> Hi Torsten, >> >> I think it is a design decision / tradeoff, and therefore there is no fundamentally "right way" to do it. For me, it is the same case as the uses: message for Traits. It's not in the template by default because it is used very infrequently. So for language simplicity it should not be there. For me, simplicity is one of the core points of Smalltalk so this is why I feel strongly about it. > > I donât see how this change make Smalltalk (the language) simpler. For me this change looks more like an obfuscation than a simplification. How many lectures did you give? It is annoying to have to explain something that usually people do not need to know. >> When I say "very infrequently", this is of course a fuzzy metric, I know. And I understand that you do not agree with this design decision. >> >> But on the other hand, I don't think that it is too hard to remember where to add the pooldictionaries: line if you need it, and the old message with this line still works, so all old examples still work. > > How should newcomers know how to enter pool dictionaries? I rarely use pool dictionaries and if I will need it I surely have forgotten about > this change and expect irritation and frustration. Newcomers do not use pooldictionaries. In 10 years smalltalking I used them twice. > > So, a -1 for this change from my side. We just need a full class template menu item.

Feb. 1, 2014