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

Guys, can you explain me, why you hating pools so much? Because you cannot find good use of them, or because you don't know how to properly use them? Or because you don't understand what is it? Pool dictionary is just a namespace, which you can share among different parts of your code (on a per-cl

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

On 31 January 2014 18:03, Andreas Wacknitz wrote: > > Am 31.01.2014 um 14:40 schrieb Johan Fabry : > > > 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. I

[Pharo-dev] [launcher] Windows Installer UAC Virtualization problems

Damien Cassou wrote in "[Pharo-dev] [FEEDBACK] Install Pharo on Windows": Hi, I've just made an executable file for installing Pharo on Windows (in program files, with a shortcut in the Start menu...). Please try it and report problems: https://ci.inria.fr/pharo-contribution/job/PharoLauncher-W

[Pharo-dev] Comparing dates

self assert: Date today = Date today. today := Date today translateTo: 2 hours. self assert: today = Date today Is this right?

Re: [Pharo-dev] back and oldBack in UTF-8 files

I wonder why we need back and oldBack (reallyOldBack ?) in the first place. Condensing sources or changes should just consist in writing source of each method/class comment sequentially (forward), and remember the position of the stream... So this backward thing must be some poorly written part.

[Pharo-dev] lookInGeneralPreferencesFolder

Hi guys, that method is raising an exception when moving the image from one OS to other

Re: [Pharo-dev] back and oldBack in UTF-8 files

Hi Pavel, On 31 Jan 2014, at 20:33, Pavel Krivanek wrote: > Hi, > > I was looking why we cannot do condenseChanges and the reason looks to be > clear: we do not have proper methods to move backwards (messages #back and > #oldBack) in UTF-8 files. The current implementation changes position b

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

On Jan 31, 2014, at 2:19 PM, Pharo4Stef wrote: > I love the changes of Johan. I would love to have a more compact class > definition :) > Now the question by henrik is really puzzling me. But is not working, isn’t it? I mean for the people. I don’t want to be critical here, only to analyse t

[Pharo-dev] back and oldBack in UTF-8 files

Hi, I was looking why we cannot do condenseChanges and the reason looks to be clear: we do not have proper methods to move backwards (messages #back and # oldBack) in UTF-8 files. The current implementation changes position by one byte but in UTF-8 files it can be up to six bytes. And it's worse.

Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo

2014-01-31 Chris Cunningham : > You'll undoubtedly run into this several more times - at least you will when > bringing in older Monticello packages or those created outside of Pharo. Not > all, but some. Some, which will be very important probably. Like Seaside, Glorp, etc. Regards!

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

Websense categorizes "association.pharo.org" as "sex". On Fri, Jan 31, 2014 at 10:56 AM, Pharo4Stef wrote: > Another week of improvements > > http://association.pharo.org/web/weekly/Commits-Jan-3 > > stef >

[Pharo-dev] Yet another week of commits

Another week of improvements http://association.pharo.org/web/weekly/Commits-Jan-3 stef

Re: [Pharo-dev] Please keep your cool new stuff for Pharo 4

On 31 Jan 2014, at 13:29, b...@openinworld.com wrote: > For instance, I've recently submitted a slice for [1] that adds two new > methods and a trivial refactoring of one other to Spec's ComposableModel (so > I can't imagine it would break anything), but in support of discipline on the > featur

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

On Jan 31, 2014, at 2:03 PM, Andreas Wacknitz wrote: > > Am 31.01.2014 um 14:40 schrieb Johan Fabry : > >> 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 T

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

Hi, Am 31.01.2014 um 08:36 schrieb Jordi Delgado : > 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 i

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

I would like to get to the bottom of this, to be doubly sure there is no remaining problem. Can you send me privately the steps to reproduce so I can have a go at it using the unfixed version? On Jan 31, 2014, at 2:04 PM, Esteban Lorenzano wrote: > No, because my pools were not there and my t

Re: [Pharo-dev] Please keep your cool new stuff for Pharo 4

On 31 janv. 2014, at 17:40, Marcus Denker wrote: > > On 31 Jan 2014, at 17:31, b...@openinworld.com wrote: > >> Esteban Lorenzano wrote: >>> So… instead following my advice, you people continue submitting and asking >>> for integration things that are API changes. As a result, instead gaining

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

Chris Cunningham wrote > maybe a specific browser to include... A real UI instead of editing a string in a workspace would make these problems go away. Show a little form there, with a button or menu to show/add pool dictionaries/Traits/whatever - Cheers, Sean -- View this message in contex

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

No, because my pools were not there and my tests were failing. But no matters, it works now :) > On 31 Jan 2014, at 17:45, Johan Fabry wrote: > > > What probably happened is that Monticello loading with pooldictionaries was > still working, but Nautilus was not showing them. This is the only

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

Am 31.01.2014 um 14:40 schrieb Johan Fabry : > 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 > ve

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

What probably happened is that Monticello loading with pooldictionaries was still working, but Nautilus was not showing them. This is the only thing that changed, and the fix addresses the showing part. So you should not worry. On Jan 31, 2014, at 1:26 PM, Esteban Lorenzano wrote: > I don’t k

Re: [Pharo-dev] Please keep your cool new stuff for Pharo 4

On 31 Jan 2014, at 17:31, b...@openinworld.com wrote: > Esteban Lorenzano wrote: >> So… instead following my advice, you people continue submitting and asking >> for integration things that are API changes. As a result, instead gaining >> stability we are loosing it… >> can you guys please be

[Pharo-dev] [pharo-project/pharo-core] 9244dd: 30733

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9244ddb91f1dfdf3d1d672636b3821c9e906e308 https://github.com/pharo-project/pharo-core/commit/9244ddb91f1dfdf3d1d672636b3821c9e906e308 Author: Jenkins Build Server Date: 2014-01-31 (Fri, 31 Jan 2014

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30733 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Please keep your cool new stuff for Pharo 4

Esteban Lorenzano wrote: So… instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing it… can you guys please be so kind and stop doing what you shouldn’t? I will ask it again: *no

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

I don’t know what happened. All that I know is that it was not working and now with the last fix it is, so I’m happy for now. worried? yes. But not too much :) On 31 Jan 2014, at 14:59, Henrik Johansen wrote: > > On 30 Jan 2014, at 6:14 , Esteban Lorenzano wrote: > >> So… that. >> >> Is s

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

Torsten I love the changes of Johan. I would love to have a more compact class definition :) Now the question by henrik is really puzzling me. Stef > Hi Johan, > > Still I really do not understand what particular problem that is solved by > changing > the template from > > MySuperclass sub

Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo

