I'll start a new thread for convenience. Some notes:
- If I start blender from a console, the toggle-system-console command shows and hides *that* console, which could be convenient. - Scripts executed with blender's -P option use the system console, and have access to the bpy module, but that probably doesn't help much because blender has not yet loaded user data. - Embedding Leo into blender as part of the blender process probably will not work, due to competing guis. However, it may be possible to run both Leo and blender simultaneously, perhaps even in the same process, using techniques similar to the ipython bridge. If this could work, it would solve a lot of problems. - Even without close integration between Leo and blender, it should be possible to use Leo to develop blender addons, provided that blender is installed in a fully writable location. I now have blender installed in c:\blender, rather than Window's weird "Program Files (x86)" folder. - Blender's autocompletion code is in blender/scripts/modules/ console. The intellisense.py file contains the top-level code. It calls the other modules in the console folder. Leo could use blender's autocompletion code as is *provided* that Leo had access to blender's data while running the autocompletion code. It's not clear whether such a bridge to blender's data is possible, but it would solve a lot of problems. Failing that, Leo could use some substitute, such as the code-description files as described by Jaworski. That's the summary of my progress and thinking so far. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
