Top-down, here is roughly what I’m looking for in a final design, functionality-wise.
- All <https://dl.dropbox.com/s/hrid3844mu8nmjw/20140604_uirequirements.png> The navigational style is miller-columns; i.e. columns from left to right, like Finder on OSX. The central difference being that each item can potentially be drawn uniquely, based on metadata associated with what the item represents - which for the sake of argument is folders on disk. - Prototype <https://dl.dropbox.com/s/8rd4q88f5ozma7e/140305_additional_column_and_smart_scroll.m4v> A few priorities: - function over looks - control over performance - quality over quantity Put another way, I’m not interested in performance nor quantity of items and I’m not getting into looks until I’ve got something that works. Some specifications; each item is drawn, or not drawn, based on metadata derived from disk; each item potentially unique in shape and content. # Based on openmetadata $ /home/marcus/.meta/hidden.bool $ /home/marcus/.meta/life.float With that out of the way, the method I’m currently using is to push/pull into objects from/to disk via a separate i/o module; it works something like this. In that objects aren’t capable of reaching outside of themselves, in terms of access to network or file-system, but are instead fed (pushed) with data and data is further put (pushed) back out by a separate library. The reason I’m in this signal-mess to begin with is due to this design. Works well in general coding, not so much embedded into graphics. Thoughts so far? Best, Marcus -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmODPBRXh%2BK6qjj52GMt6v-cKqV0O0x6gtUekc749cGAamg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
