Hi Martin, hi Mariano,
Loading FuelMooseExtensions 1.4 is broken because FuelContainer is no longer loaded.
This is due to the fact that FuelContainer was taken out of the CoreWithExtras group from ConfigurationOfFuel 1.7.
Could you take a look?
Cheers,
Doru
--
www.tudorgirba.com
"Beauty is where we see it."
Hi!
"Que tal?" in Spanish can be translated in English as "How are you? How things are going?"
It would be cool that each of us briefly summarize what he is working on and what is the future plan.
Visualization engine:
I am intensively working on Roassal. A new visualization engine that should replace Mondrian. Roassal will provide a better user experience with visually appealing animations and interactions. I will probably make some announcement at the beginning of March.
The mid-long term vision of Roassal is to have an agile and portable visualization engine. I want to make it work on VisualWorks and Amber, in addition to Pharo.
Analyzing Smalltalk application:
Together with Santiago, we are working on using unit test to refine model obtained from Smalltalk applications. The idea is to profile what is currently executing to reduce superfluous invocation candidates.
I also applied to some grant to analyze JavaScript applications in Moose. We will see how it goes.
What about you?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
I have some problem to load a mse file into the latest stable moose. When
the progress bar reaches slightly more than the middle the image crashes.
The mse file has been generated with inFamix and it is ~120MB big. The same
software parsed using inFusion generates a mse file of ~100MB and this
second file works.
using moose 4.6 on pharo #13315
and the VM of Eliot Cog 2519
Did anybody have problems with mse files generated with inFamix?
Cheers,
Fabrizio
Hi,
the error described is different but surely related because I loaded the
slice and yes, the problem was solved.
Thanks Matias.
Cheers,
Fabrizio
2012/2/14 Matias Garcia Isaia <mgarciaisaia(a)gmail.com>
> Fabrizio,
>
> can you confirm if it's the same issue that happens with
> <http://code.google.com/p/pharo/issues/detail?id=5292> ?
>
> There's a slice there, maybe you can try if that fixes your problem.
>
> On Tue, Feb 14, 2012 at 3:02 PM, Fabrizio Perin
> <fabrizio.perin(a)gmail.com> wrote:
> > Hi,
> > I just tried to add a new repository in Monticello and I got an error:
> > the error is:
> >
> > MessageNotUndestood: FileDialogWindow>>directoriesFor:
> >
> > the repository I wanted to add was a directory. It seems to work in the
> case
> > you want to add a HTTP repository.
> >
> > The problem happen on the last Moose build (#830) and on a
> > Pharo1.4a
> > Latest update: #14331
> >
> > downloaded from the pharo web site.
> >
> > Cheers,
> > Fabrizio
>
>
Hi,
We are almost done with getting Glamour work on 1.4. The model works, and most of the rendering is fine as well. The only major trouble is with the rendering of the finder. In particular, the problem is the scrolling through the panes.
The scrolling code was basically copied from OB (shamelessly :)). Something must have changed in Pharo 1.4 that disables some of the behavior. Could anyone spare a pair of eyes to look into this :).
Cheers,
Doru
--
www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
Hi,
I just tried to add a new repository in Monticello and I got an error:
the error is:
MessageNotUndestood: FileDialogWindow>>directoriesFor:
the repository I wanted to add was a directory. It seems to work in the
case you want to add a HTTP repository.
The problem happen on the last Moose build (#830) and on a
Pharo1.4a
Latest update: #14331
downloaded from the pharo web site.
Cheers,
Fabrizio
Hi,
I lost track of the latests developments around RB. What is the way to load RB in Pharo 1.4?
Cheers,
Doru
--
www.tudorgirba.com
"What we can governs what we wish."
Hello all,
We are using petitParser with a Stream by the parse method on a PPParser.
This parse method calls asPetitStream on our stream which is supposed to
return a stream with a valid format for PPParser. The problem is that this
stream do not represent our test file but a lot of white spaces. this code:
(StandardFileStream fileNamed: '/some/path/to/file/atextfile.txt' )
asPetitStream proves that.
Did someone else have a similar problem with petit parser?
thanx,
Usman & Guillaume
Hi,
I moved the moose-dev build to 1.4. Of course, it is broken :).
Cheers,
Doru
--
www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
