Right now, to work with another person on a Trint, you have to share a Trint with them. This creates a *copy* of the Trint, which they edit and then send back to *you* as a copy.
This creates a bunch of copies of a Trint.
I'd love to keep all the work in a single Trint, and avoid creating multiple Trints, which is confusing. It also is an awkward workflow.
Maybe, at some point, you could support a natural multi-user workflow. Perhaps you could do something where users could "check out" a Trint to work on, or users could "assign" a Trint to another user to work on. While a file is "checked out," others could view it, but not edit it. Only the person to whom it was assigned could edit it. And then, when the worker is done, she could "check it back in" to all users (or assign it to you). And if she wasn't responsive, you forcibly "take back" the Trint and work on it yourself (or assign it to somebody else).
That way, you'd only have one Trint, and only one person would be working on a Trint at a time.
This would be like a primitive git system. This logic is in document management software like K4 and QuarkCopyDesk, which is where I stole the idea.
Please sign in to leave a comment.