<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
El 07/23/2008 06:42 PM, Pau Arumí escribió:
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite">
<pre wrap="">On dc, 2008-07-23 at 17:58 -0300, Natanael Olaiz wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So, with all this context I ask: what do you think to add the Window
menu item, and a "close network" subitem on "file", to allow having
severals opened networks? The active one will be the one you are
seeing (on the original "Network" tab).
</pre>
</blockquote>
<pre wrap=""><!---->
And what would you do with the NetworkPlayer if the user change tabs
while running?
</pre>
</blockquote>
Ignore the requests? :)<br>
<br>
I don't know what is the best way to manage that. Maybe letting the
user to chose the view and the active one, maybe having another tab...<br>
<br>
Hernán had suggested something similar: <a
href="https://llistes.projectes.lafarga.cat/pipermail/clam-devel/2008/001875.html">https://llistes.projectes.lafarga.cat/pipermail/clam-devel/2008/001875.html</a><br>
<br>
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite">
<pre wrap="">I don't see multi-document useful in NetworkEditor (though I'm always
open to get convinced)
I think that NE with subnetworks should look like a code debugger: you
deal with two views: 1. the stack showing a list higher contexts of the
current inner executing line and 2. the code in the chosen context.
Now, back to NE: of course 2. corresponds to the network selected in 1.
And 1, could be a textual list, as a first version, and a "list" of
networks miniatures as a second version.
</pre>
</blockquote>
I imagined a main running-capable network canvas, from where you can
make/open a subnetwork (in the same, or other tab), and if from the new
canvas view you can do the same, and so on with sub-sub-...-networks.<br>
<br>
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite">
<pre wrap="">However, in my opinion subnetworks should not be approached from the UI,
but from the model. Because now it's hard to decide how will be the
model the UI will interact till it's not done.
</pre>
</blockquote>
Yes. That is the reason because I said to duplicate some parameters for
now, on the main canvas. But I though the graphical management (canvas)
as a useful tool to test and see the models. Anyway, now I understand
better your idea on the reply to Hernán in the previous thread.<br>
<br>
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite">
<pre wrap="">Refreshing a talk at irc, this should be the steps:
1. improve current Network interface to facilitate Network clients
(basically NetworkCanvas and FlowControl) getting the graph
2. make Network a composite (as in the pattern).
3. work ou the UI
</pre>
</blockquote>
But on 1. I used methods of ClamNetworkCanvas and inherited members.
For instance, how would you make the subnetworks? I started with
selecting the processings on the canvas, and reusing the actual network
xml dump and restore methods (used for loading/saving and
copy&paste). Another option I think could be to import a network as
a subnetwork. But the positions are managed from ClamNetworkCanvas, not
NetworkCanvas. Should I ignore the geometries for now, or implement
those methods on NetworkCanvas as a part of the refactoring and let all
the CLAM::Networks management be just on NetworkCanvas?<br>
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite">
<pre wrap="">Point 2 is difficult. My design proposal (discussed with David) is the
following: the root of the composite should have a FlattenedNetwork
object associated. FlattenedNetwork and Network both derive from an
abstract BaseNetwork. Only FlattenedNetwork have a NetworkPlayer and a
FlowControl, and owns all the processings in the hierarchy.
This should be more discussed, and developed test-driven in small steps.
</pre>
</blockquote>
OK.<br>
<br>
<br>
Regards,<br>
Natanael.<br>
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite">
<pre wrap="">
P
_______________________________________________
Clam-devel mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Clam-devel@llistes.projectes.lafarga.org">Clam-devel@llistes.projectes.lafarga.org</a>
<a class="moz-txt-link-freetext"
href="https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel">https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel</a>
</pre>
</blockquote>
<blockquote cite="mid:1216849375.10473.99.camel@macbook" type="cite"></blockquote>
<br>
</body>
</html>