# ANDROID BRANCH (for Mario Kosmiskas )
version=12.2.0_A
# All java.awt and java.swing references are now isolated.
# Two key packages to take a look at are:
#
# org.jmol.api.ApiPlatform -- a class that must be instantiated by
org.jmol.viewer.Viewer
# using reflection. To do this, pass the fol
I would like to second Bob's Fantastic! We've talked about this before, but
haven't had anybody with the time to pursue it. This is wonderful!
Since I'm guilty of some of the Swing portions of the Jmol code, I can say I
think Bob is right about where the is Swing. Everything I am aware of tha
Here's where I see Swing being used outside of Jmol.jar (the application):
org.jmol.applet.AppletConsole
org.jmol.export.dialog
org.jmol.modelkit.ModelKit
org.jmol.multitouch.JmolMultiTouchClientAdapter
org.jmol.popup.JmolPopup
viewer.StatusManager (prompt command display)
Not too bad, really. Mo
Mario,
Fantastic!
You might be interested in knowing that a few years back Jmol was completely
compatible with non-Swing applications, but we opted for integrating Swing
completely when we moved to Java 1.6 (sorry about that!). Let's get your
work onto SourceForge as an android branch and see wha
I was interested in making Jmol work on Android and spent some time refactoring
the code. The challenge was to isolate the graphics toolkit since Android
doesn't support Swing.
By removing the dependency on Swing I was able to successfully create a simple
Jmol Android App. The app is capable
