TGN portability, openness, standardization, and beyond-standard deployment 

Here’s a peek at the future form of visual engagement with digital models of all kinds, the future of attentive focus, and the future of technical drawing. A new TGN demo. Note the controlled visual interplay, the introspection at multiple levels (side to side, and between model and overlay). After the demo stops you can imagine the back and forth interplay continues… Use your imagination!

The idea is that these features (TGN) are for ALL apps, for every developer willing to deploy open source TGN in their modeling or drawing apps…

Does it come through that TGN is about drawing your attentive focus into the model, and establishing a recognizable and portable FORM of focused engagement with digital models? A form that lets you go in and GRASP the model as if with your eye hands? And that this form of engagement is shareable from one platform to another, from one modeling environment and app, to another?

TGN deployment from developer and user perspectives, regarding open TGN portability:

TGN implementation varies depending on whether you want TGN viewing only in your app, or TGN viewing and creation.

And how fancy you want to get with visualization in your app.

— Include model element motion too?

— Include cutting edge stylization? (For emphasis/clarity/story telling)

— Include I/O automation and customization?

— include graphics tools in your app (or use the ones you have already) to add any necessary graphics to the rigs, therefore greatly lowering dependence on I/O to drafting/illustration apps in some workflows.

— special clipping (e.g., per element)?

— parameter-based filtering, stylization, and most interestingly: node-driven TGN rigs creation and positional control? (e.g., Grasshopper driven)

— countless other possibilities

Whatever developers do at the high end, all TGN implementations should share a community-managed standard core feature set, so rigs can be shared across apps with predictable fidelity, at critical points: e.g.:

  • TGN rig clipping boundary
  • applied filter RESULT (element IDs of items that pass the filter)
  • rig viewing path and UI
  • camera transform to parallel projection at path center
  • graphics imprint at center

A bar has to be set.

  • Below the bar are shared features common to all.
  • Above the bar: limitless possibilities.

Further background and discussion are here: 

If you want TGN built into YOUR modeling application, contact me (rob snyder email) or (LinkedIn)

Website Powered by WordPress.com.

Get new content delivered directly to your inbox

%d bloggers like this: