- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by Tudor Girba

Hi, Given the current interest, I am raising the issue of GTExample again. I sent a while ago a thorough description of the current solution: http://gtoolkit.org/doc/Examples/examples.html The goal is to provide documentation for all methods and classes both by allowing simple examples (plain unary methods) and offering the potential of doing more than just simple things. Except for Nicolai, there was no other feedback. Is there an interest to have a conversation about it? Cheers, Doru > On Sep 15, 2016, at 8:40 PM, stepharo <stepharo(a)free.fr> wrote: > >>> Would you highlight all string in all code as if it contained code? Or would you add this just for >>> Pragmas? But even there, strings are string, not code. > and then? you try and if it failed then in not code and you do not highlight it. > KISS. No? >>> I think we can conclude that pragmas are not a good solution to the problem, as they are far >>> too limited to express code. >> I second that. >> Furthermore, typical examples require more than one liners, and these should be factored out separately. > > I'm talking about > > basename > "Returns the base of the basename, > i.e. > /foo/gloops.taz basename is 'gloops.taz' > / basename is '/'" > > I do not think that it makes sense to have a separate example for this. > Because you want to read everything > > > I do not see why the following would not work. > basename > "Returns the base of the basename" > <expr: '''/foo/gloops.taz'' asFileReference basename' result: 'gloops.taz'> > > Now I hate the extra ' for strings. > We should invent a syntax to be put inside comments and that we can easily parse because we need to improve > the use and discovery of the library. > > basename > "Returns the base of the basename" > " > '/foo/gloops.taz' asFileReference basename > >>> 'gloops.taz' > " > > I cannot not do anything and just complain that our methods are not that well documented. > We as a community should take this and build an super cool system. > > > Stef > > > -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Sept. 15, 2016

need new pharo features for phratch and community

by jannik laval

Hi pharoers, regularly, I have french teachers that ask me for new addons for phratch. These teachers don't like Scratch 2 or Snap! because of latency or used language or because it needs a web browser... I have 3 important points that I cannot answer because of a lack of time: - having phratch on RPi - making Arduino working with phratch - having sound working on linux and RPi These features do not depends on phratch but on pharo. I use fully functions of pharo. But I don't have time to develop now on that. Could someone help me ? Thank you Jannik -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re laboratoire DISP http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

Sept. 15, 2016

Call for design for a literal programming doc similar to PythonDocTest

by stepharo

Hi all I want something similar in the spirit to PythonDocTest https://docs.python.org/2/library/doctest.html I'm talking about basename "Returns the base of the basename, i.e. /foo/gloops.taz basename is 'gloops.taz' / basename is '/'" Pragmas do not work well i.e., basename "Returns the base of the basename" <expr: '''/foo/gloops.taz'' asFileReference basename' result: 'gloops.taz'> We should invent a syntax to be put inside comments and that we can easily parse because we need to improve the use and discovery of the library. I was thinking about basename "Returns the base of the basename" " '/foo/gloops.taz' asFileReference basename >>> 'gloops.taz' " Do you have any idea? I cannot not do anything and just complain that our methods are not that well documented. We as a community should take this and build an super cool system. I tried and defined >>> on Object to see if it works! Object >>> aResultingObject "If the method comment contains >>> then it is a pharo documentated test. We can check that it is true." " '/foo/gloops.taz' asFileReference basename >>> 'gloops.taz' " ^ self = aResultingObject Stef

Sept. 15, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by stepharo

>> Would you highlight all string in all code as if it contained code? Or would you add this just for >> Pragmas? But even there, strings are string, not code. and then? you try and if it failed then in not code and you do not highlight it. KISS. No? >> I think we can conclude that pragmas are not a good solution to the problem, as they are far >> too limited to express code. > I second that. > Furthermore, typical examples require more than one liners, and these should be factored out separately. I'm talking about basename "Returns the base of the basename, i.e. /foo/gloops.taz basename is 'gloops.taz' / basename is '/'" I do not think that it makes sense to have a separate example for this. Because you want to read everything I do not see why the following would not work. basename "Returns the base of the basename" <expr: '''/foo/gloops.taz'' asFileReference basename' result: 'gloops.taz'> Now I hate the extra ' for strings. We should invent a syntax to be put inside comments and that we can easily parse because we need to improve the use and discovery of the library. basename "Returns the base of the basename" " '/foo/gloops.taz' asFileReference basename >>> 'gloops.taz' " I cannot not do anything and just complain that our methods are not that well documented. We as a community should take this and build an super cool system. Stef

Sept. 15, 2016

60224 TestRunner warning Collections-Arithmetic manually resolved dependency not detected as a dependency!

by Ben Coman

This curious warning appeared when running TestRunner in a fresh 60224.image... Collections-Abstract: Collections-Arithmetic dependency declared in the package Manifest as manuallyResolvedDependencies not detected as a dependency! There is... ManifestCollectionsArithmetic class >> dependencies ^ #(#'Collections-Native' #'Collections-Unordered' #'Collections-Sequenceable' #Kernel #'Collections-Abstract') and removing the last element makes the error go away, but I was wondering if that was the RightThing or the warning was a symptom for something else? btw, was is "manually resolved" ? Is it just adding elements to #dependencies? cheers -ben

Sept. 15, 2016

Re: [Pharo-dev] Author / TestRunner interaction in fresh image

by Marcus Denker

> On 15 Sep 2016, at 18:38, Ben Coman <btc(a)openinworld.com> wrote: > > In a freshly downloaded build 60224, I open TestRunner and run all > tests. At run 418 I get a dialogue asking for the Author. To me that > seems wrong. I don't want any code changes made during testing to > have my normal identification on them. Tests invoked from Test Runner > should be author-tagged something like 'TestRunner' or > 'TestRunner-BenComan'. > > The question arises in this particular case due to... > RPackageMonticelloSynchronisationTest >> setUp > ... > Author fullName ifNil: [ Author fullName: 'Tester' ]. > > Minor point... this check actually is a bit pointless since #fullName > invokes #requestFullName that presents the dialog. And #fullName will > *never* return nil. At a minimum it returns 'Anonymous'. > > First step would seem to be wrapping TestCase>>runCase: > with Author useAuthor: 'TestRunner' during: [ .... ] > Yes, something like this this would be good. > But further. I envisage a time when TestRunner doesn't block the UI, > so I can happily browse around the system and code while TestRunner is > doing its thing. Obviously the system is not set up to have two > parties (myself and TestRunner) both updating code in the system, but > changing the state of the global Author uniqueInstance like thisâ¦ > Yes, Nautilus used to fork running testsâ¦ leads to lots of strange problems. > > would itself seem to a big impediment. It would be good if "Author" > was dependent on the context of the call chain. This would seem a > requirement for one day having two people working in the one Image (is > this a possible use case where someone is using a remote debugger > while another person is using the standard UI?) > Could it be part of Denis new ExecutionEnvironment concept? Marcus

Sept. 15, 2016

Author / TestRunner interaction in fresh image

by Ben Coman

In a freshly downloaded build 60224, I open TestRunner and run all tests. At run 418 I get a dialogue asking for the Author. To me that seems wrong. I don't want any code changes made during testing to have my normal identification on them. Tests invoked from Test Runner should be author-tagged something like 'TestRunner' or 'TestRunner-BenComan'. The question arises in this particular case due to... RPackageMonticelloSynchronisationTest >> setUp ... Author fullName ifNil: [ Author fullName: 'Tester' ]. Minor point... this check actually is a bit pointless since #fullName invokes #requestFullName that presents the dialog. And #fullName will *never* return nil. At a minimum it returns 'Anonymous'. First step would seem to be wrapping TestCase>>runCase: with Author useAuthor: 'TestRunner' during: [ .... ] But further. I envisage a time when TestRunner doesn't block the UI, so I can happily browse around the system and code while TestRunner is doing its thing. Obviously the system is not set up to have two parties (myself and TestRunner) both updating code in the system, but changing the state of the global Author uniqueInstance like this... Author>>useAuthor: aString during: aBlock ^ self uniqueInstance useAuthor: aString during: aBlock would itself seem to a big impediment. It would be good if "Author" was dependent on the context of the call chain. This would seem a requirement for one day having two people working in the one Image (is this a possible use case where someone is using a remote debugger while another person is using the standard UI?) So my second proposal is for Author>>fullName to invoke a Notification mechanism to determine #fullName. Something like... Notification subclass: AuthorRequest Author>>#fullName ^ AuthorRequest new signal instanceVariables: 'contextFullName'. Author>>useAuthor: tempAuthorFullname during: aBlock [ block ] on: AuthorRequest do: [ :noti | noti contextFullName: tempAuthorFullname ] with only unhandled AuthorRequests returning "Author uniqueInstance basicFullname". Thus code changes are not constrained to be assigned to a global author. Not that we *yet* have multiple people working in one image, but one more impediment is removed - step by step. What concerns would there be? cheers -ben

Sept. 15, 2016

[pharo-project/pharo-core]

by GitHub

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

Sept. 15, 2016

[pharo-project/pharo-core] a5ac37: 60225

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a5ac374f7d5509a57e8bf39fc40c332026b0c2d3 https://github.com/pharo-project/pharo-core/commit/a5ac374f7d5509a57e8bf39f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-15 (Thu, 15 Sep 2016) Changed paths: A Collections-Tests.package/WeakSetTest.class/instance/testing/testAnyOneWhenAllContentsWasGarbaged.st A Collections-Weak.package/WeakSet.class/instance/accessing/anyOne.st A Kernel-Tests.package/ClassDescriptionTest.class/instance/tests - slots/testprintHierarchy.st A Kernel-Tests.package/ClassDescriptionTest.class/instance/tests - slots/testprintSubclassesOnLevelFilterA.st A Kernel-Tests.package/ClassDescriptionTest.class/instance/tests - slots/testprintSubclassesOnLevelFilterB.st A Kernel-Tests.package/ClassDescriptionTest.class/instance/tests - slots/testprintSubclassesOnLevelFilterNil.st M Monticello.package/MCPackageManager.class/class/system changes/methodModified_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60224.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60225.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60224.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60225.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SmalltalkImage.class/instance/sources%2C change log/systemInformationString.st M Traits.package/TClassDescription.class/instance/accessing class hierarchy/printSubclassesOn_level_.st A Traits.package/TClassDescription.class/instance/accessing class hierarchy/printSubclassesOn_level_filter_.st Log Message: ----------- 60225 19093 WeakSet anyOne is not work correctly when only nil there https://pharo.fogbugz.com/f/cases/19093 19089 About dialog: add a space to Pharo6.0... https://pharo.fogbugz.com/f/cases/19089 17881 loading package which add extension method to trait from external package makes loadable package dirty https://pharo.fogbugz.com/f/cases/17881 19077 extend ClassDescription>>printSubclassesOn:level: to have a filter https://pharo.fogbugz.com/f/cases/19077 http://files.pharo.org/image/60/60225.zip

Sept. 15, 2016

[pharo-project/pharo-core]

by GitHub

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

Sept. 15, 2016