Re: [Pharo-dev] Issue with last line / line ending between FileTree and other repositoroes

2013-11-13 Thread Goubier Thierry
Hi Mariano, it is probably a bug in the way the changes are computed: in MC usually, if the timestamp of a method changes, then this is a change, even if the source code are exactly the same... No need to search for a missing end of line character :). I have been pushing for integration of

[Pharo-dev] [pharo-project/pharo-core] 7a468a: 30568

2013-11-13 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 7a468acff5960957559f8cd3760f3ce487570864 https://github.com/pharo-project/pharo-core/commit/7a468acff5960957559f8cd3760f3ce487570864 Author: Jenkins Build Server bo...@pharo-project.org Date:

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

2013-11-13 Thread GitHub
Branch: refs/tags/30568 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] smalltalkhub.com down

2013-11-13 Thread Nicolas Petton
Hi guys, I'm working on a new release of smalltalkhub. I will also check what is making it crash and monitor the website. I think I will also move the service to Inria infrastructure in the short future. Cheers, Nico Mariano Martinez Peck writes: On Tue, Nov 12, 2013 at 11:05 PM, Stéphane

[Pharo-dev] [pharo-project/pharo-core] 5061af: 30569

2013-11-13 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 5061afcc6b94bf49966bc30282409e08a25b4912 https://github.com/pharo-project/pharo-core/commit/5061afcc6b94bf49966bc30282409e08a25b4912 Author: Jenkins Build Server bo...@pharo-project.org Date:

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

2013-11-13 Thread GitHub
Branch: refs/tags/30569 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] smalltalkhub.com down

2013-11-13 Thread p...@highoctane.be
What would be cool is to have a kind of static mirror for all the mcz's so that we can go there in case of trouble. --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:p...@highoctane.be | Web: http://philippeback.eu Blog:

Re: [Pharo-dev] smalltalkhub.com down

2013-11-13 Thread Norbert Hartl
Am 13.11.2013 um 10:59 schrieb p...@highoctane.be: What would be cool is to have a kind of static mirror for all the mcz's so that we can go there in case of trouble. I didn’t look at the architecture of smalltalkhub. I only know everything is put into mongo and I can imagine the rationale

Re: [Pharo-dev] multiple files in pillar

2013-11-13 Thread Stéphane Ducasse
At the moment, Pillar assumes that one file is one chapter. When generating PDF, an index .tex file is required to construct the overall book with table of contents and others such elements. As far as I see, in HTML, there is no possibility of generating this Is there a plan to

Re: [Pharo-dev] multiple files in pillar

2013-11-13 Thread Tudor Girba
Hi, On Wed, Nov 13, 2013 at 11:18 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: At the moment, Pillar assumes that one file is one chapter. When generating PDF, an index .tex file is required to construct the overall book with table of contents and others such elements. As far as

Re: [Pharo-dev] PharoV20.source

2013-11-13 Thread Camille Teruel
On 12 nov. 2013, at 23:54, Clément Bera bera.clem...@gmail.com wrote: Hello, Currently the idea is to put the source file as a compressed AST in the image. The status is: - standard AST is 300Mb for the whole image, which is too much - standard AST with nodes shared between

Re: [Pharo-dev] PharoV20.source

2013-11-13 Thread p...@highoctane.be
Very exciting developments. How would you keep sources and changes segregated BTW? (if we can still call them like that). --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:p...@highoctane.be | Web: http://philippeback.eu Blog:

Re: [Pharo-dev] multiple files in pillar

2013-11-13 Thread Stéphane Ducasse
On Nov 13, 2013, at 11:28 AM, Tudor Girba tu...@tudorgirba.com wrote: Hi, On Wed, Nov 13, 2013 at 11:18 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: At the moment, Pillar assumes that one file is one chapter. When generating PDF, an index .tex file is required to construct

Re: [Pharo-dev] petit parser repository

2013-11-13 Thread Norbert Hartl
Am 12.11.2013 um 13:53 schrieb Stephan Eggermont step...@stack.nl: Just try with .44 Thanks very much Stephan, looks pretty good for me. Norbert

Re: [Pharo-dev] PharoV20.source

