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

Re: [Pharo-dev] About better communication in the community

by HernÃ¡n Morales Durand

Hi Stef, Good communication implies being clear when writing about sensitive topics, especially when communicating through virtual channels. I am not in Europe, so I cannot discuss these things with you face to face. Therefore is not clear to me (and others) what are your policies in many subjects. Lately I also delayed the release of packages because my lack of motivation around this community, specially when discussions exists around three or fourth topics for months. Another "motivational" case for me. I stopped to report bugs in fogbuz because I felt there was too much "Won't fix" for me (specifically by a person but I won't go there...) even in cases where it was ilogical. Then I felt tired of reading "It's like that. Invalid". About features. What's the policy about voting for default features in next Pharo images? Let's suppose I am a VM/core Pharo maintainer and I want to include MySuperPackage into a Pharo release, which nobody needs (and I don't care), but it is useful to me.... there will ever be voting there? (note it doesn't makes sense if you are a group of 50 always supporting your work) Images are becoming huge (at least for my workflows). There will be (more) packages included by default (for promotion?) ? How do you plan to manage if some people want the Tests be removed from the official Image? (Personally I never run them) Another example, what happens if another research group came with a better alternative to Calypso, Brick, Telescope, Bloc. Would you integrate first your tool to mark territory? Who decides? For example (IIRC) TxText and Twisty. The same applies if anyone came with another rewrite of classic Smalltalk Workspace, Debugger and Inspector tools, what would you do with GT? GT stays because it came before and others would be optional? There will be anything like PEPs? If someone can answer me I think that would be an example of good communication. HernÃ¡n 2016-08-24 1:51 GMT-03:00 stepharo <stepharo(a)free.fr>: > Hi guys > > the board got a good discussion at ESUG about how to improve and a lot of > the discussion turned around improving communication. We got some ideas > that we will propose soon but I would like to get *your* ideas. > > If you have idea about improving communication around pharo please tell us. > > > Stef > > >

Aug. 24, 2016

Re: [Pharo-dev] About PythonDocTest for Pharo

by stepharo

> I am sorry, but I want to said it: we have tests. Why tests are not > for same purpose? (I would say they include it). > > As Tudor said: > > "they are way too disconnected from the code" > > > And this needs to be solved. > We already have nice feature in Nautilus: it shows "test icon" on > covered methods. We could extends this idea to simplify test visibility. > > Proposed solution is much simpler. But how much it is practical? How > many code could use it? > For simple cases like String methods is super nice. But could you > imaging it for Seaside code? or Morphic? The goal is not to replace nor to use that for everything. I'm not looking for the Graal (and tests are not the graal for documentation). I'm looking for something dead simple that helps me to understand little methods. It works in python that they also have tons of other ways to tests (probably even a test system that check on the line level like in Php). So instead of being defensive we should be more open to improvements when we are talking about documentations. Stef

Aug. 24, 2016

Re: [Pharo-dev] About PythonDocTest for Pharo

by stepharo

Ok this is your taste. My reality is different. Tests are far far away. I do not see them. They live in a different time zone. They are smart have a boring setup. I want documentation in front on my nose. No extra thinking no extra click Just right there. Stef Le 18/8/16 Ã 23:14, Denis Kudriashov a Ã©crit : > Hi. > > 2016-08-18 9:34 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > withExtension: aString > > "Returns a new file reference with a different file extension" > > <exp: '/tmp/file.txt' asFileReference withExtension: 'log' > > value: '/tmp/file.log' asFileReference > > > ^ self withPath: (self path withExtension: aString) > > > So let me know what you think. > - tell me that we have already test unit (yes the ones I wrote > too) > => they do not have the same purpose > > > I am sorry, but I want to said it: we have tests. Why tests are not > for same purpose? (I would say they include it). > > As Tudor said: > > "they are way too disconnected from the code" > > > And this needs to be solved. > We already have nice feature in Nautilus: it shows "test icon" on > covered methods. We could extends this idea to simplify test visibility. > > Proposed solution is much simpler. But how much it is practical? How > many code could use it? > For simple cases like String methods is super nice. But could you > imaging it for Seaside code? or Morphic? > >

Aug. 24, 2016

About Pharo 60

by stepharo

Hi We have some ideas (because people are working on items) for the Pharo 6 roadmap and we will consolidate them soon and propose them to you. but I would like to know two kinds of points - what are the points you are working on and that would deserve more focus and help from the community? (these points are important because like that you could go faster and this is a good feeling to get done for example) - what would be points where (if magically we would get more resources - to not dream if this is not you there is a high chance that we will not make it) it would be nice to get some changes Please pay attention that if you type too fast and come up with a christmas list well it will stay a christmas list and will just make the thread larger for nothing. Stef

Aug. 24, 2016

About better communication in the community

by stepharo

Hi guys the board got a good discussion at ESUG about how to improve and a lot of the discussion turned around improving communication. We got some ideas that we will propose soon but I would like to get *your* ideas. If you have idea about improving communication around pharo please tell us. Stef

Aug. 24, 2016

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

by stepharo

Hi nicolai I remember that I read everything and fix typos. Did you got my review or did I suuceed to lose it ;). Stef Le 6/8/16 Ã 15:24, Nicolai Hess a Ã©crit : > > > 2016-07-28 16:18 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > I will! > > I love to read nice comments > > Stef > > > > I updated the slice and added some more example (much more is needed > but I think it is better than having no doc :) ). > I changed some help topics on refactoring support in nautilus to > directly used the refactoring classes comments (no need to maintain > two docs), but > this is not applicable for all refactorings, for example "generate > superclass" and "insert superclass" needs its own description, as > there is only one RBAddClassRefactoring comment. > > please help with reviewing, I am not good at writing this kind of text. > > The refactoring engine is a great and powerfull piece of code and it > would be great to have a proper documentation "in-image". > I have seen some bugs, bad code or wrong bug fixes by contributors not > fully understanding the framework (me too :) ). > > just load the slice and open > HelpBrowser openOn: RefactoringHelp. > > > thanks > nicolai > > > Le 28/7/16 Ã 00:38, Nicolai Hess a Ã©crit : >> Hi, >> >> I recently added some class comments to the Refactoring-Package. >> (RBBrowserEnvironments, RBRefactoring, RBNamespace). >> >> Now I added some more HelpTopics describing the refactoring >> framework, some background information, RBPatternParser and >> Metavariables, some examples and put the existing class comments >> into the HelpBook. >> >> see fogbugz issue 18829 >> <https://pharo.fogbugz.com/f/cases/18829/Add-a-RefactoringFramework-System-H…> >> Add a RefactoringFramework System HelpTopic >> you can load the slice and open the HelpBook with >> >> HelpBrowser openOn: RefactoringHelp. >> >> Would be nice if someone can help with proofreading and of >> course, amy feedback is welcome. >> >> nicolai > >

