Community
Participate
Working Groups
I would very much like to know what CDO is, since cool people are talking about it. So I went to http://www.eclipse.org/cdo/ and clicked the big Documentation link. The result is a page with a navigation bar on the left, but no content. So I clicked "About" but this gives a 404 Not Found. Going back, I clicked on "Manual 2.0" and this resulted in an almost-empty "Work in Progress" page. Finally I clicked on Presentations and this led to a series of slides mostly written in the Presentation Zen style... i.e. very pretty but totally useless as standalone documents. Overall the approach to documenting this project seems far too zen-like. When it comes to documentation, less is NOT more. Please fix this!
Hi Neil, thanks for your interest. We are aware that the volume of documentation is less than optimal and we would really like to have more of it. Currently the best sources for information are (probably in that order): 1) The CDO webinar listed in the Presentations section of the homepage 2) The wiki http://wiki.eclipse.org/CDO 3) The JavaDocs of the interfaces Unfortunately the sponsors of CDO are not funding documentation work in particular but rather some large and very interesting new features like an offline mode. Hopefully I (or somebody else) will find time to add necessary manual pages for Helios...
At some eclipse democamps I presented our redview - CDO Integration. there was much discussion about missing documentation and examples of CDO: * easy download of a default-configured CDO Server * example of EMF Library with Editor to open and edit from CDO Server ekke
(In reply to comment #2) > * easy download of a default-configured CDO Server Generally a good idea but a bit vague. Do you mean OS-specific executables? I would like that idea and long ago I filed a CQ for the usage of an installation wizard. It was rejected by the foundation ;-( > * example of EMF Library with Editor to open and edit from CDO Server Why does it have to be the Library example? We have a somewhat complexer "Company" example. Maybe we should mention that in the docs...
(In reply to comment #3) > (In reply to comment #2) > > * easy download of a default-configured CDO Server > > Generally a good idea but a bit vague. Do you mean OS-specific executables? I > would like that idea and long ago I filed a CQ for the usage of an installation > wizard. It was rejected by the foundation ;-( at first it could help a short description "HowTo start a CDO server" something like: install EPP Modeling add updatesite xxxx choose bundle a + b copy configfile xxx from xxx to config location xxxxx (OS specific) import launch config start server and then the hint "never quit application - always use close from cosole - otherwise at restart server reports corrupt data much better would of course be something more automated like install CDO Server then provide a client to test the server with a simple hello world example > > > * example of EMF Library with Editor to open and edit from CDO Server > > Why does it have to be the Library example? We have a somewhat complexer > "Company" example. Maybe we should mention that in the docs... this was only an example ;-) doesnt matter what, but (as Jochen Krause said) it must be easy to follow so the developer has success and then is motivated to go deeper into CDO only my 2cts
Rebasing all outstanding enhancements requests to version 4.0
Moving all open enhancement requests to 4.1
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
*** Bug 391103 has been marked as a duplicate of this bug. ***
Moving all outstanding enhancements to 4.3
Moving all open enhancement requests to 4.4
Moving all open bugzillas to 4.5.
I've finally managed to add a complete User's Guide that explains how to use the new CDO Explorer user interface and an Operator's Guide that explains how to configure and operate a CDO Server. I've also added some articles to the Programmer's Guide.
The changes are committed to master: http://git.eclipse.org/c/cdo/cdo.git/commit/?id=25e044eec0e03b601204ef0daaaf07ae23aff194
And back-ported to 4.4 via bug 478047.
Closing.
