Beiträge von tinynestproject

Thank you for the info, I really appreciate it.
I guess I will have to include a separate "fullscreen" link outside of my iframe that simply loads the dedicated tour page... maybe I can write it such that it only shows on iOS, as to not clutter the rest of the sane world :P

Zitat

The iPhone doesn't support the HTML5 fullscreen mode at all.

How can Apple be this bad... I have no words to express my feelings of frustration towards things like this... it's completely nonsensical...
Is there official Apple documentation that describes this lack of support?

Is everything that runs inside iOS affected? or is it per-browser? (e.g. does Chrome for iOS support it?)

Thanks for the code to force support... if I were to add this (to tour.xml?) what would happen on an iPhone? would there be a fullscreen button that simply does nothing?

I do not own an apple device, so I only noticed this problem at a recent convention, when I had someone load a page that contains an iframe embed of one of my virtual tours, using an ipad. This problem is not present on Chrome on Android, but it is present in the DuckDuckGo browser on Android (which I'm currently using for testing).

I recently solved a similar problem that WAS present on Chrome on Android... there was an update to chromium that blocked mobile sensor access, resulting in the removal of the VR and gyro buttons from my embedded vtours (embedded using iframes). The solution that I found was two parts:
1. all data had to originate from secure locations (https)
2. I had to add updated tags to my iframe
I thought this had solved the problem (because it was fixed on Android), but now I know that the ability to toggle fullscreen is still missing from some mobile browsers.

Here is my iframe after solving that chromium update problem:

<iframe src="https://www.tinynestproject.com/explore/zyl-vardos/damselfly/" width="100%" height="320" allow="fullscreen; gyroscope; accelerometer; magnetometer; vr; xr"></iframe>

And here is my iframe after much effort to brute-force the allowing of fullscreen:

<iframe src="https://www.tinynestproject.com/explore/zyl-vardos/damselfly/" width="100%" height="320" allow="fullscreen; gyroscope; accelerometer; magnetometer; vr; xr" allowfullscreen webkitallowfullscreen mozallowfullscreen allowvr="true" allowfullscreen="true"></iframe>

none of the following would enable the fullscreen button in DuckDuckGo:
allow="fullscreen"
allowfullscreen
webkitallowfullscreen
mozallowfullscreen
allowfullscreen="true"
allowfullscreen="yes"

Banging my head against a wall here... what is preventing fullscreen from working? VR and gyro seem to work, which require access to the device's sensors...
Here is my testing page -> https://www.tinynestproject.com/explore/demo/

I have also found mobile VR to be quite laggy/jerky.
I may be remembering wrong, but when I first started experimenting with krpano about 2 years ago, it was better... have there been browser updates that put more load on a phone when it's trying to track motion?

Zitat von dan_R

sorry that i revive this old thread, but since i want to do exactly the same i thought to ask my question here.
i want to link the plugins folder to a specific path on our webserver. I tried to change every "%SWFPATH%/plugins/swffile.swf" to "https://www.website.com/code/plugins/swffile.swf" whitout luck. Now i want to change the %SWFPATH% path globally, but i don`t know how to do that with the embedpano line.

Here is an example from one of my tour.html files. Note that my folder-structure always has a tour-specific-folder inside a company-named-folder, and my global folder is at the same level as the company-named-folders. This is why you see ../../ because the global folder is always found two levels above the tour.html file. I have a template file from which I copy this chunk and paste it over any new tours that I make. It's a single added step during tour-creation.

<script src="../../KRPANO-GLOBAL/krpano.js"></script>
<div id="pano" style="width:100%;height:100%;">	<noscript><table style="width:100%;height:100%;"><tr style="vertical-align:middle;"><td><div style="text-align:center;">ERROR:<br/><br/>Javascript not activated<br/><br/></div></td></tr></table></noscript>	<script>		embedpano({swf:"../../KRPANO-GLOBAL/krpano.swf", xml:"tour.xml", target:"pano", html5:"auto", mobilescale:1.0, passQueryParameters:true});	</script></div>

Zitat von lerayfle

First, skins and plugins locations are usually %SWFPATH%/plugins and %SWFPATH%/skin, most of the time hardcoded in vtourskin or plugins themselves.
If you want to change locations:
- either you change %SWFPATH% globally (through the embedpano line in js)
- either you ctrl+f the whole code, and override all attributes where you can see %SWFPATH% and change it to your needs, but it will be a lot of work, and it may break on future krpano updates. If you still want to do it, you can take as an example the "skin_base" style in vtourskin, nicely done with a calculated path rather than a hardcoded %SWFPATH%.

Second, for your code structure, modifying vtourskin.xml is a bad habit because when you have a lot of code there, it can become a pain on each krpano upgrade.

You could for instance split your code in 3 parts :
- vtourskin_mod.xml : all that is vtourskin.xml direct modifications (fixes, changing order of layers in the bottom bar, etc...), all that is directly linked to vtourskin and could break on a krpano upgrade. Also, in vtourskin_mod add the "include vtourskin" line;
- default.xml : all skinsettings or plugin settings, and all that is shared or could be needed by all your tours (events, actions, etc...), but that is not in vtourskin_mod.xml. In there add an "include vtourskin_mod.xml" line.
- tour.xml : all that is specific to your tour and not shared with other tours. In your tour.xml, include default.xml and you'll have all your default actions, events, settings, etc ... + it will cascade automatically and include vtourskin.xml and vtourskin_mod.xml.


On a krpano update, you'll (ideally) only have to check vtourskin_mod.xml if it is still aligned. If you split things correctly, default.xml and tour.xml (the biggest parts of your code) should keep working through updates. Maintain vtourskin_mod.xml the smallest possible, but if you note actions in default.xml often break on updates, you can send parts back to vtourskin_mod.xml not to forget to check them on next update. This way you have a simple file to check on updates.

Alles anzeigen

Thanks for all this info. I will definitely reference this the next time there is an update.
The last time I did a krpano update, I went through a process of comparing the new xml to the existing one I had modified, and manually copied over my alterations... it was a bit of a pain, but it meant that I was starting with a fresh updated file (from the new version) and making my modifications again from scratch.
There hasn't been an update to krpano since then, so I haven't had to struggle through this process a second time so far... it's actually nice to have software that is reliable without needing constant updates :)

I found a solution by posting to a chromium google group and receiving a reply.
The thread is here: https://groups.google.com/a/chromium.org…dev/5yqfAXibz1I
The short answer was that I now have to explicitly allow some things within my iframes.

allow="gyroscope; vr"

I'm having a similar issue which is very problematic for my use-case... I create virtual tours of tiny homes for builders/designers to embed directly on their websites. I just noticed that the embed is not showing the VR option on mobile browsers (which is a feature that I promise to clients). Both my site and the client's site are secure HTTPS, but I guess this update to chromium does not treat the embed as secure?

Here is the actual tour location -> https://www.tinynestproject.com/explore/tiny-h…omes/hugge_skp/
Here is the page on which it is embedded -> https://www.bengarratt.com/workshops

On my desktop I see the VR toggle in both cases, but on mobile it is missing from the embed (and obviously this VR is intended to be viewed on smartphones).

Any idea for a workaround? Is there a property that can be assigned to the embed somehow? Or a different method of embedding? This is my embed code:

<div style="text-align:center;width:80%;min-width:240px;max-width:640px;margin:0 auto"><iframe src="https://www.tinynestproject.com/explore/tiny-healthy-homes/hugge_skp/" width="100%" height="320" allowfullscreen></iframe><figcaption style="line-height:150%"><a href="https://youtu.be/mUjA1b8HmBM" target="_blank"><img src="https://www.tinynestproject.com/explore/EMBED-ASSETS/vr-embed_how-to_250x60_rev3.png" alt="How To Use This Tour" width="120"></a><a href="https://www.tinynestproject.com/embedded-tour/" target="_blank"><img src="https://www.tinynestproject.com/explore/EMBED-ASSETS/vr-embed_powered-by_250x60_rev2.png" alt="Powered by Tiny Nest" width="120"></a></figcaption></div>

EDIT: I just checked that the VR+gyro are available on mobile in embeds that are on my own site (within the same domain as the location of the actual tour) such as here -> https://www.tinynestproject.com/explore/services/
So the issue has to do with how the iframe is loading off-site content... is there any way to "validate" the contents of an iframe?

Thanks for the reply :) I finally got it working the way I want.
But even with your feedback, I struggled to get this working, so I thought I'd share a few things that I learned along the way:
My syntax for the path to my custom skin xmls was correct from the start. I was getting errors because I had made modifications to the base vtourskin.xml file (to hide some UI elements), and since that file references all the image files (pngs for the buttons etc.) it was looking for them in the same directory as itself... I had only placed 2 xml files in my central location, without the images... so once I added the rest of the skin folder contents to my central directory (alongside my custom files), it loaded fine.
The other thing that was tripping me up was that I could not find any reference to the "plugins" folder, and no information in the links you provided... I did find ONE occurrence of the word "plugins" in the main .js file and figured that it was the same situation as the skin xml: it looks for a plugin folder in the same directory as itself... so my central directory now contains krpano.js, krpano.swf, plugins folder, and skin folder... then I point to the new .js and .swf location via tour.html, and point to the new skin xml location via tour.xml... the plugins folder is found by the fact that it is in the same directory as the .js (as far as I can tell).
Does this sound right? It seems to be working fine.

Hi, this is my first post and I wasn't entirely sure what sub-forum would be best, so I am posting this here and maybe it can be moved if needed?

Last night it came to my attention that VR for my virtual tours was broken. I searched the forum and found the solution, which was that an update to some math in Chrome (degrees vs radians) had caused it, and that I just needed to update my plugin, js, and swf files (I was on pr12, so updated to pr16). In doing so, I found it very cumbersome to replace the contents of the "plugins" folder inside every vtour individually. The number of vtours I manage will only increase over time, so it would be very helpful to be able to make a single edit (per vtour, at the time of creation) that causes it to look for plugins in a central location. This way I would only ever need to update the contents of one folder. I looked through the xml and html files, but could not find any reference to "plugins" path anywhere. Is this centralization possible? What do I need to modify?

On the same theme, I would like to centralize the customizations I've made to my vtour skin. This one is more obvious HOW to do, but I can't seem to make it work... in the tour.xml file, you can "include" extra files that will modify the skin. The default path which works fine is the "skin" folder, which is inside the root vtour folder for a given vtour. So including my custom file looks like this:

<include url="skin/vtourskin_tntweaks_rev01.xml" />

<include url="../../SKIN-CUSTOMIZATIONS/vtourskin_tntweaks_rev01.xml" />