Quoting wrobell <[EMAIL PROTECTED]>:
hello,
sometime ago i have created stereotypes branch for gaphor. the
goals of this branch are:
- describe how diagram items are developed
- create well designed abstract classes and remove unnecessary ones,
for example:
- there should be common code for diagram items for UML NamedElement
classes
- there should be common code for stereotypes
- catch common cases for item elements, i.e. putting names near lines,
centering names in items for classes, use cases, etc.
- allow to set stereotype using any diagram item
above, when finished (ca. one month since now i hope) should allow
us to
- accelerate development of new diagram items
- lower barrier for new programmers of gaphor
what has been improved so far (every item below gave us code
simplification... of course, there are some little glitches
and problems to solve):
- there is no Relationship class anymore, relationships are
implemented using python descriptors (simplified multiple inheritance
of diagram items)
- names of named items are aligned in NamedItem abstract class
(killed few abstract classed introduced by me like: RectNamedItem,
SimpleNamedItem, etc.)
- it is possible to set stereotype using every named item (no support
for lines, yet), see PackageItem class source code for an example of
code simplification
in doc directory there are few new files:
- items.tex
- items.gaphor
- align.svg
these should describe process of diagram items development. this
document is not formal one, but still it can be useful to see what
is happening on the branch. i am constantly working on
items.{tex,gaphor} to make it more clear and easier to understand.
arjan, i have a question about UML named elements. are all of them
part of namespace? should all named elements appear in tree view
on the left? if not all, then which one in your opinion?
Technically all NamedElements, which are children of Namespace elements are
displayed in the tree view.
The tree view is pretty simple since it only displays Namespace elements and
their children (with a notable exception for Associations, which are also
Namespace elements but are supressed).
I once had the idea to make users toggle which items are displayed by
providing
some toggle buttons, but I never actually made it.
I think, for a start, items should just be visible in the tree view, we can
always disable them.
Regardsm
Arjan
regards,
wrobell <[EMAIL PROTECTED]>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Gaphor-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gaphor-list
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Gaphor-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gaphor-list
