- Pharo-dev - lists.pharo.org

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

by Tudor Girba

Hi, > On Oct 13, 2016, at 2:16 PM, stepharo <stepharo(a)free.fr> wrote: > > >>> what if you want to have side by side two different themes to compare the best icons >>> choices? >> >> This is a valid concern, but I do not understand how this would work if the only thing you pass in iconName: is just one symbol: >> >> act: aBlock iconName: aSymbol entitled: aString >> >> So there needs to be a lookup. This lookup will depend on the current icon theme. So, you could open on window with one theme, switch the theme and then open another window. Or did I misunderstand something? > > The idea is that all the tools: should have an iconProvider and not a global lookup (even if the lookup can access a global) >> My idea was that we leave the public API of Glamour to be: >> >> act: aBlock icon: aSymbolOrForm entitled: aString >> >> and then if you want to play with things, you can also explicitly pass one icon or another (beside relying on the default lookup behavior). >> >> What do you think? > I would like to avoid clients to use Symbol >> asIcon it can be an internal implementation. I think I am missing something. If it is the concrete tool that should dispatch on the concrete icon set, then Glamour cannot get a symbol because Glamour does not know the tool. I am a bit under time pressure, and I likely need some days to look at this, but I will look at the code and get a better picture. Cheers, Doru >> >> Doru >> >>> >>>> >>>> In this way we do not have to change the external interface, and only the internal implementation has to send an âasIconâ before using it? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>>> On Oct 12, 2016, at 10:33 PM, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>> I'm adding >>>>> >>>>> act: aBlock iconName: aSymbol entitled: aString >>>>> self act: aBlock icon: (self iconNamed: aSymbol) entitled: aString >>>>> >>>>> and >>>>> >>>>> act: aBlock iconName: aSymbol on: aCharacter entitled: aString >>>>> self act: aBlock icon: (self iconNamed: aSymbol) on: aCharacter entitled: aString >>>>> >>>>> and others .... >>>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Every thing has its own flow." >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "We are all great at making mistakes." >> >> >> >> >> >> >> >> > -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

Oct. 13, 2016

Re: [Pharo-dev] Shout style table editor (Request for Feedback)

by Nicolai Hess

Thanks for the feedback. I'll start first with adding some small enhancements to the styler (so it really uses all the existing style options) see : 19179 <https://pharo.fogbugz.com/f/cases/19179/Styler-does-not-support-all-style-t…> Styler does not support all style table tokens 2016-10-11 21:37 GMT+02:00 stepharo <stepharo(a)free.fr>: > > > Le 10/10/16 Ã 19:30, Sven Van Caekenberghe a Ã©crit : > >> Wow, that looks very nice ! >> > > + 10 > I want that :) > > > >> On 10 Oct 2016, at 18:42, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> I am working on a syntax style table editor, see issue for some >>> background about this. >>> 18322 Settings for Syntax Highlighting a bit confusing >>> 15409 A more complete set of syntactic colors is needed >>> >>> >>> Load package >>> >>> ST-StylingPreview >>> ST-StylingPreviewShoutExtension >>> >>> from >>> >>> MCHttpRepository >>> location: 'http://smalltalkhub.com/mc/Ni >>> colaiHess/StylerTableEditor/main' >>> user: '' >>> password: '' >>> >>> And open the preview/editor with: >>> >>> STStylerPreview open. >>> >>> This is a prototype, you can view builtin style tables, create and edit >>> new custom style tables. >>> This has some fake code styler methods to make the styling work for the >>> code preview pane, and it supports more styling attributes than the >>> default styler. >>> >>> This is what I would like to have as a syntax style setting dialog >>> instead of the current >>> confusing behavior. It may be helpful to actually see what syntax >>> styling attributs are >>> actually available. >>> >>> >>> <PharoScreenshot.3.png> >>> >> >> >> > >

Oct. 13, 2016

Re: [Pharo-dev] itemIcon: and Spotter

by Tudor Girba

Hi, Ok. I did not look at the changes yet. Could you give me a quick update: are base changes with iconNamed: integrated already? Doru > On Oct 13, 2016, at 2:51 PM, stepharo <stepharo(a)free.fr> wrote: > > Doru > > It would be nice to take some action here too. > > I would like to remove the Smalltalk ui icons iconNamed: > > spotterMonticelloWorkingCopyFor: aStep > <spotterOrder: 1> > aStep listProcessor > title: 'Monticello Working Copy'; > allCandidates: [ Array with: self workingCopy ]; > itemIcon: [ Smalltalk ui icons iconNamed: #versionControlIcon ]; > filter: GTFilterSubstring > > -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

Oct. 13, 2016

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