> this little thread points nicely to the major problem that I have > quite often with PyMol: it is a really powerful program, but the > documentation is somewhere scattered between various incomplete > sources (manual, reference list, wiki, bulletin board, user home > pages, ...). This makes it very difficult for the average user like > me to make full use of PyMol's capabilities. I would _really_ prefer > to have a good and up-to-date documentation available, at least for > the last official version, rather than more and more improvements > with poor documentation.
In my experience, pymol's build in help system is a very good guide. Most of the questions I get from local users, as well as my own questions, can be resolved that way. When that fails, it's generally because I'm trying to do something that isn't directly supported (so I fall back on grep -nir $whatever in the source directory or the mailing list/list archives). I completely agree that having good documentation is important; but I haven't found pymol to be significantly lacking in that regard. I wouldn't mind more comments in the source code (particularly the underlying c modules), but that's probably due to lack of experience with 3d graphics programming on my part than anything else. just my opinion... Pete Pete Meyer Fu Lab BMCB grad student Cornell University