Aug. 24, 2016

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

by Nicolai Hess

2016-08-06 15:24 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-07-28 16:18 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> I will! >> >> I love to read nice comments >> >> Stef >> >> > I updated the slice and added some more example (much more is needed but I > think it is better than having no doc :) ). > I changed some help topics on refactoring support in nautilus to directly > used the refactoring classes comments (no need to maintain two docs), but > this is not applicable for all refactorings, for example "generate > superclass" and "insert superclass" needs its own description, as there is > only one RBAddClassRefactoring comment. > > please help with reviewing, I am not good at writing this kind of text. > > The refactoring engine is a great and powerfull piece of code and it would > be great to have a proper documentation "in-image". > I have seen some bugs, bad code or wrong bug fixes by contributors not > fully understanding the framework (me too :) ). > > just load the slice and open > HelpBrowser openOn: RefactoringHelp. > > > thanks > nicolai > > I'll put it on fixed to review now, If you have any comments, notes or suggestions please comment on the issue or in this thread thanks nicolai > > > >> Le 28/7/16 Ã 00:38, Nicolai Hess a Ã©crit : >> >> Hi, >> >> I recently added some class comments to the Refactoring-Package. >> (RBBrowserEnvironments, RBRefactoring, RBNamespace). >> >> Now I added some more HelpTopics describing the refactoring framework, >> some background information, RBPatternParser and Metavariables, some >> examples and put the existing class comments into the HelpBook. >> >> see fogbugz issue 18829 >> <https://pharo.fogbugz.com/f/cases/18829/Add-a-RefactoringFramework-System-H…> >> Add a RefactoringFramework System HelpTopic >> you can load the slice and open the HelpBook with >> >> HelpBrowser openOn: RefactoringHelp. >> >> Would be nice if someone can help with proofreading and of course, amy >> feedback is welcome. >> >> nicolai >> >> >> >