2013-11-13 Thread Stéphane Ducasse
Anyway, even if at the end it takes more memory than the current source file, we should not forget that having persistant ASTs that you can freely annotate brings far more than compression, it opens *many* doors :) The annotations on the nodes would take memory too. Well, at least for the

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Christophe Demarey
Hi, I have some questions: 1/ Before the removal of morphic dependencies in spec, I used aNode selectedNode parentNode item to get the parent of the selected item. What is the new way to do that? 2/ I also defined specific nodes for a Tree model. These nodes overrode the childrenItems

Re: [Pharo-dev] PharoV20.source

2013-11-13 Thread Marcus Denker
On 13 Nov 2013, at 12:02, p...@highoctane.be wrote: Very exciting developments. How would you keep sources and changes segregated BTW? (if we can still call them like that). changes are modelled by Martin’s system (EPICEA). Marcus

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Benjamin
Ben On 13 Nov 2013, at 12:43, Christophe Demarey christophe.dema...@inria.fr wrote: Hi, I have some questions: 1/ Before the removal of morphic dependencies in spec, I used aNode selectedNode parentNode item to get the parent of the selected item. What is the new way to do that?

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Benjamin
Stef, what is the advantages of writing it in Pier compared to markdown ? Ben

Re: [Pharo-dev] Questions about Athens

2013-11-13 Thread Igor Stasenko
I doubt it is related to Athens. I think it is initialization problem. If morph's extent depends on external factors, you should properly initialize them before computing it. It could be that you calling #checkSession before.. which leads to DNU, because no extent can be computed at given point

Re: [Pharo-dev] Where is the FileDirectory-based version of ZnFileSystemUtils?

2013-11-13 Thread Mariano Martinez Peck
On Wed, Nov 13, 2013 at 3:36 AM, Sven Van Caekenberghe s...@stfx.eu wrote: On 13 Nov 2013, at 03:08, Mariano Martinez Peck marianop...@gmail.com wrote: Hi Sven, I was seeing your code of ZnFileSystemUtils ... yes... I probably need the same... but I miss the other subclass ;) that

Re: [Pharo-dev] Instrumenting field accesses with Opal?

2013-11-13 Thread Camille Teruel
On 13 nov. 2013, at 14:21, Alexandre Bergel alexandre.ber...@me.com wrote: Hi! Is there a way to get notified when fields are accessed? That would be awesome You can use the current reflectivity prototype. It's on RMoD CI: https://ci.inria.fr/rmod/job/Reflectivity/ It should look like

Re: [Pharo-dev] PharoV20.source

2013-11-13 Thread Igor Stasenko
2 cents. just want to make a note, it is important to preserve original text (yes i am talking about formatting, spacing, tabs etc).. because without it i can easily imagine you can raise compression ration to the skies.. but as to me the original text is important part of game. On 13 November

Re: [Pharo-dev] Instrumenting field accesses with Opal?

2013-11-13 Thread Marcus Denker
On 13 Nov 2013, at 14:44, Camillo Bruni camillobr...@gmail.com wrote: On 2013-11-13, at 14:42, Camille Teruel camille.ter...@gmail.com wrote: On 13 nov. 2013, at 14:21, Alexandre Bergel alexandre.ber...@me.com wrote: Hi! Is there a way to get notified when fields are accessed? That

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Nicolas Cellier
Yes, a Wrapper would provide the legacy API. And yes, the name of a stream should better not be part of the API. Most stream don't have a name, and adding such API adds all sort of un-needed complexity. It's an internal detail that can eventually help for reporting error if accessible, but

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Chris Muller
I know nothing about Xtreams but, IMO, this obsession with sterility borders on mental illness. All sort of un-needed complexity? That's overstating it a bit, don't you think? So you must really feel stressed that ALL Object's, in fact, have a #name, huh? I admit this seems to push the limits

Re: [Pharo-dev] NativeBoost: Documentation Suggestion and Question

2013-11-13 Thread Sean P. DeNigris
Igor Stasenko wrote PaError Pa_OpenDefaultStream(NBExternalAddress * stream ... ) then your call site will look like following: streamHandle := NBExternalAddress new. Okay, one step closer. I somewhat randomly guessed to use NBExternalAddress, but didn't have the correct thing in the

