- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Latest changes broke Icons

by Esteban Lorenzano

Ho Torsten, No, it is not broken. As I said, is an ongoing change: https://pharo.fogbugz.com/f/cases/16651 ThemeIconPack is finally renamed as ThemeIcons and all external packages extending it will be able to use. Now, some thing will not be backward compatibility: - if you used directly ThemeIcons children - it you used outside the class some of the private methods (like *IconContents, etc.) - if you extended ThemeIcons children instead ThemeIcons they will need to be adapted. I hope there are not so many because those issues were never recommended anyway :) (but even if not recommended, I needed to change a lot of miss-uses in some packagesâ¦ I would like to have a monkey rule to forbid this kinds of integrations into the image :S) I started this change last friday, in commit 50357â¦ it is tuesday and we are in commit 50366. Itâs been just 4 days and 9 buildsâ¦ (and btw SLICE is not integrated because some weird monkey issues, not because is not ready). so, pleaseâ¦ be patient! ;) Esteban > On 06 Oct 2015, at 09:54, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Esteban, > > It's broken: "Smalltalk ui icons" now returns an instance of ThemeIconPack instead > of the usual ThemeIcons/subclass. > > But most external packages extended ThemeIcons or subclasses with own icons > as this is/was up to the change the default way to do it. It's not possible to > access these extensions anymore using > > Smalltalk ui icons myIcon > > now. I understand that you needed a "break" - but it is not fun if you "break" ;) > > Bye > T. >

Oct. 6, 2015

Re: [Pharo-dev] [Pharo-users] Better Code Completion

by Nicolai Hess

2015-10-06 10:31 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > On 06 Oct 2015, at 09:09, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > Am 04.10.2015 23:53 schrieb "Peter UhnÃ¡k" <i.uhnak(a)gmail.com>: > > > > This is both rant and list of questions/notes/observations... > > > > ...but first of all: > > do Smalltalkers not like code completion? Because the one in Pharo is > really poor and not only that nobody is doing anything about it, but also > nobody is complaining; this leads me to believe that you either > > > > a) don't have the manpower (this is true pretty much always, so no > complaints here) > > b) don't care about this that much (since you lived without it for 45 > years) > > > > at least from the lack of complaining to me it seems that b) is more > likely scenario... > > > > But since I do use it, I get annoyed by it quite a bit, especially since > I regularly work in IDEs where this thousand times better. > > > Can you Name one, for a dynamic OO - language? > (Maybe we can borrow some ideas). > > > Ruby? > > I think that RubyMine has to do something with code completion. > Wow, that looks great, do you work with it? > > Uko > > > > > > Now I would like to get things moving a bit (or bury it and forget it), > so I have couple of questions and would appreciate if someone could provide > some feedback. > > > > 1. Methods of core/top classes should be deprioritized > > > > Since Object has almost 500 methods whatever I will start typing > Object/TClass/TBehavior/... will have a list of answers... > > I think this is difficult, even though this classes are big and you don't > use most of the methods, > > are you sure we dont use some of the methods *often*. Morphic, > ComposeableModel or many collection classes, for example. > > > > > so let's start typing... > > > > > > > > > > > > Very often I have to type almost full word to see what I want. > > This is doesn't happen often to me. It is far from perfect but most of the > time I only type a small part and find the correct completion. > > > > Shouldn't the completion follow the inheritance chain? So first it shows > me matches from the class itself (especially since it actually knows the > type) and only after then it's parents and so on? > > Currently, it only collects all selectors into a set and sorts by > matching and length. > > We could add the class info and sort by inheritance distance. > > This needs some change how sorting is implemented, for now,it is typeless > and may need some double dispatching. > > > > > > 3. Or maybe even show the (closest) class that implements it. > > So the last two items would have somewhere (beginning or the end) > written '(Object)' and the first two '(yourself)' (or the class's name). > > This needs some additional work too, now the menu text is the actual > completion content. But it > > shouldn't be that difficult and some code looks like it was intended to > work that way. > > > > > > > 2. The window has fixed size, so if I have longer method (as in picture > above) I don't see it all. > > > > 3. Is middle-of-the word really that often used? See > moseIntere<sti>ngEntity above. It feels to me that it just creates a lot of > false positives (I have this problem also with inspector btw, so I often > have to prefix it with >># or if I see it already lot of <arrow down>, > which is annoying) > > I often search for "Dictionary" or "Morph" and expect results even if the > typed word is not at the beginning, quite often. > > > > > > > > > > 4. We write tests, however how often have you manually created an > instance of a test class by hand? I think they should be either filtered or > deprioritized as they create visual clutter. This is probably also true for > many other classes such as ConfigurationOf/Manifest/... Nobody instantiates > them by hand. > > Be careful will statements like "nobody ...." > > I do a lot of reviews for pharo issues, and this involves working in > workspace and instantiating classes (Yes, Tests, Refactoring, LintRules) > most people don't use them this way but by the tools (SUnit, CriticBrowser) > > But I do. > > > > > > > 5. How often do you send #abs to a dictionary? > > seldom, never? but how could a completion framework detect that? > > > > > > > > 6. If I have already written part of the selector it's impossible to > "continue" and add an extra parameter. This is because it doesn't know if I > am code completing for dict, or #key. > > Maybe different shortcuts? <tab> to code complete on #key, and > <shift+tab> to code complete on the previous one... > > good idea! > > (did you know, that there is a shortcut to jump from one message send > argument to another (not related to completion, but very helpful). Sadly > this is gone or I couldn't find > > it in rubrics shortcut handling). > > > or maybe cycle through them because this can be nested (the currently > code completed item would have to be highlighted somehow). > > > > > > 7. So if I don't want to see the above I have to type it manually; which > is fine for #at:put: but not for longer words.. (just to find out ten > seconds later that I have a stupid typo there). > > > > 8. The code completion doesn't show parameter names. This is very > helpful because it often reveals what it actually accepts. Now I have to > actually look into the code of the method. > > Yes, I tried to change that for issue "10219 > <https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn…> > Completion: enter on accept awkwardness", but again, the completion only > knows about the methodDict keys, the selector, > > not the mehod code. But I would like to change that and test if it is much > slow. > > > > > > Now we can hardly compete with typed languages, but I think there's a > lot lot room for improvement. > > > > For comparison from other languages/IDE's. > > > > PhpStorm/PHP > > > > (notice how it shows the whole method if it's longer than the window and > doesn't it just clip)â > > > > NetBeans/C++ > > > > > > > > In the picture above it âstill provides hinting when typing the > parameter. > > > > TypeScript playground > > > > > > â(similar to NetBeans) > > > > Also they have in their online playground better and nicer code > completion than we have in actual env ( > http://www.typescriptlang.org/Playground ) > > > > So if you have any thoughts/feedback/whatnot on this matter, I would > greatly appreciate it. > > > > > > > > Peter > > > > >

Oct. 6, 2015

Re: [Pharo-dev] Slack?

by Craig Latta

Slack works very well for large groups. I'm already using it with a group that is larger than this one. -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Oct. 6, 2015

Re: [Pharo-dev] Slack?

by Max Leske

We use slack at work. Itâs great, but I doubt its usefulness for a large community (thereâs a lot going on even with only 12 people). > On 06 Oct 2015, at 12:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi guys, > > Iâm thinking whether live chat can make sense for communication. And I know that there is IRC, but for some reason itâs not working for me (maybe because of clients). > > Iâve seen many teams using Slack [1]. Is anybody willing to try that out. Or also maybe some have already created a pharo team on Slack? > > Cheers. > Uko > > [1]: https://slack.com/ <https://slack.com/>

Oct. 6, 2015

Slack?

by Yuriy Tymchuk

Hi guys, Iâm thinking whether live chat can make sense for communication. And I know that there is IRC, but for some reason itâs not working for me (maybe because of clients). Iâve seen many teams using Slack [1]. Is anybody willing to try that out. Or also maybe some have already created a pharo team on Slack? Cheers. Uko [1]: https://slack.com/ <https://slack.com/>

Oct. 6, 2015

Re: [Pharo-dev] About Magritte Seaside

by Stephan Eggermont

On 06-10-15 11:11, stepharo wrote: > I will do a separate configuration of magritte seaside. You need to load the correct groups. Separate configurations are a bad practice and should be eliminated, not encouraged. The configuration has a lot of essential complexity, as many different combinations of components are needed in different situations. We need tools that recognize that essential complexity and support it, not tools that try to hide it and then have no practical usability. Stephan

Oct. 6, 2015

Re: [Pharo-dev] About Magritte Seaside

by Skip Lentz

> On Oct 6, 2015, at 11:11 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > How can I get Magritte seaside (and a working version not one breaking on XML I do not what)? > I loaded the published stable version of Magritte into Pharo and there is no seaside version. > I checked the configuration and it is so complexâ¦. I think you have to load the âSeaside" group of ConfigurationOfMagritte3, but I am not sure.. A month ago I played with Magritte and Seaside and I basically loaded a bunch of configurations until it worked. As a new user I loaded âMagritteMagicâ without knowing better. This one is broken if you load it on Pharo 4. Later I found out that MagritteMagic was just for demonstration purposes. So maybe it should get an âexampleâ or âdemoâ tag in the Project Catalog.

Oct. 6, 2015

Re: [Pharo-dev] Latest Build added items that are not yet set as "to include"

by stepharo

I thought that I did it so may be I did it on the wrong issue. Now it would be nice if you could get much nicer with people spending their time to improve Pharo. You are not the only one looking at bug and improving pharo. Stef Le 6/10/15 10:47, Marcus Denker a Ã©crit : > >> On 06 Oct 2015, at 10:45, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Just relax and trust me. It would help me. >> > thatâs not the point. It is about communication. And exactly about that: > >> They were tested already. I checked that. >> The problem is that the monkey is restarting to check because I did >> not close them fast enough. >> > Exactly that does not happen if you put the issue on âfix to includeâ. > Itâs not hard to do and solved > many problems. Why not do it? > >> Le 6/10/15 10:34, stepharo a Ã©crit : >>> Yes I always take time to close them to be sure that everything is >>> integrated :) >>> Tx for the warning. >>> >>> Le 6/10/15 10:17, Henrik Nergaard a Ã©crit : >>>> The latest build #50365 added two Issues (#16722 and #15162), but >>>> in Fogbugz these are still under review by the Monkey, and not set >>>> as âto includeâ. >>>> Best regards, >>>> Henrik >>> >> >> >

Oct. 6, 2015

About Magritte Seaside

by stepharo

Hi guys How can I get Magritte seaside (and a working version not one breaking on XML I do not what)? I loaded the published stable version of Magritte into Pharo and there is no seaside version. I checked the configuration and it is so complex.... I have the impression that we need to distinguish Magritte from Magritte seaside. So I will do a separate configuration of magritte seaside. Stef

Oct. 6, 2015

[pharo-project/pharo-core]

by GitHub

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

Oct. 6, 2015