March 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Duration year

by Maximiliano Taborda

Hi Richard, In Chalten, if you don't talk of a year in particular, February 28th + 1 day always returns March 1st. This is because Chalten asumes the structure of a non-leap year for calculate this. But, if you know the year, like in my previous example (the year 2012) then February 28th, 2012 + 1 day returns February 29th, 2012. Then, as 2012 is a leap year and I want to add 1 year to the last day of February of year 2012 (the 29th), then the result is the last day of February of 2013 (the 28th). Note that in one case we are talking about days of month (i.e. February 28th) and in the other case we are talking about dates (i.e. February 28th, 2012). Is it more clear now? By the way, reading your mail I found a little bug in Chalten. I will fix it in a couple of days. Thanks! Kind regards, Maxi 2015-03-20 14:47 GMT-03:00 Richard Sargent < richard.sargent(a)gemtalksystems.com>: > Maximiliano Taborda wrote > > Hi all. > > > > The same examples using ChaltÃ©n: > > February twentyninth, 2012 next: 1 yearMeasure. "=> February 28th, > > 2013" > > This I don't get. Why would <February 28th> + 1 day + 1 year ever not be > March 1st? ~75% of the time it would be, but ~25% it would be a day less? > > > > March first, 2011 next: 1 yearMeasure. "=> March 1st, 2012" > > March first, 2011 next: 12 monthsMeasure. "=> March 1st, 2012" > > > > Hilaire, In ChaltÃ©n a year is a year so you don't need to care about of > > the > > number of days in it. > > > > Regards. > > Maxi > > > > > > 2014-12-02 16:37 GMT-03:00 Chris Cunningham < > > > cunningham.cb@ > > > >: > > > >> GenericYear does this. The generic Year will take > >> '2/29/2000' asDate + 1 year "=> 28 February 2001" > >> In other words, we want it at the same time next year; more importantly > >> the same month and close to what we have now. > >> Also: > >> '3/1/2001' asDate - 1 year "=> 1 March 2000" > >> Still, same month - we want to be at the beginning of the month the > >> previous year. > >> > >> Basically, my idea (and, more importantly, what I expect - hence my > code) > >> is that I want to pretend that we do have a field-based representation > >> and > >> make it work that way. except better (since there is no 2/29/2001). > >> > >> > Ej, which one of the followings is OK? > >> > '2011-03-01' asDate + 1 year "=> 2012-02-29" > >> > >> Well, I have a bug here. That needs to be fixed. > >> > >> -cbc > >> > >> > >> On Tue, Dec 2, 2014 at 8:34 AM, Sean P. DeNigris < > > > sean@ > > > > > >> wrote: > >> > >>> Esteban A. Maringolo wrote > >>> > Ej, which one of the followings is OK? > >>> > '2012-02-29' asDate + 1 year "=> 2013-02-28" > >>> > '2011-03-01' asDate + 1 year "=> 2012-02-29" > >>> > >>> One solution (just ignore the source ha ha) - > >>> > >>> > http://msdn.microsoft.com/en-us/library/system.datetime.addyears%28v=vs.110… > >>> > >>> > >>> > >>> ----- > >>> Cheers, > >>> Sean > >>> -- > >>> View this message in context: > >>> http://forum.world.st/Duration-year-tp4791727p4793656.html > >>> Sent from the Pharo Smalltalk Developers mailing list archive at > >>> Nabble.com. > >>> > >>> > >> > > > > > > -- > View this message in context: > http://forum.world.st/Duration-year-tp4791727p4813662.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

March 26, 2015

Re: [Pharo-dev] Update question

by Stephan Eggermont

On 25/03/15 20:01, Norbert Hartl wrote: > That wouldn't work. I save my image often under a different image name > because I tend to break the image or it crashes. With the changes log > not working the only feasible way is to make a lot of copies of your > images. So symlinking is not working that way. Saving an image under a different name could be recognized by PharoLauncher, and integrated in the image list. That would then become an extra level in the tree. Assuming the simple case of saving in the same directory. Stephan

March 26, 2015

Re: [Pharo-dev] New Pharo-Launcher package for Mac and Windows

by kilon alios

I was talking with a new Pharo user and she was telling me that PharoLauncher was not working on Windows , glad you manage to fix it. Great work Damien , thanks :) I am using it on macos , works great . On Thu, Mar 26, 2015 at 5:46 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > Hi, > > I've just updated the 2 installers for mac and windows. > > http://files.pharo.org/platform/launcher/Pharo_0.2.4.dmg > http://files.pharo.org/platform/launcher/pharo_installer-0.2.4.exe > > - the windows installer should have the PharoV30.sources file that was > missing > > - both installers now install the most recent Pharo launcher > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

