News on Mondrian
by Alexandre Bergel
Hi!
I am please to announce that Mondrian now includes an help and tutorial. These are accessible from the Easel menu and the World menu (help item).
You can load Mondrian with:
Gofer new
squeaksource: 'Mondrian';
package: 'ConfigurationOfMondrian';
load.
(Smalltalk at: #ConfigurationOfMondrian) perform: #loadDefault.
I would be please to hear feedback on them. The PharoByExampleV2 chapter on Mondrian will be based on the tutorial. I am currently working on a Tutorial->Latex importer.
What I did in the plane on the way back form esug.
582: No leaf class is abstract. Move down some methods from MOShape to MONodeShape
581: Help and tutorial finished. Added some new test and renamed a few things
580: easel examples are better commented and more descriptive
579: Added submenu in Easel help
578: MOAnnouncer>>forward:
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
12 years, 6 months
Re: Moose on pharo 1.2
by Stéphane Ducasse
this is ok for me :)
Stef
On Sep 23, 2010, at 9:05 AM, Tudor Girba wrote:
> The main reason for getting the Moose dev version on top of the latest Pharo dev version is because this is the simplest way to utilize the limited resources in the Smalltalk community. It is the same reason why I argue for Moose users to always use the latest Moose dev. Of course, it can be painful at times, but if you get enough users that feel the pain and that are willing to work with you, the core tends to become and stay stable.
>
> Cheers,
> Doru
>
>
> On 22 Sep 2010, at 16:31, Mariano Martinez Peck wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>>
>> On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:
>>
>>>
>>>
>>> On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote:
>>> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>>>
>>> But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
>>> You cannot make progress without breaking things.
>>>
>>> I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ? Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.
>>
>>
>> As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
>> I just let other people debug the process for now...
>>
>> That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.
>>
>> The only reason I found is what Stef said...if you want to help Pharo, report issues and fix them, then this is useful.
>>
>>
>>
>> Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.
>>
>>
>> However, I do not think it is useful for a Hudson report. What is the sense of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken even itself ?.
>>
>> Again, from my point of view, if you DO spend time trying to use Moose in Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just wait until it is stable.
>>
>>
>>
>>
>>>
>>> Cheers
>>>
>>> Mariano
>>>
>>>
>>>
>>> Alexandre
>>>
>>>
>>>
>>> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>>>
>>>> I just tried to load Moose on pharo1.2
>>>>
>>>> I only do this script (loading OB is not needed I think):
>>>>
>>>> =====
>>>> Gofer new
>>>> squeaksource: 'rb';
>>>> package: 'AST-Core';
>>>> package: 'Refactoring-Core';
>>>> package: 'Refactoring-Critics';
>>>> package: 'Refactoring-Environment';
>>>> package: 'Refactoring-Spelling';
>>>> package: 'Refactoring-Changes';
>>>> load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'shout';
>>>> version: 'Shout-cyrille_delaunay.87';
>>>> package: 'ShoutWorkspace.1';
>>>> package: 'ShoutTests';
>>>> load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'MetacelloRepository';
>>>> package: 'ConfigurationOfOmniBrowser';
>>>> load.
>>>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>>>>
>>>> Gofer new
>>>> squeaksource: 'Moose';
>>>> package: 'ConfigurationOfMoose';
>>>> load.
>>>> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
>>>> =====
>>>>
>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>> So we do not save our work on moose repository.
>>>>
>>>> What do we do for next steps ?
>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>>>
>>>> Cheers,
>>>> ---
>>>> Jannik Laval
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "One cannot do more than one can do."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12 years, 6 months
Re: Moose on pharo 1.2
by Simon Denier
On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:
>
>
> On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote:
> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>
> But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label says "unstable".
> You cannot make progress without breaking things.
>
> I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need so much that ? Maybe you should wait a little until Pharo 1.2 gets code freeze and releases a first beta or RC.
As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
I just let other people debug the process for now...
That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes, it's already done and we can move on while retaining a stable dev environment.
Actually, we had another motivation to load Moose in 1.2 which was building Hudson reports, but we will probably try a different way now, using Metacello and Monticello importer.
>
> Cheers
>
> Mariano
>
>
>
> Alexandre
>
>
>
> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>
> > I just tried to load Moose on pharo1.2
> >
> > I only do this script (loading OB is not needed I think):
> >
> > =====
> > Gofer new
> > squeaksource: 'rb';
> > package: 'AST-Core';
> > package: 'Refactoring-Core';
> > package: 'Refactoring-Critics';
> > package: 'Refactoring-Environment';
> > package: 'Refactoring-Spelling';
> > package: 'Refactoring-Changes';
> > load.
> >
> > Gofer new
> > squeaksource: 'shout';
> > version: 'Shout-cyrille_delaunay.87';
> > package: 'ShoutWorkspace.1';
> > package: 'ShoutTests';
> > load.
> >
> > Gofer new
> > squeaksource: 'MetacelloRepository';
> > package: 'ConfigurationOfOmniBrowser';
> > load.
> > ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
> >
> > Gofer new
> > squeaksource: 'Moose';
> > package: 'ConfigurationOfMoose';
> > load.
> > (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
> > =====
> >
> > With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
> > So we do not save our work on moose repository.
> >
> > What do we do for next steps ?
> > Do we change our Pharo system and go to 1.2 or working on 1.1 ?
> >
> > Cheers,
> > ---
> > Jannik Laval
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
12 years, 6 months
moose 4.1
by Tudor Girba
Hello,
We are happy to announce the Moose Suite version 4.1:
http://moosetechnology.org/download
What's new:
• Significant speed improvements of Mondrian and Glamour
• Improved Mondrian drawing of complex shapes
• Improved Glamour engine to handle cyclic updates
• New user interface look an feel
• Improved set of Glamour widgets
• Re-packaging to strengthen the naming convention
• Re-organization of the code to break unwanted dependencies
• Cleaning of FAMIX
• New extensible design of the Moose Finder
• New PetitParser-based parsers for MSE, Java, and MANIFEST.MF files
• New browser for meta-models described in MSE files
• Based on Pharo 1.1
A complete list of issues fixed in this release can be found at:http://code.google.com/p/moose-technology/issues/list?can=1&q=status=F...
An incomplete set of future actions:
• Better browsers for various analyses use cases
• Improved FAMIX query API (MooseChic)
• Improved Glamour widgets
• EyeSee engine for drawing charts
• AST for Java
Have fun,
The Moose Team
12 years, 6 months
Re: Moose on pharo 1.2
by Stéphane Ducasse
On Sep 22, 2010, at 7:24 PM, Colin Putney wrote:
> On Wed, Sep 22, 2010 at 2:51 AM, Stéphane Ducasse
> <stephane.ducasse(a)inria.fr> wrote:
>
>> MIT and I hope that colin will change it slightly and that we can integrate it in Pharo.
>
> Right, it's MIT-licensed, and I'm quite happy to have it integrated in
> Pharo. I'm currently implementing some of the changes we discussed at
> the conference, and I'll make sure the next release works on Pharo.
excellent!
I would love to have that in 1.2 so that we can start integrating it fully in 1.3
Jannik it would be a good nice little article for linux mag and book chapter
There is the blog of lukas already and once colin will repackage and rename (FSPath :D)
we can start writing a nice documentation :).
Stef
12 years, 6 months
Re: Glamour and Magritte validation
by François Tanguy
Hi,
I have a class Exercice holding 3 instance variables where I store integers.
Magritte descriptions are like follows:
descriptionNumberOfRepetitions
^ MANumberDescription new
accessor: #numberOfRepetitions;
label: 'Number of repetitions';
priority: 100;
yourself
And the Glamour piece of code using Magritte description.
(browser transmit)
from: #activities;
to: #details;
andShow: [ :a |
a magritte
title: 'Details';
description: #description].
The values are correctly displayed but when changing them, the validation fails. See the screenshot.
Regards,
Francois
12 years, 6 months
Re: Moose on pharo 1.2
by Stéphane Ducasse
Yes
Now moose people can also consider the list of pending issues and help.
There are some important fixes that nobody even packaged so that we can have a look at them.
Stef
On Sep 22, 2010, at 3:11 PM, Alexandre Bergel wrote:
> We have to make sure that Pharo 1.2 is working well. Yesterday, I couldn't inspect a value from the debugger because of an error raised with some mapping with closure. This is annoying.
>
> Alexandre
>
>
>
> On 20 Sep 2010, at 10:43, Laval Jannik wrote:
>
>> I just tried to load Moose on pharo1.2
>>
>> I only do this script (loading OB is not needed I think):
>>
>> =====
>> Gofer new
>> squeaksource: 'rb';
>> package: 'AST-Core';
>> package: 'Refactoring-Core';
>> package: 'Refactoring-Critics';
>> package: 'Refactoring-Environment';
>> package: 'Refactoring-Spelling';
>> package: 'Refactoring-Changes';
>> load.
>>
>> Gofer new
>> squeaksource: 'shout';
>> version: 'Shout-cyrille_delaunay.87';
>> package: 'ShoutWorkspace.1';
>> package: 'ShoutTests';
>> load.
>>
>> Gofer new
>> squeaksource: 'MetacelloRepository';
>> package: 'ConfigurationOfOmniBrowser';
>> load.
>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
>>
>> Gofer new
>> squeaksource: 'Moose';
>> package: 'ConfigurationOfMoose';
>> load.
>> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
>> =====
>>
>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>> So we do not save our work on moose repository.
>>
>> What do we do for next steps ?
>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>
>> Cheers,
>> ---
>> Jannik Laval
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12 years, 6 months
Moose on pharo 1.2
by Laval Jannik
I just tried to load Moose on pharo1.2
I only do this script (loading OB is not needed I think):
=====
Gofer new
squeaksource: 'rb';
package: 'AST-Core';
package: 'Refactoring-Core';
package: 'Refactoring-Critics';
package: 'Refactoring-Environment';
package: 'Refactoring-Spelling';
package: 'Refactoring-Changes';
load.
Gofer new
squeaksource: 'shout';
version: 'Shout-cyrille_delaunay.87';
package: 'ShoutWorkspace.1';
package: 'ShoutTests';
load.
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfOmniBrowser';
load.
((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5') load.
Gofer new
squeaksource: 'Moose';
package: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
=====
With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
So we do not save our work on moose repository.
What do we do for next steps ?
Do we change our Pharo system and go to 1.2 or working on 1.1 ?
Cheers,
---
Jannik Laval
12 years, 6 months
Re: Moose on pharo 1.2
by Stéphane Ducasse
On Sep 21, 2010, at 9:43 PM, Laval Jannik wrote:
>
> On Sep 20, 2010, at 18:52 , Simon Denier wrote:
>
>>
>> On 20 sept. 2010, at 17:14, Laval Jannik wrote:
>>
>>> Hi guys,
>>>
>>> It is not so easy to load Moose on Pharo1.2 :)
>>> There are two deprecated call during the loading. This is due to FileSystem, we cannot change the source code on the repository.
>>
>> What's the licence? Can we copy the package in Moose repo until fixes are integrated?
MIT and I hope that colin will change it slightly and that we can integrate it in Pharo.
>
> I don't know, it is on wiresong.
>
>>
>>> ====
>>>
>>> For now our fixes are on files attached to the mail.
>>> Cheers,
>>> Jannik
>>>
>>> <Mondrian-jl.581.mcz><Moose-MonticelloImporter-jl.12.mcz><ShoutWorkspace.1-jl.7.mcz><Glamour-Morphic-Renderer-jl.6.mcz>
>>
>>
>> Do the fixes break in Pharo 1.1? Could we integrate them and still run in 1.1?
>
> Only Mondrian seems to be broken with my changes.
> So tomorrow, I will commit the rest.
>
> Cheers,
> Jannik
>
>>
>>
>>>
>>> On Sep 20, 2010, at 16:43 , Laval Jannik wrote:
>>>
>>>> =====
>>>>
>>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1.
>>>> So we do not save our work on moose repository.
>>>>
>>>> What do we do for next steps ?
>>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ?
>>
>>
>> Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now.
>>
>> Actually the best plan is to check whether we could maintain the compability for a while.
>>
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> ---
> Jannik Laval
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12 years, 6 months
MAVector
by Alexandre Bergel
Hi!
I analyzed a bit the presence and usage of abstract methods in Moose.
MAVector>>initializeSize: is abstract.
MOClusteringVector is a subclass of MAVector. MOClusteringVector does not override initializeSize: and is not subclassed. MOClusteringVector is therefore abstract without subclasses.
Something has to be fixed somehow. I found a similar situation in Mondrian, and I fixed it.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
12 years, 6 months
