[Fiware-miwi] 3D UI Usage from other GEs / epics / apps

[Philipp Slusallek]

Hi,

Thanks for taking the initiative here. I fully agree and the API is the 
main thing that is still missing also from our documentation. So 
defining them soon is obviously important.

BTW, have we made the current GE documentation available to FI-WARE yet? 
Have they sent feedback? I do not remember seeing anything.

So if could come up with good suggestions for interfaces for the GEs 
this would be very welcome. We can then jointly discuss them in the call 
or per email.


Best,

	Philipp

Am 30.10.2013 08:51, schrieb Toni Alatalo:
> Hi again,
> new angle here: calling devs *outside* the 3D UI GE: POIs, real-virtual
> interaction, interface designer, virtual characters, 3d capture,
> synchronization etc.
> I think we need to proceed rapidly with integration now and propose
> that one next step towards that is to analyze the interfaces between 3D
> UI and other GEs. This is because it seems to be a central part with
> which many others interface: that is evident in the old 'arch.png' where
> we analyzed GE/Epic interdependencies: is embedded in section 2 in the
> Winterthur arch discussion notes which hopefully works for everyone to
> see,
> https://docs.google.com/document/d/1Sr4rg44yGxK8jj6yBsayCwfitZTq5Cdyyb_xC25vhhE/edit
> I propose a process where we go through the usage patterns case by case.
> For example so that me & Erno visit the other devs to discuss it. I
> think a good goal for those sessions is to define and plan the
> implementation of first tests / minimal use cases where the other GEs
> are used together with 3D UI to show something. I'd like this first pass
> to happen quickly so that within 2 weeks from the planning the first
> case is implemented. So if we get to have the sessions within 2 weeks
> from now, in a month we'd have demos with all parts.
> Let's organize this so that those who think this applies to their work
> contact me with private email (to not spam the list), we meet and
> collect the notes to the wiki and inform this list about that.
> One question of particular interest to me here is: can the users of 3D
> UI do what they need well on the entity system level (for example just
> add and configure mesh components), or do they need deeper access to the
> 3d scene and rendering (spatial queries, somehow affect the rendering
> pipeline etc). With Tundra we have the Scene API and the (Ogre)World
> API(s) to support the latter, and also access to the renderer directly.
> OTOH the entity system level is renderer independent.
> Synchronization is a special case which requires good two-way
> integration with 3D UI. Luckily it's something that we and especially
> Lasse himself knows already from how it works in Tundra (and in
> WebTundras). Definitely to be discussed and planned now too of course.
> So please if you agree that this is a good process do raise hands and
> let's start working on it! We can discuss this in the weekly too if needed.
> Cheers,
> ~Toni
>
>
> _______________________________________________
> Fiware-miwi mailing list
> Fiware-miwi at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-miwi
>


-- 

-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschäftsführung:
   Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
   Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
   Prof. Dr. h.c. Hans A. Aukes

Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973, Steuernummer:  19/673/0060/3
---------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slusallek.vcf
Type: text/x-vcard
Size: 441 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131030/3cc84b7b/attachment.vcf>