Currently I don't work on MediSnap. Maybe this will change in the near future if there is interest in this product. Especially this might get interesting in case a widely used medical system wants to bundle MediSnap with it's own product. (Which definitely is possible and allowed thanks to the free license of MediSnap!)
Anyway, if you provide me with cool patches, I'll be glad to integrate them into the main release!
If you don't send me your patch, you'll have to integrate your own changes into MediSnap everytime you upgrade to a newer version of MediSnap. If your patch got integrated into the official MediSnap development trunk, it automatically will be integrated in all future releases. Thats how free software works.
| /src/CreateCompileTimeConstants/ | Very small java helper application source. CreateCompileTimeConstants gets executed during the build process of the MediSnap Client Java Application just to create some constants during build time (e.g. current date-time-string to hard-include this as version-information into MediSnap.jar). |
| /src/Installer/ | A started but never finished installer for MediSnap. It's based upon NSIS (http://sourceforge.net/projects/nsis/). |
| /src/MediSnap/ | This is the main MediSnap Java client application source code. The GUI is created and managed with Netbeans. |
| /src/MediSnapStarter/ | This contains the source files for the MediSnap.exe, MediSnapBackground.exe and GDTStart.exe. These C++ files use some MFC stuff and thus need some commercial software to be compiled. I don't have this, so no binaries of these starters are included in the release. |
| /src/MediSnapStarterJava/ | This is probably the best starter for MediSnap if your system allows jar-files to be executed directly. The Java MediSnap Starter is completely configurable through the configuration-file MediSnapStarter.properties. If started with the command-line parameter 'gdt' it tries to connect to a running MediSnap instance and then tells it that a GDT-Call has been invoked. If no running instance was found it first starts MediSnap, and then calls the GDT-Interface. If no gdt-parameter was supplied, MediSnap is, if running, brought to the front from background or MediSnap is started into the foreground if its not running at all. Thus, if you use this starter, in the end always one instance of MediSnap will be running and shown if the configuration is correct :). |
| /src/interfaces/camera/OlympusMocha/ | Contains the C++ JNI Wrapper for the Olympus Mocha DLL. So the Olympus E-System sdk can be used with java applications. This wrapper is used by the package medisnap.camera.* in the /src/MediSnap client application source code. Of course it also needs the orginal Olympus DLLs provided by the Olympus SDK and a proper installation of the appropriate Olympus Mocha Services. It's a pity that Olympus is not able to provide these for non-ms systems.. |
| /src/interfaces/camera/OlympusRye/ | Contains the C++ JNI Wrapper for the Olympus Rye DLL. So the Olympus Rye sdk can be used with java applications. This wrapper is used by the package medisnap.camera.* in the /src/MediSnap client application source code. Of course it also needs the orginal Olympus DLLs provided by the Olympus SDK. It's a pity that Olympus is not able to provide these for non-ms systems.. |
| /src/web/ | This web site. |