On Fri, Jan 31, 2014 at 3:57 AM, Torsten Bergmann wrote: > Now that Pharo uses real packages beside categories I see some > lowercase "ghost" packages in Monticello Browser list after loading > Seaside. > > To reproduce just load Seaside using config browser and check in > Monticello browser. > >

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

On Thu, Jan 30, 2014 at 11:42 PM, Torsten Bergmann wrote: > Please make it a setting - so one can see the creation message with > poolDictionaries in Nautilus > as before in the browser and is able to fill out the template. > > When using NB one requires them. > > Well, since it seems that the di

Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo

On 31 Jan 2014, at 11:57, Torsten Bergmann wrote: > Now that Pharo uses real packages beside categories I see some > lowercase "ghost" packages in Monticello Browser list after loading Seaside. > > To reproduce just load Seaside using config browser and check in > Monticello browser. > > >

Re: [Pharo-dev] xpath?

2014-01-30 Tudor Girba : > Hi, > > Does anyone know what is the currently functional XPath library? > > I just tested XPath from PharoExtras, but it does not work with the latest > XMLParser. > > The XPath library is not complete, although supports querying attributes with @. Try for example: | d

Re: [Pharo-dev] Nautilus often loses context

There is also a show stopper bug: when adding a protocol to a new class. It a show stopper I faced with my students. I did a quick fix and uploaded it. https://pharo.fogbugz.com/f/cases/12473/Wrong-behavior-of-ListDialogWindow-when-adding-new-protocol On 31 janv. 2014, at 11:42, Johan Brichau wrot

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

