October 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] New release of iceberg

by Tudor Girba

> On Oct 13, 2016, at 8:28 PM, stepharo <stepharo(a)free.fr> wrote: > > > > Le 13/10/16 Ã 19:02, Esteban Lorenzano a Ã©crit : >> in principle, Iceberg is meant to work on Pharo6+ >> No idea about backward compatibility (it shouldnât be so hard eitherâ¦) > > No ressources for that. > First iceberg should work for Pharo 60. > Everything else is a bonus. Exactly. Cheers, Doru >> Esteban >> >>> On 13 Oct 2016, at 19:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>> Hi Nicolas, >>> >>> After installing it in Pharo 5.0 (#50761, Win 7) and clicking World Menu -> Tools -> Iceberg >>> I got the Exception in the screenshot attached. >>> >>> >>> 2016-10-13 9:25 GMT-03:00 Nicolas Passerini <npasserini(a)gmail.com>: >>> Hi, we are releasing a new version of Iceberg, with several new features and bugfixes. I would't yet say that is 100% production ready, but it is close, so I want to invite you to test it and provide feedback. >>> >>> You can install it by doing: >>> >>> Metacello new >>> baseline: 'Iceberg'; >>> repository: 'github://npasserini/iceberg'; >>> load. >>> >>> More installation instructions and documentation can be found at https://github.com/npasserini/iceberg. >>> >>> Some of the new features in this version are: >>> - Allow to commit several packages together in the same commit. >>> - Show diffs for incoming and outgoing commits (i.e. before push/pull you can browse the difference between the remote and the local versions). >>> - New History view allows to see any commit in any branch and compare it to the current loaded version. >>> - Better support for interacting code loaded outside Iceberg (smaltalkhub, filetree, gitfiletree, etc). >>> - From the diff view, revert changes or browse them (i.e. open a Nautilus on the changed class/method). >>> - Automatically update presentations on code / repository changes. >>> - Integration with Metacello, i.e. after installing Iceberg you do something like >>> >>> Metacello new >>> >>> >>> baseline: 'TaskIt' >>> ; >>> >>> repository: 'github://sbragagnolo/taskit' >>> ; >>> load. >>> >>> >>> (By default) it will be loaded using iceberg (there is a setting to avoid it if you prefer traditional behavior. >>> >>> - Improved handling of git errors. >>> - Improved performance for several operations. >>> - Improved documentation. >>> - ... and several bug fixes and other minor improvements (please look at https://github.com/npasserini/iceberg/milestone/7?closed=1 for more details). >>> >>> >>> Please do not hesitate to contact me if you have any doubts. >>> >>> <IceberError.jpg> >> > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

Oct. 13, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by Tudor Girba

Hi Nicolas, Great work! I will test it again. I kindly ask everyone else to follow the call and test this release. Ideally, create a repository on GitHub and play with it. It is important to get this piece as stable as possible to make Git part of the default Pharo experience. Cheers, Doru > On Oct 13, 2016, at 2:25 PM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > > Hi, we are releasing a new version of Iceberg, with several new features and bugfixes. I would't yet say that is 100% production ready, but it is close, so I want to invite you to test it and provide feedback. > > You can install it by doing: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg'; > load. > > More installation instructions and documentation can be found at https://github.com/npasserini/iceberg. > > Some of the new features in this version are: > - Allow to commit several packages together in the same commit. > - Show diffs for incoming and outgoing commits (i.e. before push/pull you can browse the difference between the remote and the local versions). > - New History view allows to see any commit in any branch and compare it to the current loaded version. > - Better support for interacting code loaded outside Iceberg (smaltalkhub, filetree, gitfiletree, etc). > - From the diff view, revert changes or browse them (i.e. open a Nautilus on the changed class/method). > - Automatically update presentations on code / repository changes. > - Integration with Metacello, i.e. after installing Iceberg you do something like > > Metacello new > > > baseline: 'TaskIt' > ; > > repository: 'github://sbragagnolo/taskit' > ; > load. > > > (By default) it will be loaded using iceberg (there is a setting to avoid it if you prefer traditional behavior. > > - Improved handling of git errors. > - Improved performance for several operations. > - Improved documentation. > - ... and several bug fixes and other minor improvements (please look at https://github.com/npasserini/iceberg/milestone/7?closed=1 for more details). > > > Please do not hesitate to contact me if you have any doubts. -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

Oct. 13, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by stepharo

Le 13/10/16 Ã 19:02, Esteban Lorenzano a Ã©crit : > in principle, Iceberg is meant to work on Pharo6+ > No idea about backward compatibility (it shouldnât be so hard eitherâ¦) No ressources for that. First iceberg should work for Pharo 60. Everything else is a bonus. > > Esteban > >> On 13 Oct 2016, at 19:00, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >> >> Hi Nicolas, >> >> After installing it in Pharo 5.0 (#50761, Win 7) and clicking World >> Menu -> Tools -> Iceberg >> I got the Exception in the screenshot attached. >> >> >> 2016-10-13 9:25 GMT-03:00 Nicolas Passerini <npasserini(a)gmail.com >> <mailto:npasserini@gmail.com>>: >> >> Hi, we are releasing a new version of Iceberg, with several new >> features and bugfixes. I would't yet say that is 100% production >> ready, but it is close, so I want to invite you to test it and >> provide feedback. >> >> You can install it by doing: >> >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://npasserini/iceberg'; >> load. >> >> More installation instructions and documentation can be found at >> https://github.com/npasserini/iceberg >> <https://github.com/npasserini/iceberg>. >> >> Some of the new features in this version are: >> - Allow to commit several packages together in the same commit. >> - Show diffs for incoming and outgoing commits (i.e. before >> push/pull you can browse the difference between the remote and >> the local versions). >> - New History view allows to see any commit in any branch and >> compare it to the current loaded version. >> - Better support for interacting code loaded outside Iceberg >> (smaltalkhub, filetree, gitfiletree, etc). >> - From the diff view, revert changes or browse them (i.e. open a >> Nautilus on the changed class/method). >> - Automatically update presentations on code / repository changes. >> - Integration with Metacello, i.e. after installing Iceberg you >> do something like >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit'; >> load. >> >> >> (By default) it will be loaded using iceberg (there is a setting >> to avoid it if you prefer traditional behavior. >> >> - Improved handling of git errors. >> - Improved performance for several operations. >> - Improved documentation. >> - ... and several bug fixes and other minor improvements (please >> look at >> https://github.com/npasserini/iceberg/milestone/7?closed=1 >> <https://github.com/npasserini/iceberg/milestone/7?closed=1> for >> more details). >> >> >> Please do not hesitate to contact me if you have any doubts. >> >> >> <IceberError.jpg> >

Oct. 13, 2016

Re: [Pharo-dev] About icon: and iconNamed:

by stepharo

Denis You can have a look the changes I did. There is more work to be done but I started. https://pharo.fogbugz.com/f/cases/19201/iconNamed-part-4 What I see is that a command hierarchy is clearly missing because SmartSuggestion, Glamour reimplement the same. Stef Le 13/10/16 Ã 17:30, Denis Kudriashov a Ã©crit : > > 2016-10-13 17:19 GMT+02:00 Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>>: > > Is most of that expense come from passing the same Form over a > link multiple times? I vaguely wonder if content-addressable > caching would help there. > > > You see: current state requires such kind of tricks. But if users > always work with icon names it will not the case completely. > > But anyway, wouldn't a remote browser work at a higher level that > being a remote UI? and the user want to use their local theme > rather than that from the remote image? > > > I want to do it like this. But now classes define concrete form which > should be used in UI. I would call it "no late binding for icons".

Oct. 13, 2016

Re: [Pharo-dev] Path >> fullName should not be the same as printString

by Damien Pollet

Yes, I knew about the per-drive current directoryâ¦ Could you give an example what the file:// URLs look like when they contain a drive letter? For context, my goal looking at this was to make Path instances able to output a string representation of themselves that is useable independently of a FileSystem. A good example would be inside a configuration file committed in git, so that has to work whatever the system the working copy resides on, but that we can assume will contain nothing too system-specific. The URL path could be a nice example too. On 13 October 2016 at 18:15, Ben Coman <btc(a)openinworld.com> wrote: > Its awkward to deal with. Some notes here... > https://pharo.fogbugz.com/default.asp?13094#154946 > > > On Fri, Oct 14, 2016 at 12:05 AM, Damien Pollet <damien.pollet(a)gmail.com> > wrote: > >> I explored a bit more and I'm stumped. Fixing it for Unix is easy, but it >> breaks Windows paths, because those use their first element to store the >> drive name (c: d: etc) which shouldn't be preceded by a /. >> >> I'm starting to think the Absolute/Relative dichotomy is either wrong or >> incomplete and we need windows-specific subclasses. Doesn't it feel strange >> that we can pass strings with different syntax and assumptions to Path >> class >> from: and get instances from the same classes? >> >> On 8 October 2016 at 19:21, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >>> It's a breaking change and I don't know if there's a way to do it with >>> proper deprecationâ¦ my hope is that there are not many users of it, but I >>> haven't checked yet. Any opinions among users of FileSystem? >>> >>> On 8 October 2016 at 19:12, stepharo <stepharo(a)free.fr> wrote: >>> >>>> So damien what is the solution? >>>> >>>> >>>> >>>> Le 7/10/16 Ã 18:18, Damien Pollet a Ã©crit : >>>> >>>> Path >> printString returns a self-evaluating representation, which is >>>> fine. Its symmetric is thus Compiler >> evaluate: aString. >>>> >>>> (Path from: aString) parses the unix/url representation of a path and >>>> results in a Path instance. As far as I understand, #fullName should be the >>>> symmetric of that, so that we always have (modulo syntactic normalization, >>>> maybe) : >>>> >>>> (Path from: aString) fullName = aString >>>> >>>> Note that there's an edge case with the empty string that is wrong (at >>>> least it should be confusing to unix guys): >>>> >>>> Path from: ''. "Path root" >>>> >>>> Usually the absolute path for the root of the filesystem is explicitly >>>> noted '/', and an empty path is equivalent to '.' >>>> >>>> -- >>>> Damien Pollet >>>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>>> >>>> >>>> >>> >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >> >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 13, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by Esteban Lorenzano

in principle, Iceberg is meant to work on Pharo6+ No idea about backward compatibility (it shouldnât be so hard eitherâ¦) Esteban > On 13 Oct 2016, at 19:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Nicolas, > > After installing it in Pharo 5.0 (#50761, Win 7) and clicking World Menu -> Tools -> Iceberg > I got the Exception in the screenshot attached. > > > 2016-10-13 9:25 GMT-03:00 Nicolas Passerini <npasserini(a)gmail.com <mailto:npasserini@gmail.com>>: > Hi, we are releasing a new version of Iceberg, with several new features and bugfixes. I would't yet say that is 100% production ready, but it is close, so I want to invite you to test it and provide feedback. > > You can install it by doing: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg'; > load. > > More installation instructions and documentation can be found at https://github.com/npasserini/iceberg <https://github.com/npasserini/iceberg>. > > Some of the new features in this version are: > - Allow to commit several packages together in the same commit. > - Show diffs for incoming and outgoing commits (i.e. before push/pull you can browse the difference between the remote and the local versions). > - New History view allows to see any commit in any branch and compare it to the current loaded version. > - Better support for interacting code loaded outside Iceberg (smaltalkhub, filetree, gitfiletree, etc). > - From the diff view, revert changes or browse them (i.e. open a Nautilus on the changed class/method). > - Automatically update presentations on code / repository changes. > - Integration with Metacello, i.e. after installing Iceberg you do something like > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > > (By default) it will be loaded using iceberg (there is a setting to avoid it if you prefer traditional behavior. > > - Improved handling of git errors. > - Improved performance for several operations. > - Improved documentation. > - ... and several bug fixes and other minor improvements (please look at https://github.com/npasserini/iceberg/milestone/7?closed=1 <https://github.com/npasserini/iceberg/milestone/7?closed=1> for more details). > > > Please do not hesitate to contact me if you have any doubts. > > <IceberError.jpg>

Oct. 13, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by HernÃ¡n Morales Durand

Hi Nicolas, After installing it in Pharo 5.0 (#50761, Win 7) and clicking World Menu -> Tools -> Iceberg I got the Exception in the screenshot attached. 2016-10-13 9:25 GMT-03:00 Nicolas Passerini <npasserini(a)gmail.com>: > Hi, we are releasing a new version of Iceberg, with several new features > and bugfixes. I would't yet say that is 100% production ready, but it is > close, so I want to invite you to test it and provide feedback. > > You can install it by doing: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg'; > load. > > More installation instructions and documentation can be found at > https://github.com/npasserini/iceberg. > > Some of the new features in this version are: > - Allow to commit several packages together in the same commit. > - Show diffs for incoming and outgoing commits (i.e. before push/pull you > can browse the difference between the remote and the local versions). > - New History view allows to see any commit in any branch and compare it > to the current loaded version. > - Better support for interacting code loaded outside Iceberg (smaltalkhub, > filetree, gitfiletree, etc). > - From the diff view, revert changes or browse them (i.e. open a Nautilus > on the changed class/method). > - Automatically update presentations on code / repository changes. > - Integration with Metacello, i.e. after installing Iceberg you do > something like > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > > > (By default) it will be loaded using iceberg (there is a setting to avoid > it if you prefer traditional behavior. > > - Improved handling of git errors. > - Improved performance for several operations. > - Improved documentation. > - ... and several bug fixes and other minor improvements (please look at > https://github.com/npasserini/iceberg/milestone/7?closed=1 for more > details). > > > Please do not hesitate to contact me if you have any doubts. >

Oct. 13, 2016

Re: [Pharo-dev] Path >> fullName should not be the same as printString

by Ben Coman

Its awkward to deal with. Some notes here... https://pharo.fogbugz.com/default.asp?13094#154946 On Fri, Oct 14, 2016 at 12:05 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > I explored a bit more and I'm stumped. Fixing it for Unix is easy, but it > breaks Windows paths, because those use their first element to store the > drive name (c: d: etc) which shouldn't be preceded by a /. > > I'm starting to think the Absolute/Relative dichotomy is either wrong or > incomplete and we need windows-specific subclasses. Doesn't it feel strange > that we can pass strings with different syntax and assumptions to Path > class >> from: and get instances from the same classes? > > On 8 October 2016 at 19:21, Damien Pollet <damien.pollet(a)gmail.com> wrote: > >> It's a breaking change and I don't know if there's a way to do it with >> proper deprecationâ¦ my hope is that there are not many users of it, but I >> haven't checked yet. Any opinions among users of FileSystem? >> >> On 8 October 2016 at 19:12, stepharo <stepharo(a)free.fr> wrote: >> >>> So damien what is the solution? >>> >>> >>> >>> Le 7/10/16 Ã 18:18, Damien Pollet a Ã©crit : >>> >>> Path >> printString returns a self-evaluating representation, which is >>> fine. Its symmetric is thus Compiler >> evaluate: aString. >>> >>> (Path from: aString) parses the unix/url representation of a path and >>> results in a Path instance. As far as I understand, #fullName should be the >>> symmetric of that, so that we always have (modulo syntactic normalization, >>> maybe) : >>> >>> (Path from: aString) fullName = aString >>> >>> Note that there's an edge case with the empty string that is wrong (at >>> least it should be confusing to unix guys): >>> >>> Path from: ''. "Path root" >>> >>> Usually the absolute path for the root of the filesystem is explicitly >>> noted '/', and an empty path is equivalent to '.' >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >>> >>> >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Oct. 13, 2016

Re: [Pharo-dev] Path >> fullName should not be the same as printString

by Damien Pollet

I explored a bit more and I'm stumped. Fixing it for Unix is easy, but it breaks Windows paths, because those use their first element to store the drive name (c: d: etc) which shouldn't be preceded by a /. I'm starting to think the Absolute/Relative dichotomy is either wrong or incomplete and we need windows-specific subclasses. Doesn't it feel strange that we can pass strings with different syntax and assumptions to Path class >> from: and get instances from the same classes? On 8 October 2016 at 19:21, Damien Pollet <damien.pollet(a)gmail.com> wrote: > It's a breaking change and I don't know if there's a way to do it with > proper deprecationâ¦ my hope is that there are not many users of it, but I > haven't checked yet. Any opinions among users of FileSystem? > > On 8 October 2016 at 19:12, stepharo <stepharo(a)free.fr> wrote: > >> So damien what is the solution? >> >> >> >> Le 7/10/16 Ã 18:18, Damien Pollet a Ã©crit : >> >> Path >> printString returns a self-evaluating representation, which is >> fine. Its symmetric is thus Compiler >> evaluate: aString. >> >> (Path from: aString) parses the unix/url representation of a path and >> results in a Path instance. As far as I understand, #fullName should be the >> symmetric of that, so that we always have (modulo syntactic normalization, >> maybe) : >> >> (Path from: aString) fullName = aString >> >> Note that there's an edge case with the empty string that is wrong (at >> least it should be confusing to unix guys): >> >> Path from: ''. "Path root" >> >> Usually the absolute path for the root of the filesystem is explicitly >> noted '/', and an empty path is equivalent to '.' >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 13, 2016

Re: [Pharo-dev] About icon: and iconNamed:

by Denis Kudriashov

2016-10-13 17:19 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > Is most of that expense come from passing the same Form over a link > multiple times? I vaguely wonder if content-addressable caching would help > there. You see: current state requires such kind of tricks. But if users always work with icon names it will not the case completely. > But anyway, wouldn't a remote browser work at a higher level that being a > remote UI? and the user want to use their local theme rather than that > from the remote image? I want to do it like this. But now classes define concrete form which should be used in UI. I would call it "no late binding for icons".

Oct. 13, 2016