Suggestions on how to make ODAC documentation better.

[Challenger]

Dear users,

In the next stage of constant ODAC development we decided to focus on its documentation. As we value your opinion on our products, you are welcome to make comments and suggestions on what you would like to see in the documentation.

We invite you to share your experience and point out what aspects of ODAC documentation should be improved. Please post your comments and suggestions in this topic.

Core Lab development team
http://www.crlab.com/

[kurtbilde]

I'll susgest that you make an addition to your documentation. In order for us to understand the components I'll suggest that you make tutorials shows how to use a given component. It could be a client / server app build from gound and up, explaning i detail what to consider and how to do things.

-Kurt

[jfudickar]

For me it's a must that the help is integrated into D2007.

Greetings
Jens

[polsol]

My suggestion would be to make the documentation available in PDF format.
Not sure about others but I hate to sit in front of a PC trying to learn the 'ins and outs' of software. Spend enough time in front of a PC as it is.
Rather sit in an arm chair and go through it.

The printing system in D2007 from help doesn't work properly anyway so one must print page by page. A real pain not to mention waste of paper.

Otherwise agree with kurtbilde that tutorials are the easier route to learn software - but again, as PDF documents, not help files!

[Plash]

You can download ODAC help in PDF format from our web site (see 'Documentation and Demo' section):
http://www.crlab.com/odac/download.html

[mxwx]

I'll susgest that you make an addition to your documentation. In order for us to understand the components I'll suggest that you make tutorials shows how to use a given component. It could be a client / server app build from gound and up, explaning i detail what to consider and how to do things.

-Kurt

and even so to explain "special" features that couldn't or won't be used in the example "base-application". What I have waste some time with was to find out what component is interacting with wich one in what kind. Maybe a overall-plot of the components and its "connections" would be fine. I even had some difficulties to get explained (to find info in the doc's) some of the properties of a component. At the beginning I had sometimes problems to find out which property is interacting or has what kind of effect concerning to other properties or components.