Hi Jeremy,
I wanted to let you know I succesfully implemented the helix toolkit wpf viewer using the suggested decoupling of processes. See attachted image. The example of IPC for disentanglement of CEFSharp was based on a windowsforms application, so I had to make some changes to make it work with a WPF Window.
Now that I can launch a viewer from within the revit context, and can communicate with it from my revit command/application, the next step is to get geometry from revit to the viewer. I already succesfully tested to generate an OBJ file using your OBJ exporter voor Revit 2014 (upgraded to 2018) and display it in the viewer. However, as I was reading, I found your ideas on creating an improved version of your exporter using the custom exporter framework. Is this something you already implemented, or have planned to do?
I will continue to make my addin work with the existing pieces of the puzzle I have so far. An improvement on the OBJ exporter would be a nice-to-have feature, but your existing exporter does the trick. Once I have cooked something up, I'm happy to share my efforts if you're interested.
Again briefly my use-case: I want to create an addin that lets the user generate some revit ceiling geometry, and adjust the position and composition of this ceiling interactively with some sliders and input fields in my addin. This to-be-created geometry depends on existing wall and room geometry in the revit project. As such, in my addin, I want to preview the to-be-created- ceiling geometry, in the context of the relevant revit geometry. For this I want to import some relevant revit elements into my viewer to display the context, and then display the the to-be-created geometry in that viewer as well. When the user is satisfied, he can click ok, the preview will close, and the addin will generate revit objects according to the layout and settings chosen in the viewer.