- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spec terminology: renaming some terms

by Johan Fabry

The problem is that people are confused by the term Model, so they will also be confused by Logic. I want to remove the confusion and make clear that it is a user interface (and that it is composable by default) -> ComposableUI. It could also be ComposableUserInterface but we do not win anything by that name, as UI is a standard acronym + we would have to type more when subclassing it. So I prefer ComposableUI. > On Feb 19, 2015, at 14:37, stepharo <stepharo(a)free.fr> wrote: > > I know :) > So may be Logic because this is the logic of the application. > > Stef > Le 19/2/15 18:16, Sven Van Caekenberghe a Ã©crit : >> Well, it means User Interface ;-) >> >> The thing that got everybody confused is precisely the word Model, if we keep that the confusion will continue. >> >>> On 19 Feb 2015, at 18:11, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi Johan >>> >>> For me UI does not mean anything. >>> So may be ComposableUIModel? >>> Or ComposableUILogic >>> >>> >>> Stef >>> >>> Le 19/2/15 13:22, Johan Fabry a Ã©crit : >>>> Hi all, >>>> >>>> I donât read mails on pharo-dev usually, so sorry if this has been discussed before (and then pointers to the discussion would be appreciated). >>>> >>>> Last week, in Pharo-users I proposed the Spec terminology changes below. Responses were positive. I am willing to volunteer to do that next week so itâs finished before the 28th and itâs included in Pharo 4. And then I will update the documentation as well. But first I want to know if there are any objections from people on this list. >>>> >>>> I propose to rename: >>>> - ComposableModel to ComposableUI >>>> - all the protocols âprotocol-*â to âAPI-*â >>>> >>>> Other renaming-related comments are also welcome. >>>> >>>> ---> Save our in-boxes! http://emailcharter.org <--- >>>> >>>> Johan Fabry - http://pleiad.cl/~jfabry >>>> PLEIAD lab - Computer Science Department (DCC) - University of Chile >>>> >>>> >>>> >>> >> >> > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 19, 2015

Re: [Pharo-dev] Why was #asLegalSelector removed?

by Damien Pollet

I'm usually extremely apprehensive of changing code I don't own, to the point I â sadly â contribute nearly nothing to Pharo. Now, cleaning the platform â and in this case, by cleaning, I really mean hazmat suits, industrial grade acid, and flame throwers â is going to break things. I'm all for a process to help others follow such changes, but if we want a process to work, it has to be even simpler than not having a process. In any case I don't want to have to stress over touching platform code. I think it would make sense to publish a configuration for DeprecationFinder in the configuration browser. Does it work on any Pharo image, or is it written on top of Moose ? About #asComment : since class comments are free text, any string will do and there is no escapement sequences to enforce. Maybe ideally we would have string un/escaper objects responsible for translating between free text and and specific encodings (comments, strings, regexes, URLsâ¦) On 19 February 2015 at 15:05, stephan <stephan(a)stack.nl> wrote: > The way this was handled can be improved. It is sometimes difficult for us > not in Lille > to find out what is going on. > > - a specific issue name helps us notice what changes > - check where code is used. DeprecationFinder works for that > (and should add more repos and team projects). > > And a specific one: the rename from #asSmalltalkComment > to #asComment is problematic. There are 2 kinds of thing > casually known as comments: the comment text in a method, > and the class comment. The method name should reflect that. > > Stephan > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Feb. 19, 2015

Re: [Pharo-dev] Spec terminology: renaming some terms

by stepharo

I know :) So may be Logic because this is the logic of the application. Stef Le 19/2/15 18:16, Sven Van Caekenberghe a Ã©crit : > Well, it means User Interface ;-) > > The thing that got everybody confused is precisely the word Model, if we keep that the confusion will continue. > >> On 19 Feb 2015, at 18:11, stepharo <stepharo(a)free.fr> wrote: >> >> Hi Johan >> >> For me UI does not mean anything. >> So may be ComposableUIModel? >> Or ComposableUILogic >> >> >> Stef >> >> Le 19/2/15 13:22, Johan Fabry a Ã©crit : >>> Hi all, >>> >>> I donât read mails on pharo-dev usually, so sorry if this has been discussed before (and then pointers to the discussion would be appreciated). >>> >>> Last week, in Pharo-users I proposed the Spec terminology changes below. Responses were positive. I am willing to volunteer to do that next week so itâs finished before the 28th and itâs included in Pharo 4. And then I will update the documentation as well. But first I want to know if there are any objections from people on this list. >>> >>> I propose to rename: >>> - ComposableModel to ComposableUI >>> - all the protocols âprotocol-*â to âAPI-*â >>> >>> Other renaming-related comments are also welcome. >>> >>> ---> Save our in-boxes! http://emailcharter.org <--- >>> >>> Johan Fabry - http://pleiad.cl/~jfabry >>> PLEIAD lab - Computer Science Department (DCC) - University of Chile >>> >>> >>> >> > >

Feb. 19, 2015

Re: [Pharo-dev] [FIX (Maybe ; ))]: Issue 14959: MC Hook for Default Credentials

by stepharo

I was thinking that we could use Author to provide a password because this is boring to always have to type it. Stef Le 19/2/15 03:15, Sean P. DeNigris a Ã©crit : > Fix in inbox: > SLICE-Issue-14959-MC-Hook-for-Default-Credentials-SeanDeNigris.1 > > When creating a repo in the MC Browser, it would be great to pre-populate > the user and password fields. > > Thus, we declare a CredentialSource role collaborating with MCHttpRepository > and subclasses. The in-kernel default is a no-op Null object, but users can > install (via MCHttpRepository class>>#credentialSource:) any object that > responds to #defaultUserFor: and #defaultPasswordFor: > > I'd like to apply this to Gofer, too, but I found a big switch statement in > ZnUrl>>#mcRepositoryAsUser:withPassword: and now my head hurts ;) > > Anyway maybe this will spur discussion... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/FIX-Maybe-Issue-14959-MC-Hook-for-Default-Credentials… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Feb. 19, 2015

Re: [Pharo-dev] Spec terminology: renaming some terms

by Sven Van Caekenberghe

Well, it means User Interface ;-) The thing that got everybody confused is precisely the word Model, if we keep that the confusion will continue. > On 19 Feb 2015, at 18:11, stepharo <stepharo(a)free.fr> wrote: > > Hi Johan > > For me UI does not mean anything. > So may be ComposableUIModel? > Or ComposableUILogic > > > Stef > > Le 19/2/15 13:22, Johan Fabry a Ã©crit : >> Hi all, >> >> I donât read mails on pharo-dev usually, so sorry if this has been discussed before (and then pointers to the discussion would be appreciated). >> >> Last week, in Pharo-users I proposed the Spec terminology changes below. Responses were positive. I am willing to volunteer to do that next week so itâs finished before the 28th and itâs included in Pharo 4. And then I will update the documentation as well. But first I want to know if there are any objections from people on this list. >> >> I propose to rename: >> - ComposableModel to ComposableUI >> - all the protocols âprotocol-*â to âAPI-*â >> >> Other renaming-related comments are also welcome. >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD lab - Computer Science Department (DCC) - University of Chile >> >> >> > >

Feb. 19, 2015

Re: [Pharo-dev] Spec terminology: renaming some terms

by stepharo

Hi Johan For me UI does not mean anything. So may be ComposableUIModel? Or ComposableUILogic Stef Le 19/2/15 13:22, Johan Fabry a Ã©crit : > Hi all, > > I donât read mails on pharo-dev usually, so sorry if this has been discussed before (and then pointers to the discussion would be appreciated). > > Last week, in Pharo-users I proposed the Spec terminology changes below. Responses were positive. I am willing to volunteer to do that next week so itâs finished before the 28th and itâs included in Pharo 4. And then I will update the documentation as well. But first I want to know if there are any objections from people on this list. > > I propose to rename: > - ComposableModel to ComposableUI > - all the protocols âprotocol-*â to âAPI-*â > > Other renaming-related comments are also welcome. > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > >

Feb. 19, 2015

Re: [Pharo-dev] Running Pharo on Ubuntu 14.04.1 LTS 64-bit

by stephan

And if you want to have athens graphics, e.g. when you want to use Roassal2, you might need to add cairo apt-get install libcairo2-dev:i386 On Ubuntu 14.10 this currently results in a broken package. I could fix that with sudo apt-get update sudo apt-get autoclean sudo apt-get clean sudo apt-get autoremove

Feb. 19, 2015

Re: [Pharo-dev] Super fast delay

by Ben Coman

On Thu, Feb 19, 2015 at 9:50 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Mon, Feb 16, 2015 at 4:01 PM, Holger Hans Peter Freyther < > holger(a)freyther.de> wrote: > >> On Thu, Oct 30, 2014 at 06:32:48PM -0400, stepharo wrote: >> >> Good Morning Ben, Stef, >> >> > We really need people to have a look at the code of Ben. >> >> I downloaded a Pharo-4 image today and executed: >> > > To clarify. The fix is not yet in Pharo-4. > > >> >> time pharo --nodisplay --headless ./Pharo-40490.image eval "(Delay >> forSeconds: 5) wait" >> a Delay(5000 msecs) >> >> real 0m1.254s >> user 0m1.192s >> sys 0m0.060s >> >> >> So the first delay doesn't appear to wait the five seconds. I >> would like to work on kqueue/epoll and remove polling and it >> looks this involves code with Delay as well. I wonder if you >> could provide an overview of what needs to be done and what is >> done? >> > > The pre-requisite issue 14942 is waiting for review. It really should take > only 10 minutes to review... > 1. In latest Pharo 4, inspect "Delay newCodeEnabled" and observe that it > is "true". > 2. Open the Pharo4Inbox and filter on 14942. > 3. Select newest slice and <Merge>. > 4. Observe the diff shows all "false" parts removed (it doesn't really get > much simpler than this to review). > 5. Click <merge> to finish. > 6. Observe the image continues to run smoothly. > 7. Report your observations on https://pharo.fogbugz.com/default.asp?14942 > > btw, after the cleanup done by Issue 14942, Issue 14966 can delete ten class variables from Delay. When 14942 is integrated, can 14966 be integrated very soon after that. I am basing the change of Delay to microsecond delay off 14966. cheers -ben > > I need to refresh myself on the fix I did back in 2-Dec. Its languished > while some support infrastructure was added to help the system ride-through > the change. > > cheers -ben >

Feb. 19, 2015

Re: [Pharo-dev] NativeBoose-Win32 fix in Pharo4

by Marcus Denker

> On 19 Feb 2015, at 15:13, Richard Wettel <wettel(a)gmail.com> wrote: > > Hi > > Some time ago I found a bug in NativeBoost-Win32, which would not allow me to run CodeCity in Pharo 4 (CodeCity depends on this package, through a dependency onConfigurationOfNBOpenGL, version: #stable): > https://pharo.fogbugz.com/f/cases/14728 <https://pharo.fogbugz.com/f/cases/14728> > > I fixed the bug and the fiix was integrated on 14.01, with the comment "in 40443". > My expectation was that as soon as I would switch to Pharo 4, I would also get this bug fix. > > That is not the case at the moment. I get Name: NativeBoost-Win32-TheIntegrator.54 and the one including my fix is the next one, NativeBoost-Win32-TheIntegrator.56 (in http://smalltalkhub.com/mc/Pharo40/main <http://smalltalkhub.com/mc/Pharo40/main>). > > It seems that something is still missing there. > I would appreciate any help. strangeâ¦ I have put it on fix to include and add is with the next update. Marcus

Feb. 19, 2015

Re: [Pharo-dev] Spec terminology: renaming some terms

by Sean P. DeNigris

Ben Coman wrote > Thanks for this Johan. +1 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-terminology-renaming-some-terms-tp4806486p480651… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 19, 2015