Aug. 23, 2016

[pharo-project/pharo-core]

by GitHub

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

Aug. 23, 2016

[pharo-project/pharo-core] 46ae65: 60191

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 46ae6557594467c838b7b75baa52bbe399eb2072 https://github.com/pharo-project/pharo-core/commit/46ae6557594467c838b7b75b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-08-23 (Tue, 23 Aug 2016) Changed paths: M Collections-Tests.package/OrderedDictionaryTest.class/README.md A Collections-Tests.package/TDictionaryAssociationAccessTest.class/instance/tests - dictionary assocition access/testAssociationAtIfPresent.st M Collections-Unordered.package/Dictionary.class/instance/accessing/associationAt_ifPresent_.st M Collections-Unordered.package/SmallDictionary.class/instance/accessing - associations/associationAt_ifAbsent_.st A Collections-Unordered.package/SmallDictionary.class/instance/accessing - associations/associationAt_ifPresent_.st A Kernel-Tests.package/ClassTest.class/instance/referencing methods/referencingMethod1.st A Kernel-Tests.package/ClassTest.class/instance/referencing methods/referencingMethod2.st A Kernel-Tests.package/ClassTest.class/instance/referencing methods/referencingMethod3.st M Kernel-Tests.package/ClassTest.class/instance/testing - navigation/testMethodsReferencingClass.st M Kernel-Tests.package/ClassTest.class/instance/testing - navigation/testMethodsReferencingClasses.st M Kernel.package/Categorizer.class/instance/accessing/allMethodSelectors.st M Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/buildVariableMenuFor_variablesFrom_menuItemBy_.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/buildInitializeCodeFor_.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/buildSetUpCodeFor_.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/buildTearDownCodeFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60190.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60191.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60190.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60191.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Base.package/AbstractTool.class/instance/class/addTraitIn_.st M Tool-Base.package/AbstractTool.class/instance/method/categorizeMethods_of_from_.st M Tool-Base.package/HistoryCollection.class/instance/protocol/mostViewedElements.st Log Message: ----------- 60191 18967 wrong title for "add trait" dialog https://pharo.fogbugz.com/f/cases/18967 18954 ClassTest>>#testMethodsReferencingClass and testMethodsReferencingClasses should not use external packages https://pharo.fogbugz.com/f/cases/18954 18975 copy sort --> sorted https://pharo.fogbugz.com/f/cases/18975 18976 SmallDictionary>>#associationAt:ifPresent: is not implemented https://pharo.fogbugz.com/f/cases/18976 http://files.pharo.org/image/60/60191.zip

Aug. 23, 2016

Re: [Pharo-dev] Character encoding and line ending in OSSubprocess

by Mariano Martinez Peck

Hi Nico, I am on holidays now, so my answer will be short. I would like to provide some encoding facility if you think if may make sense to provide that at that level. This issue is the second time it appeared, that's why I am asking. Whenever you make the PR, can I see the changes and see if I could put that in OSSubprocess itself ? Thanks On Tue, Aug 23, 2016 at 5:00 AM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > > > On Mon, Aug 22, 2016 at 4:29 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> >> >> 2016-08-22 16:08 GMT+02:00 Nicolas Passerini <npasserini(a)gmail.com>: >> >>> >>> On Mon, Aug 22, 2016 at 3:31 PM, Thierry Goubier < >>> thierry.goubier(a)gmail.com> wrote: >>> >>>> does this happens when you are using one of the GitFileTree generated >>>> command or when you use directly the command line api (runGitCommand and >>>> friends)? >>>> >>> >>> I think that it happens in both cases, the most obvious is that it fails >>> to bring my github name, which happens to have an "Ã¡". >>> >> >> Hum, I may be missing a string convert on some arguments of the git clone >> command... >> >> > Ok, if that's the way to go I can try to fix it and send you a pull > request. > I was thinking if it can not be resolved by OSSubprocess itself. > > >> But I will check your idea, to be sure. >>> >>> >>>> Does this happens with OSProcess as well? >>>> >>>> I am not sure about this, can I use gitfiletree with OSProcess, how can >>> I test it? >>> >>> >> Just load OSProcess before loading GitFileTree, it should notice it and >> avoid loading OSSubprocess. >> >> >> Ok, I will try that, thankyou. > -- Mariano http://marianopeck.wordpress.com

Aug. 23, 2016