[Pharo-dev] Fwd: In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Nicolas Cellier
-- Forwarded message -- From: Nicolas Cellier nicolas.cellier.aka.n...@gmail.com Date: 2013/11/13 Subject: Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic The long answer is simple: the more responsibility you put in Stream, the more complexity you get.

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Nicolas Cellier
Just forgot to add this reductio ad absurdum: I suggest Object ^'John Doe', this is a relatively current name, so it shouldn't hurt. 2013/11/13 Nicolas Cellier nicolas.cellier.aka.n...@gmail.com -- Forwarded message -- From: Nicolas Cellier nicolas.cellier.aka.n...@gmail.com

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
I give up. Stef On Nov 13, 2013, at 1:19 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: Stef, what is the advantages of writing it in Pier compared to markdown ? Ben

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
do it in whatever you want but do not ask me to edit it nor to put it in our book. Stef On Nov 13, 2013, at 1:19 PM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: Stef, what is the advantages of writing it in Pier compared to markdown ? Ben

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
do you really think that I insist of using pier syntax because A- I want to lose my time B- this is for my ego? C- because I'm funny D- ... No seriously? If you want to get an answer read the thread that yuri raised a while ago. Because we already discussed

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
What is the point of this folder? Do you expect us to write documentation there? Why do you systematically are again pier? especially when I wrote successfully the seaside book with it and so far the only book I saw using markdown are not book? May be I should go back to write in plain latex

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Frank Shearar
On 13 November 2013 16:48, Chris Muller asquea...@gmail.com wrote: I know nothing about Xtreams but, IMO, this obsession with sterility borders on mental illness. All sort of un-needed complexity? That's overstating it a bit, don't you think? So you must really feel stressed that ALL

Re: [Pharo-dev] Instrumenting field accesses with Opal?

2013-11-13 Thread Alexandre Bergel
Thanks for discussing this issue. This is really interesting! Alexandre On Nov 13, 2013, at 12:02 PM, Camille Teruel camille.ter...@gmail.com wrote: On 13 nov. 2013, at 15:18, Andrei Chis chisvasileand...@gmail.com wrote: YourClass methods do: [ :method | method ast

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Benjamin
It was a real question, and it feels like you overreacted the answer … To me, markdown or pier is a new syntax to learn so I am asking … To me, doing Pier because you do or because you said to is no really an argument. Then I am open to a real answer but I also see that markdown is integrated

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Sven Van Caekenberghe
On 13 Nov 2013, at 19:59, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: It was a real question, and it feels like you overreacted the answer … To me, markdown or pier is a new syntax to learn so I am asking … To me, doing Pier because you do or because you said to is no really an

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Nicolas Cellier
Exactly, every specialized stream has its specialized API and/or specialized implementation. File streams don't even have a name, because they need not to. You can browse XTFileReadStream and XTFileWriteStream, you won't find such thing. The file has a name, the stream does not need any. Before

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Benjamin
On 13 Nov 2013, at 20:05, Sven Van Caekenberghe s...@stfx.eu wrote: On 13 Nov 2013, at 19:59, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: It was a real question, and it feels like you overreacted the answer … To me, markdown or pier is a new syntax to learn so I am asking …

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Alexandre Bergel
Why not generating markdown code from pier code? If the whole problem is exposure on the web. Someone has considered pdf2html or latex2html? Maybe my question is naive, I do not know. On some point, i have tried to generate the roassal documentation from the Roassal Help, but it makes the

Re: [Pharo-dev] PharoV20.source

2013-11-13 Thread Stéphane Ducasse
Anyway, even if at the end it takes more memory than the current source file, we should not forget that having persistant ASTs that you can freely annotate brings far more than compression, it opens *many* doors :) The annotations on the nodes would take memory too. Well, at least for the

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Sven Van Caekenberghe
On 13 Nov 2013, at 20:22, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: On 13 Nov 2013, at 20:05, Sven Van Caekenberghe s...@stfx.eu wrote: On 13 Nov 2013, at 19:59, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: It was a real question, and it feels like you overreacted

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Sven Van Caekenberghe
On 13 Nov 2013, at 20:22, Alexandre Bergel alexandre.ber...@me.com wrote: Why not generating markdown code from pier code? If the whole problem is exposure on the web. Someone has considered pdf2html or latex2html? Maybe my question is naive, I do not know. It is not silly, and yes it could

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
So read the thread that yuriy rasied last week my sumarry - write in pier publish in latex, html, markdong - too many variation of markdown - do not want to ask in haskell, ruby… to extend libraries - markdown does not support references and other

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
On Nov 13, 2013, at 8:22 PM, Alexandre Bergel alexandre.ber...@me.com wrote: Why not generating markdown code from pier code? If the whole problem is exposure on the web. Someone has considered pdf2html or latex2html? Maybe my question is naive, I do not know. this is planned. Now I can

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
On Nov 13, 2013, at 8:22 PM, Alexandre Bergel alexandre.ber...@me.com wrote: Why not generating markdown code from pier code? If the whole problem is exposure on the web. Someone has considered pdf2html or latex2html? I did = suicidal tendencies. The results looks like shit. I did not try

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Chris Muller
On Wed, Nov 13, 2013 at 1:17 PM, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: Exactly, every specialized stream has its specialized API and/or specialized implementation. File streams don't even have a name, because they need not to. You can browse XTFileReadStream and

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread kilon alios
Stephane I think you need to sit down and write the Guidelines for Pharo Documentation, explaining the tools, the workflow, the goals, the principles and most importantly where documentation can be found. Post it on pharo website. This way you will save a lot of time from answering questions here

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
It would be completely silly to have class comments in MD (no matter how cool this would be) _and_ *not* be able to have Nautilus parse/render them, with active links, etc… With Athens inside the image we will use the pier parser to generate a document tree and render it inside the image.

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
I will write and send a proposal to the list. Good idea. Stef Stephane I think you need to sit down and write the Guidelines for Pharo Documentation, explaining the tools, the workflow, the goals, the principles and most importantly where documentation can be found. Post it on pharo

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Stéphane Ducasse
thanks for this discussion it is interesting. I like small api fully implemented vs large and bogus ones Stef On Nov 13, 2013, at 6:47 PM, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: -- Forwarded message -- From: Nicolas Cellier

