Changeset 1142

Timestamp:

02/28/07 22:43:32 (2 years ago)

Author:

arjanmol

Message:

--

Files:

• gaphor/trunk/TODO (modified) (7 diffs)
• gaphor/trunk/doc/undo.txt (modified) (2 diffs)
• gaphor/trunk/utils/command/build_mo.py (modified) (1 diff)

gaphor/trunk/TODO

@@ -24 +24 @@
-   !!! Create some example diagrams,
-
+ - get rid of resource(). Create an Application instance instead (should
+   make unit testing easier too).
+   This should get rid of the pseudo singletons (_default* instances per module)
+   
- - using stereotypes
- - components and stuff
@@ -33 +37 @@
- - Use actions only for action definitions. use Events for notification
-   between actions.
+    * use zope.component.event for centralized event notification.
+ 
+ - use GTK's UIManager for menu management.
+    * figure out naming conventions, also for diagram item popup menus.
+    * 
+
+- Copy/Paste for diagramitems
+  - How to do a copy/paste? shallow copy or deep copy? -> just create a diagram
+    item item referening the same model element or also copy the model element?
+    I think we should stick with shallow copy for now.
-
- - namedelement.py: from NamedElement
@@ -42 +56 @@
- - Use setuptools (pkg_resources) to load plugins.
-   Maybe define stuff in terms of services, like PIDA does (pida.org?)
+
+ - In some cases (like when editing attributes) Enter should be used to
+   complete the edit action.
-
-Older (long term ;) todo items:
@@ -57 +74 @@
-   Zope classes are quite optimized. However, mainly provides the same
-   functionality as Actions, but not as fine grained.
+   Use zope.component.events for all notification!
-
-- Add meta data (such as text alignment) to the model file (add a meta:
@@ -63 +81 @@
-- Fix namespace relations between Lifeline and Interaction and Message and
-  Interaction
-
-- Allow to make Action objects, instead of defining classes.
-  Should use meta-classes for registration too (define __abstract__ or\something to prevent registration).
-
-- disable actions when editing.
@@ -76 +91 @@
-  them into other models.
-
-
+ Solved by setuptools
-
-- Exporting diagrams to UML XMI (work in progress),
-  code, images (SVG/png), etc. - make a plugin!
-
-- fix accelarators (HOW?), partially done, accelerators on items in popup menus
-  does not work.
-  Accelerators should be activated by the (Abstract)Window, should not depend
-  on menu items. Intercept Window::key_pressed_event and let it handle
-  popup menu actions.
-
-- In some cases (like when editing attributes) Enter should be used to
-  complete the edit action.
-
-- Create a good algorithm for placement of lines and maybe nodes too.
-
-- Use default GTK+ menu classes, in stead of the home-brew one.
-
-- Use GTK+ 2.4 UIManager and ActionGroups (?):
-  * Reconsider since GTK+ 2.8 bindings are fairly better than the 2.4 bindings
-  . We have to keep the gaphor.misc.action module intact.
-  . As far as I can see, cross action updates, are not supported.
-  . Properties can be mapped in a straightforward way.
-  . Should actions be split up: one for the main window, one group per
-    diagram and one group per item type?
-  . GtkUIManager looks useful, some structures in Gaphor may have to be
-    reconsidered. What to do with AccelMaps for example. (I really have
-    to read the tutorial some day ;-).
-  . The current structure is simple and quite Pythonic. It should be this way.
-  . Stuff like a recent-file box will be easier to create (I guess).
-  Previous conclusion: keep using the gaphor.misc.action code
-
-- Automatically draw relations when an item is DND-ed from the tree-view
-  to the diagram.
-
-- Copy/Paste for diagramitems
-  - in order to make copy/paste work, the load/save functions should be
-    generatlised to allow a subset to be saved/loaded (which is needed
-    anyway for exporting/importing stereotype Profiles).
-  - How many data should be saved? (e.g. we copy a diagram item, remove it
-    (the underlaying UML element is removed) and the paste the copied item.
-    The diagram should act as if we have placed a copy of the removed item
-    on the canvas and make the uml element visible again.
-
-- Undo/redo functionality
-
-#- Stereotypes: check documentation page 581 (597 absolute). Fixed. An extra
@@ -131 +110 @@
-functinality should be provided for those.
-
-- Deployment diagram:
-  . Node
-  . Artifact
-  . some relations
-- Sequence diagram:
-  . Life line

gaphor/trunk/doc/undo.txt

@@ -43 +43 @@
-
-  Canvas:
-
-
+
+
+
-    request_update() (should be performed as part of undo action when called)
-
-  Solver (?):
-
+
+
+
-
-  In Gaphor, connecting two diagram items is considered an atomic task,
@@ -54 +57 @@
-  tasks (properties set and a constraint created).
-
+  For methods, it should be possible to create a decorator (@reversable) that
+  schedules a method with the same signature as the calling operation, but with
+  the inverse effect (e.g. the gaphas.tree module):
+
+  Tree(object):
+
+    @reversable(lambda s, n, p: s.remove(n))
+    def add(self, node, parent=None):
+        ... add 
+
+    @reversable(add, self='self', node='node', parent='self.get_parent(node)')
+    def remove(self, node):
+        ... remove
+
+ Okay, so the second case is toucher...
+ 
+ 
-We have three options:
-

gaphor/trunk/utils/command/build_mo.py

@@ -36 +36 @@
-            self.set_undefined_options('build',
-                                       ('build_base', 'build_dir'))
-inguas
+ocale
-
-        self.all_linguas = self.all_linguas.split(',')