[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dash-dev] Dashboard architecture
|
The architecture makes sense, although it's true: when you have a
hammer, everything looks like a nail. And right now my hammer has been
EMF, RCP and Visualization. I am wondering how we can build Ecore
models for this data and visualize them in an RCP application.
I'm not sure if an Eclipse plugin which summarizes this data would
necessarily be useful to a developer, but it might be nice to have it
contained within Eclipse rather than having to hit a URL. Just a thought.
Cheers,
Ian
Bjorn Freeman-Benson wrote:
Ward and I have been working on the Commits Explorer
(http://dash.eclipse.org/dash/commits/). The basic architecture of
this dashboard is in three parts:
* A database summarizing all commits to all the Eclipse CVS
repositories
* A web API to run specific queries against this database (e.g.
http://dash.eclipse.org//dash/commits/commit-summary.php?top=y&year=x)
* A web front end to take the API results and
massage/format/navigate them in interesting ways (e.g.
http://dash.eclipse.org/dash/commits/summary.cgi)
We plan to build the same sort of structure for the old dashboard
data: newsgroups, mailing lists, bugzilla, etc. The combination of the
web API and the web front end allows other front ends to use the same
raw data. And the other front ends can run on other non-Eclipse machines.
What do you all think? Is this a reasonable approach?
- Bjorn
------------------------------------------------------------------------
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev
