Your comments
Unfortunately the webview currently can't prevent zooming on its own.
I could put in a feature request to implement scalesPageToFit="No" as an option in our engine.
Let me double check to see if there isn't a solution that already exists.
I could put in a feature request to implement scalesPageToFit="No" as an option in our engine.
Let me double check to see if there isn't a solution that already exists.
Yes. The web tag can use most panel tags including all dimension parameters (height, width, xpos, ypos, etc.) and action triggers (onclickup, onswiperight, etc).
This makes the panel a VERY important object for most other objects. In the documentation we chose to call out only unique attributes outside of the extended ones. Though in this case it might make sense to list height and width as required on the web tag documentation.
Thanks!
This makes the panel a VERY important object for most other objects. In the documentation we chose to call out only unique attributes outside of the extended ones. Though in this case it might make sense to list height and width as required on the web tag documentation.
Thanks!
Great, I am glad you got it working.
Our best practice is to use the action <load url="about:blank" target="WEBTAGALIAS" /> targeting your web panel anytime you plan to navigate away from it in your app, this helps keep memory to a minimum.
Our best practice is to use the action <load url="about:blank" target="WEBTAGALIAS" /> targeting your web panel anytime you plan to navigate away from it in your app, this helps keep memory to a minimum.
Interesting. A couple of things to note here.
First of all onloadcomplete will only work when a datasource is being coupled to the panel in question.
I was able to load a web page just fine using your code minus the onloadcomplete portion:
Can you give me a little more detail about your device? Are you able to see your app in the fusebox list? Can you see the webview loading with a wait spinner and your toolbar or is the app not launching at all?
First of all onloadcomplete will only work when a datasource is being coupled to the panel in question.
I was able to load a web page just fine using your code minus the onloadcomplete portion:
<wire>
<main>
<panel name="web" alias="WEB" height="100%" width="100%" ypos="0">
<toolbar name="toolbar" height="5%" width="100%" align="left" valign="top">
<panel name="button" width="10%" height="80%" align="left" margin="10" valign="center" background="#888888" cornerradius="5" >
<text name="back" width="50%" height="50%" color="#000000" font="" size="12" align="center" valign="center" text="Back"></text>
</panel>
</toolbar>
<web name="web-panel" alias="WEBPANEL" width="100%" height="95%" valign="bottom" url="http://cnn.com"></web>
</panel>
</main>
</wire>
Can you give me a little more detail about your device? Are you able to see your app in the fusebox list? Can you see the webview loading with a wait spinner and your toolbar or is the app not launching at all?
Also can you confirm that you have your wifi or cellular working?
You can use <code> blocks to display your code.
I would be happy to take a look.
I would be happy to take a look.
Generally PDFs on tablets need to find the sweet spot depending on the device you are targeting.
You need to find the middle ground between the size of the PDF and the crispness of the images on the device you are targeting. This usually means that all of the images inside of your PDF need to be rendered anywhere between 132 DPI and 264 DPI. This is not quite print ready, which approaches 300 DPI.
We typically use a product called PDF Enhancer in house to optimize PDFs as they come in from clients. This helps us remain consistent from one app to the next.
You need to find the middle ground between the size of the PDF and the crispness of the images on the device you are targeting. This usually means that all of the images inside of your PDF need to be rendered anywhere between 132 DPI and 264 DPI. This is not quite print ready, which approaches 300 DPI.
We typically use a product called PDF Enhancer in house to optimize PDFs as they come in from clients. This helps us remain consistent from one app to the next.
You are not the first person to bring this up. It has been placed on our roadmap and will be under discussion.
Thanks for the request!
Thanks for the request!
By defining your height/width to full screen (width="1024" height="768" OR height="100%" width="100%") and not using fullscreen="yes", you can force the video tag to ignore minimize by using scalingmode="fit".
Customer support service by UserEcho
email me at community@rarewire.com and we can work out some details. We would be more than happy to come out and see what we can do.