sketchucation logo sketchucation
    • Login
    ℹ️ GoFundMe | Our friend Gus Robatto needs some help in a challenging time Learn More

    Unlimited hierarchies for components and scenes (1)

    Scheduled Pinned Locked Moved Developers' Forum
    1 Posts 1 Posters 273 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • chrisglasierC Offline
      chrisglasier
      last edited by

      Click on image for full size
      This is a proposal to develop the nameset interface and mechanisms as an alternative to Sketchup layers and a supplement to outliner and scenes. The first step I want to take is to seek help to test the basic functionality, stability and acceptability of the interface itself. It has been made as a plugin but for simplicity interaction with models is delayed until this step is deemed complete.

      ANIMATION
      ns01.gif

      As the interface is more machine than metaphor for paperwork, it needs to be read differently. The names in the grey row represent a navigable trail. All the other names in the white panel offer associated options to branch off onto others.

      ns02.gif

      Selection of names activates horizontal and vertical animation to slide new options into view.

      ns37.gif

      Selection of menu prompt opens available devices. (only one for this stage).

      ns38.gif

      Selection of menu option opens the device (in this case nsetCreate.js)

      ns39.gif

      Device prompts open but menu prompts remain accessible.

      ns45.gif

      Device options. Note menu prompt to slide menu prompts back

      ns46.gif

      Menu and device columns also slide vertically.

      ns48.gif

      Selection in white panel slides menu prompts back.

      FUNCTIONALITY
      ns72.gif

      Functionality relies on the html and javascript (see attached files) but also on the key/value pairs in the record (as above). Each record is given a number label. Each record has a Forelink key which has an array of number labels associated with it. The other key/value pairs are explained with the device that creates them.

      ns74.gif

      "Example_2" is a sharable nameset link. When it was created with the machineCreate device it was given "NSET" and "VIEW" as its Forelink array. It is saved in a file of the same name and its first two records are "NSET" and "VIEW" in order to make the coupling.

      When another sharable nameset link is selected, the previous one is unhooked and saved and the new one coupled.

      ns77.gif

      Sets and scenes have a different color to avoid confusion with NSET names. The NSET is temporarily attached to a scene in order to record required visibility of components. All components can be hidden with one selection.

      ns78.gif

      And made visible again by selecting collections or components further down the trail.

      Due to images restrictions Devices, Files and Planned are in part 2


      Extract into plugins; check nameset extension

      With TBA interfaces we can analyse what is to be achieved so that IT can help with automation to achieve it.

      1 Reply Last reply Reply Quote 0
      • 1 / 1
      • First post
        Last post
      Buy SketchPlus
      Buy SUbD
      Buy WrapR
      Buy eBook
      Buy Modelur
      Buy Vertex Tools
      Buy SketchCuisine
      Buy FormFonts

      Advertisement