Giter Site home page Giter Site logo

Container Interactions about core HOT 2 OPEN

mottosso avatar mottosso commented on August 11, 2024
Container Interactions

from core.

Comments (2)

mottosso avatar mottosso commented on August 11, 2024

Some food for thought.

Assets are ultimately connected from one to the other, similar to nodes in a network of nodes.

 _________________________        _________________________ 
|                         |      |                         |
o input            output o----->o input            output o
|                         |      |                         |
|                         |      |                         |
|                         |      |                         |
|_________________________|      |_________________________|
 1000.MyCharacter01               Bruce.lookdevDefault

So, how about representing them as such, visually as a node graph?

from core.

mottosso avatar mottosso commented on August 11, 2024

Yet another thought about this.

Slots

Rather than facilitate an arbitrary connection between any two assets, which may lead to complexity and potential over-engineering, how about establishing a few pre-defined connections, like slots.

image

In this example, a character is pre-defined with exactly two inputs, and may have only one input connected to any one asset. This makes sense, it couldn't have more than a single look, nor a single fur set-up.

What this enables us to do is establish relationships between assets (as per #129) with less explicit information.

{
  "Asset1": {
    "inputs": ["myFurSetup/12", "myLook/15"]
  }
}

Here the destination for each input is implied by their type. The character provides an input for the types "look" and "fur", and any fur or look looking to connect only has one place to go.

Set-up and configuration could potentially look like this.

api.register_input(
  source="mindbender.look",
  destination="mindbender.animation",
  connect=look_to_animation)

Where look_to_animation could be a function accepting the two assets as parameters.

def look_to_animation(source, destination):
  assert "out_SET" in source
  assert "in_SET" in destination

  for input, output in zip(source["in_SET"], source["out_SET"]):
    connect(input, output)

Where connect is a generic function taking two absolute path to two objects and making a connection. In Maya, that may take the form of cmds.connectAttr.

from core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.