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

Re: [Pharo-dev] About a better filedialog

by ducasse

Alex Have a look at the one I propose and play with it. Let me know what you think. Stef > On 18 Mar 2019, at 21:20, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: Re: [Pharo-dev] About a better filedialog > Date: 18 March 2019 at 21:20:35 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > I do not have time to personally work on this. But yes, having a better file dialog would be fantastic > > Alexandre > >> On Mar 18, 2019, at 4:31 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi guys >> >> I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. >> what do you think? >> >> https://github.com/Ducasse/file-dialog >> >> I would also like that the filedialog remembers the last list of visited directory. (I will see if I can add this). >> When Spec2 is out I would like to port it to Spec2. >> >> Does anybody want to help? Because it would be super nice and Iâm full with cleaning textEditor and pluggableTextMorph. >> >> Stef >> >> >> > > > >

March 18, 2019

Re: [Pharo-dev] About a better filedialog

by Alexandre Bergel

I do not have time to personally work on this. But yes, having a better file dialog would be fantastic Alexandre > On Mar 18, 2019, at 4:31 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi guys > > I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. > what do you think? > > https://github.com/Ducasse/file-dialog > > I would also like that the filedialog remembers the last list of visited directory. (I will see if I can add this). > When Spec2 is out I would like to port it to Spec2. > > Does anybody want to help? Because it would be super nice and Iâm full with cleaning textEditor and pluggableTextMorph. > > Stef > > >

March 18, 2019

Re: [Pharo-dev] About a better filedialog

by ducasse

What is cool is that you can add bookmarks :) I did it to list the place where I store all my iceberg repo :) > On 18 Mar 2019, at 20:31, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi guys > > I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. > what do you think? > > https://github.com/Ducasse/file-dialog > > I would also like that the filedialog remembers the last list of visited directory. (I will see if I can add this). > When Spec2 is out I would like to port it to Spec2. > > Does anybody want to help? Because it would be super nice and Iâm full with cleaning textEditor and pluggableTextMorph. > > Stef > > >

March 18, 2019

About a better filedialog

by ducasse

Hi guys I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. what do you think? https://github.com/Ducasse/file-dialog I would also like that the filedialog remembers the last list of visited directory. (I will see if I can add this). When Spec2 is out I would like to port it to Spec2. Does anybody want to help? Because it would be super nice and Iâm full with cleaning textEditor and pluggableTextMorph. Stef

March 18, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 11 March 2019

by ducasse

> On 18 Mar 2019, at 18:00, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi Sean, > > This is how the menus are done ultimately, not âthe wayâ of doing it. > In general, you will do menus using something like Commander: you define commands, then you dynamically build the menus based on a context given (this is how Pharo itself will doit). > - Or you build your own command library and build menus your way (see this experiment: https://github.com/estebanlm/Lieutenant/tree/try-superlight-version and its clases LtMenuBarBuilder, LtContextMenuBuilder). > - Or you collect the items (MenuItemPresenter) from a pragma and you sort them some way. > > You are free to do as you want, but at the end, it has to have the structure described in the log :) I think that Spec should propose a nice default way. And as Sean mentioned it, Iâm not unable to nicely extend Epicea menu so Iâm hacking inside and this is not good. > > One important things I didnât remarked, is that in Spec, all menu accessors are âvaluablesâ. Means that for example ListPresenter>>contextMenu: will receive anything that understands value and it will be executed on demand: > > self newList > contextMenu: [ self collectMyContextMenu ]; > etcâ¦. > > Will work as expected. > (I hope this helps to understand the design better). > > Cheers! > Esteban > > >> On 18 Mar 2019, at 17:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> EstebanLM wrote >>> addGroup: [ :group | >>> group >>> addItem: [ :item | item name: 'Something 1'; action: [ >>> "doSomething"] ]; >> >> How would one extend a menu with this approach e.g. add an item to the group >> from elsewhere (outside the block)? Is it even possible? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> > >

March 18, 2019

Re: [Pharo-dev] [Issue Trackker][Help Needed]: Move issues from Fogbugz to GitHub

by Tim Mackinnon

Marcus - do we just manually copy over the title and description (and any relevant comments) - or is there some tool to do this with? Tim > On 18 Mar 2019, at 07:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We should all look at the old issues: > > https://pharo.fogbugz.com/f/filters/57/All-newest-first <https://pharo.fogbugz.com/f/filters/57/All-newest-first> > > and move them to the new one: > > https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> > > instead of moving them automatically, we should take the chance to > clean up. > > Please check, first for the issues that *you* added: > > -> is it still relevant? > ->if yes: add a new issue on GitHub > ->close this issue, there is now an explicit âmoved to GitHubâ state. > > > Marcus

March 18, 2019

Is String withUnixLineEnding mutation behavior a bug?

by Ronie Salgado

Hi, I just noticed that String >> withUnixLineEndings modifies the the original string, at least when the string only has cr, and not crlf. For example, try the following (in Pharo 7) in a Playground: original :='asa' , String cr , 'asa'. newString := original withUnixLineEndings. original at: 4. Best regards, Ronie

March 18, 2019

[Pharo 8.0] Build #150: 2877-whichSelectorsAccess-and-slots

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #150 was: SUCCESS. The Pull Request #2878 was integrated: "2877-whichSelectorsAccess-and-slots" Pull request url: https://github.com/pharo-project/pharo/pull/2878 Issue Url: https://pharo.fogbugz.com/f/cases/2877 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 18, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 11 March 2019

by Esteban Lorenzano

Hi Sean, This is how the menus are done ultimately, not âthe wayâ of doing it. In general, you will do menus using something like Commander: you define commands, then you dynamically build the menus based on a context given (this is how Pharo itself will doit). - Or you build your own command library and build menus your way (see this experiment: https://github.com/estebanlm/Lieutenant/tree/try-superlight-version and its clases LtMenuBarBuilder, LtContextMenuBuilder). - Or you collect the items (MenuItemPresenter) from a pragma and you sort them some way. You are free to do as you want, but at the end, it has to have the structure described in the log :) One important things I didnât remarked, is that in Spec, all menu accessors are âvaluablesâ. Means that for example ListPresenter>>contextMenu: will receive anything that understands value and it will be executed on demand: self newList contextMenu: [ self collectMyContextMenu ]; etcâ¦. Will work as expected. (I hope this helps to understand the design better). Cheers! Esteban > On 18 Mar 2019, at 17:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> addGroup: [ :group | >> group >> addItem: [ :item | item name: 'Something 1'; action: [ >> "doSomething"] ]; > > How would one extend a menu with this approach e.g. add an item to the group > from elsewhere (outside the block)? Is it even possible? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 18, 2019

[Pharo 8.0] Build #149: 2847-Implement-method-to-remove-class-side-slot

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #149 was: FAILURE. The Pull Request #2875 was integrated: "2847-Implement-method-to-remove-class-side-slot" Pull request url: https://github.com/pharo-project/pharo/pull/2875 Issue Url: https://pharo.fogbugz.com/f/cases/2847 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 18, 2019