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

On Sat, Sep 17, 2016 at 3:45 AM, Nicolai Hess wrote: > > > 2016-09-16 18:42 GMT+02:00 Eliot Miranda : >> >> Hi All, >> >> >> >> _,,,^..^,,,_ (phone) >> > On Sep 14, 2016, at 10:50 PM, Marcus Denker >> > wrote: >> > >> > >>

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

Yes, I will first cleanup the one in the book archetype, and unify it with the Enterprise & Spec books, since they seem to be the most up-to-date with Pillar. On 16 September 2016 at 21:19, stepharo wrote: > Damien Pollet started to have a look at the makefile and this is on

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

On 16 September 2016 at 20:42, stepharo wrote: > Daemons of over-engineering are tempting us because this is cooler to to > design something complex. > Dreaming of crazy features is a good thing. Talking from experience, I prefer that to not dreaming, which is pretty dull.

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

2016-09-16 18:42 GMT+02:00 Eliot Miranda : > Hi All, > > > > _,,,^..^,,,_ (phone) > > On Sep 14, 2016, at 10:50 PM, Marcus Denker > wrote: > > > > > >>> > >>> We can change it back and maybe add support for the reformatter to not > convert it to

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

Damien Pollet started to have a look at the makefile and this is on my todo to try. Stef Le 15/9/16 à 00:13, Johan Fabry a écrit : Hi Doru, it looks like there’s a problem with copySupport.mk, I had the same problem with the Spec booklet. The file is using Linux only syntax for the cp

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

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. Why don't we have yet package comments ? Just

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

Le 16/9/16 à 15:26, Damien Pollet a écrit : On 16 September 2016 at 13:42, Clément Bera > wrote: Why don't you just change nautilus to have two text areas, one with the test corresponding to the method and the other one with

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

This is what I thought first, we already have the association between methods and tests, Nautilus can detect if there is a corresponding test , for example browse Fraction>>truncated, it will show a test icon, that will run the test FractionTest>>#testTruncated. This works already good, and I

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

+ 1 Changing the language metamodel for simple validated comments is a huge effort for nothing. Clement is good at VM level but not at other level :) Stef Le 16/9/16 à 14:18, Denis Kudriashov a écrit : 2016-09-16 13:42 GMT+02:00 Clément Bera

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

Le 16/9/16 à 13:42, Clément Bera a écrit : Why don't you just change nautilus to have two text areas, one with the test corresponding to the method and the other one with the method's code ? You're saying: /Their values is active documentation that can be automatically validated./ That can

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

Hi 2016-09-16 13:21 GMT+02:00 stepharo >: - there is an overlap between examples and test cases. I saw many people that argued that already. I am not against examples, but I think we should (whichever implementation is chosen) draw a

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

Yes, that would be great. I just wander if the increased complexity pays off... normally if I am running my tests I do not have lots of tasks in mind, I will decide what to do next after seeing that my tests are green. Maybe I just want to browse some code, I do not need super fancy

Re: [Pharo-dev] Maintainer of DependencyAnalyser: Action needed

This is christophe! Whoever maintains DependencyAnalyser: There is a fix ready since 22 August 2016. We need to get this into the system *soon*. https://pharo.fogbugz.com/f/cases/18963/DANode-browseClass-sends-unimplemented-fullOnClas Marcus

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

Hi All, _,,,^..^,,,_ (phone) > On Sep 14, 2016, at 10:50 PM, Marcus Denker 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 :)

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

How is all of this PackageManifest mechanism working? Doc anywhere? Phil Le 16 sept. 2016 17:02, "Nicolai Hess" a écrit : 2016-09-16 0:19 GMT+02:00 p...@highoctane.be : > I'd be more interested with a package level doc than a class doc or test. >

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

2016-09-16 0:19 GMT+02:00 p...@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 >

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

Sorry for the mistake, 2016-09-16 15:51 GMT+02:00 Damien Pollet : > On 16 September 2016 at 15:35, Thierry Goubier > wrote: > >> Could we have a Pillar-way of organizing comments so that, based on >> sections, one could automatically find,

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

