Re: [cosmos-dev] Data Visualization Code Base Structure

[Sheldon Lee-Loy <sleeloy@xxxxxxxxxx>]

Hi Marius,

The document is not ready to be published
on the web area.  That's why it's in the COSMOS CVS.  

From my understanding ATF is not an
AJAX runtime toolkit.  It provides tooling to develop AJAX applications
using existing AJAX runtime toolkits such as DOJO,prototype etc.

The api is a rough sample api just so
that the reader gets an idea of the level of abstraction.  Yes, we
need to come up with a list of cursor "like" apis.

Thanks,

Sheldon
______________________________________
Sheldon Lee-Loy
Tivoli Autonomic Computing, IBM Toronto Lab

Marius Slavescu/Toronto/IBM@IBMCA
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

04/20/2007 02:54 PM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To	Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
cc
Subject	Re: [cosmos-dev] Data Visualization Code Base Structure

Hi Sheldon, 

The images doesn't show up in the design document, it's a problem with
CVSView, please post this document in CVS in the COSMOS web area, in a
similar place like TPTP feature area. 

You should also mention Eclipse  AJAX Toolkit Framework http://www.eclipse.org/atf/
project in your AJAX toolkit list, I suppose that would be the one that
we will use in COSMOS. 

Also I would try to avoid to represent query results as arrays, as they
cannot be paged, like in your facade sample: 

        public CommonBaseEvent[] getCBEsFilteredBy(String
criteria) 

a cursor like interface (see java.sql.ResultSet)
would be better (or even a simple extension to java.util.List
interface would let you control how to load the underlining data). 

Thanks !

Marius Slavescu
IBM Tivoli Autonomic Computing - Toronto Lab
Phone: 905-413-3610

Sheldon Lee-Loy/Toronto/IBM@IBMCA
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

04/20/2007 02:31 PM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To	cosmos-dev@xxxxxxxxxxx
cc
Subject	[cosmos-dev] Data Visualization Code Base Structure

Based on the design document (http://wiki.eclipse.org/index.php/CosmosDataReportingComponent)
I propose the following structure: 

Presentation Service plugins 
============================== 
org.eclipse.cosmos.dr.ps.common - core framework to create visualization
views 
org.eclipse.cosmos.dr.ps.components - component ui library (ie. navigator
mashup, properties mashup,etc.) 
org.eclipse.cosmos.dr.ps.report - birt preconfigured report components

Graphical Visualization Service plugins 
======================================== 
org.eclipse.cosmos.dr.gvs.views - examplar of the cosmos ui application
org.eclipse.cosmos.dr.gvs.report - report templates 

Data Retrieval Service plugins 
================================ 
org.eclipse.cosmos.dr.drs.service.handlers - services that will provide
REST(http://en.wikipedia.org/wiki/Representational_State_Transfer) handlers
for the cosmos UI. 

This information is captured under bug 180069.   https://www.eclipse.org/bugs/show_bug.cgi?id=180069


Comments? 

Thanks,

Sheldon
______________________________________
Sheldon Lee-Loy
Tivoli Autonomic Computing, IBM Toronto Lab_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev