Jump to content
Storyist Forums

mainranger

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mainranger

  • Rank
    Newbie
  1. Steve, True... but considering that Storyist is a single-user system, this shouldn't be an issue. What I'm suggesting puts Storyist in complete control of the synchronization process. The only scenario where this breaks down is when the user decides to change files in two places simultaneously (that is, from the iPad and the desktop at the same time... which is unlikely) As you can see, I'm interested in doing ALL of my work in Storyist but not be burdened with the overhead of constantly transferring all of the static research documents that typically don't change once I've done them, keeping them as part of the project for handy reference... Just a thought... :-) David
  2. I'd like to see some improvements with project synchronization. I feel the present strategy limits the use of Storyist for iPad to text-only applications. If a project contains images, research documents, etc., then a change to a single word in a manuscript means the entire project is synchronized between the iPad and the cloud. IMO it's a lot of overhead transferring all of this stuff repeatedly for a simple manuscript change, and it makes me think twice before pressing the sync button, because it's a costly operation. I like to sync frequently... I think a better way to manage synchronization is to represent Storyist projects in the Cloud as a folder structure with a project manifest. This way only the changes gets sync'd, nothing more. Syncing the entire project is an expensive operation, especially for 3G customers with a data cap. The desktop and iPad apps read the manifests and locally build the project on the fly. D.
×
×
  • Create New...