I loaded MooseLoader load
then CAnalyzer with a couple of warning and
then I selected packages
then packageDependency map
viewPackageMapOn: view
| graph kruskal tree otherEdges edges |
kruskal := MOKruskal new.
graph := self buildGraph: kruskal.
tree := kruskal run.
view nodeShape: (MORectangleShape new width: [:p | p model classes
size * 3]; height: [:p | p model extensionClasses size * 3] ).
view nodes: graph nodes.
view edgeShape: (MOCurveFitterShape new color: [:e| self
edgeColorFor: e default: Color brown]; width: 1).
otherEdges := graph edges copyWithoutAll: tree.
otherEdges := view edges: otherEdges from: #from to: #to.
view edgeShape: (MOStraightLineShape new color: [:e| self
edgeColorFor: e default: Color black]; width: 2).
edges := view edges: tree from: #from to: #to.
view treeLayout userDefinedEdges: edges
Stef
Hi,
We will organize a Moose Dojo on Sunday, August 30 during Camp
Smalltalk.
The goal of the dojo is to spread the knowledge about Moose and to
tackle issues related to the 4.0 release.
More information can be found at:
http://moose.unibe.ch/events/2009-08-30-dojo
If you are interested in participating, please either add yourself to
the webpage or send an email to this mailing list.
Cheers,
Doru
--
www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
Dear All,
Over the last months, I worked on CAnalyzer, an extension to FAMIX to
cope with C. I think it is mature enough to be part of the Moose
release.
In VW, the Moose distribution was an aggregation of tools. Installing
Moose installed all functional tools.
I think we should have a similar setting for the Pharo version of Moose.
Shall I augment MooseLoader with CAnalyzer?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
MooseLoader caused problems in the latest Pharo due to a missing
Traits-related method, so it crashed when loading Nile. So, for the
moment I removed this dependency. Actually, I do not know why we
needed it, because tests are still green.
I also removed for the moment the Moose-File and the dependency to Rio
because Rio caused an ugly error when switching the image from Mac to
Windows.
All in all, MooseLoader load works again in a Dev image.
When loading in the Core image there is a problem with loading Shout.
I have to investigate further.
Cheers,
Doru
--
www.tudorgirba.com
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
Hi
The FAMOOSr2007 proceeding is not available on MOOSE site.
There is a problem that the link of FAMOOSr2007Proceeding points to
"unkwon"!
Thanks,
Hani
CALL FOR CONTRIBUTIONS
FAMOOSr 2009 - 3rd Workshop on FAMIX and Moose in Reengineering
http://moose.unibe.ch/events/famoosr2009
Co-located with WCRE 2009, Lille, France
http://web.soccerlab.polymtl.ca/wcre2009/
We solicit experience reports and position papers (2-4 pages, IEEE
format). Experience reports will be expected to discuss meta-modeling
and software analysis using, but not limited to, FAMIX or Moose.
Position papers will be expected to describe new directions and
challenges for software analysis infrastructures, like FAMIX or Moose.
Papers may address issues along general themes, including but not
limited to:
• Analysis specific meta-models for evolution data, dynamic traces,
bug entries, etc...
• Meta-modeling in reengineering tools
• Visualization techniques.
• Analysis techniques: clustering, data mining, machine learning,
pattern matching, probabilistic approaches, etc...
• Mechanisms for tool composition and rapid tool prototyping.
• Reusability of research: making research results and tools
available to and reusable by the community.
• Persistency and manipulation of models and meta-models.
Submissions are not limited to FAMIX and Moose or to their active
users. We welcome any related ideas.
During the workshop, authors are expected to present their ideas using
a short format, lasting 3 to 7 minutes, in order to spawn vivid
discussions between participants. More information about this format
can be found at:http://moose.unibe.ch/events/famoosr2008/presenterskit
Submissions should be made via Easychair at
http://www.easychair.org/conferences/?conf=famoosr2009
Important dates
• submission: August 28
• notification: September 18
• workshop: mid October
Organizers:
• Simon Denier, INRIA Lille, France
• Tudor Girba, University of Bern, Switzerland
Dear List
Making Pharo interacting with Javascript has been the cup of tea of
the Seaside community.
I am wondering whether there has been an attempt to produce a parser
for Javascript within Pharo.
We are interested in getting Javascript models within Moose.
For now, it is likely what we will use the parser of Mozilla to
produce MSE files.
Cheers,
Alexandre
NB: Sorry for the cross-posting
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Pascal,
I am now on holidays. I will probably fix this next week.
Cheers,
Doru
On 19 Aug 2009, at 22:57, pascal.vollmer(a)nexgo.de wrote:
> Hi,
>
> I tried the combination Pharo 09.08.1 / Moose download as indicated
> in squeaksource.com. But the Rio-issue remains. The installation
> does not get completed.
>
> Does anyone know a workaround?
>
> kind regards
> Pascal
>
>
> ----- Original Nachricht ----
> Von: Tudor Girba <girba(a)iam.unibe.ch>
> An: pascal.vollmer(a)nexgo.de
> Datum: 10.08.2009 22:05
> Betreff: Re: Aw: [Moose-dev] moose 4.0 alpha 2 release
>
>> Hi Pascal,
>>
>> Thanks for reporting. I solved the first issue.
>>
>> For the second one it seems that something goes bad with the Rio
>> library during the initialization. Actually, we should check whether
>> we need this library at all. It is basically only used in the import
>> of files.
>>
>> Cheers,
>> Doru
>>
>>
>> On 10 Aug 2009, at 19:40, pascal.vollmer(a)nexgo.de wrote:
>>
>>> Hi Doru,
>>>
>>> under Windows
>>>
>>> 1) a small detail:
>>>
>>> <appdir>\moose.exe expects <appdir>\Contents\Resources\pier.image
>>>
>>> but it finds <appdir>\Contents\Resources\moose.image.
>>>
>>> 2) when the image opens it freezes with:
>>>
>>> MNU: RioLocalDosExecutive class>>initializeD....
>>> RioLocalExecutive class>>performStartUpMigration
>>> RioLocalExecutive class>>startUp:
>>> (..)
>>>
>>> Debug button does not react.
>>>
>>> ShoutWorkspace, MoosePanel are visible.
>>>
>>> cu
>>> Pascal
>>>
>>> ----- Original Nachricht ----
>>> Von: Tudor Girba <girba(a)iam.unibe.ch>
>>> An: Moose-dev Moose Dev <moose-dev(a)iam.unibe.ch>
>>> Datum: 10.08.2009 16:20
>>> Betreff: [Moose-dev] moose 4.0 alpha 2 release
>>>
>>>> Hi,
>>>>
>>>> A new alpha release is now available at:
>>>> http://moose.unibe.ch/download/pharo
>>>>
>>>> The new release solves (among others) the blueprint error in the
>>>> Moose
>>>> Finder.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "In a world where everything is moving ever faster,
>>>> one might have better chances to win by moving slower."
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>
>>> Pascal Vollmer
>>> Email: pascal.vollmer(a)ieee.org
>>>
>>> Plantschen oder Grog? Der Arcor-Wetterdienst weiss Bescheid!
>>> Wassertemperaturen für den Urlaub jetzt checken:
>> www.arcor.de/rd/wetter_wasser
>>>
>>
>> --
>> www.tudorgirba.com
>>
>> "From an abstract enough point of view, any two things are similar."
>>
>>
>>
>>
>
> Pascal Vollmer
> Email: pascal.vollmer(a)ieee.org
>
> Noch keine Pläne für das nächste Wochenende? Klicken Sie rein in den
> neuen Veranstaltungskalender auf arcor.de: http://events.arcor.de/
>
--
www.tudorgirba.com
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
