Just to clarify some points that Ron George made (Thanks for the mention, Ron!)
* Flow's versioning function was designed to be insanely easy - in short, when you save a file in any supported app, Flow creates a "version" (list can be found here http://www.gridironsoftware.com/products/flow/Flow_supported_apps.pdf though a few are missing such as the Mac Finder) The number of versions can be controlled in preferences as well as the type of files versioned. You can dedicate, say, 5% of your hard drive (internal, external, or server) to versions. * Flow has a mechanism for sharing data about a project over a local network via Share Maps. As such, everyone working on the same project sees the same changes in the map and has access to the same files and all previous versions thereof. * We don't, in version 1.0, do any kind of "clouding" (Is that a word yet?) making the assets and map visible across the internet. I've taken copious notes from the other responses in this list, however, and will be making a few feature requests for the next version. :) Any questions, feel free to email me directly. Daniel Brown GridIron Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=45252 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