2016-09-16 15:51 GMT+02:00 Damien Pollet : > On 16 September 2016 at 15:35, Thierry Goubier > wrote: > >> Could we have a Pillar-way of organizing comments so that, based on >> sections, one could automatically find, from a book-like comment of

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

Yes, that would be great. I just wander if the increased complexity pays off... normally if I am running my tests I do not have lots of tasks in mind, I will decide what to do next after seeing that my tests are green. Maybe I just want to browse some code, I do not need super fancy features.

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

Another example: https://docs.racket-lang.org/scribble/index.html First example: https://docs.racket-lang.org/scribble/getting-started.html#%28part._first-example%29 On Fri, Sep 16, 2016 at 10:51 AM, Damien Pollet wrote: > On 16 September 2016 at 15:35, Thierry

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

Original Message On Fri, Sep 16, 2016 at 12:47 PM, Marcus Denker > wrote: > On 16 Sep 2016, at 12:43, Nicolas Passerini > wrote: > > I think it

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

On 16 September 2016 at 15:35, Thierry Goubier wrote: > Could we have a Pillar-way of organizing comments so that, based on > sections, one could automatically find, from a book-like comment of the > package or the class, which section applies to a given method? I

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

2016-09-16 15:26 GMT+02:00 Damien Pollet : > On 16 September 2016 at 13:42, Clément Bera > wrote: > >> Why don't you just change nautilus to have two text areas, one with the >> test corresponding to the method and the other one with the method's

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

On 16 September 2016 at 13:42, Clément Bera wrote: > Why don't you just change nautilus to have two text areas, one with the > test corresponding to the method and the other one with the method's code ? Exactly, we already have that with class comments, so why not

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

2016-09-16 14:25 GMT+02:00 Nicolai Hess : > > > 2016-09-16 13:42 GMT+02:00 Clément Bera : > >> Why don't you just change nautilus to have two text areas, one with the >> test corresponding to the method and the other one with the method's code ? >>

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1

Anyone can help here ? On Wed, Sep 14, 2016 at 7:26 PM, Serge Stinckwich wrote: > Always same error message ... > > ExternalAddress loadSymbol: 'Rf_initEmbeddedR' from: RLibrary > > returns FailedPrimitive > > On Wed, Sep 14, 2016 at 3:55 PM, Blondeau Vincent >

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

2016-09-16 13:42 GMT+02:00 Clément Bera : > Why don't you just change nautilus to have two text areas, one with the > test corresponding to the method and the other one with the method's code ? > > You're saying: > *Their values is active documentation that can be

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

2016-09-16 13:42 GMT+02:00 Clément Bera : > Why don't you just change nautilus to have two text areas, one with the > test corresponding to the method and the other one with the method's code ? > > You're saying: > *Their values is active documentation that can be

Re: [Pharo-dev] Maintainer of TxText: action needed

As of now, I do not think there is any maintainer of TxText. Doru > On Sep 16, 2016, at 1:28 PM, stepharo wrote: > > Marcus we should integrate it. > > > Le 16/9/16 à 13:22, Marcus Denker a écrit : >> Hi, >> >> Whoever maintains TxTxt: there is a fix ready since 19 July

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

Why don't you just change nautilus to have two text areas, one with the test corresponding to the method and the other one with the method's code ? You're saying: *Their values is active documentation that can be automatically validated.* That can also be applied to test we've already had with

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

On Fri, Sep 16, 2016 at 12:47 PM, Marcus Denker wrote: > > > On 16 Sep 2016, at 12:43, Nicolas Passerini > wrote: > > > > I think it would be nice to be able to run tests in background. > > > > The easiest is to start multiple images… this way they

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

Hi 2016-09-16 13:21 GMT+02:00 stepharo : > - there is an overlap between examples and test cases. I saw many people > that argued that already. I am not against examples, but I think we should > (whichever implementation is chosen) draw a line and set some guidelines. > > To

[Pharo-dev] [pharo-project/pharo-core] b402df: 60227

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b402df88fd1de5a005362c220e24808cbf004c27 https://github.com/pharo-project/pharo-core/commit/b402df88fd1de5a005362c220e24808cbf004c27 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

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

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

