On Mon, Feb 13, 2012 at 3:54 AM, nakedmind <[email protected]> wrote:
> For the past several months now, i've been heavily using leo at work > to manage my project files and for developing tools and scripts. I > love the way that i'm able to organize all my work scripts and tools. > Also tinkered a bit with leo's code to hack some workarounds to fit > leo into my  workflow. This has lead me to think of ideas/wishlist for > leo that i think will be useful to me and hopefully to others. Haha. The more Leo has, the more people want. That's just the way I like it. > So there's an editor for viewing/editing polygon mesh data, materials editor > for editing materials nodes, an attribute editor for changing node > attributes, etc. They even provide an outliner editor as one way of viewing > and editing all the nodes. > I would like to implement something similar in leo. My idea is to define node > types for each type of data that leo will support. The view-rendered plugin does pretty much what you want. Yes, you might want to do more, or do things differently, but it seems like Leo already provides the framework for the kinds of things you want. I am interested in how you think viewrendered could be improved or extended. 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.
