[Pharo-dev] [pharo-project/pharo-core] 2e15c1: 50290

2015-08-30 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 2e15c1662791017cdad4be9996bd915896242c89 https://github.com/pharo-project/pharo-core/commit/2e15c1662791017cdad4be9996bd915896242c89 Author: Jenkins Build Server Date: 2015-08-31 (Mon, 31 Aug 2015

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

2015-08-30 Thread GitHub
Branch: refs/tags/50290 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Marcus Denker
> > The only problem is that it does a whole-method refactoring while it should > only affect the node > that triggered the deprecation. Else there could be wrong transformations if > the same selector > is used but only one of the implementations need to be rewritten, while if we > are able t

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Marcus Denker
> On 31 Aug 2015, at 08:41, stepharo wrote: > > But the tool of mark is a ui tool so why would you want to get a tool to > define a rule in your case? > Yes, it would be nice to have a tool for creating the rules. But then, one can use Mark’s tool as is for this already now for creating the

Re: [Pharo-dev] [Pharo5] new feature: #sourceNodeExecuted on Context

2015-08-30 Thread stepharo
Nice :) I hope you put this example as comment. Le 31/8/15 08:37, Marcus Denker a écrit : Hi, I added a method that returns the sub-tree of the AST that was executed by this context. (e.g. the message send node of the message that was send that is the reason why we are now executing thisCon

Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition

2015-08-30 Thread stepharo
yes may be a cleanup. Le 31/8/15 01:00, Nicolai Hess a écrit : Oh, thats funny. Maybe this comes from the release buidling process, (condense changes / sources) anything that resets some world state? 2015-08-30 22:29 GMT+02:00 Torsten Bergmann >: Nicolai Hess wro

[Pharo-dev] [Pharo5] New Feature: persistent properties on temporary variables

2015-08-30 Thread Marcus Denker
Hi, Since last week, TemporaryVariable meta-objects are made persistent if you put a property on them. (they are saved in the method’s properties). This means we can annotate temps without having to keep the AST around. When not used all the machinery behind has no cost in terms of memory. tes

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread stepharo
But the tool of mark is a ui tool so why would you want to get a tool to define a rule in your case? In the future if mark and camille come up with a better rewrite engine then of course we will use it. Le 30/8/15 18:31, Marcus Denker a écrit : No, just plain old ParseTreeRewriter.. but integ

[Pharo-dev] [Pharo5] new feature: #sourceNodeExecuted on Context

2015-08-30 Thread Marcus Denker
Hi, I added a method that returns the sub-tree of the AST that was executed by this context. (e.g. the message send node of the message that was send that is the reason why we are now executing thisContext). e.g. testSourceNodeExecuted | sourceNode | sourceNode := thisContext send

Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition

2015-08-30 Thread Nicolai Hess
Oh, thats funny. Maybe this comes from the release buidling process, (condense changes / sources) anything that resets some world state? 2015-08-30 22:29 GMT+02:00 Torsten Bergmann : > Nicolai Hess wrote: > >What does not work in 40608? > > What Julien describes in [1] when he uses Pharo 4 with

Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition

2015-08-30 Thread Torsten Bergmann
Nicolai Hess wrote: >What does not work in 40608? What Julien describes in [1] when he uses Pharo 4 with DesktopManager. I use Pharo 5 and did not have this effect.   To reproduce I used latest.zip from http://files.pharo.org/vm/pharo/win/   one time with #40608 and one time with #5   Gofer n

Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition

2015-08-30 Thread Nicolai Hess
2015-08-30 21:38 GMT+02:00 Torsten Bergmann : > Which Pharo 4 image was used to create Build initial Pharo 5 image > (build 5000)? According to the mailinglist archive from April [1] > it seems to be build 40608. > > I wonder since in build 5 the desktop manager works and in the > Pharo 4 imag

[Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition

2015-08-30 Thread Torsten Bergmann
Which Pharo 4 image was used to create Build initial Pharo 5 image (build 5000)? According to the mailinglist archive from April [1] it seems to be build 40608. I wonder since in build 5 the desktop manager works and in the Pharo 4 image 40608 it is not working. Was there anything applied sp

[Pharo-dev] what is the protocol between a data source and a FTlist?

2015-08-30 Thread stepharo
Hi esteban I'm wondering how the list is updated when the data source change. What is the protocol. I was looking at the examples but I could not see it. Stef

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Marcus Denker
No, just plain old ParseTreeRewriter.. but integrating Mark’s tool would be very nice as a next step. > On 30 Aug 2015, at 14:34, Peter Uhnák wrote: > > Is this based on Mark's Rewrite Tool? > > On Sun, Aug 30, 2015 at 10:27 AM, Marcus Denker > wrote: > Hi, >

Re: [Pharo-dev] QANautilusPluggin Logic Question

2015-08-30 Thread Marcus Denker
Hi, All methods (and methods of blocks) that are executing already will keep executing the wrong code. As only offsets change, one could do on-stack replacement of these methods, but nobody has implemented that yet. It might be good to have a check that warns when changing layout of classes t

[Pharo-dev] Keeping morph vs model

2015-08-30 Thread stepharo
Hi I'm updating my mini browser to FastTable and Rubric and I was wondering if it is better to keep the model of the list instead of the morph in the browser model. Stef

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

2015-08-30 Thread GitHub
Branch: refs/tags/50289 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 8d8dcc: 50289

2015-08-30 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 8d8dccc7cfec41199d85513365f95b5f89b52c30 https://github.com/pharo-project/pharo-core/commit/8d8dccc7cfec41199d85513365f95b5f89b52c30 Author: Jenkins Build Server Date: 2015-08-30 (Sun, 30 Aug 2015

Re: [Pharo-dev] allChildren raise error when don't have read permission

2015-08-30 Thread stepharo
we should improve this part of fileSystem. We were making a list of the issue and see if we cannot pay someone to fix them because we are too busy. Le 30/8/15 17:21, Brice GOVIN a écrit : Hi, I was playing a bit with the FileSystem to get all files on my computer (/FileSystem root allChildren

[Pharo-dev] allChildren raise error when don't have read permission

2015-08-30 Thread Brice GOVIN
Hi, I was playing a bit with the FileSystem to get all files on my computer (FileSystem root allChildren) and I had the error “DirectoryDoesNotExist” for a directory that actually exists but i don’t have the read permission. I am not sure wether I’m not using the right method for what I want or t

Re: [Pharo-dev] [Moose-dev] Re: Still some issue with Bloc :-(

2015-08-30 Thread stepharo
Thanks nicolai. Alain told me that he was breaking his fireplace to build a new one so not much bloc to finish the holidays :) Stef Le 30/8/15 16:09, Nicolai Hess a écrit : fixed: ready to review 16267 Fastta

Re: [Pharo-dev] [Moose-dev] Re: Still some issue with Bloc :-(

2015-08-30 Thread Nicolai Hess
fixed: ready to review 16267 Fasttable isn't visible in athens (in bloc) 2015-08-29 18:54 GMT+02:00 Tudor Girba : > FastTable does not work in Bloc. You have to disable it from the Settings > to work with Nautilu

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Yuriy Tymchuk
But it can be integrated with Rewrite Tool ;), it’s not so easy for everyone to write down a rewrite rule from scratch. Yes, I think that having transformation applied without re-styling will be a huge improvement. Because now there is an “autofix” button, but I don’t use it myself as it restyl

Re: [Pharo-dev] PetitParser speed and cost of PPFailure

2015-08-30 Thread Holger Freyther
> On 17 Aug 2015, at 13:03, Jan Kurš wrote: > > Dear Jan, > As the compiler is not production ready and as we are looking for a use > cases, I can import your grammar and let you know how to make it working with > our tool and what would be the performance gain. In that case, I would need

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Mark Rizun
As far as I'm concerned, it's not based on my tool. 30 серп. 2015 3:34 пп "Peter Uhnák" пише: > Is this based on Mark's Rewrite Tool? > > On Sun, Aug 30, 2015 at 10:27 AM, Marcus Denker > wrote: > >> Hi, >> >> Small experiment: >> >> 1) add this method to Object: >> >> deprecated: anExplanationS

Re: [Pharo-dev] QANautilusPluggin Logic Question

2015-08-30 Thread Yuriy Tymchuk
Yes, but the situation is weird, because if you look at the variable in the debugger - everything is ok. Is there a way to understand what has not mutated? Uko > On 30 Aug 2015, at 13:35, stepharo wrote: > > may be code executing the check did not get mutated when the system changed > shape.

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Peter Uhnák
Is this based on Mark's Rewrite Tool? On Sun, Aug 30, 2015 at 10:27 AM, Marcus Denker wrote: > Hi, > > Small experiment: > > 1) add this method to Object: > > deprecated: anExplanationString rule: aRule > | builder ast rewriteRule method | > builder := RBCompositeRefactoryChange

Re: [Pharo-dev] QANautilusPluggin Logic Question

2015-08-30 Thread stepharo
may be code executing the check did not get mutated when the system changed shape. Le 30/8/15 11:00, Marcus Denker a écrit : On 30 Aug 2015, at 10:57, Yuriy Tymchuk wrote: So the byte symbol comes from the “position” inst var of the superclass. I’m not completely sure how it works on low lev

Re: [Pharo-dev] QANautilusPluggin Logic Question

2015-08-30 Thread stepharo
I just added an instance variable to Model. Le 28/8/15 11:34, Yuriy Tymchuk a écrit : Wow, this is weird. Yes, GLMAsyncTask spawns a process. I use it not to block the ui in nautilus while critics are retrieved. So when you switch to a new method it changes plugin’s critic list to “loading p

Re: [Pharo-dev] QANautilusPluggin Logic Question

2015-08-30 Thread Marcus Denker
> On 30 Aug 2015, at 10:57, Yuriy Tymchuk wrote: > > So the byte symbol comes from the “position” inst var of the superclass. I’m > not completely sure how it works on low level, but I guess that because you a > a new variable, the others shift and it accesses the value that is actually > map

Re: [Pharo-dev] QANautilusPluggin Logic Question

2015-08-30 Thread Yuriy Tymchuk
So the byte symbol comes from the “position” inst var of the superclass. I’m not completely sure how it works on low level, but I guess that because you a a new variable, the others shift and it accesses the value that is actually mapped to another variable. Is it the issue of my implementation?

Re: [Pharo-dev] Nautilus and Work group

2015-08-30 Thread stepharo
Le 25/8/15 08:52, Torsten Bergmann a écrit : Nautilus in Pharo 5 now includes per default a group "Configuration" and "Work". I would like to slowly rename it "Project" But one has to manually put new work into the "Work" group. If you load the configuration via the catalog browser and us

[Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

2015-08-30 Thread Marcus Denker
Hi, Small experiment: 1) add this method to Object: deprecated: anExplanationString rule: aRule | builder ast rewriteRule method | builder := RBCompositeRefactoryChange named: 'deprecation'. method := thisContext sender sender method. ast := method ast copy.

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

2015-08-30 Thread GitHub
Branch: refs/tags/50288 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] e9dc91: 50288

2015-08-30 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e9dc91e2a02254e383983637de6cf1d1009770ea https://github.com/pharo-project/pharo-core/commit/e9dc91e2a02254e383983637de6cf1d1009770ea Author: Jenkins Build Server Date: 2015-08-30 (Sun, 30 Aug 2015