2016-09-16 12:43 GMT+02:00 Nicolas Passerini : > I think it would be nice to be able to run tests in background. > > What would be the problem? A test case that fails because you were doing > something at the same time? I think it is not so serious, it is up to you > to know

Re: [Pharo-dev] Maintainer of TxText: action needed

Marcus we should integrate it. Le 16/9/16 à 13:22, Marcus Denker a écrit : Hi, Whoever maintains TxTxt: there is a fix ready since 19 July 2016. Can we get this into the system, please? https://pharo.fogbugz.com/f/cases/18788/TxTextStyler-do-not-work (or we should give up

[Pharo-dev] Maintainer of DependencyAnalyser: Action needed

Whoever maintains DependencyAnalyser: There is a fix ready since 22 August 2016. We need to get this into the system *soon*. https://pharo.fogbugz.com/f/cases/18963/DANode-browseClass-sends-unimplemented-fullOnClas Marcus

[Pharo-dev] Maintainer of TxText: action needed

Hi, Whoever maintains TxTxt: there is a fix ready since 19 July 2016. Can we get this into the system, please? https://pharo.fogbugz.com/f/cases/18788/TxTextStyler-do-not-work (or we should give up in this being maintained “externally”)

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

Hi, I was thinking on the metro way to work, and I also saw that this discussion is actually split in multiple threads, so it was not easy to follow :). Some of my feelings about this: - Pragmas are nice because they are easy to "interpret". Parsing them is already provided. However,

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

> On 16 Sep 2016, at 12:43, Nicolas Passerini wrote: > > I think it would be nice to be able to run tests in background. > The easiest is to start multiple images… this way they can destroy whatever without impacting you. I think Guille has something in preparation…

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

I think it would be nice to be able to run tests in background. What would be the problem? A test case that fails because you were doing something at the same time? I think it is not so serious, it is up to you to know which tests did you run and do nothing that would conflict with the test run.

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

2016-09-15 18:46 GMT+02:00 Marcus Denker : > > 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

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

Hi. 2016-09-15 18:38 GMT+02:00 Ben Coman : > 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

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

> On 16 Sep 2016, at 10:02, Guille Polito wrote: > > Hi, > > I was thinking on the metro way to work, and I also saw that this discussion > is actually split in multiple threads, so it was not easy to follow :). > > Some of my feelings about this: > > - Pragmas

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

On Thu, Sep 15, 2016 at 10:09 PM, Tudor Girba wrote: > 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

Re: [Pharo-dev] 60224 TestRunner warning Collections-Arithmetic manually resolved dependency not detected as a dependency!

Some dependendies cannot be easily detected in a static way. For example, when you use reflection, or when you send a polymorphic message that has implementations over many packages. In such cases, it is not obvious for the tool to see what is the actual dependency. Then, the user can resolve

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

Hi, I was thinking on the metro way to work, and I also saw that this discussion is actually split in multiple threads, so it was not easy to follow :). Some of my feelings about this: - Pragmas are nice because they are easy to "interpret". Parsing them is already provided. However,

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

error not related, build works well after restart -- Pavel 2016-09-15 22:11 GMT+02:00 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:

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

I will play with it :) I was thinking to have >>> instead of association to make sure that we can disambiguate from -> Thanks for the protoype. This kind of little action can change completely the face of Pharo library. I always ***LOVED*** little examples inside method when I discovered

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

Le 16/9/16 à 00:19, p...@highoctane.be a écrit : I'd be more interested with a package level doc than a class doc or test. It is at another level and it will come. The manisfest is here and we should update Nautilus to show other information. Now I'm curious to see how many people will use

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

Le 15/9/16 à 22:16, Esteban A. Maringolo a écrit : 2016-09-15 17:09 GMT-03:00 Tudor Girba : 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

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

2016-09-16 8:54 GMT+02:00 stepharo : > > 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

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

On Fri, Sep 16, 2016 at 2:45 AM, stepharo 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

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

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

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

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