On 30 Jan 2014, at 6:14 , Esteban Lorenzano wrote: > So… that. > > Is super cool to remove poolDictionaries from the default class template. > What is not cool *at all* is the fact that now my low level projects, who > uses them intensively, does not work anymore. > The reason? the classes

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 b

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

Hi Johan, Still I really do not understand what particular problem that is solved by changing the template from MySuperclass subclass: #Foo instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Bar-Core' to MySuperclass subclass: #Foo

[Pharo-dev] [pharo-project/pharo-core] f9646c: 30732

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: f9646c28c8894ed09c36f4847da5fae306d6f147 https://github.com/pharo-project/pharo-core/commit/f9646c28c8894ed09c36f4847da5fae306d6f147 Author: Jenkins Build Server Date: 2014-01-31 (Fri, 31 Jan 2014

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30732 Home: https://github.com/pharo-project/pharo-core

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

just to be clear: I’m not agains this change, I think is a good one. I just was (and I still am) pissed with the fact that we do not fully understand the signification of “frozen” version, and sometimes I feel like nobody notices the HUGE effort that means to close a version in a reliable and s

Re: [Pharo-dev] xpath?

probably… honestly when I did it I had a very concrete problem at hands and I just implemented what I needed to solve it :S On 31 Jan 2014, at 11:44, Tudor Girba wrote: > Thanks. I actually looked for it, but I could not find it. I now checked it > and it works fine. > > However, it provides

[Pharo-dev] Seaside extensions and lowercase package names in Pharo

Now that Pharo uses real packages beside categories I see some lowercase "ghost" packages in Monticello Browser list after loading Seaside. To reproduce just load Seaside using config browser and check in Monticello browser. I guess this is coming from methods in lowercase extension categories

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

I don't see why there needs to be a configuration for that. You can still add them, just put pooldictionaries: 'foo bar' on the next-to-last line as it was before, et voilá … you have them in your class. This is the same behavior as traits and the uses: message. There is not configuration opt

Re: [Pharo-dev] [ANN] GitFileTree with no git command line at all

It uses OS Process. > How does it interact with git? Does it shell out, call a library or have a > full git implementation in Smalltalk? > > Cheers > Philippe > > >

Re: [Pharo-dev] [ANN] GitFileTree with no git command line at all

It rely on OSProcess for Mac and Linux to call the appropriate git commands. Thierry De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Philippe Marschall [philippe.marsch...@netcetera.ch] Date d'envoi : vendredi 31 janvier 2014 12:15 À : pha

Re: [Pharo-dev] FOSDEM

Anyone? Stephan

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

Torsten wrote >Please make it a setting - so one can see the creation message with >poolDictionaries in Nautilus >as before in the browser and is able to fill out the template. Please don’t. Settings as a replacement for design are evil Stephan

Re: [Pharo-dev] [ANN] GitFileTree with no git command line at all

On 30.01.14 11:12, Goubier Thierry wrote: Hi all, I'm announcing a GitFileTree for Pharo3.0 version with full support for working from github (and probably all other git remote repositories such as bitbucket) without touching any git command line, for Linux and Mac at least (and Windows as soon

Re: [Pharo-dev] xpath?

Thanks. I actually looked for it, but I could not find it. I now checked it and it works fine. However, it provides a similar but not quite the same functionality as XPath. For example, I did not find support for matching against attributes with @. Doru On Thu, Jan 30, 2014 at 8:43 AM, Torsten

Re: [Pharo-dev] Nautilus often loses context

