- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] <example>/<examplar>

by Dimitris Chloupis

I will probably sound stupid but here I go. I am no fan of Pragmas. I feel that their syntax is weird and unnecessary and what they do can be easily achieved with a secondary class that provides this meta data. In case of examples it would have been possible to have examples in a separate package together with a class that provides the additional info the IDE needs to trigger the right tools. On the other hand I was neither a fan of using example as part of a method name. Saying that instancePrototype sounds a lot more clear than examplar. On Mon, 22 Aug 2016 at 08:39, stepharo <stepharo(a)free.fr> wrote: > Hi sean > > this is exactly with <sampleInstance> but this is not exactly the > solution doru envision. > > But I think that sampleInstance is letting people build extra tools and > also let people use the sample method > > in their test and others. > > > Stef > > > Le 21/8/16 Ã 02:01, Sean P. DeNigris a Ã©crit : > > Tudor Girba-2 wrote > >> In this case, you will not be able to use the resulting object, and the > >> new energy around examples started from the need to utilize that ability > >> The other solution is to delegate the action to another pragma that can > >> complement the example one. > > Isn't that what we've settled on? That is, <sampleInstance> for when you > > need the result? It seems that all bases are covered if those methods > return > > an instance and the browser button takes that instance and opens an > > inspector, no? > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/example-examplar-tp4911728p4912083.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > >

Aug. 23, 2016

Re: [Pharo-dev] About PythonDocTest for Pharo

by Nicolas Passerini

On Thu, Aug 18, 2016 at 11:28 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-08-18 13:32 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> withExtension: aString >> >> "Returns a new file reference with a different file extension" > > > Does this comment is really needed? > I only see extra word "different". And rest is same as method name. IMHO > we should rename method to "withDifferentExtension:" and remove comment. > I think that it is interesting that the comment also says that it will return a FileReference... of course there are other ways to know that, but it is nice that the comment avoids the research/guessing. More over, which is not obvious is that it will *change* the extension, because the "with" prefix could mislead you to think that it will *add* the extension. Maybe we can come up with a better name (withDifferentExtension: works better, I agree) or we need the comment to be explicit about it.

Aug. 23, 2016

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

by Nicolas Passerini

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.

Aug. 23, 2016