Posts by Luis Erantzcani

    Hello Klaus, thanks for your insights.

    Haven't tried/tested yet, I just didn't know this kind of tools existed and it's somehow frustrating to know they're there.

    I'll take a look to see what can be done and will share my findings here, hope indeed newest versions don't allow this tool to work.

    Anyway, if somebody else has had some experience with this situations would be interesting if you could share your thoughts

    Hello!

    I'm coding a krpano maps plugin where I create/move/remove layers (mapspots), I store all mapspots info at an array with this shape:

    <map_mapspots>
    <spot name="scene_name_1" x="03" y="123" parent="map_image_2" headingoffset="30"/>
    <spot name="scene_name_2" x="30" y="023" parent="map_image_2" headingoffset="40"/>
    ...
    <spot name="scene_name_n" x="33" y="003" parent="map_image_2" headingoffset="00"/>
    </map_mapspots>[/code]

    I then want to copy this code to clipboard, but haven't found any way to do it. I can copy text to clipboard and access/edit/remove values/items at array, but in this case I'd like (if possible) to get either the children elements of the <map_mapspots> array or whole array code.

    Any idea of how to achieve this?

    Thank you! *thumbsup*

    Luis

    Hello Klaus,

    Hoping you're doing well, with the recent launch of 3DVista's 3dModel feature (https://www.youtube.com/watch?v=X8Oc2EIs2d4) some days ago I wonder if there's any plans to incorporate this into future updates of Krpano beyond current three.js feature?

    I love krpano much more over 3dvista but I don't see any smooth way to integrate 3d models / photogrammetry with panoramas or krpano structure. Some clever coders have shown me good examples of 3d model integration but still is more of an ingenious code gimmick than a native suport.

    I haven't seen for example any way to embed hotspots into a 3d model point which could trigger some krpano actions like showing a menu or manipulating the model (E.g. opening car doors / turning on lights).

    I know Krpano has been intended since the beginning for 360 photo/video and does it's job very well, I'd love it to count with a 3d extension in some point (huge application potential) so hope you're considering it, or if not would be good to know it won't come or will but not in the nearby future.

    Thank you!

    Luis *thumbup*

    Hello Klaus and community,

    I'm implementing a new structure for my krpano tours and need some help! This is the new way I'm structuring tours on my site :

    SKIN URL https://mydomain.com/skin/ (Skin folder: krpano .js/.swf files and xml's)
    TOUR URL https://client.mydomain.com/ (Subdomain linked to a folder with tour files: tour.xml / panorama tiles)

    This allows to use an A record to mirror tour.domain.com into client's website subdomain (360.clientdomain.com) and also have a global skin which can be easily updated for all my tours.

    I already set the embedding code at https://tour.mydomain.com/index.html to link files from https://mydomain.com/skin/ with the basic embedpano functionality as:

    <body>
    <script src="https://mydomain.com/skin/skin/tour.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:"https://mydomain.com/skin/skin/tour.swf", xml:"tour.xml", target:"pano", html5:"always", mobilescale:1.0, passQueryParameters:true, bgcolor:"#000000"});</script>
    </div>
    </body>

    This method loads the krpano SWF/JS files but doesn't get to load skin.xml as I get the following message:

    FATAL ERROR:
    https://mydomain.com/skin/skin.xml - loading failed! (0)

    This skin.xml file is called internally from tour.xml by an include element (<include url="%VIEWER%/skin.xml"/>). As tour.js path already was declared I'd expect it to load (it does load directly at URL https://mydomain.com/skin/skin.xml) so I'm confused here.

    I tried different placeholders:

    <include url="%VIEWER%/skin.xml"/>
    <include url="%SWFPATH%/skin.xml"/>
    <include url="%ROOT%/skin.xml"/>


    None of them is working. So have you had this kind of integration before, Klaus, what do you think could be done here?

    Best

    Luis *thumbup*

    Hi,

    Just met today the new drone tech by Skydio with 3D scan powered by AI, kindda "The autonomous aerial Matterport" which seems a perfect match to capture the 3d model for above tours:

    https://www.youtube.com/watch?v=rzOrle…_channel=Skydio

    As I mention I see photogrammetry is having huge advances in many fields, so it will demand better tour experiences at some nearby point that complement our current flat interactive panoramas approach.


    Since I met Krpano many years ago it has always shown great capability to adapt to tech evolution, so I'd really love we could have better tools in future releases to met requirements for what pictures itself as a future branch of virtual tour experiences.

    Would love to hear your thoughts about this Klaus.


    Best

    Hello community,

    Just posted this third party 3d/360 tour on facebook Krpano coders group which grabbed some attention so I bring the discussion here. Honestly it surprised me as I haven't seen something like this before and I think it offers a very nice UX blending photogrammetry scans and 360 panoramas:

    https://www.kroscloud.com/3d/valdstejn-castle/7bon

    As you may know in recent years 3d scans have become easier and easier to create so I guess it was a matter of time till somebody integrated both in a tour experience. Maybe there had been something like this before, I don't know, this one is the first I see and IMO it shows a possible route of deveolpment in future virtual tour experiences. ¿What do you think?

    The way Krpano is coded now I guess we could be working out this kind of integration with some "3D scenes" in which the 3d models "live", then just use our current tools to load 360 scenes, layers, hotspots and everything else. I haven't look in depth but this platform seems to be coded in three.js, we already have that one available but haven't seen much use of it and personally haven't tried, I don't know till which point could we be getting this performance and customization. (Integration of "floating" hotspots in 3d models for example).

    What do you think Klaus, are this kind of tours currently "doable" in Krpano? or in case, do you see potential in upgrading in this direction in future releases?

    Best

    Luis

    Hello Indexofrefraction, yes, I know server/client side difference. Indeed, article mentions meta would be generated server side in what seems to be Python, though index.php as you mention may work as well.


    Now, what I don't have a clue is about URL update. I've seen a couple of tours here where "folder structure" seems to be present when in fact it seems to be updated the same way as current krpano's deeplinking by javascript on client side. If query is not used then same way would work, or PHP would be needed. Any idea? What would be needed is that URL generated meta could match what USER AGENTS see, that's the thing.


    About what I mention for KRPANO is that I if a global solution (including PHP) could be added to the "kit", that would be very useful for everyone, as currently only people that develops this can access the feature. If I get it I don't disregard selling it as a plugin, I know many people would appreciate this (I definitely would buy it), though would be very nice to count on that one as the current deeplinking has the limitations I mention, which basically will affect anyone sending a whatsapp, Linkedin message and probably many other platforms.


    I'd appreciate anyone else's insight about this subject.


    Best

    Hi!

    I've been using Krpano's integrated deeplink feature for some time but recently I began having limitations. For example in LinkedIN query seems to be removed by their messaging application, so yeah, instead of showing the specific panorama I intend person to see it takes them to root. Already had some misunderstandings because of this. With Whatsapp what happens is that if user clicks on link then it works, but if user clicks on thumbnail then it leads to root.

    Another problem with deeplinking with query parameters is that meta for the site is the universal one (at index.html), so thumbnail/data doesn't match the shared link scene which also creates communication issues and loose so much "punch".

    I know some of you have solved this issue elegantly so I'd appreciate some insights about how to create single URL's for each panorama that also allow to use specific meta.

    Been doing some research about this and found this very nice article about "SINGLE PAGE APPS", which as I understand is krpano virtual tours case. This girl basically advices developers to implement USER AGENTS that will identify social platform crawlers and render for them a meta-only html, while identifying users as well and showing them the content.

    https://speakerdeck.com/sienatime/facebook-sharing-for-single-page-apps[size=10]
    [/size]
    I'm not that skilled coder out of Krpano (though I'm always open to learn) so I don't know how to for example generate URL's in the form of a folder structure (PHP maybe?) and conect all that with meta crawlers. So any advice/hints here would be greatly appreciated, same if there's another way of coding this whole feature.

    Klaus, if you're reading, I don't know if an "universal solution" can be created here, but if possible I think this would be an amazing feature to have in future updates. I know there are much more tour developers out there who have the same need as current deeplinking solution has those limitations I mention.


    Thank you!

    Sorry people, last weeks have been such a rush of work I had to disconnect.

    Klaus, thanks for your open mind to new ways to improve Krpano, that's exactly what I think had taken your viewer to the place is now.

    I came to create this post as the way of thinking I've adopted for some time in krpano is like "This would be the easiest simplest way to code it" then find ways to make it possible. Generally I can handle everything by myself or by posts on the forum but in this case this required higher support so I thought about sharing this view here.

    As I mention I think a "special placeholder" would be the best easiest way for multilanguage, just set it for attributes/elements and that's it. Any tour, no matter how complex it's structure could be easily taken to many languages. Main issue with this is dynamical config, that's it . I agree with your example below, I see we definitely have to have another variable/dimension added to attributes/layers that could sort the parser and be available for later dynamical actions:

    Code
    html.lang.en="Hello" html.lang.de="Hallo"
    url.lang.en="english.png" url.lang.de="german.png"

    I get it would be interfering directly with style asignation so it would require deeper modification of the viewer and parsing process, though, this may open new paths for other funcionalities as well? Surely you have other priorities of development but now you have this in mind in case you see this is worth to explore further.

    I know all people in this post are perfectly capable of doing complex stuff (much beyond this) but let's not forget new people is arriving to community, and I think the lower the entry barrier to adopt krpano the better impact will have on overall adoption growth.

    Cheers!

    Luis *thumbsup*

    Yes, adding it as a higher level sounds like some change in the way we do it, right?, but I think it can be useful and straight forward for coding multilanguage and in the end doesn't conflict with any of the methods already used by community (just leaving lang="null").

    As I mentioned currently we're basically coding turnarounds to this (specifying language "inline" and using actions to configure it dynamically, basically more codelines) so why not to have it supported by the viewer?



    Anyway, this are just some thoughts I wanted to share, I'd be glad if they can help but if not it's ok. Klaus, there's all this posts above so you decide if this makes some sense or not. *wink*


    Best

    Hello people, yes, as I mentioned I also can think of some ways of doing this by actions and dynamic code (been doing krpano for some years) but I think the most straight simple way to do it (IMO) would just coding language attribute or "surname", no extra actions, no calc, just set which language would each "item" be.

    If krpano parser could handle this It could be doing the task for everything (is this correct Klaus?), layers, hotspots, data and even other elements (I use a lot of custom ones like <photo> <gallery> <notifications>, etc, not accesbile by for regular data, layers, hotspot loops) and wouldn't require any extra actions, just defining language maybe at embed code in html or as a query (Matterport guys do it this way BTW), or not defining it at all for the same behavior we have right now.

    Taking the example by Piotr as a dynamic language config structure, I can see it perfectly working but in number of codelines compare that with just adding the language attribute to both data elements, now if krpano also has to have something similar for hotspots, layers and other elements, it will needmuch more lines in comparison to just adding some attributes right?

    BTW, look at your own code, by syntax structure the language "surname" has to be specified in some way, either by an element name or some attribute, or attribute value or somewhere else, that "_eng", "_it" "_spanish" thing is already there, just managed diferently by everybody so I just say, why not adding some native support in krpano?

    The downside of this method as I can see now is that to change language krpano would need to "restart" the tour/scene (with a new "language value"), though if you see most websites all over the web work just like that.

    Now this way I mention is one option though there may be some better way to do it in a native way, if you have some thoughts about just go ahead mention them. Fact is there's no krpano specific support for multilanguage right now and I'd just love to have something in the future to not have to do more code than needed in my favorite 360 viewer. *wink*

    Hello Klaus,

    I've been thinking recently about multilanguage support in krpano, currently It's done in many ways by community but I have this idea that maybe could work and ease out things for all us.

    Right now I love the way krpano manages multidevice with the DEVICE global variables that is used to specify specific ELEMENTS for each platform, example:

    Code
    <layer name="button1" devices="desktop".../> <layer name="button1" devices="tablet".../>

    And ATTRIBUTES with the attached "surname" for the device that let's us specify then in a very specific way. Example:

    Code
    width.desktop="80%" width.mobile="100%"

    Following this already existing path could it be possible that we have a similar LANG (LANGUAGE) global variable? Then if we declared it as let's say "en" for english or "es" for spanish then hotspots, layers, etc. would be defined very quickly in code for each specific language, example:

    Code
    html.en="[h1]Welcome![/h1]" html.es="[h1]¡Bienvenido![/h1]"
    Code
    <data name="body_text" lang="es">...</data> <data name="body_text" lang="en">...</data>

    For regular non specific language it could be left empty so it didn't apply, like currently done when device is not specified.

    I can think of some hacks right now to enable this on my own tours but in the end would be turnarounds for this idea, so I think it would be great if we could have this in a native way.

    I don't know if something like this exists (haven't seen it) or can be possible (though I know you make everything possible *squint* ) so I'd love to hear your insight about this.

    If somebody else wants to share thoughts or experience go ahead, I think we can all benefit of multilanguage native support in next Krpano versions.

    Thank you.

    Luis *thumbup*