File: gaphor.txt

package info (click to toggle)
gaphor 0.13.0-1
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 3,692 kB
  • ctags: 2,971
  • sloc: python: 19,981; xml: 247; makefile: 54; sh: 40
file content (43 lines) | stat: -rw-r--r-- 1,529 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Gaphor
~~~~~~

Gaphor is a UML CASE tool aiming for symplicity. It is written in Python.
The goal is to write as much as possible in Python (easy scriptable for
code generators).

So here's what has to be created:
- A main window containing a tree-like representation of the classes
- Windows which display the various diagrams
- A model that contain all abstract data (generate from the UML metamodel
  definition)
- Graphical items for classes, use cases, etc. (in C)
- Keep the code modular and easy to extend in Python

Main Window
~~~~~~~~~~~
The main window can be created in Python. It can be created using Glade.
We need a custom GtkTreeModel class that acts as a view over the UML model.
The model is very extensive since it is generated from the UML Metamodel
definition.

Diagram Windows
~~~~~~~~~~~~~~~
Diagrams have to be displayed in separate windows. Each window should carry
a toolbox with diagram related objects. We do not restrict the use of elements
from different diagram types in one diagram (like the Catalyst method).
Actually we do restrict as little as possible, as long as it is permitted by
the "MetaModel".

Data Model
~~~~~~~~~~
The data model itself is generated from the UML Metamodel. This has the
advantage that we can do everything with it as long as the OMG's (Object
Management Group <http://www.omg.org>, they develop UML now) rules are
not violated.

Graphical items
~~~~~~~~~~~~~~~
Of course we need something to draw. The items that are to be placed on the
diagrams need to be created.