MistyLaraCarrara opened this issue on Mar 08, 2014 · 17 posts
Pret-a-3D posted Tue, 11 March 2014 at 1:19 PM
Ah man, don't say that, would have been cool to see it dockable!
It cannot be done and it was designed since the beginning to not be a panel.
Reality needs a fully featured UI that goes well beyond what you can fit in a dockable panel. Reality is more than about 200,000 lines of C++ code. There is no way I would convert that to Python and no there is no reason for doing that.
On top of that Reality is written to be host-agnostic. There is a DAZ Studio version of Reality and using your approach would mean to re-write from scratch ever version. Even if there were more people than simply myself that would be just an absurd amount of work that would be completely unviable. In fact the original version of Reality was wrtten for Studio and it was completely boudn to it. I wrote Reality 3 from scratch and decided on a design that would be non tied to a specific host.
Reality 3 has been designed from scratch to be one app that runs with both Poser and, soon, DAZ Studio. There is a tiny layer of Poser python that runs inside Poser, and there is a small layer of C++ that runs inside Studio. These layers communicate with the main application, which doesn't need to be rewritten for a new host. 95% of what Reality does is done by the app and so portiong to a new host is simple enough to be done in a few months.
There are a host of benefits in Reality being a separate application:
It doesn't not interfere with Poser
It doesn't not slow down Poser
The OS can prioritize it automatically
It does not take memory away from Poser
It can perform a series of tasks in parallel
The UI can be expanded to any level of complexity without polluting the Poser UI
If it crashes it lives Poser unaffected
Hope this helps.
Cheers.
Paolo
https://www.preta3d.com
FB: https://www.facebook.com/RealityPlugIn
Tw: @preta3d
G+:
https://plus.google.com/106625816153304163119
The
Reality Gallery: https://reality-plug-in.deviantart.com