March 26, 2015

Re: [Pharo-dev] New Pharo-Launcher package for Mac and Windows

by stepharo

thanks Damien. Stef Le 26/3/15 16:46, Damien Cassou a Ã©crit : > Hi, > > I've just updated the 2 installers for mac and windows. > > http://files.pharo.org/platform/launcher/Pharo_0.2.4.dmg > http://files.pharo.org/platform/launcher/pharo_installer-0.2.4.exe > > - the windows installer should have the PharoV30.sources file that was > missing > > - both installers now install the most recent Pharo launcher >

March 26, 2015

New Pharo-Launcher package for Mac and Windows

by Damien Cassou

Hi, I've just updated the 2 installers for mac and windows. http://files.pharo.org/platform/launcher/Pharo_0.2.4.dmg http://files.pharo.org/platform/launcher/pharo_installer-0.2.4.exe - the windows installer should have the PharoV30.sources file that was missing - both installers now install the most recent Pharo launcher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 26, 2015

Re: [Pharo-dev] collecting Pharo 4.0 Contributors

by Esteban Lorenzano

> On 26 Mar 2015, at 15:19, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > > Damien Cassou <damien.cassou(a)gmail.com> writes: > >> I pair programmed with Jean-Christophe Bach on a few bug fixes. > > but Jean-Christophe Bach is not :-) ouch! yes :) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill >

March 26, 2015

Re: [Pharo-dev] Existing <script> <example> pragmas and new GT needs

by Esteban Lorenzano

