11 |
Issues |
Issues |
12 |
====== |
====== |
13 |
|
|
14 |
|
- Do we need to get rid of zzStructure? |
15 |
|
|
16 |
|
RESOLVED: Yes. Using a patented technology that |
17 |
|
will not be openly licensed is strictly against our |
18 |
|
free software philosophy. |
19 |
|
|
20 |
|
- Does this take away the whole basis of the project? |
21 |
|
|
22 |
|
RESOLVED: No. Even though we *started* from zzStructure, |
23 |
|
the project has in fact outgrown it. The structure |
24 |
|
gave us good insights and points of view (bidirectionality, |
25 |
|
fine-grain hyperstructure, ...), but in practical applitudes |
26 |
|
the code to handle the structure was always more complicated |
27 |
|
than it should have needed to be. |
28 |
|
|
29 |
|
We have developed several interesting technologies |
30 |
|
that we can *easily* slot around some other structure |
31 |
|
(vobs, uml linker, storm, ...). |
32 |
|
|
33 |
|
- What about Xanalogical hypertext? Can we use that? |
34 |
|
|
35 |
|
RESOLVED: Yes. Ted has said it's not patented, it was |
36 |
|
only protected by trade secrets, and since the technologies |
37 |
|
have now been openly disclosed, there are no limitations |
38 |
|
to their use. |
39 |
|
|
40 |
- Should we really split the code? |
- Should we really split the code? |
41 |
|
|
42 |
SUGGESTED RESOLUTION: Yes. It will be far easier for others |
SUGGESTED RESOLUTION: Yes. It will be far easier for others |
75 |
frozen APIs; this is especially important since now others may |
frozen APIs; this is especially important since now others may |
76 |
begin to rely on those APIs. |
begin to rely on those APIs. |
77 |
|
|
78 |
|
.. UML:: projectsplitting |
79 |
|
|
80 |
|
package UMLLinker |
81 |
|
|
82 |
|
package Storm |
83 |
|
use UMLLinker |
84 |
|
|
85 |
|
package XuStorm |
86 |
|
use UMLLinker |
87 |
|
use Storm |
88 |
|
|
89 |
|
package LibVob |
90 |
|
use UMLLinker |
91 |
|
|
92 |
|
package LibPaper |
93 |
|
use UMLLinker |
94 |
|
use LibVob |
95 |
|
|
96 |
|
package TheCoreProjectThatHasNoNameYetButIsTheRealOverallGoal |
97 |
|
use UMLLinker |
98 |
|
use Storm |
99 |
|
use XuStorm |
100 |
|
use LibVob |
101 |
|
use LibPaper |
102 |
|
|
103 |
|
--- |
104 |
|
XuStorm.c = Storm.c + (100, 100); |
105 |
|
LibPaper.c = LibVob.c + (100, 100); |
106 |
|
|
107 |
|
TheCoreProjectThatHasNoNameYetButIsTheRealOverallGoal.c = UMLLinker.c + (500,0); |
108 |
|
|
109 |
|
.5[Storm.c, LibPaper.c] = .5[UMLLinker.c, TheCoreProjectThatHasNoNameYetButIsTheRealOverallGoal.c]; |
110 |
|
Storm.c = LibVob.c + (0, 300); |
111 |
|
|
112 |
|
|
113 |
--------- |
--------- |
114 |
UMLLinker |
UMLLinker |
116 |
|
|
117 |
:Maintainer: Asko Soukka |
:Maintainer: Asko Soukka |
118 |
|
|
119 |
|
A software engineering documentation tool using ReST and providing |
120 |
|
multidirectionally hyperlinked UML diagrams. |
121 |
|
|
122 |
----- |
----- |
123 |
Storm |
Storm |
125 |
|
|
126 |
:Maintainer: Benja Fallenstein |
:Maintainer: Benja Fallenstein |
127 |
|
|
128 |
|
A new type of distributed computer storage framework with global, unique |
129 |
|
ids. |
130 |
|
|
131 |
Todo: |
Todo: |
132 |
""""" |
""""" |
133 |
|
|
134 |
- Figure out whether to do the "storm2" headerless stuff? |
- Figure out whether to do the "storm2" headerless stuff? |
135 |
|
|
136 |
|
- URN-5 code should be moved into this software |
137 |
|
|
138 |
|
-------- |
139 |
|
Xu-Storm |
140 |
|
-------- |
141 |
|
|
142 |
|
:Maintainer: Tuomas J. Lukka or Benja Fallenstein |
143 |
|
|
144 |
|
An implementation of xanalogical hypertext on top of the distributed Storm |
145 |
|
library. |
146 |
|
|
147 |
|
|
148 |
------ |
------ |
149 |
LibVob |
LibVob |
150 |
------ |
------ |
151 |
|
|
152 |
:Maintainer: Tuomas J. Lukka |
:Maintainer: Tuomas J. Lukka |
153 |
|
|
154 |
|
A graphical library providing automatic animation between unrelated |
155 |
|
views, if the views are reasonably defined. |
156 |
|
|
157 |
Todo: |
Todo: |
158 |
""""" |
""""" |
159 |
|
|
162 |
- Make the renderable structure better and easily extensible by |
- Make the renderable structure better and easily extensible by |
163 |
external code |
external code |
164 |
|
|
165 |
|
- document well |
166 |
|
|
167 |
-------- |
-------- |
168 |
LibPaper |
LibPaper |
169 |
-------- |
-------- |
170 |
|
|
171 |
:Maintainer: Janne V. Kujala |
:Maintainer: Janne V. Kujala |
172 |
|
|
173 |
|
A library which creates unique backgrounds from given seed values. |
174 |
|
The backgrounds are maximally recognizable as well as legible for black |
175 |
|
text. |
176 |
|
|
177 |
|
|
178 |
Todo: |
Todo: |
179 |
""""" |
""""" |
183 |
- Might it be possible / feasible / worth it to untie the code from LibVob; |
- Might it be possible / feasible / worth it to untie the code from LibVob; |
184 |
possibly later. |
possibly later. |
185 |
|
|
|
-------- |
|
|
Xu-Storm |
|
|
-------- |
|
|
|
|
|
:Maintainer: Tuomas J. Lukka |
|
|
|
|
|
|
|
186 |
----------------------------------------------------- |
----------------------------------------------------- |
187 |
TheCoreProjectThatHasNoNameYetButIsTheRealOverallGoal |
TheCoreProjectThatHasNoNameYetButIsTheRealOverallGoal |
188 |
----------------------------------------------------- |
----------------------------------------------------- |
189 |
|
|
190 |
:Maintainer: Tuomas J. Lukka |
:Maintainer: Tuomas J. Lukka |
191 |
|
|
192 |
|
Todo: |
193 |
|
""""" |
194 |
|
|
195 |
|
- Figure out the new structure |
196 |
|
|
197 |
|
- Write the code to make use of the new structure |
198 |
|
|
199 |
|
|
200 |
|
|