Support people always want to answer your questions with a story. Usually its the story they told the last person who asked ‘that question’.
So could we please just get to the facts?
- What file format does the IOS version of Scrivener need to use to store its content?
- Do we have to plan that a synced project folder (the thing that ends in .scriv) on dropbox has to be set to produce .txt files if we want to open the project folder (the thing that ends in .scriv) on IOS?
- Why don’t you guys start thinking like people who produce software for a living and stop trying to get people to use workflows that your application cannot manage and instead start partnering with providers that can provide a reliable technical solution for sharing files across device types?
- If you just don’t want to walk too far from the latte, then build a git interface into your app so it can manage versioning and synchronization for a file folder? That would fix the failed sync issue. Since your project package is a folder that looks like a file and you talk about it as if it were a file, and name it with an extension as though it were a file, even though it is only a folder and can only behave like a folder, you need to have a capability in your app to treat it like it wants to be treated: like a folder. Git does that, and its ‘free’.
- And this thing where, on a mac, you ask a user to create ‘the thing that ends in .scriv’ when their cursor is pointed inside a folder, and then your app creates a folder that ends in .scriv that you call a ‘project’. But then in the ‘external folder/sync’ situation, when their cursor is pointed inside a folder, your app wants to use the folder they are ‘in’ and turn that into ‘the thing that ends in .scriv’ so that the folder they thought was going to be the folder inside which your app was going to create their project has become ‘the thing that ends in .scriv’ and now the folder where they expected to find ‘myProject.scriv’ is the folder holding the project sub-folders. BUT… your app cannot rename a folder that existed before it wanted to create a project, especially when your app is already inside that folder, so it sticks the project sub-folders into the enclosing folder which does not end in .scriv. So how come that is?
- And the part where you can’t really explain how it works… and so instead you explain how to be aware that it ain’t gonna work so well… I just don’t buy that as a responsible position for a company who’s got the ability to both build and explain. So if you aren’t proud of the explanation, just finish the application (if it don’t work, it just ain’t done yet) so we can enjoy the latte of your labors?
Thanks for the headaches,
Kimball Johnson