Hi stefan
This is good that you could reproduce it because I was mad at it. I found
another case in Moose but esteban could not reproduce it
in plain Pharo. We just spent some times chasing the wrong bug :)
Stef
On 24 Jan 2014, at 14:51, Stephan Eggermont wrote:
> Esteban wrote:
>> I would
https://pharo.fogbugz.com/f/cases/12718
that should fix the problem.
we’ll see :P
Esteban
On 24 Jan 2014, at 14:58, Benjamin wrote:
> Step to reproduce:
>
> Open latest Pharo30719.
> Create a new package with shortcut or menu.
> Name it ‘AST-Monkey’ (to have a RPackage not a Tag)
> Go in ano
Step to reproduce:
Open latest Pharo30719.
Create a new package with shortcut or menu.
Name it ‘AST-Monkey’ (to have a RPackage not a Tag)
Go in another package.
Select some classes.
CMD M + CMD C (and probably with the menu too) (note that the Drag n’ Drop
works)
Type the name of the package ‘AS
Esteban wrote:
>I would really like a reproducible case… in the form of an image, if no else.
>
>btw… moose 5.0 images are severely broken in that area, so if you are using
>one of them you *will* have problems.
I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac
Op
I would really like a reproducible case… in the form of an image, if no else.
btw… moose 5.0 images are severely broken in that area, so if you are using one
of them you *will* have problems.
Esteban
On 24 Jan 2014, at 13:28, Goubier Thierry wrote:
>
>
> Le 23/01/2014 18:57, Benjamin Van
Le 23/01/2014 18:57, Benjamin Van Ryseghem a écrit :
Just that you know I faced it again :(
I created a new RPackage, move classes in the newly created RPackage.
And when I wanted to commit the code, it was empty.
Have you tried with the old Browser to see if your classes were in the
right c
Just that you know I faced it again :(
I created a new RPackage, move classes in the newly created RPackage.
And when I wanted to commit the code, it was empty.
I added also
forceRefreshMetaclassDefinedSelectors
| dict |
dict := Dictionary new.
self definedClasses do: [ :
Ben had to define the method on the class RPackage:
forceRefreshClassDefinedSelectors
| dict |
dict := Dictionary new.
self definedClasses do: [ :e || set |
set := Set new.
e protocols
select: [ :p | (p beg
but that is a hack, not a real solution… we need to find the place where
RPackage loses the update.
On 15 Jan 2014, at 18:17, Alexandre Bergel wrote:
> Ben had to define the method on the class RPackage:
>
> forceRefreshClassDefinedSelectors
> | dict |
>
> dict := Dictionary
Le 15/01/2014 17:34, Esteban Lorenzano a écrit :
yeah, I know… I was just pointing how it is. Not sure how it has to be… AFAIR,
this was a requested feature too :S
Ok, I leave the requested "feature" :)
For now, I have a test case which exhibit a bug. I'm pushing it on 12655
if you want t
Le 15/01/2014 16:59, Benjamin a écrit :
We are also facing some RPackage cache not in sync anymore with system
leading to the impossibility to commit the code :(
Ben
I'm onto something with very few manipulations. Now I have a class
belonging to A listed in B too, but with the system catego
We are also facing some RPackage cache not in sync anymore with system leading
to the impossibility to commit the code :(
Ben
On 15 Jan 2014, at 12:56, Goubier Thierry wrote:
>
>
> Le 15/01/2014 16:46, Alexandre Bergel a écrit :
>>> Do you have an issue on that? Or does it happens just when
Le 15/01/2014 16:46, Alexandre Bergel a écrit :
Do you have an issue on that? Or does it happens just when moving classes from
any package to another?
I do not know. I do not see on https://pharo.fogbugz.com how I can list issues
that contains the RPackage and that are still open.
The prob
Le 15/01/2014 16:46, Marcus Denker a écrit :
On 15 Jan 2014, at 16:34, Alexandre Bergel wrote:
Hi!
We are constantly facing problems when moving classes between packages. This is
highly discouraging. This involves tricky parts of the system that both
difficult to understand and to debug.
On 15 Jan 2014, at 16:34, Alexandre Bergel wrote:
> Hi!
>
> We are constantly facing problems when moving classes between packages. This
> is highly discouraging. This involves tricky parts of the system that both
> difficult to understand and to debug.
>
Yes, this one:
https://ph
> Do you have an issue on that? Or does it happens just when moving classes
> from any package to another?
I do not know. I do not see on https://pharo.fogbugz.com how I can list issues
that contains the RPackage and that are still open.
The problems we are facing usually involves having more t
Do you have an issue on that? Or does it happens just when moving
classes from any package to another?
Thierry
Le 15/01/2014 16:34, Alexandre Bergel a écrit :
Hi!
We are constantly facing problems when moving classes between packages. This is
highly discouraging. This involves tricky parts o
17 matches
Mail list logo
