A couple suggestions that I think would really help on the documentation front:

1) Take all the documentation that's currently available only in PDF
and make it also available in an HTML format

2) Host the current API javadocs online

And then, of course, more user participation in the Wiki. Replacing or
supplementing the mailing list with forums would also be nice.

I've been able to discover most of what I've needed about iBATIS so
far, but the above changes would have made it a lot easier.

On 9/27/05, Farsi, Reza <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been working with iBATIS and find it very good. The documentation
> has not the same high quality like the framework. I wonder if there is
> any document like e.g. iBATIS best practices.
>
> I'm reading the Developer Guide (DevGuide.pdf). I miss figure 1 on page
> three. Is it a converting problem (doc2pdf)?
>
> Regards
> Reza
>

Reply via email to