We've had a major obstacle with the use of the browser widget confirmed and
fixed.. and "awaiting release" it has to do with the browser widget not being
"destroyed" when no longer in view if you open a second stack in mobile, the
browser widget is still there in the pixel space above the whole stack (even
though you can't see it) and is trapping all tap/touch events…
see:
http://quality.livecode.com/show_bug.cgi?id=17962
for details.
it would be ideal to know when the "release" will be, but I guess that is
classified.
In the meantime it puts one on the fence… for development going forward, use
the widget or revert to the old "revBrowser"? The has, at least on the surface
of it, a much more robust API for controlling the web UX than the widget… (I'm
probably wrong there.. but just looking at the dictionary commands for either
one, that's the feeling one gets)
So the questions are:
1) what are the differences between the browser Widget and the old RevBrowser…
2) why would you choose one over the other?
3) Does the widget simply use an LBC wrapper for the same web it that the "old"
revBrowser uses?
Brahmanathaswami
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
