Hi Jose Maria, > 2. Displaying composition results > >Jose Maria suggested, and I completely agree, that the demo would be incomplete if
we didn't have a separate tab that graphically displays the results >output by the composition.
I'm not sure where the breakdown is between what Optnet can generally provide and what the application/composition writer
>needs to code, perhaps someone has suggestions? >I have been thinking on it. Given that at the end we may not having user profiles (everybody can do anything on authorized applications/blocks/whatever),
I
>suggest to have "views". A view for BM compositions, another for BM compositions of compositions (for the controller), a view for data at BM, etc. I think I completely agree with this, but I just want to make sure I understood it :). The idea is to have different "views" that can be easily shown/enabled/disabled depending of the needs of the demo and of the logged-in user. The possible views are: 1. Composition view 2. Distributed composition view (compositions of compositions, but note that this also will contain the ability to draw node topologies) 3. Operator view (for the distributed BM demo, showing computers, what compositions are on them, CPU utilization, etc, etc) 4. Report view (not sure what dashboard is, is it part of this view?) 5. DEMONS/WPOC view (to be defined as the project progresses) Thus the 3 demos mentioned in your previous email would contain: 1. Single-node BM demo: views 1 and 4 2. Distributed BM demo: views 1,2 (1 for creating compositions, 2 for putting them together into a distributed composition) and 4 (for a user); and view 3 (for an operator) 3. DEMONS demo: views 1-5 Within each view, multiple tabs may be used as needed (for instance, view 1 would contain one tab per composition, since a user may be working on several at once). Is this right? -- Felipe |
Archive powered by MhonArc 2.6.16.