- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

by Levente Uzonyi

On Fri, 25 Oct 2013, StÃ©phane Ducasse wrote: >> <rant> >> It's part of the Pharo manifesto: "Not backward compatible" >> </rant> > > Levente I hope that writing this little pun created some jubilation to you. Or I do not understand your point. > But this is ok for me. If pun on Pharo helps you then this is ok and they make me smile, and I'm serious > If I can laugh from them this is that I should be quite strong no? I'm sorry if you guys didn't get my message, but it was as serious as it could be. I understand that you don't what to be backwards compatible, because it makes it easier to change stuff. As I see, people need various levels of backwards compatibility. Currently the package maintainers are the most affected, who would like to provide the same codebase for various versions of Pharo, and/or other Smalltalk dialects. As time passes, and the number of users increases, you'll have to give in, and provide it some way. > > We are all committed to build a robust and clean system that people can use to > create their own wealth and feed their family. We are > making HUGE progress. I mean REALLY HUGE and the space it opens is LARGE. I'm not following the developement of Pharo closely anymore, mainly because it's not transparent enough for my taste. I see that you're making big changes, but I still haven't seen the breakthrough: I don't see the advantage of using Pharo over another open source Smalltalk dialect, from business point of view. Levente > It is not easy but people like marcus, sven, esteban, igor, camillo and many many others > are dedicated to that goal. > All the rest does not matter :) > > I'm just sad that other smart people do not understand that we want to create a future to everybody not just > a bunch of fun programmers else we would only focus on what is fun and exciting for us. Writing a new text editor is not what really makes igor having real fun but he does it because this is needed for y-our future. > Same for esteban, removing Package info or improving our VM is not the most exciting topics but he does it > and I thank them for that. > > Stef > > >

Oct. 25, 2013

Re: [Pharo-dev] About BitBlt current -> BitBlt (Fuel)

by Max Leske

On it! On 25.10.2013, at 16:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I just pushed a change cleaning some strange usage. > BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). > Apparently in Squeak they removed it too. > > Now it touches Fuel so Fuel guys can you merge on your side too? > > https://pharo.fogbugz.com/f/cases/12009/BitBlt-current-BitBlt > > Stef

Oct. 25, 2013

Re: [Pharo-dev] Pharo30Inbox commit rights

by Marcus Denker

I added you as a contributor there On 25 Oct 2013 at 16:11:09, Yuriy Tymchuk (yuriy.tymchuk(a)me.com) wrote: > >Hi guys, > >can you give me http://smalltalkhub.com/#!/~YuriyTymchuk rights to commit to Pharo30Inbox? > >Cheers! >Uko >

Oct. 25, 2013

About BitBlt current -> BitBlt (Fuel)

by StÃ©phane Ducasse

Hi I just pushed a change cleaning some strange usage. BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). Apparently in Squeak they removed it too. Now it touches Fuel so Fuel guys can you merge on your side too? https://pharo.fogbugz.com/f/cases/12009/BitBlt-current-BitBlt Stef

Oct. 25, 2013

Re: [Pharo-dev] DeepCopier>>isItTimeToCheckVariables

by Martin Dias

xD yes, DeepCopier, our old friend! mmmm but it's not about replacing by Fuel or something like that. It was just a random pick for "fix a triviality a day", what Marcus proposed some weeks ago. On Fri, Oct 25, 2013 at 3:56 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Martin watching the DeepCopier??? > mmmm I am afraid to ask why ;) > > > On Fri, Oct 25, 2013 at 6:10 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Hi, >> >> This method in DeepCopier has no senders (in Pharo 3) and it's the only >> who references the class variable NextVariableCheckTime. >> >> The time stamp says 1999... Unused code to remove? >> >> >> isItTimeToCheckVariables >> >> | now isIt | >> NextVariableCheckTime ifNil: [ >> NextVariableCheckTime := Time totalSeconds. >> ^ true]. >> now := Time totalSeconds. >> isIt := NextVariableCheckTime < now. >> isIt ifTrue: ["update time for next check" >> NextVariableCheckTime := now + self intervalForChecks]. >> ^isIt >> >> >> Cheers, >> MartÃn >> > > > > -- > Mariano > http://marianopeck.wordpress.com >

