- Pharo-dev - lists.pharo.org

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

by stepharo

> So, until know, I didn't really know what pythondoctest is about. I > first thought the "test" is about unit tests > and thought our way how we can generate or jump from methods to the > corresponding is better, > but know I understand that it is about "perform regression testing by > verifying that interactive examples are working" > And that is of course a good idea. To me this is more than that. This is having simple scenario always validated and in front of my nose when I read the code. > > > If we have ' ' then it would be good that the syntax higlighter > works with a special mode inside the ' ' > > > Not for pragma arguments, I think this would be confusing. Yes I cam to the same conclusion than marcus. > > I did some expreiments with formatting code in comments. I 'll write > shortly about it. > >> >> >> nicolai >> >> >> >> Stef >> >> >> 60220 >> 19086 do not allow expressions as pragma arguments >> https://pharo.fogbugz.com/f/cases/19086 >> <https://pharo.fogbugz.com/f/cases/19086> >> >> >> >> > >

Sept. 16, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by Ben Coman

On Fri, Sep 16, 2016 at 2:45 AM, stepharo <stepharo(a)free.fr> wrote: > 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? basename "Returns the base of the basename" """ '/foo/gloops.taz' asFileReference basename ==> 'gloops.taz' """ self size == 0 "the root node" ifTrue: [ ^ '/']. ^ self at: self size I like this idea. But a fine semantic.... We should think of these less as "tests" and more as "howto" snippets that are tested for correctness. They should show just the *simplest* was to get an object to which the method can be sent. Maybe they could be also displayed via the gtExample interface ?? cheers -ben

Sept. 15, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by phil＠highoctane.be

I'd be more interested with a package level doc than a class doc or test. Package level doc is quite useful to outline how some things are working together, something which is quite hard to figure out except by reading external doc or inferring things by walking through the code or a running test. Having the ability to read about a package would be very useful. Basically, this is what Java provides. http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javadoc.html#p… Phil On Thu, Sep 15, 2016 at 8:45 PM, stepharo <stepharo(a)free.fr> wrote: > 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] Call for design for a literal programming doc similar to PythonDocTest

by Nicolai Hess

