File naming principles - Panorama name and tour directory

[John360]

File naming principles - Panorama name and tour directory

by John360 » Mon Jan 13, 2014 3:37 pm

Im experiencing that the file naming system is less than ideal, and would like to suggest that file name in output structure ( Tour directory name ) and panorama name in Krpano GUI should be separated.

Its a problem when editing published VTs.

My case: I have a tour with more than 100 360`s published on clients server. When the client wants to change names on the 360s I end up having to delete old project from server and uploading new project. With 3 iterations of name changing I end up uploading 300.000 files.

I could edit the code, yes, but then I will have to do same changes every time I do new renderings of the project as well.

May it be possible to separate Presentation and Data in the Panotour GUI, seperate "Panorama Name" and "Tour Directory Name"? It will need a new field where one name is the identifier of the file, and the other is the presentation name of the 360.

Feedback or suggestions?

John

Last edited by John360 on Tue Jan 14, 2014 1:51 am, edited 1 time in total.

[mediavets]

Re: File naming principles - Panorama name and tour director

by mediavets » Mon Jan 13, 2014 6:57 pm

Feedbak or suggestions?

John

Give the client a good slapping?

What names does yoru client forever wish to be changing and why?

I trust you are charging the client appropriately for the work involved?

[John360]

Re: File naming principles - Panorama name and tour director

by John360 » Tue Jan 14, 2014 1:55 am

The tour is of a technical facility with technical names on all rooms. That is why things get changed. Changing a few names in a menu should be possible without uploading the files again.

Presentation and data/architecture should be separated.

John

[jschrader]

Re: File naming principles - Panorama name and tour director

by jschrader » Tue Jan 14, 2014 5:36 am

Thank you, John.
I strongly second that.

[benji33]

Re: File naming principles - Panorama name and tour director

by benji33 » Tue Jan 14, 2014 8:54 am

Hi,

Filenames are generated the first time there are requested.
On build or on click on the Info button into the panorama properties.
So the best way to have good name is to rename panorama before build or before click on the info button. After that the name is fixed.
I know it can be annoying but it's like that to avoid too long time on build.

Thanks, benjamin

[John360]

Re: File naming principles - Panorama name and tour director

by John360 » Tue Jan 14, 2014 1:11 pm

Hi.

I just realised now that there are 3 different file name schemes in the generated tour. Some have numbers 1,2,3 etc, some having the file name, and some having the given name in the menu.

Thats not ideal.

[John360]

Re: File naming principles - Panorama name and tour director

by John360 » Tue Jan 14, 2014 2:08 pm

@Benjamin.

Is it possible to "render" the project again with consistent file names or is it sticky in PanoTour project file once rendered?

[benji33]

Re: File naming principles - Panorama name and tour director

by benji33 » Tue Jan 14, 2014 4:24 pm

@Benjamin.

Is it possible to "render" the project again with consistent file names or is it sticky in PanoTour project file once rendered?

I'll ask for this point but I seems that's impossible.

[John360]

Re: File naming principles - Panorama name and tour director

by John360 » Sun Jan 19, 2014 5:07 pm

@Benjamin.

I'll ask for this point but I seems that's impossible.

I`d like to ask for some priority on this one, because the way it is using PTP on large project may lead to lot of extra unbillable extra work on larger projects, or suboptimal file structure with extra hassle when working manually with the code.

The delivery to customer, the final code and images should be structured well. It should also be easy to follow naming schemes from raw files to pano files and project file to PTP file and build with xml and file structure.

Like it is today its likely to end up with 2-3 different folder naming schemes. Its not possible to rebuild either by changing panorama file in editor. the only solution is to remove the file completely and import it again, and add all hotspots and other features once agin.

Customer do ask for changes and they expect minor things like a little reorganizing and changing of names to happen quick. With a 100-200 node project small changes will lead to sick amounts of extra work - unbillable. Or delivering with totally messy file structures, which should not be a feature of PTP, it should be defined as a logic design bug.

You are of course in feature freeze by now, but this one should be fixed with a solution before release of V2.

John