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

Re: [Pharo-dev] WhatsUp from: 2015-10-05 until: 2015-10-18

by stepharo

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Revisiting Magritte tutorial: nearly there. - Working on Mooc > > ### What's next, until 2015-10-18 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > (*) we'll be expecting results by then ;) > >

Oct. 6, 2015

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

by stepharo

Just relax and trust me. It would help me. 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. 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

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

by Marcus Denker

but it would be good to put them on âto includeâ before integration. This way we do not do double work (someone reviewing even if it is already ok) or that the monkey re-starts to check them after integration. > On 06 Oct 2015, at 10:34, stepharo <stepharo(a)free.fr> wrote: > > 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

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

by stepharo

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

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

by Yuriy Tymchuk

> 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 <mailto:i.uhnak@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. 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 <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

Latest Build added items that are not yet set as "to include"

by Henrik Nergaard

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

Re: [Pharo-dev] Latest changes broke Icons

by Torsten Bergmann

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

[pharo-project/pharo-core]

by GitHub

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

Oct. 6, 2015

[pharo-project/pharo-core] 313229: 50365

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 313229ecd6a4b6f5cf5c86b2affc8d3516d674d9 https://github.com/pharo-project/pharo-core/commit/313229ecd6a4b6f5cf5c86b2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-10-06 (Tue, 06 Oct 2015) Changed paths: M Collections-Strings.package/String.class/instance/converting/asLegalSelector.st A Collections-Strings.package/String.class/instance/converting/asValidSelector.st A MonticelloGUI.package/MCTool.class/instance/morphic ui/accept.st A MonticelloGUI.package/MCTool.class/instance/morphic ui/menu.st A MonticelloGUI.package/MCTool.class/instance/morphic ui/summary_.st M MonticelloGUI.package/MCTool.class/instance/morphic ui/textMorph_.st M Rubric.package/RubAbstractTextArea.class/instance/editing/acceptContents.st M Rubric.package/RubAbstractTextArea.class/instance/menu/lookupMenu.st R Rubric.package/RubEditingArea.class/instance/initialize-release/beForMinimalEditor.st M Rubric.package/RubEditingMode.class/class/menu/menuKeyword.st M Rubric.package/RubEditingMode.class/definition.st A Rubric.package/RubEditingMode.class/instance/accessing/acceptAllowed.st A Rubric.package/RubEditingMode.class/instance/accessing/acceptAllowed_.st R Rubric.package/RubEditingMode.class/instance/as yet unclassified/isCodeCompletionAllowed.st A Rubric.package/RubEditingMode.class/instance/initialize-release/initialize.st A Rubric.package/RubEditingMode.class/instance/testing/isCodeCompletionAllowed.st M Rubric.package/RubFloatingEditorBuilder.class/instance/private/buildEditor.st R Rubric.package/RubMinimalEditorMode.class/README.md R Rubric.package/RubMinimalEditorMode.class/class/menu/menuKeyword.st R Rubric.package/RubMinimalEditorMode.class/definition.st R Rubric.package/RubNullGetMenuPolicy.class/README.md R Rubric.package/RubNullGetMenuPolicy.class/definition.st R Rubric.package/RubNullGetMenuPolicy.class/instance/accessing menu/lookupMenu.st R Rubric.package/RubNullGetMenuPolicy.class/instance/accessing menu/lookupShiftMenu.st M Rubric.package/RubPlainTextMode.class/class/menu/menuOn_.st M Rubric.package/RubPluggableTextMorph.class/README.md A Rubric.package/RubScrolledTextMorph.class/instance/accessing menu/allowMenu.st A Rubric.package/RubScrolledTextMorph.class/instance/accessing menu/forbidMenu.st A Rubric.package/RubScrolledTextMorph.class/instance/accessing menu/menuAllowed_.st R Rubric.package/RubScrolledTextMorph.class/instance/initialize-release/beForMinimalEditor.st M Rubric.package/RubScrolledTextMorph.class/instance/model protocol/on_text_accept_readSelection_menu_.st M Rubric.package/RubTextEditor.class/instance/typing support/dispatchCommandOn_return_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50364.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50365.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50364.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50365.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/SyntaxErrorDebugger.class/class/instance creation/buildMorphicViewOn_.st M Tools.package/SyntaxErrorDebugger.class/instance/other/contents_notifying_.st Log Message: ----------- 50365 16722 Fixing RubScrolledText and removing some users of RubPluggableTextMorph https://pharo.fogbugz.com/f/cases/16722 15162 #asLegalSelector: bad name and wrong for selectors with args https://pharo.fogbugz.com/f/cases/15162 http://files.pharo.org/image/50/50365.zip

Oct. 6, 2015

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

by Nicolai Hess

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). > > 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