Skip to main content
C
ClayHelberg18-Opal
18-Opal
February 3, 2021
Solved

Allow copy/paste of views (or some other method of duplicating a view)

  • February 3, 2021
  • 2 replies
  • 5356 views

Some applications end up with multiple views, 95% of which are identical, for example the customer wants a choice between a spatial target and a model target, but otherwise wants the experience the same.

 

Currently, this requires either tedious recreation of a lot of content in Vuforia Studio, or else hacking the project files to duplicate the *.js and *.json files with new names.

 

It would be really nice to have an easy, reliable way to duplicate a view for cases like this.

    Best answer by RolandRaytchev

    Hi @ClayHelberg ,

    to clearify this issue I reported to R&D PTC and will provide a feedback so far Info is received. Thx (ptc reference VTS-331)

    2 replies

    D
    dsgnrClarK16-Pearl
    16-Pearl
    February 4, 2021

    YES, this would be a GREAT feature!

    (Even the Project has to be reopened)

     

    Thinking about this every time I duplicate *.JSON and *.JS. 😅

      M
      mwodarz_INNEO14-Alexandrite
      14-Alexandrite
      February 4, 2021

      In cases like this, I would delete the resources from the model container and clear the not necessary items from the uploaded resources - and save the project.

      Then I would copy or move the project from the project folder to the ProjectTemplates. After restart the VS service, you can use this templates for all the "95 % similar projects".

       

      Maybe you know this way or maybe this would help (a bit)

       

      CheerEO

      Marco

      C
      ClayHelberg18-OpalAuthor
      18-Opal
      February 4, 2021

      Thanks, Marco. I'm afraid you haven't quite understood my use case, though. I'm not trying to develop multiple projects that are all similar--which would be the perfect scenario for your recommendation. Rather, I'm developing a single experience (project) with multiple views, where the views differ only in a few details (primarily the type of target used, thingmark/spatial target/model target).

       

      The idea is this: suppose you don't know for sure whether your user will be standing in front of your product or not when viewing the experience. For the case where they have the physical device in front of them, you want to use a model target. But you also want an option for someone who isn't there with the actual device, so you provide an alternative view with a spatial target and a fully virtual device. Other than the difference in target, the two options should work very much the same--same menus, same UI controls, same sequences, same code and CSS, same IoT data, etc.

       

      That's the use case I'm asking about. It would be nice to be able to develop the "virtual" (spatial target) version of the experience, and then copy that View and paste it as a new View. Then it's a simple matter of swapping out the spatial target for a model target in the new View, and I'd be done.

       

      I can approximate this by fiddling in the guts of the project directory and duplicating the JS and JSON view files, but it would be less of a headache if it were baked into the UI.

        R
        RolandRaytchev21-Topaz IAnswer
        21-Topaz I
        February 5, 2021

        Hi @ClayHelberg ,

        to clearify this issue I reported to R&D PTC and will provide a feedback so far Info is received. Thx (ptc reference VTS-331)

          Terms & ConditionsAccessibility statement