Hello,

I already have bought a krpano licinse but it is not a v1.20 license.
The version that I am using is an early v1.19.
I should be able to download and use the latest 1.19 version (1.19 pr16) package for free, right?
The problem is that I can not find any earlier versions of krpano in download page.
Where can I get that?

Thank you,
Mahmood Hamidi
stockholm360@gmail.com

Thank you guys, I'll send a mail to mail@krpano.com

I am using v1.19 on my site and it works quite well actually but my version is an early 1.19 which creates tours with Flash.
The latest 1.19 versions can create tours without flash, whcih is what I am looking for.

Thanks
/MH

Hmm, that is fine but what horrifies me is the potential work I need to put in the migration from 1.19 to 1.20.
My site contains in excess of 450 panoramas and over 15 virtual tours based on custom maps of the venue.
What kind of upgrading work are we talking about here?
Do I need to do anything to all the xml files, to the licenses?
Do I need to regenerate all tours (or panoramas) and upload them again?
My first and foremost reason for upgrade is to get rid of Flash in my tours, but maybe I should do something to all the other stuff I have?

Thanks for any guidance?

Kind regards,
/MH

Thank you Klaus for your reply,

As I understand you recommend to upgrade to gain the benefits.

But as I am not that knowledgeable about different components I have to ask in very elementary manners.
When I use the "MakePano(Normal)Droplet" for "MyPano", it produces a few files:
In the 1.19 version they are:

1. A folder av panorama tiles "MyPano.tiles" (13 files, 6 normal tiles and 6 mobile tiles + 1 preview)
2. A skin "skin" folder containing an XML file "defaultskin.xml"
3. An html file "MyPano.html"
4. A JavaScript file "MyPano.js"
5. An XML file "MyPano.xml"

I also have the following file on the root folder of my site.
- krpanoiphone.js
- krpanoiphone.license.js
Do I still need these files?

When you say I need to change only the browser and the plug-ins, which of these files are the ones you mean to be changed?
.html file or .html + .js file? or any others?

I normally use exactly the same skin folder and defaultskin.xml for all panoramas.
Also I use the same .js file for all panoramas
I dynamically create an specific xml file and html file for panorama to show.
Can I continue in this manner even for the new version?

I tested the 1.20 version and found that there are some differences in the file names
1. skin folder containing defaultskin.xml (as before)
2. "MyPano.tiles" folder but with only 7 files (6 mobile files are gone)
3. html file named "index.html"
4. the .js file name is "pano.js"
5. xml file name is "pano.xml"
6. tour_testingserver.exe
7. tour_testingserver_macos

It seems that the xml and html files are more or less similar, right?
Is the important upgrade in the .js file?
Is this what you mean when you say the browser?
Can I use the same (new) .js for all panoramas?

Which are the plug-in files?

Many thanks in advance;
/MH

Thank you so much for the answers Tuur.

OK, I suppose Viewer is the .js file, right?
I tried to use only the viewer for my old panoramas, it shows a big DEMO VERSION in the middle of the panorama.
Also, I could not make the plugin work, but that is my second issue.

I would like to stay on 1.19-pr16 a while, if I get that version, I should be able to have that version without paying for the new version, and that is what I would like to do for now.

I'd appreciate if I could get that version in full package.

Many thanks
/MH
www.stockholm360.net