Re: [Pharo-dev] Instrumenting field accesses with Opal?

2013-11-13 Thread Stéphane Ducasse
Hi! Is there a way to get notified when fields are accessed? That would be awesome You can use the current reflectivity prototype. It's on RMoD CI: https://ci.inria.fr/rmod/job/Reflectivity/ It should look like something like that: YourClass methods do: [ :method | method ast

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Nicolas Cellier
Chris, I have to completely disagree. The idea of breaking a complex object into simpler parts is not just theories and extremism. Assigning several roles to an object is sometimes convenient for a start, but generally does scale very badly. It's a collective experience driven by pragmatic

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

2013-11-13 Thread Nicolas Cellier
Of course, since this is a question of style, all was invented way before the computer era :) https://en.wikipedia.org/wiki/Metonymy#Synecdoche 2013/11/13 Chris Muller asquea...@gmail.com These are really excellent arguments, Nicolas. Good discussion. On Wed, Nov 13, 2013 at 3:32 PM,

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
It would be completely silly to have class comments in MD (no matter how cool this would be) _and_ *not* be able to have Nautilus parse/render them, with active links, etc… With Athens inside the image we will use the pier parser to generate a document tree and render it inside the

Re: [Pharo-dev] Spec new release :)

2013-11-13 Thread Stéphane Ducasse
On Nov 14, 2013, at 1:03 AM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: On 13 Nov 2013, at 20:40, Stéphane Ducasse stephane.duca...@inria.fr wrote: So read the thread that yuriy rasied last week my sumarry - write in pier publish in latex, html, markdong

Re: [Pharo-dev] help needed with fixing the SpecDebugger

2013-11-13 Thread Tudor Girba
Hi, Thanks for looking into this. However, as I wrote in the issue, the fix does not work. There are still problems. I reopened the issue. Cheers, Doru On Tue, Nov 12, 2013 at 1:15 PM, Clément Bera bera.clem...@gmail.comwrote: I added a slice and a comment here:

[Pharo-dev] [pharo-project/pharo-core] 340f1e: 30571

2013-11-13 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 340f1ecf713d5e0ad9c662b77975cb72c6554fae https://github.com/pharo-project/pharo-core/commit/340f1ecf713d5e0ad9c662b77975cb72c6554fae Author: Jenkins Build Server bo...@pharo-project.org Date:

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

2013-11-13 Thread GitHub
Branch: refs/tags/30571 Home: https://github.com/pharo-project/pharo-core