I personally like the PDF documentation. I think the wiki is good for one off examples or learning about a specific part of iBATIS. The PDF seems to flow together more like a good book. After I'm done reading a section I usually continue reading the next section. After 15min or so I find that I've read 3 or 4 sections and I go away with more knowledge than I had originally intended.
I can never find what I'm looking for with wikis. It seems like there's so much information and pages are scattered all over the place. Is the wiki really that active? I get the impression that its just as dormant as patches for the existing pdf documentation. I looked at the wiki today and saw that several pages had been updated recently but I think this was due to the recovery efforts from last week(?). In theory wikis are a great idea; anyone can update content without having to have a special xml editor program. I don't think we should think about switching from the xml based documentation until the wiki is at least as active as the mailing lists... --- Clinton Begin <[EMAIL PROTECTED]> wrote: > What if we ditched the documentation altogether and started using the > wiki > as our primary documentation? > > * We could update it quicker and easier > * Anyone could update it > * Confluence has a PDF export feature > > Thoughts? > > Clinton > > On 9/27/05, Dan Bradley <[EMAIL PROTECTED]> wrote: > > > > 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 > > > > > >