2016-09-15 20:45 GMT+02:00 stepharo <stepharo(a)free.fr>: > 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 > > Ok, this is a quick hack ( do not look at the code :), yes using regex here is a bit fragil) You can add code in comments between backticks (`) The formatter will highlight the text like smalltalk code (or not if it is not valid code). + an icon styler with an icon showing a warning icon for faulty code or an information icon otherwise you can click on the icon, if the code is an association expression -> result it executes the expression and compares it with the result, (with assert:equals: ) opens debugger if it fails and does nothing otherwise if the code is just an expression, it opens an inspector. This is just one way to do some tests and experiments with this idea, don 't yet know if this is a good idea or if we can / should find a better way to connect code with examples. first result, I find expressions in comments, highlighted as code, confusing :) (file in attached cs in a recent pharo 6.0 and look at the method AbstractFileReference>>#baseName . Or add an expression with backticks in a method comment ` your code here ` > > Stef > > >

Sept. 15, 2016

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

by Tudor Girba

Hi, > On Sep 15, 2016, at 10:16 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-09-15 8:12 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > > On Sep 15, 2016, at 7:50 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > >>> > >>> We can change it back and maybe add support for the reformatter to not convert it to the literal array #(3 #+ 4) . > >> > >> I do not know in fact this is why I asked :) > >> Now may be my idea to use pragma to get something like pythondoctest is a bad idea > >> but I really want to have literal programming. > >> What do you think? > >> > > I like the idea to show examples/tests close to code, but pragmas are not really good... > > > >> If we have ' ' then it would be good that the syntax higlighter works with a special mode inside the ' ' > > > > it is just a string. How do you know that it contains code? > > > > 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. > > > > 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 really like the one liners that you can find im some method comments, like in Color class>>#wheel: > if you are new to pharo and start exploring the system, it makes fun to see these little one lines and > just execute it. (even if they aren't onelines like in some method in class Form). > I like one liners, too. But, should a documentation mechanism be confined to only work with small examples? Cheers, Doru > Cheers, > Doru > > > > > > Marcus > > > > > > > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing should have the right to be different." -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

Sept. 15, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by Esteban A. Maringolo

2016-09-15 17:09 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > However, one thing to keep in mind is that one reason why these solutions exist is because they assume no UI environment. Thus, the only thing they have is text and the solution is built around it. > > In Pharo, we can think of concatenating information in the environment. If we have a casual connection between examples and the code they exemplify, the interface can provide all this information at the same time. The advantage here is that the syntax remains simple. +1 I wouldn't like that syntax, nor PharoDoc (a la JavaDoc), nor anything "polluting" the code that way. The comment or examples can be attributes of the method itself, just like the class comment are today. Regards! Esteban A. Maringolo

Sept. 15, 2016

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

by Nicolai Hess

2016-09-15 8:12 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > > On Sep 15, 2016, at 7:50 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > > > > >>> > >>> We can change it back and maybe add support for the reformatter to not > convert it to the literal array #(3 #+ 4) . > >> > >> I do not know in fact this is why I asked :) > >> Now may be my idea to use pragma to get something like pythondoctest is > a bad idea > >> but I really want to have literal programming. > >> What do you think? > >> > > I like the idea to show examples/tests close to code, but pragmas are > not really good... > > > >> If we have ' ' then it would be good that the syntax higlighter works > with a special mode inside the ' ' > > > > it is just a string. How do you know that it contains code? > > > > 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. > > > > 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 really like the one liners that you can find im some method comments, like in Color class>>#wheel: if you are new to pharo and start exploring the system, it makes fun to see these little one lines and just execute it. (even if they aren't onelines like in some method in class Form). > > Cheers, > Doru > > > > > > Marcus > > > > > > > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing should have the right to be different." > > > > > >

Sept. 15, 2016

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

by Nicolai Hess

2016-09-14 21:24 GMT+02:00 stepharo <stepharo(a)free.fr>: > > Hi nicolai >> >> Why we should not accept >> >> foo >> <func: (3+4) res:0> >> ^ self >> >> and be forced to put around '' >> >> foo >> < func: '(3+4)' res: 0 > >> ^ self >> >> I understand that we store literal but why you do not like it :). >> > > First of all, the old compiler did not accept this. And I am a bit > sensitive about changes, we allow a different syntax > just because RB happens to allow this (and maybe no one knows why or it > just does not happens on purpose). > > > valid point. > > > And another reason, even without my fix, if we don't put quotes around > that expression, the reformatting the source will convert this to: > > foo > <func: #(3 #+ 4) res: 0> > ^ self > > What I noticed is that I could not write > > foo > <expr: 3 + 4 result: 7> > > but it worked when I put () so I did it in the new code I wrote. > > And, even if (3+4) looks like an expression, it is just a list of literals > something like this: > > foo > <func: ([[[}}}) res:0> > ^ self > > would be allowed too. > > This one is ugly > > But of course this is only my own opinion :) > > We can change it back and maybe add support for the reformatter to not > convert it to the literal array #(3 #+ 4) . > > > I do not know in fact this is why I asked :) > Now may be my idea to use pragma to get something like pythondoctest is a > bad idea > but I really want to have literal programming. > What do you think? > So, until know, I didn't really know what pythondoctest is about. I first thought the "test" is about unit tests and thought our way how we can generate or jump from methods to the corresponding is better, but know I understand that it is about "perform regression testing by verifying that interactive examples are working" And that is of course a good idea. > > If we have ' ' then it would be good that the syntax higlighter works with > a special mode inside the ' ' > Not for pragma arguments, I think this would be confusing. I did some expreiments with formatting code in comments. I 'll write shortly about it. > > > nicolai > > > >> Stef >> >> >> 60220 >>> 19086 do not allow expressions as pragma arguments >>> https://pharo.fogbugz.com/f/cases/19086 >>> >> >> >> > >

Sept. 15, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 4d8aa6: 60226

by stepharo

This change break the miniimage. I will check with pavel. Stef Le 15/9/16 Ã 22:05, GitHub a Ã©crit : > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 4d8aa66f6cb150f6aef66a9d807106bb89404cf5 > https://github.com/pharo-project/pharo-core/commit/4d8aa66f6cb150f6aef66a9d… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2016-09-15 (Thu, 15 Sep 2016) > > Changed paths: > M FontChooser.package/AbstractFontSelectorDialogWindow.class/class/icons/taskbarIcon.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousAccept.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousAdd.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousAlarm.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousBookmark.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousBrowse.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousBug.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousCancel.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousClose.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousDown.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousDropDown.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousEdit.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousExample.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousFolder.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousGo.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousGrayCircle.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousGrayCircleEmpty.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousGreenCircle.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousHelp.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousInspect.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousInto.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousLargeGrayCircleEmphasized.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousLeft.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousLeftSide.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousMore.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousOpen.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousOpenFromUrl.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousOver.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousPlay.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRedCircle.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRedo.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRefresh.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRemove.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRestart.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRight.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousRightSide.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousSave.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousSaveToUrl.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousSearch.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousSpawn.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousThrough.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousTrash.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousUndo.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousUp.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousZoomIn.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousZoomOut.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamorousZoomToFit.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamourousNextFailure.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamourousNextParser.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/class/icons/glamourousNextProduction.st > M Glamour-Morphic-Theme.package/GLMUIThemeExtraIcons.class/definition.st > M HelpSystem-Core.package/ClassAPIHelpBuilder.class/instance/private building/buildSubnodesForMethods.st > M HelpSystem-Core.package/ClassAPIHelpBuilder.class/instance/private building/buildSubnodesForSubclasses.st > M MonticelloGUI.package/MCSaveVersionDialog.class/class/icons/taskbarIcon.st > M MonticelloGUI.package/MCVersionInspector.class/class/icons/taskbarIcon.st > M MonticelloGUI.package/MCWorkingCopyBrowser.class/class/icons/taskbarIcon.st > A Morphic-Base.package/MenuMorph.class/class/icons/iconNamed_.st > M Morphic-Base.package/MenuMorph.class/class/private - utilities/confirm_trueChoice_falseChoice_.st > A Morphic-Core.package/Morph.class/class/icons/iconNamed_.st > A Morphic-Core.package/Morph.class/instance/icons/iconNamed_.st > M Morphic-Examples.package/WidgetExamples.class/class/examples/exampleGroups.st > M Morphic-Examples.package/WidgetExamples.class/class/examples/exampleWindowWithToolbars.st > M Morphic-Examples.package/WidgetExamples.class/definition.st > M Morphic-Widgets-Basic.package/ThreePhaseButtonMorph.class/class/instance creation/checkBox.st > M Morphic-Widgets-Basic.package/ThreePhaseButtonMorph.class/class/instance creation/radioButton.st > M Morphic-Widgets-PolyTabs.package/TabGroupMorph.class/class/example/example.st > M Morphic-Widgets-Windows.package/SystemWindow.class/class/icons/taskbarIcon.st > M Morphic-Widgets-Windows.package/SystemWindow.class/class/menu items/windowMenuOn_.st > M Nautilus.package/CategoryWidget.class/instance/icon/categoryIconFor_.st > M Nautilus.package/NautilusMonticello.class/class/monticello menus/packagesChangesMenu_.st > M Nautilus.package/NautilusMonticello.class/class/monticello menus/packagesCommitsMenu_.st > M Nautilus.package/NautilusMonticello.class/class/monticello menus/packagesCreateMenu_.st > M Nautilus.package/NautilusMonticello.class/class/monticello menus/packagesOpenMenu_.st > M Nautilus.package/NautilusMonticello.class/definition.st > M Polymorph-Widgets.package/AboutDialogWindow.class/class/instance creation/openForPharo.st > M Polymorph-Widgets.package/AlertDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/ChooseDropListDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/DenyDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/ErrorDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/MessageDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/PopupChoiceDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/ProceedDialogWindow.class/class/icons/taskbarIcon.st > M Polymorph-Widgets.package/TextEditorDialogWindow.class/class/icons/taskbarIcon.st > M ProfStef-Core.package/ProfStef.class/class/zen/menuCommandOn_.st > M ProfStef-Core.package/ProfStef.class/definition.st > M RecentSubmissions.package/RecentMessageList.class/class/icons/icon.st > M SUnit-UI.package/TestRunner.class/class/icons/taskbarIcon.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60225.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60226.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60225.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60226.st > M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/assignment/createInlineTemporary.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/class-var/createAccessors.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/class-var/createRenameClassVariable.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/class-var/createUseAccessorToVar.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/class/createBrowseReferences.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/class/createRenameClass.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/inst-var/createAccesorsFor.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/inst-var/createAccessesToVariable.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/inst-var/createRenameVariable.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/inst-var/createVariableStoresInto.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/messages/createFindImplementors.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/messages/createFindSenders.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/messages/createInline.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createAddParameter.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createBreakCommand.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createBreakConditionCommand.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createBreakOnceCommand.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createCounterCommand.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createDeprecateMethod.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createMoveMethod.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createPullUp.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createPushDown.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createRemoveMethod.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createRemoveParameter.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createRenameMethod.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createSwapMethod.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/methods/createWatchpointCommand.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/source/createExtractMethod.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/source/createExtractSentences.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/source/createExtractToLocalVariable.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/source/createFormatSourceCode.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/temp-var/createRenameTemporaryVariable.st > M SmartSuggestions.package/SugsSuggestionFactory.class/class/unknown-var/createVariableCorrection.st > M SmartSuggestions.package/SugsSuggestionFactory.class/definition.st > M Spec-Core.package/TreeModel.class/class/examples/exampleWithCustomColumnsAndNodes.st > M Spec-Inspector.package/AbstractEyeElement.class/definition.st > R Spec-Inspector.package/AbstractEyeElement.class/instance/icon/iconNamed_.st > R Tool-Base.package/AbstractTool.class/instance/icon/iconNamed_.st > M Tool-Base.package/AbstractTool.class/instance/icon/icon_.st > R Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/initialization/setTextModelForTransformationRule_.st > M Tool-FileList.package/FileDialogWindow.class/class/icons/taskbarIcon.st > M Tool-ProcessBrowser.package/ProcessBrowser.class/class/icons/taskbarIcon.st > M Tool-Profilers.package/TimeProfiler.class/class/icons/taskbarIcon.st > M Tool-Profilers.package/TimeProfiler.class/class/opening/fullReportMenuOn_.st > M Tool-Workspace.package/Workspace.class/class/icons/taskbarIcon.st > M Transcript.package/ThreadSafeTranscript.class/class/icons/taskbarIcon.st > M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/class/icons/configurationChangedIcon.st > M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/class/icons/configurationLoadedIcon.st > M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/class/ui/menuCommandOn_.st > M Versionner-Spec-Browser.package/VersionnerToolBar.class/class/icons/loadIcon.st > M Versionner-Spec-Browser.package/VersionnerToolBar.class/class/icons/newIcon.st > M Versionner-Spec-Browser.package/VersionnerToolBar.class/class/icons/openIcon.st > > Log Message: > ----------- > 60226 > 19094 cleaning iconNamed: > https://pharo.fogbugz.com/f/cases/19094 > > http://files.pharo.org/image/60/60226.zip > >

Sept. 15, 2016

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

by Tudor Girba

Hi, I think this is an interesting idea. However, one thing to keep in mind is that one reason why these solutions exist is because they assume no UI environment. Thus, the only thing they have is text and the solution is built around it. In Pharo, we can think of concatenating information in the environment. If we have a casual connection between examples and the code they exemplify, the interface can provide all this information at the same time. The advantage here is that the syntax remains simple. At the same time, we also want to have Pillar more thoroughly supported in our tools. Could it be that we could extend Pillar to support literate programming? Cheers, Doru > On Sep 15, 2016, at 8:45 PM, stepharo <stepharo(a)free.fr> wrote: > > 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 > > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

Sept. 15, 2016