While I like the idea of having something visual and DB-centric that people can
use for various purposes, I still can't wrap my head around of how to do
modeling away from access to the real DB and my Java projects. To me the main
value of the Modeler (since 4.1 anyways) is "cdbimport" and
Hi Ari,
I thought a bit about a web-based version of CM, too. I kind of liked the
idea (especially for your point #5 -- a Google Docs type of collaborative
editing), but ultimately decided it would introduce security/deployment
concerns I'd rather not focus on. I'd be happy to discuss the idea
One advantage of an html/js frontend would be to offer a service on our
website into which a user could paste their DDL as SQL, and get back:
1. a Cayenne map xml
2. a visual representation of their schema [1]
3. an editor which allows them to make changes
4. The ability to export an updated
