Webviewer Render local html file

Discuss
#1

Hello,

I have a local file created by the user. It is basic html and named 232432,html

I am trying to render it with the Webviewer component .local using the file name.
When I load it with the component method, it shows the raw HTML and not it rendered.

Any tips?

#2

Can you please show the blocks?

#3

Well there is nothing to show. I call the component and I try either an HTML variable or a stored file and neither render.

I call the file, and on file get text I store it to a variable, or I just use the filename in a variable.

Both techniques show the raw HTML and not it rendered.

image
image.png1126Ă—114 13.7 KB

#4

Try using the .PathToAssets block from Taifun’s Tools Extension:

Screenshot_20190123-183008_1
Screenshot_20190123-183008_1773Ă—204 25.8 KB

I haven’t tried it but I think it will work. Let me know how it goes. :slightly_smiling_face:
P.S.: You must have the HTML file uploaded in the app’s assets.

#5

It is not an assett. It is a local created one based on the users interaction with the app.

Finding the file is not an issue. It sees it, and the correct version . It just does not render. It shows the raw HTML .

</

etc

It is about showing it as a proper rendered page which is my issue.

#6

Use GoToUrl block instead.

05cbb620c5c3182a4cea286d2bf8d3438b5b145f
05cbb620c5c3182a4cea286d2bf8d3438b5b145f.png736Ă—323 21.3 KB

I use something like this in my music player.

4 Likes
#7

That is exactly what I am looking for. Second question @Fabio How did you find the full path?

1 Like
#8

I use file:///storage/emulated/0/… for files in the device internal storage. I’ve learned it from tutorials on the internet.

1 Like
#9

Ok Thanks. Cause I saw you prefixed your file with / and the ToolTip says that goes to an SD card.

Let me give it a go. You have been a great help.

Thanks!

— UPDATE (I am not trusted enough to reply to myself) —

So as an update, it appears that there was a conflict with my layout, as well as some real nasty lag on the screen.

So what I did was setup a new screen, and a temporary tag in the tinyDB to pass the url. In short, I moved the webviewer to another screen and it works perfect now.

1 Like
#10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.