On Thursday, April 25, 2024 at 1:55:38 PM UTC-4 Thomas Passin wrote: On Thursday, April 25, 2024 at 1:25:21 PM UTC-4 Thomas Passin wrote:
>From an architectural point of view, the current Leo editor widget could get replaced by a widget with several child widgets (a tabbed widget is one possibility), of which one is the current editor widget, and most keyboard and mouse input will go to it no matter whether the text or rendering widget is visible. This plan would require minimal changes to the rest of Leo's code. Once we have such a widget, VR3 could render right to it, just as it does now to a log pane tab. VR3 may not be exactly what we want to end up with in the long run, but going this route would very quickly give us a working prototype to get experience with. The approach is to make the rendering widget in the new node display widget be VR3's rendering widget. We already have such a widget and all the machinery we need! It's the Log frame. We create a frame like the Log frame but with the LeoQt edit widget instead of the Log widget. We put this frame into the location that currently holds the edit widget. We use the same technique to insert the VR3 widget into the Log frame but instead we put it into the new Edit/Render frame. This would require no changes to VR3 or the LeoQt edit widget. If all goes well we could even have a prototype working in hours, or days at the most. Most of the work would be in constructing the Edit/Render frame (based on the Log frame), and setting it up when a commander is constructed. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ac51e552-92c3-41bc-8887-1a6f8c2bcc18n%40googlegroups.com.
