← Revision 2 as of 2005-10-27 18:26:44
Size: 1426
Comment:
|
← Revision 3 as of 2005-10-28 05:28:24 →
Size: 1561
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 14: | Line 14: |
* MetaNodes * Discussion of how to handle "compound" node types -- e.g. complexes, families (sets) (related to MetaNodes above...) |
This is just a brainstorming session right now. We can prioritize discussion and ideas for projects later.
Discuss the difference between node hide and delete concepts -> Goal: get conceptual clarity and a plan to document/implement any necessary changes based on this
- Improve conceptual clarity and better document the core and graph model - Is the root graph a multigraph or a graph? Is the root graph directed, undirected or mixed? How about graph perspective? Can nodes or edges be duplicated? etc.
- Discuss switching to a numbered node system instead of the current node ID as a string system
- Discussion of undo manager
- Prioritize subsystems for refactoring
- Discuss new documentation options e.g. wiki based, which can be translated to PDF and Java help.
- Plan core code cleanup - removing old libraries, old classes, clean up of package structure
- How can we package code so it is easier for developers to load - we have a problem with core plugin and library code being in too many places.
- Clarify and document the difference between core and non-core and decide on policies for making future decisions on this.
Review community development process and core coding conventions, etc -> goal is to increase quality of our codebase and application
- Discuss user interface standardization issues (Benno brought this up 2 years ago)
Discussion of how to handle "compound" node types -- e.g. complexes, families (sets) (related to MetaNodes above...)
- Please add your discussion points here.