You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TagUI was initially designed for non-developer users. Thus it has provisions that make getting thing done as easy as possible for non-developer users. Steps like show and save are nothing more than read followed by printing out to screen or saving to text file.
Porting these steps over adds bloat to the Python API. Thus raising an issue to track and remove the redundant show() and save(). In place of t.show(), print(t.read()) or t.echo(t.read()) can be used. In place of t.save(), t.dump(t.read()) can be used.
Also, TagUI has a helper function visible() which checks webpage base on CSS rules whether a web element is visible on the page. An element can be present in the backend DOM but hidden from rendering. This helper function would be overly confusing and only adds a small benefit, since present() can be used and most users do not care of the fine line between being present in DOM but not visible. Also, for visual automation, present() and visible() means the same thing. Thus removing visible() improves clarity to standardise usage to present().
The text was updated successfully, but these errors were encountered:
Details at respective issues below.
#13 - Support OCR capability and regions of interests for read() and snap()
#12 - Streamlining API - remove show() and save(), remove visible()
Details at respective issues below.
#13 - Support OCR capability and regions of interests for read() and snap()
#12 - Streamlining API - remove show() and save(), remove visible()
kensoh
changed the title
Streamlining API - remove show() and save(), remove visible()
Streamlining API - remove show() and save(), remove visible() [done]
Jun 22, 2019
TagUI was initially designed for non-developer users. Thus it has provisions that make getting thing done as easy as possible for non-developer users. Steps like show and save are nothing more than read followed by printing out to screen or saving to text file.
Porting these steps over adds bloat to the Python API. Thus raising an issue to track and remove the redundant show() and save(). In place of
t.show()
,print(t.read())
ort.echo(t.read())
can be used. In place oft.save()
,t.dump(t.read())
can be used.Also, TagUI has a helper function visible() which checks webpage base on CSS rules whether a web element is visible on the page. An element can be present in the backend DOM but hidden from rendering. This helper function would be overly confusing and only adds a small benefit, since present() can be used and most users do not care of the fine line between being present in DOM but not visible. Also, for visual automation, present() and visible() means the same thing. Thus removing visible() improves clarity to standardise usage to present().
The text was updated successfully, but these errors were encountered: