Posts by autiomaa

At least some plugin elements can use relative sizes in percents (like size as 100% etc.) as described in:
https://krpano.com/docu/xml/#plugin.width

Hopefully that helps to get things to work.

Haven't exactly been testing it but isn't 140 MB video file bit too big? You could make things much better by compressing it
to smaller sized file since many people these days still have bit too slow connections… at least when one considers that
people won't spend that much time in one scene of virtual tour waiting for a video to download (even more if they don't realize it's loading).

Try to use some tool like Apple Compressor or even Video Monkey etc. to make smaller file to speed up the download process.
What works for localhost does not neccessarily work when content is located in the web (as the connection speed is often slower).

Quote from Nelike imagery

The fullscreen button for iphone does not work properly because it already is in fullscreen. You can't hide the browsers bottom bar (tested with a friend with iphone and fullscreen worked but buttons went under the browsers bottom). I think it should be done as an application to make fullscreen go really fullscreen but have no time to even look at that now.

It's nice to see other finns in the forum There are not many of us who do this job, atleast fulltime.

There's way to make user able to use tour in fullscreen mode… but not directly. They need to add bookmark from Safari to homescreen (icon for going to tour directly) and that helps since there isn't any browser GUI visible in the screen. The same way is often used by other (totally different) web-based apps that are designed to work on mobile screens (and might look like totally native apps even while they aren't). For the time being, it's just best to hide the unneeded buttons, anyway.

Yeah, nice to see you too. :) Have been working with krpano little bit over year already and mostly on the XML side. Tried to avoid visual editors before since they produced so painfully messy code that it was difficult to maintain so have found it easier to do things myself instead of relying of WYSIWYG tools that (while look easier) could make things more difficult in the process. It surely takes more time to learn things but as some has said… "Use the source, Luke." ;)

Hoping to see how your city tour thing will turn out in the process. :)

Nice scenery, indeed. Used to drive the same road at least few times
per month during 2003–2004 when I was living near Imatra.

Tried to look the same thing with iPhone and while it looks nice, noticed that navigation is
bit too small to be usable and there is also problem with the fullscreen button.
Look at https://krpano.com/docu/xml/#plugin.devices to learn how to target different devices.

Understandably you use Panotour as HTML title and XML files say but after
looking at your other projects (keskustademo etc.) I'm sure you have already read it quite bit.
There are also other things you need to learn, most importantly checking the syntax of XML
files so that they wouldn't fail when used with JavaScript-based version of krpano (in mobile devices).
(This nice little tour was surely fine but should try to check keskustademo tour files again).

I can confirm that it's also broken in latest Safari for OS X 10.6 — Version 5.1 (6534.50).

Didn't even realize it was working better under Firefox until I tried just a moment ago and compared both.
Editor has probably been same for a long time already (at least for a year, as far I can tell…) and
there really would be need for improvements for it. Scrollbar would be good things for example. :)

zyON, one way to be able to move around in the editor is using Fn -key and up/down arrows.
You can also use Cmd + down arrow to go to bottom and Cmd + up to go back to top.
That has been the main way I have used Editor view for most of the time…

It's just that there aren't that much of details about the actual usage in the plugin page… :(

Nice scenery, interesting to see pictures from place that is still under build process.

And about thread topic… it's "rainbow", not "bainbow". ;)

Quote from roelofdevries

its working with lightbox now!
Example: http://littleplanet.nl/florence/player/tour.html

Interesting example. Thanks for sharing. :)

Noticed little problem in your http://littleplanet.nl/florence/player/skin/defaultskin.xml
where you have defined one parameter (onovercrop="171|0|161|23") several times inside same tag,
causing syntax failure and possible problems if one would try to use it with plain JavaScript krpano version.

Quote from klaus.krpano

Hi,

the video there is from http://www.virtual-surfers.com,
I'm not sure yet, but I think a Ladybug camera was used for it,

There are some specifications on their website about data rate and other things so one could compare that to specs of Ladybug etc.

Anyway, the image quality of video panoramas is still quite low but could be enough if size of panorama is small enough.
Hopefully quality of video gear improves in the future… :(

Tested with iMac 27"

OS X — 10.6.6 – Build 10J567
Safari — 5.0.3 (6533.19.4)
Flash Player — 10.2.152.33

Works nicely.

Quote from jordi

But with krpano, I have seen there are much more possibilities, and it seems to me that also there's much more performance, and so I have a lot of work to study the way of organizing files projects declaring actions, ...
Is there any post talking about the best architecture / workflow / files order....??
The other question would be, what this code would be used for in the real world ??
I have to build a similar project to this http://rcdespanyol.visita3d.com/en.html but in krpano, any suggestions ?? is better to have an xml file for every pano or is better to use scenes .....??

Quite impressive scenery in that RCD tour (but sadly the image quality is somewhat missing).

As for one file per panorama or using separate files for each panorama, it really depends on the amount of different panoramas you will have at the tour. If there's tens of scenes in the same file, it can really slow down loading time at least in some older iOS devices so dividing things to different files improves at least initial loading performance quite a bit. Also, have tried using bunch of scenes in multiple files but got to trouble with it. Depending on what you do with things (and how you handle navigation), you could actually use both separate files and bunch of scenes inside them.

Still, you have to note that even while krpano has quite bit of documentation, there are usage/implementation cases that aren't always as clear as they could be. Documentation is improving slowly but you should invest some of your time on browsing forum as there's quite bit of interesting ideas and tips around here. :) Welcome to the game.