wellâ¦ I do agree now is a bit late to change things. We failed to understand the different purposes of âexampleâ and âgtExampleâ at the beginning, so now we are more or less paying the consequences of that miss-spot. In any case, as any non-critical stuff, it can wait until Pharo 5 to be solved. Esteban > On 26 Mar 2015, at 14:30, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I/we do not want to impose anything on anyone. > > <gtExample> was introduced a long time (more than 1 year) ago in GT/Moose. It is used both for documentation purposes and for generic stress tests for the Inspector and Spotter (and let's not even count that the concept offers an alternative to SUnit testing that we will pursue in the near future). It got integrated in Pharo and then renamed to <example> 6 months ago (in October) after a public discussion on this mailing list. It later got mixed with the example* selectors as part of #isExampleMethod and used in Nautilus with a looser interpretation to essentially trigger the example. > > This debate started 7 days before the release. The reason why the debate started is that exactly one method started to use it differently than all other <example> methods from the Pharo image. While this debate fired on, GT does not build and cannot be integrated, even though in parallel we work like mad to meet the deadline and fix all issues that are being reported. > > And the way the debate took place is also borderline for my taste, too. I do not appreciate being shout at. I am not mad, but please do not expect me to be happy either. > > I also find it discouraging that people talk about GT as if it would not be Pharo or as if we would want to force people to do things. We are indeed a standalone team with an own set of ideas, but we do not want to force our work on anyone. As the decision was to make GT a central part of Pharo, we kindly ask you to treat us as part of Pharo. > > We never shied away from debates and listening to people. In fact, we think we are going over the board with actively listening and reacting. We can still debate the <example>, but not now. We have a release to meet. We can talk about it afterwards. But, for this to happen, I also kindly ask you to remove the <example> check from #isExampleMethod. This would allow us to start from a clean slate in Pharo 5. > > Cheers, > Doru > > > > On Thu, Mar 26, 2015 at 12:06 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Okâ¦ my 2c: > > Basically there is a difference between an âexampleâ and a prototype, which is what the gtExample intends to do. Exemplar is just another way to name a prototype. > Sorry to make you sad and tiredâ¦ but when you introduce such an important new tool as all the gtools are, you cannot expect people to accept all your choices âas isââ¦ and debate is the only way to achieve some consensus. > > Esteban > > ps: we are just days from release and we are all stressed a lotâ¦ so lets take a breath and consider things with the appropriate distance. We are not talking about the cure for cancer here, just the right name for a pragma, in a method. > > > On 26 Mar 2015, at 10:02, Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: > > > > Hi Tudor, > > > >> We will rename <example> back to <gtExample> and keep the API as it is. That will leave Pharo 4 with one <example> method while the other 100 will >use <gtExample>. This will be available with the next GT integration. > > > > As I already wrote (and Guillermo equally pointed out): most of them are there because you created/introduced many extension > > methods with GT to provide these sample instances like in $a for Charater or 42 for Integer, ... > > Which is completely valid to demonstrate how usefull your new extension is. But it is because you investigated so far more to > > demonstrate this new mechanism. > > > > > > And yes, currently we have just one <example> in the image (beside some other in external projects). But if we do not > > want to rely on the exampleXXX pattern anymore we will mark the typical example methods with <example> in the future and would > > have around 140 in the latest image: > > > > |coll| > > coll := IdentitySet new. > > Object withAllSubclassesDo: [:aClass | > > aClass class selectorsDo: [:selector | > > (selector beginsWith: 'example') ifTrue: [ coll add: selector ] > > ]]. > > ^coll > > > > If we dont mark them I agree that there are only a few counterwise. > > > > But again: from my side it is not about the current numbers. It is about the future mechanism, clear and > > understandable concepts and naming. > > > > The usualy exampleXXX demos for code fits well with <example> from the name and mentally. "Example" > > is a very generous term for something to look at and learn. > > > > In Pharo one can now demonstrate in the new GT inspector lively ready made instances! > > You feature and the research bound to it is not only important but a real improvement. > > I like that and I'm sure this will push us forward a lot. > > > > Still IMHO mentally using <example> for depicting "code to look at" does fit namewise and > > conceptualy very well with the known and usual example methods in the image or external > > packages. Some of them provide an instance, but many of them just show how to use code. > > > > And yes: I would the new GT mechanism to use a term and pragma name that better depicts > > what should be provided from the one who uses it: typical example instances or exemplars > > of the class. > > > > When one creates a class > > > > Object subclass: #RevolutionarySystem > > instanceVariableNames: 'name' > > classVariableNames: '' > > category: 'The-World' > > > > he can implement a class side method to use the new mechanism: > > > > uniqueExemplar > > <exemplar> > > > > ^RevolutionarySystem called: 'Pharo' > > > > And this class side method returns an exemplary instance. If such a method should > > also serves as an example method (in the tradition of a code example to look at) > > one can even mark it with both pragmas. > > > >> The decision has nothing to do with arguments. > > > > Why do you negotiate instead of (at a minimum) ellaborate what you think of the made > > proposal to use "exemplar" for the new GT mechanism. > > > > See the definition for <exemplar>: > > > > http://dictionary.reference.com/browse/exemplar <http://dictionary.reference.com/browse/exemplar> > > "a model or pattern to be copied or imitated" > > "a typical example or instance" > > > > http://www.thefreedictionary.com/exemplar <http://www.thefreedictionary.com/exemplar> > > "One that is worthy of imitation; a perfect example or model" > > "One that is typical or representative" > > > > http://www.merriam-webster.com/dictionary/exemplar <http://www.merriam-webster.com/dictionary/exemplar> > > "an admired person or thing that is considered an example that deserves to be copied" > > "a typical example" > > > > http://www.ldoceonline.com/dictionary/exemplar <http://www.ldoceonline.com/dictionary/exemplar> > > "formal a good or typical example" > > > > http://www.dict.cc/?s=exemplar <http://www.dict.cc/?s=exemplar> > > "instance" > > "specimen" > > "sample" > > > > All the 100 instances now returns by GT extension are such exemplars: they are > > typical instances like $a or 42 one can use as a model or pattern to be copied > > or imitated. > > > > Would'nt that perfectly fit with what you intended with your new feature: the preview > > should help people to just inspect a class, look at the new "e.g." tab and learn from > > premade instances? > > > >> The release is too important and we got distracted from the goal. > > > > No doubt that the release is important and fixing it NOW from the technical side is easy > > as I demonstrated with the changeset. I guess rolling back <gtExample> would take you > > more time than reviewing it. > > > > Before doing any action on your side I would really like to know your opinion about > > <exemplar>. I'm fine when you can not accept it - but please tell me about the reasons. > > > > Bye > > T. > > > > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

March 26, 2015

Re: [Pharo-dev] Some Memory Leak

by stepharo

This is really great! Le 26/3/15 14:24, Andrei Chis a Ã©crit : > Now, with Alain's help, also the memory leak from Rubric is solved. > All fixes will be in the next version, which will hopefully be ready > today. > > Cheers, > Andrei > > On Wed, Mar 25, 2015 at 7:05 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > +1 > > > Le 25/3/15 11:52, Sven Van Caekenberghe a Ã©crit : > > YES! > > My image went from 65Mb to 34Mb (it contains Seaside/Bootstrap > and several resources). > > Thanks a lot, you guys (and everybody else who contributes) rock! > > Let's hope this solves the issue. > > On 25 Mar 2015, at 11:26, Andrei Chis > <chisvasileandrei(a)gmail.com > <mailto:chisvasileandrei@gmail.com>> wrote: > > To load the latest version in an image execute: > > { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. > { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. > { 'ConfigurationOfGTInspectorCore'. 'Moose'. > 'GToolkit' }. > { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. > 'GToolkit' }. > { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. > { 'ConfigurationOfGToolkitCore'. 'Moose'. > 'GToolkit' }. > } do: [ :spec | > Gofer new > smalltalkhubUser: spec second project: > spec third; > package: spec first; > load ]. > ConfigurationOfGToolkitCore loadDevelopment. > > Then run cleanUp: > > Smalltalk cleanUp: true except: #() confirming: false. > > Now only the latest instance of playground/spotter is not > garbaged collected, but that would be fixed very soon. > > > Cheers, > Andrei > > > > > On Wed, Mar 25, 2015 at 11:21 AM, Sven Van Caekenberghe > <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > Please tell us when this gets integrated so that we can > test the effect. > > Or to go faster, please give some instructions (an > executable expression) that we can execute in the latest > image to load the relevant changes. > > We need more eyeballs. > > On 25 Mar 2015, at 09:50, Tudor Girba > <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> > wrote: > > Up to now, we identified two issues that lead to > objects not being garbage collected: > > - GLMHintableActionButtonBrick triggers a singleton > asynctask that was not cleaned after the task was > ready. Now, that problem should be solved in GT. > > - RubFindReplaceService has a Singleton class > variable. At the same time, RubFindReplaceService also > keeps a reference to the textArea which is part of the > morph tree and will prevent the whole UI that includes > it to be garbage collected. We are working on dealing > with this issue. > > There might be other issues. We need to keep looking. > > Cheers, > Doru > > > > On Wed, Mar 25, 2015 at 8:52 AM, stepharo > <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Hi henrik > > your analyses are great. > What do you think about > > GTSpotterStep>>#candidates > > ^ candidates ifNil: [ > candidates := GTSpotterCandidatesList new. > candidates announcer weak subscribe: > GTSpotterCandidateAdded do: [ self candidates > hasOnlyOneItem ifTrue: [ self selectFirst ] ]. > candidates announcer weak subscribe: > GTSpotterAllCandidatesAdded do: [ self selectFirst ]. > candidates announcer weak subscribe: > GTSpotterAllCandidatesRemoved do: [ self selected: nil ]. > candidates ] > > Le 24/3/15 21:38, Henrik Sperre Johansen a Ã©crit : > > A tiny bit of code review while I'm at it... > > GTSpotterResultsBrick >> initialize > super initialize > self band hSpaceFill. > self announcer weak subscribe: > GLMBrickScrollPositionChanged send: > #onScrolled to: self > > This is a tempting, but sneaky anti-pattern, you > should never, ever, ever > have to subscribe to your own announcer: > The reason for calling it an anti-pattern is; if your > code actually depends > on this, it means other sources might invoke changes > in you indirectly > through your announcer, which quickly becomes > debugging hell if you allow > it, and something screws up. (I speak from experience) > > It's much easier to understand when done directly, in > this case that means > extending the super method where announcement is made: > > GTSpotterResultsBrick >> privateScrollPosition:anInteger > super privateScrollPosition:anInteger. > self onScrolled > > Cheers, > Henry > > P.S. Announcements are objects, they are intended to > hold the data > subscribers might be interested in. > Whenever you find yourself writing something like: > someAnnouncer announce: SomeAnnouncement new > ask yourself twice if that may lead to subscribers > accessing state that > would more naturally be part of the announcement > through other channels > (such as keeping extra instvars, etc). > > > > -- > View this message in context: > http://forum.world.st/Some-Memory-Leak-tp4814779p4814912.html > Sent from the Pharo Smalltalk Developers mailing list > archive at Nabble.com. > > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > > > > > > > >

March 26, 2015

Re: [Pharo-dev] PharoLauncher: Great Tool, Confusing Name

by Damien Cassou

Ben Coman <btc(a)openinworld.com> writes: > I'd really like to do away with the "Local" template folder and on the > original remote template indicate that it is cached locally - but I haven't > found the time to experiment. agree. Someone needs to do it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 26, 2015

Re: [Pharo-dev] PharoLauncher: Great Tool, Confusing Name

by Damien Cassou

Ben Coman <btc(a)openinworld.com> writes: > I second this. What is philosophy behind installing PharoLauncher as > "Pharo"? I can't see the gain. To me "Pharo Launcher" is a suitable > descriptive application name. > cheers -ben the PharoLauncher is supposed to disappear and be the default Pharo download (maybe for Pharo 5). As a new user: 1- you download pharo (= the launcher) from pharo.org by clicking the large download button 2- you double-click what you've just downloaded and you are presented with the launcher window 3- you select a template on the right or an image on the left 4- you are done So, there is no more notion of launcher. Try with Eclipse. When you start Eclipse, you are presented with a little window that asks you which workspace you want to use. This is not called the Eclipse Launcher but just Eclipse. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 26, 2015