Indeed, that is exactly the case. Thank you. Please integrate! ;-) Johan On 30 Jan 2014, at 22:56, Nicolai Hess wrote: > 2014-01-30 Sabine Knöfel : > me too, but it is only sometimes I can not tell, how to reproduce it. > > > On Thu, Jan 30, 2014 at 8:31 PM, Johan Brichau wrote: > Hi all, >

Re: [Pharo-dev] xpath?

Thanks. I somehow did not see PetitXPath in the PetitParser repo and that is why I went for the Lukas' repo. I now checked, and I confirm that the one from the Moose/PetitParser works fine. Cheers, Doru On Thu, Jan 30, 2014 at 9:53 AM, Esteban Lorenzano wrote: > I used PetitXPath everyday... i

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

Yep you're right, it looks a lot to what is reported in 12316 and 12469 . I will keep an eye on them. Thanks. Bests, Jordi > 2014-01-31 Jordi Delgado : > >> Hi, >> >> I realized that sometimes, when creating n

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

2014-01-31 Clément Bera : > I had the same problem. I had to reload my project from a fresh image to > solve it. Very hard to reproduce. > > In addition, after editing a few method you cannot anymore edit the class > comment (you need to open another Nautilus to do it). > > That was me, sorry for

Re: [Pharo-dev] Call for action: Help to improve the class comment quality of Pharo 3.0

Marcus wrote: > > Maybe we should add a test to ReleaseTest class that forces us to do it and > > that stays red until > > the situation improved. > > I advice against this. We tried it in the past and it does not work. Having a > green build that goes > non-green means action, having a constan

Re: [Pharo-dev] [Pharo3] Reviewers of fixes needed

Ok boss, on my way. On Fri, Jan 31, 2014 at 10:30 AM, Marcus Denker wrote: > > On 31 Jan 2014, at 10:26, p...@highoctane.be wrote: > > https://pharo.fogbugz.com/default.asp?11674 looks ok for me and I hit the > "resolve" button yesterday. > > Do you need anything else from my side? > > > the

Re: [Pharo-dev] Call for action: Help to improve the class comment quality of Pharo 3.0

> > > > Maybe we should add a test to ReleaseTest class that forces us to do it and > that stays red until > the situation improved. I advice against this. We tried it in the past and it does not work. Having a green build that goes non-green means action, having a constant yellow build mea

Re: [Pharo-dev] [Pharo3] Reviewers of fixes needed

On 31 Jan 2014, at 10:26, p...@highoctane.be wrote: > https://pharo.fogbugz.com/default.asp?11674 looks ok for me and I hit the > "resolve" button yesterday. > > Do you need anything else from my side? > the resolve button just move the state to one of the resolved states. If the issue was a

Re: [Pharo-dev] [Pharo3] Reviewers of fixes needed

https://pharo.fogbugz.com/default.asp?11674 looks ok for me and I hit the "resolve" button yesterday. Do you need anything else from my side? Phil On Fri, Jan 31, 2014 at 9:06 AM, Marcus Denker wrote: > Hi, > > As I have integrated some wrong things recently, I would like to only > integrat

[Pharo-dev] Call for action: Help to improve the class comment quality of Pharo 3.0

There are many undocumented classes left in the system Object allSubclasses select: [:each | each comment includesSubstring: 'x' ] Exactly 2731 by now in Pharo3.0 Latest update: #30731. Around 400 classes are test classes with a pair class that they test as a test unit and

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

2014-01-31 Jordi Delgado : > 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

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

I had the same problem. I had to reload my project from a fresh image to solve it. Very hard to reproduce. In addition, after editing a few method you cannot anymore edit the class comment (you need to open another Nautilus to do it). 2014/1/31 Jordi Delgado > Hi, > > I realized that sometimes

[Pharo-dev] [Pharo3] Reviewers of fixes needed

Hi, As I have integrated some wrong things recently, I would like to only integrate fixes where at least two other people (then me or the author) checked that this is a) correct b) not introducing more bugs and c) really for Pharo3 (and not Pharo4). https://pharo.fogbugz.com/f/filters/45