[x3d-public] Editor framework

doug sanden highaspirations at hotmail.com
Tue Apr 21 12:22:56 PDT 2015


Round-tripping - thanks, that could/should be a design parameter / constraint / criterion for an Editor Framework.
Lets make that the first criterion. It must have enough API so that round-tripping -or more precisely never needing to leave- is possible.
-Doug
>
> That's an interesting idea.
>
> I've been thinking about the "round-trip" concept. The more I think
> about it, the more I think it's not possible with content authoring
> tools (CAT) such as Maya. There are lots of small things that make
> round-tripping a problem.
>
> However, using frame work for editing might make some of this possible
> where pieces of the scene graph move back and forth between CAT
> programs, and a more X3D specific authoring tool such as Titania.
>
> Using the idea of a framework, something like Titania could offer full
> round-trip capability among X3D applications, and more limited
> content-specific round-trip capabilities between CAT programs and
> Titania.
>
> I don't know if that's what you were thinking.
>
> Aaron
>

>>> But, as you have already told, you will still need an 3D modelling
>>> program like Blender or even Maya to create your desired 3D objects.
>>
>>
>> One fuzzy idea is a framework for editing, that takes plugins for each
>> 'content/context type'.
>> Then allows you to recurse into sub-contexts of same or different
>> context type, (and pop back out).
>>
>> For example lets say you have a cityGML or KML scene, and some nodes in
>> the scene are VRML/x3d. You pick that node, and hit a button to push
>> that content/context type editor -and that node - onto a stack. You may
>> get to choose between optional editors for that context/content type.
>> Your menus change in response. Lets say you are in vrml/X3D. And lets
>> say you want to edit an ImageTexture image. You do something similar
>> there and get an image editor. Then pop back out. Similarly with a
>> geometry node.
>>
>> Q0. would it be useful?
>> Q1. Has someone already done this?
>> Q2. what's a good name for it?
>> Q3. what would the plugin api need to expose?
>> Q4. what technology / computer language would/should it be in?
>> Q5. if its done for editing, could something analogous be done for rendering?
>>
>> -Doug

 		 	   		  


More information about the x3d-public mailing list