Miguel wrote: > > Hello, > > > > I found some issues in the documentation. JmolDevelopersGuide.docbok.xml > > does not contain valid xml[1]. I fixed this. But: I use tabs (the > > current source is mix of tabs and spacings) for indent and I don't use > > linewrap after 80 chars for a better look. > > > > Q: Does anyone run into problems with such a xml file? (maybe someone > > uses console for writing the dosc) > > Well, I never used tabs and I always wrap at 80 chars ...
I will see, if I find an easy way to rewrite the doc without tabs and 80-chars lines. [xml translation] > > Next: I found the next cyclic dependency during my work to provide > > common Debian packages. The point is, that I need jmolApis.jar and > > jmolIO.jar for compiling the CDK-classes, and then I need the > > CDK-classes for compiling Jmol(Applet). > > Why do we need the CDK classes to compile? jmol2cdk.jar and jmolappletcdk.jar contain cdk classes. I'm working on a situation, where I do not need any precompiled java libs. I know, that someone is working on vecmath and Acme for Debian. At the moment, I can substitute all other jars with Debian ones. There are only the above mentioned libs (and vecamth + Acme) left. So I took a look into them and found, that they contain cdk classes. So my way is: - build jmolApis.jar and jmolIO.jar - use them to create the cdk jars - use cdk-*.jar instead of jmol2cdk.jar and jmolappletcdk.jar to compile Jmol and JmolApplet That's the idea behind. If I'm right, there is no need for me to use jmol2cdk.jar and jmolappletcdk.jar. > Is it because of the CdkModelAdapter? Yes. But there are also Jmol.java and JmolEditBus.java, which try to import cdk-classes (also see 'find src | xargs grep -n import.*\.cdk\. | less') > > So I patched build.xml, that I > > can compile the jmolApis.jar and jmolIO.jar only (without compiling the > > whole source). Means: I made a apisio.classes files and the targets > > apis-jar/io-jar depend on their own project-path and classes-directory. > > > > Q: Can I add this to the upstream build.xml? It will not affect the > > upstream. It is only for compile _only_ jmolApis.jar and jmolIO.jar, > > without compiling the whole Jmol source. > > OK Thx. [sample directory in source distribution] > > Q: Can we agree to exclude the sample directory from the source tarball > > and better distribute the samples in their own tarball? > > Agreed! I will upload the necessary changes with my next updates to build.xml. Regards, Daniel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