Immersive Media's system is certainly much more than just the camera as there is quite big need for processing the amount of video material from camera(s).
Even more, if someone needs live video feeds, it's probably beyond what can be currently done with krpano.

Having problems with multi-file virtual tour where there's tons of different scenes divided to ~20 different XML files.

Problems are related to loading the specific scene from still unloaded XML file. Have about 3–9 scenes per XML file and while had them initially working nicely by using onstart="loadscene(scene_scenename, null, MERGE);" in the beginning of each XML file, now that I have moved to implement bit different kind of navigation system, would want to get things working so that I could jump to different scenes using something like this:

<!-- Load XML file -->
<!-- Load scene from the loaded file -->
<action name="panorama">
	loadpano(%1); loadscene(%2,null,MERGE);"
</action>


<plugin name="navigation-testing"	style="style_navigation"
	x="0" y="180"
	onclick="panorama(area2.xml,scene_2_room_1);"
	/>

Haven't got this working and as I still have problems with it, thought of asking help. Getting blank screen initially when clicking plugin (in this case, generic image defined in project wide XML file). Second click usually goes to the scene as the XML file has been loaded to the browser's cache.

As I'm not that experienced with inner working of Actions and don't know enough about programming, I could be missing something essential but hoping that some of you could help a bit. It would be needed that the solution would work on both Flash and JavaScript -based versions of krpano.

Little bit of background:

Initially, every panorama was in it's own XML file but after release of krpano 1.0.8.12 I moved to using multiple scenes in one file. It was working nicely but the problem was the initial loading time of JavaScript -based krpano version (on iOS it was basically totally unusable until after long long wait before things had been loaded to the memory of the iOS device). Found solution for painfully slow load time of the presentation by dividing scenes to different files (each area in it's own file). Initially, things were working nicely as I found good way to link from file to next in my custom made bottom navigation and used onstart to jump to right start scene on each area. Problems started to come visible after I tried to get secondary navigation (map-based thing having tons of hotspots) to work: ability to jump to all locations was lost after moving from central file to area files. This is why I have been using quite bit of time trying to get things work in right way…

Apparently there are some spam bots that search for wikis and automatically fill them up…

Was it required that user must be registered before being allowed to write or modify content?

Some type of CAPTCHA might help but even those have been broken automatically. :(

Your project for adding more powerful interface library to krpano looks quite promising.
I'm sure there will be need for it, keep working on it. :)

Also, when you have refactored it enough, please put the source back to GitHub so
one could help you little bit with it. I'm not that good with JavaScript but
might be able to help in some way.

If you need some tips regarding use of GitHub, just ask.
Have been using service for year already so I know few things already.

Surely, I second your request. That would surely help much.

Also, creation of hotspots with Editor could be made more effective to avoid wasting too much of time.

That's true, should try doing things that way…
Thanks for reminding. :)

Tested on <contextmenu> but it didn't work at all:

<item caption="Open in fullscreen" onclick="switch(fullscreen);" />

Tested <item caption="FULLSCREEN" /> many times before but it didn't produce working menu entry either.

Strangely fullscreen mode works when set as option to button.

onclick="switch(fullscreen);

I really hope that this problem would be solved as it would be sad to rely on workarounds (=buttons) if <contextmenu> fails to work…

Have been testing with at least 3+ computers and apparently bug is related to <contextmenu>
as fullscreen mode would work from button but not from menu.

Same problem is visible in examples of krpano.com so it's not only about me…

Quote from fellipe

So Jarredja, how can I make a link to an specific panorama (xml) that is embedded) in the swf file?

Not sure if that's possible since iPhone don't have support for Flash so reading XML files from inside of .swf wouldn't be normally possible without some not-so-elegant tricks…

There is information at https://krpano.com/iphone/#howtouseit

Quote

The Javascript viewer is an additional file - the krpanoiphone.js. It must be placed in the same folder as the krpano.swf and will be loaded automatically on the iPhone / iPad / iPod Touch devices by swfkrpano.js embedding script (other embedding scripts will follow).

This viewer is an Add-on to the normal krpano licenses, so there is an additional license necessary - get it here - it's a personalized license file - the krpanoiphone.license.js, it must be placed in the same folder as the krpanoiphone.js.

The embedding syntax is the same like for the krpano Flash Panorama viewer, no changes are necessary here, but note - it's important to set some iPhone specific meta settings in HTML for correctly scaling, just use the included HTML template!