21 |
|
|
22 |
- xyz implicates Text, Image, Sound and Page etc. |
- xyz implicates Text, Image, Sound and Page etc. |
23 |
|
|
24 |
Another PEG will explain the enfilade handling of nodes. |
The content_handler--mudyc PEG will explain the enfilade |
25 |
This PEG only tells how node is to be placed knowning |
handling of nodes. This PEG only tells how node is to be |
26 |
nothing about the content. |
placed knowning nothing about the content. |
27 |
|
|
28 |
|
|
29 |
|
|
37 |
In the past we did usually have only text to show for user. |
In the past we did usually have only text to show for user. |
38 |
Today we have more media types: pagespans and images at least. |
Today we have more media types: pagespans and images at least. |
39 |
The View framework has been designed too much for text only. |
The View framework has been designed too much for text only. |
|
Text based design is also very deeply seen in Space where we have |
|
|
*VStreamNodeTexter* but that's an another story. |
|
40 |
Although text is the most common view media we should |
Although text is the most common view media we should |
41 |
easily be able to show any content in nodes. |
easily be able to show any content in nodes. |
42 |
|
|
124 |
Changes |
Changes |
125 |
------- |
------- |
126 |
|
|
127 |
I propous several interfaces to be implemented by suitable content state handler: |
I suggest several interfaces to be implemented by suitable content state handler: |
128 |
|
|
129 |
:: |
:: |
130 |
|
|
140 |
|
|
141 |
public interface PageState { |
public interface PageState { |
142 |
void setBackgroundTexVisible(boolean b); |
void setBackgroundTexVisible(boolean b); |
143 |
|
boolean isBackgroundTexVisible(); |
144 |
} |
} |
145 |
|
|
146 |
|
|
171 |
Changes |
Changes |
172 |
------- |
------- |
173 |
|
|
174 |
When NodeView has a new node to place it should mention it to ViewContext. |
When NodeView has a new node to be placed it should mention it to ViewContext. |
175 |
|
|
176 |
So ViewContext should implement the following interface: |
So ViewContext should implement the following interface: |
177 |
|
|
209 |
public abstract class NodeView implements NodeContent { |
public abstract class NodeView implements NodeContent { |
210 |
|
|
211 |
// Space/FenfireContext |
// Space/FenfireContext |
212 |
// for asking content - see the PEG followed be this PEG ;) |
// for asking content - see the PEG content_hanler--mudyc followed be this PEG |
213 |
protected Space/FFC/Fen foo; |
protected Space/FFC/Fen foo; |
214 |
|
|
215 |
// ViewContext - see 3) |
// ViewContext - see 3) |
220 |
protected RDFNode current; |
protected RDFNode current; |
221 |
|
|
222 |
// correct state/context handlers.- see 2) and 3) |
// correct state/context handlers.- see 2) and 3) |
223 |
// and see the PEG followed by this PEG. |
// and see the PEG content_hanler--mudyc followed by this PEG. |
224 |
public TextHandler text; |
public TextHandler text; |
225 |
public ImageHandler image; |
public ImageHandler image; |
226 |
public PageHandler page; |
public PageHandler page; |
227 |
} |
} |
228 |
|
|
229 |
It's important that all 1), 2) and 3) are combined in NodeView because it's so often used. |
It's important that all 1), 2) and 3) are combined in NodeView because it's so often |
230 |
Noone wants to use continuos type casting with long interface names. |
used. Nobody wants to use continuos type casting with long interface names with Java. |
231 |
|
|