How to start the One Step Adapter (OSA)

Click below to start Geogebra OSA in Version 5.0. Particular builds of GGB is used:

• Latest Build generated by GitHub Actions (now 720)

GGB builds generated by GitHub Actions are available as releases in this repository. 

How to use the OSA

The OSA  starts as a Geogebra page. To obtain a OSAed version of SomeName.ggb file one has to fill the input boxes  and click the button "Select Files". Then a file picker comes up and you can select one or more files SomeName.ggb.

The service do his work and then  prompts to download  the OSAed  ggbs that are the adapted versions of the input ggbs. The user can specify with "Output Filename Suffix"  ONE suffix to be added to the output filenames.  Here are the meanings of the input fields. When the situation requires more inputs they can be given as a ash (#) separated list. If the situation requires a list of lists you can put an hash separated list of percent (%) separated lists. For instance as in "Valider%Delete[Valider]#Bouton2%Delete[Bouton2]" where one finds the two couples Valider%Delete[Valider] and Bouton2%Delete[Bouton2]. Here is the list of input fields and their meaning:

• Name or caption of deleted objects: the given list of strings are taken as GGB objects name that must be deleted. If they are not found then the OSA searches for objects that have these strings as captions. If nothing is found no action is taken and the OSA proceeds.
• Name or caption for appended code: a list of couples, e.g. a|code1,b|code2,c|code3 is required. Then OSA searches for objects (named or with caption) a,b,c and append the string  code1 (for a), code2 (for b etc.) to the script associated with the object. What actually happens depends much on the GGB internals. Please consider that if the object a has a GGB script then string code1 must be a valid GGB script fragment (not a JS fragment). The type of the object also plays a big role. For buttons the code goes to  the onclick script.
• Name or caption for substituted code: similar to the previous field. The existing code is deleted and the given code  is placed instead of it.
• Libraries: a list of strings that are taken as URLs for JS files that will be  loaded by the OASed GGB activity when launched. These files ARE NOT loaded when running this OAS service.
• Output Filename Suffix: just one string e.g. "-one" and the output of processing foo.ggb will be foo-one.ggb
• Init code: a string with a JS fragment that will be added to the initialization code run by the OASed .ggb when starting.
• Initialization Functions and JS global variables: a list of strings that are the prefixes of the names of the global variables and functions that are needed in the initialization code. Please note that initialization to global variables are not propagated. You should add it yorself in the the initialization code. On the other hand the code for the functions is scanned to find other functions names that are needed. If some functions are needed in other places put them in this list. To limit the number of functions to be searched the filter in the field "Filter" is applied. The Filter is a list of strings that acts as prefixes. If the Filter is, for instance, "RT_,ST_" only functions starting with RT_ and ST_ are included.
• Buttons to add: a list of triples e.g. name|caption|code. For instance n1|c1|sw1. creates button named n1 with caption c1 and with handler given as the function named sw1
• Global variables outcore in GGB text: if set the global variables one might set and retrieve with functions in the package ggbGlob.js are kept in GGB text variables and are persistent. If not set the functions in ggbGlob.js use JS variables. that are more compact and fast but are not persistent.
•  Filename on: if set some code is added to have a GGB text variable holding the name of the original .ggb file. This variable is a global variable that must be accessed by the functions in the package ggbGlob.js and is named THISFILENAME (what else?).

In particular the choice in the example will give files SomeName-one.ggb decorated with an additional button LOG that you can use to output a html file (by function RT_R_DocHndl) with the snapshot taken with the function RT_R_oneHndl2 linked to the button Bouton2 in the initialization code.This snapshot the GGB exercise situation every time Bouton2 is pressed.  The other code ensures that Bouton2 is deleted upon the first  click. For completeness let's add that RT_R_oneHndl2 snapshot both Graphics and Graphics2 views while there is provision in the code for the function RT_R_oneHndl that just snapshots Graphics.

Browser problems

The translator tool works only in the Geogebra web version some  problems might come from security limitations of the browser. You can circumvent it by running the Geogebra applet in Chrome with the option `--disable-site-isolation-trials --disable-web-security` e.g. in Windows

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-site-isolation-trials --disable-web-security --user-data-dir="I:\temp"

For Chrome you might try also --disable-web-security --allow-no-sandbox-job --allow-sandbox-debugging  --no-sandbox  --no-sandbox-and-elevated  --no-zygote --no-zygote-sandbox --run-without-sandbox-for-testing --disable-popup-blocking   --user-data-dir="I:\temp" they could help.

The file index<somename>.html loads the GGB application and the GGB activity `valinonestep.ggb` into a GGB Applet that runs in a browser. Loading could be slow. While debugging you can re-initialize the translator from the GGB File menu by reloading the `valinonestep.ggb` file.

Eclipse Repository

This project was developed and maintained using Eclipse and Egit. Not all the files have a  clear meaning. The repository is undoubtedly messy. Nevertheless the repository contains all files generated by Eclipse. By forking this in GitHub and by cloning your fork directly from  GitHub into Eclipse with a Egit clone operation you will get an Eclipse project to modify and develop this package on your own. If you feel that later on you can cooperate with us  branch your project locally this will make your contribution later submit-able as a pull request. The `.launch` files you will find in this repo must be imported into Eclipse separately to get debug configurations.