Oct. 25, 2013

about Morphic-Core

by StÃ©phane Ducasse

It looks cool :) Now I was wondering why Canvas and friends are part of it and not into Graphics Stef

Oct. 25, 2013

Re: [Pharo-dev] ensureCreateDirectory?

by StÃ©phane Ducasse

+1 > The problem with #ensure style selectors is that they are confusing because they both test something and maybe do something to create a certain condition. The only way to take away the confusion is to make a very long selector. That is why comments are also important. > > Like Stef said, this was already debated for quite some time. The current choice is maybe not perfect, there is nothing stopping anyone from suggesting a better alternative. Good luck with getting a consensus. > > On 25 Oct 2013, at 15:28, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Stef, >> >> I really donât want to stretch this into an argue â¦. but I have problems understanding that. There are refactorings of method selectors because it is said it is important that includesSubString: is written as includesSubstring: and there are other examples. Now we have a selector that people find confusing and that is not important? I donât understand it and the only difference I can see by now is the way you or your team is involved in the action. So the only thing I would understand is sensitivities meaning you are sick of complaints regarding your work. Otherwise I donât understand that. >> >> Norbert >> >> Am 25.10.2013 um 15:04 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> can we focus on real problems? >>> The method has a comment. >>> >>> Stef >>> >>> On Oct 25, 2013, at 10:39 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> >>>> Am 25.10.2013 um 10:11 schrieb Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>> >>>>> So action=create object=directory >>>>> you want to be sure that you create a directory? >>>>> What if it already exists? >>>>> Since you want to be sure to create, will you erase and re-create? >>>>> You see the kind of misunderstanding this could create... >>>>> IOW, self ensureCreateMisunderstanding >>>>> >>>> +1 I didnât like it in the first place. It is just confusing. And probably an example how hard it can be if two or more non-native speaker try to find something that makes sense. >>>> >>>> Norbert >>>>> >>>>> 2013/10/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> Consistency >>>>> ensureActionObject >>>>> >>>>> ensureCreateDirectory >>>>> ensureCreateFile >>>>> >>>>> We discuss a lot with camillo when we did it and I think that this is good right now. >>>>> >>>>>> Out of curiosity, what was the motivation behind Issue 10924: Simplifying >>>>>> ensure* and create protocol? >>>>>> >>>>>> For me #ensureCreateDirectory is less intention revealing than >>>>>> #ensureDirectory because the "ensure" means "create only if necessary", not >>>>>> "definitely create" a directory. What am I missing? Thanks. >>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> Cheers, >>>>>> Sean >>>>>> -- >>>>>> View this message in context: http://forum.world.st/ensureCreateDirectory-tp4716925.html >>>>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>>>>> >>>>> >>>>> >>>>> >>>> >>> >> > >

Oct. 25, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

by StÃ©phane Ducasse

Indeed I'm all in favor to have ConfigurationOf in the image because they are metaData of the packages and projects!!! I do not understand why UI concerns show up into structure of the system. I do not see why having a long list is a problem: there is a search behavior there is a smart group So it would be good not to mix systematically this issue. I'm quite sure that we can open Nautilus on an empty RBBrowserEnvironment and it will work so? Let us move on. I spent time rebuilding from scratch some configurations and I will continue because I want to create a Pharo image from a set of projects and I must have configuration for doing so. Stef > I agree with this. In particular, the configuration classes offer extra information that can be used by smart browsers. We need them. > > Cheers, > Doru > > > On Fri, Oct 25, 2013 at 3:18 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Why do we need to remove configurations of projects loaded into the image? > I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. > > Le 25 oct. 2013 Ã 14:00, GitHub a Ã©crit : > > 12005 unload BaselineOfFileTree, BaselineOfMetacello > > https://pharo.fogbugz.com/f/cases/12005 > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 25, 2013

Pharo30Inbox commit rights

by Yuriy Tymchuk

Hi guys, can you give me http://smalltalkhub.com/#!/~YuriyTymchuk rights to commit to Pharo30Inbox? Cheers! Uko

Oct. 25, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 25, 2013