![]() |
|
updated 2020-03-17 |
Herbalists' BootCamp
|
Subtopics on this page… Tutorial #2-supplement(APPS): Apps vs. Java shellscriptsYears ago, the --.app (MacOS-X) and --.exe (Windows) versions of our software were packaged as standard MacOS-X and Windows applications as well as Java apps launchable via shellscripts (like --macosx-cmd and --.windows-bat ). The problem with apps: both Microsoft and now Apple like to play nasty games with developers by subtle changes in their application programming interface (API) every few years. That is the primary reason why many of your old apps will frequently ‘"break" and no longer work unless you upgrade the apps along with your OS. The way around this is for us, the developer, to package everything as a Java application plus command line shellscript launcher, because this makes us dependent only on Oracle Java, which is a mega-company whose task is to ensure continued compatibility of legacy (old) Java software with all newer OS (Windows, MacOS-X, Linux). While we are dependent on Oracle doing its job correctly and living up to its promise, so far Oracle has kept this promise quite well. We can still run most of our legacy software from the year 2000 on current operating systems. No guarantees for future changes in Java, which is out of our control, but so far this has worked extremely well for us. Here is how to set your HerbalThink-TCM Preferences so that the ‘command’ version for MacOS-X will always start when clicking the HerbalTutor button. It is only the very last option below that no longer works on latest MacOS-X systems.
Go back to Tutorial #2: CaseQuery
|