Open GoogleCodeExporter opened 8 years ago
Hello,
Could you explain your use-case? If you want to provide a browser functionality
to your Glassware, why not launching an Activity with a browser intent instead?
You can do that with the ACTION_VIEW intent
(http://developer.android.com/reference/android/content/Intent.html#ACTION_VIEW)
and an "http" or "https" scheme in the intent URI.
Best,
Alain
Original comment by ala...@google.com
on 9 Jan 2014 at 4:24
Hello Alain,
Use case is as follows:
We want to retain control of the view so we can get back to our app and we want
to be able to call into the WebView to provide additional functionality.
Best,
Mike
Original comment by MikeSmal...@googlemail.com
on 10 Jan 2014 at 8:23
Hello,
Sorry for the late reply... Could you provide more details as to your use-case?
What would the user experience be like?
The reason I'm asking is to understand what a user would do on your app and how
you expect the user to interact with the WebView.
Thanks!
Alain
Original comment by ala...@google.com
on 14 Jan 2014 at 11:57
Sorry to dredge this back up, but the ability to pan and scroll a webview is
ESSENTIAL for us.
I cannot believe you cannot! Correct me if mistaken? You CANT even 'scroll' a
webview on Glass? At least, that's what i've seen.
The use case for this is content delivery, we have a system by which there is a
native application and various 'modules' from our custom CRM loaded into the
app, by way of providing live 'code changes' from a web panel and hide any real
knowledge that it is in fact a webview.
Original comment by Br...@live.co.uk
on 4 May 2014 at 10:11
Check out my workaround uploaded to Github here:
https://github.com/mikesmales/GoogleGlassCrosshairs
Original comment by MikeSmal...@googlemail.com
on 17 May 2014 at 7:35
Original issue reported on code.google.com by
MikeSmal...@googlemail.com
on 9 Jan 2014 at 10:20