tebelorg#86 - initial fix for homebrew openssl issue

see tebelorg#86 for more details

tebelorg#41 - adding setup message on Linux visual automation

follow-up commit to bump version in readme to v1.17

tebelorg#81 - move to Corretto OpenJDK + 64-bit check

see tebelorg#81 for details

tebelorg#71 - bug fix for select(), change to exact match

fix implemented upstream, see tebelorg#71 for details

tebelorg#36 - deploy on PCs without internet

see issue tebelorg#36 for details

tebelorg#62 - support changing directory halfway

See tebelorg#62 for more details

tebelorg#57 - clipboard() to get or put text

Follow-up commit to let both single and double quotes work properly if trying to put text to clipboard containing quotation marks.

---

To put text to clipboard or get clipboard text. See issue tebelorg#57 for details

tebelorg#50 - follow-up to frame()

sync upstream code-fix logic for frame step

tebelorg#36 tebelorg#50 tebelorg#52 - added frame() & popup(), fixed …

…snap() & read()

tebelorg#36 - add link to license in tagui.py to facilitate air-gap deployments (without internet access to pip)

# 50 - add frame() function to access web page frames (supports main frame and sub frame). add popup() function to access webpage popup tabs launched from webpage.

tebelorg#52 - bugfix for snap() and read(), when 'page' is used to mean entire webpage a 'cannot find page' error message appears.

tebelorg#35 tebelorg#34 - cleaner execution and error handling

tebelorg#35 - Cleaner usage and execution without TagUI intermediary files

During usage, the following temporary files will be generated in order to use TagUI -

tagui_python - simple flow to initiate TagUI live mode
tagui_python.raw - raw file for TagUI module expansion
tagui_python.js - generated JavaScript code for TagUI
tagui_local.js - TagUI for Python custom functions file
tagui_python.log - log file for automation execution
tagui_python.txt - to retrieve data output from TagUI

When debug mode is on using debug(True), only tagui_python.log and tagui_python.txt will be retained while the rest are deleted. That essentially means that the first 4 files above do not really add value to the typical TagUI for Python user. Having them in the script folder during execution may add clutter, clunkiness and confusion.

Furthermore, TagUI for Python has been downloaded over 5000 times since initial release, without users reporting issue that requires above 4 temporary files for debugging and troubleshooting.

Raising issue to update code to immediately delete the first 4 files upon connecting to TagUI to remove clutter. For the last 2 files, they will be retained until close() is used, where they will be deleted if debug(False) (default).

tebelorg#34 - graceful error handling on Windows folder path with space

On Windows, if script is used in folder path name with space, error message can appear without any meaningful information.

Some components of upstream project TagUI cannot work with spaces in the path and folder name containing the TagUI automation script. Solution is store the script in a folder path without space, or run it from a folder path without space in it.