ImGui

[Geoff Evans]

https://github.com/ocornut/imgui

Might be useful for debug menu stuff.

[Philip Degarmo]

That looks really neat. I'd love to see reflection driving populating that for any object. That reminds me, the editor property inspector needs some work. :)

On Friday, August 15, 2014, Geoff Evans <gor...@gmail.com> wrote:

https://github.com/ocornut/imgui

Might be useful for debug menu stuff.

--
You received this message because you are subscribed to the Google Groups "Helium Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heliumprojec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Geoff Evans]

Yeah, the Editor is the big to-do for me for the hackathon next weekend.  Its been a long time coming.  Last we talked I think you were going to start in on device support?

I have been thinking a lot about how that should work.  I think we should move the loader frameworks and asset process stuff to a systray app "Pipeline", and do some basic network replication of the object model and processed asset data onto the engine running on the device.  The systray owns the real loader framework, pipeline processors, and file system watchers.  It processes and dispatches per-target-platform data based on what device is connected.

Source content is edited in the Editor and unsaved changes can be sent directly to the Pipeline systray app for processing and dispatch back to the Editor (as well as any connected devices).  "Save" operations from the Editor cause the change to be reprocessed via the File Watcher.  This design should support WYSIWYG on multiple devices in realtime.  It should be cool because you could choose to see unsaved chanages just in the editor, or on all devices in near-real time.

The only bit necessary to keep everything fast is to cache the state of the world on each endpoint.  Re-launching any app should just uncached the state of the world and continue running.  Then connect to Pipeline and start playing back what has changed.  This will then stream in changes as they are processed and fetched.  Ultimately Pipeline could contain a giant cache of all target platform processed data, or even connect to a network cache of processed data for asset format version changes, et al (in a hypothetical future where Helium is in use at a big studio).

--
Geoff Evans

[Philip Degarmo]

This sounds awesome. I could also see it enabling multi-user scenarios which would be really sexy. Just point your editor and devices at any systray and connect. 

Philip