Hi,
We're slowly building up the parse tree of a Delphi project. Here is the first visualization:
The WhiteStarUML project is a GPL tool written in Delphi. It consists of 89 units at the interface level.
There might be more units that are referred to in the implementation. 4 units cannot be found to be
parsed, 5 units cannot be parsed. For each unit the number of classes defined in the interface is
shown as a yellow square.
Cheers,
Diego & Stephan
Hello guys
Is there any demo of Arki in the standard Moose distribution? I would like to give a demo of Moose, including an example with a user browsing custom concerns. I did not see any sample for Arki in Moose 4.6
--
Simon
Updates:
Status: WontFix
Comment #1 on issue 361 by alexandr...(a)gmail.com: Glamour status bar should
take into account Mondrian window status
http://code.google.com/p/moose-technology/issues/detail?id=361
In Roassal, we should instead add an element about this. It should not take
that long to do it.
FYI
Doru
---------- Forwarded message ----------
From: Oscar Nierstrasz <oscar.nierstrasz(a)gmail.com>
Date: Thu, Oct 4, 2012 at 2:06 PM
Subject: [Esug-list] Call for PhD candidates in the Software
Composition Group, U Bern
To: esug-list(a)lists.esug.org
Applications are invited for PhD candidates at the Software
Composition Group, University of Bern, Switzerland, to contribute to
the SNSF project "Agile Software Assessment".
The Software Composition Group carries out research in software
analysis and programming language design and implementation, with a
view to enabling software evolution. The SCG is led by Prof. Oscar
Nierstrasz and is part of the Institute of Computer Science and
Applied Mathematics (IAM) at the University of Berne.
Details about the research project can be found here:
http://scg.unibe.ch/research/snf13
The candidate must have a MSc in Computer Science (equivalent to a
Swiss MSc), should demonstrate strong programming skills, and have
research interests in several of the following areas:
- software evolution
- program understanding
- software modeling
- model-driven engineering
- reverse engineering
- domain specific languages
- dynamic analysis
- integrated development environments
- programming language design
- virtual machine technology
To apply, please send an email including your CV to Prof. Oscar
Nierstrasz (oscar(a)iam.unibe.ch).
---
Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch
Software Composition Group -- http://scg.unibe.ch/oscar
University of Bern -- Tel/Fax +41 31 631.4618/3355
_______________________________________________
Esug-list mailing list
Esug-list(a)lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org
--
www.tudorgirba.com
"Every thing has its own flow"
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 835 by step...(a)stack.nl: MooseGroup symbolsUsedInName uses
deprecated methods
http://code.google.com/p/moose-technology/issues/detail?id=835
String withoutTrailingBlanks and withoutLeadingBlanks
Fixed in Moose-MondrianPaintings-Stephan.Eggermont.170 in
http://www.squeaksource.com/Moose
Additional information: platform, context which may impact the problem
Please fill in the labels with the following information:
* Type-Defect
* Component-Mondrian
Updates:
Cc: tudor.girba
Comment #1 on issue 396 by alexandre.bergel: Mondrian should provide teh
start and end nodes in the edge action
http://code.google.com/p/moose-technology/issues/detail?id=396
I started to work on this (testHandlerOnEdge). However, I am unsure for few
things.
view interaction on: MOMouseDown do: [ :v | ... ]
What v is supposed to be? The announcement or the value on which one has
clicked?
It has to be the value I believe. However, it may brake already existing
code. We could leave it like this, and introduce on:withValueDo:
What do you think?
Cheers,
Alexandre
Updates:
Status: WontFix
Comment #1 on issue 398 by alexandr...(a)gmail.com: From and To positions
need extension
http://code.google.com/p/moose-technology/issues/detail?id=398
fromPositions: and toPositions: have disapeared in Roassal. Objects have to
be used instead of selectors
Status: New
Owner: ----
CC: alexandr...(a)gmail.com
Labels: Type-Defect Priority-High Component-Mondrian Milestone-4.6
New issue 698 by tudor.gi...(a)gmail.com: Mondrian does not properly raise
MOElementSelection
http://code.google.com/p/moose-technology/issues/detail?id=698
When in Glamour, often when selecting a Mondrian element does not populate
the selection because the MOCanvas does not raise MOElementSelection.
The reason for this seems to be a race condition due to changes in the
announcement framework. In the new announcement framework from Pharo 1.3,
the order of announcements is not guaranteed.
The issue seems to be due to the logic of the announcement:
MOCanvas>>mouseUp:
..
(lastEnteredGraphElement isNil not and: [
(lastEnteredGraphElement class ~~ MORoot and: [
lastEnteredGraphElement isNotSelected ])])
ifTrue: [
selectionEvent := MOElementSelection event: anEvent on:
lastEnteredGraphElement.
anEvent commandKeyPressed ifTrue: [ selectionEvent setAsMultiple ].
self announce: selectionEvent.
anEvent wasHandled: true.
^ self ].
Sometimes, "lastEnteredGraphElement isNotSelected" returns false because
somehow the element gets selected beforehand. This is most likely related
to the fact that the selection of a node actually happens by handling the
same MOElementSelection announcement:
MOCanvas>>announce: anAnnouncement
...
anAnnouncement element isNil ifFalse: [
anAnnouncement element announcer announce: anAnnouncement ].
self announcer announce: anAnnouncement.
MOViewRenderer>>setUsefulHandlersForNodes
...
self interaction on: MOElementSelection
do: [:ann |
ann isUnique
ifTrue: [ self root allSelectedNodes
do: [ :node |
node
deselect;
announce: (MOElementDeselection new) ] ].
ann element select.
self updateWindow ].
Following on from recent pharo-project 'Roassal Survey' posts which
asked for features for Roassal to be a universal diagram tool, I have
cobbled together a concept demo. I was quite surprised and pleased that
I was able to achieve this over the weekend - which I think is a
testament to the potential power of the clean design that Alexandre has
achieved for Roassal. Glamour also helped ease the way.
Operation is quite basic - only interactively adding nodes and applying
different layouts. Adding edges between nodes is still to go.
Previously Roassal has been used only for scripting, so there are some
bugs in the way I've forced it to operate, but I thought I'd release as
early as possible to garner feedback and interest. Perhaps I get lucky
and a Fuel expert finds this interesting. Help with moving the drawings
to file and back would be appreciated.
The attached package Glamour-Roassal-Interactive-BenComan.3 is based off
Moose 4.7, tested against a fresh copy downloaded 2012-10-03 which
contained:
ConfigurationOfRoassal.AlexandreBergel.605
ConfigurationOfGlamour.TudorGirba.98
cheers -ben