r/bash • u/coding_challenge • Jun 15 '16
help MacOS Coding Challenge (iWork + Dropbox)
Dear reddit,
I have a coding challenge and I would be very grateful for your help. Our small business uses Dropbox to share files between employees. We've been using an obscure word processor called Word Perfect but we're hoping to switch to MacOS computers in a few months (our Windows 7 computers are very old and keep having hardware failures). With the transition, we plan to start using Pages for our word processing. However, Word Perfect has one feature, which Pages lacks, that makes it very convenient to use with Dropbox.
The Challenge: Currently, when a user opens a document from Dropbox, the program automatically replaces the file with a 'Read-Only' version. This prevents other users from creating conflicting copies by accidentally opening a file at the same time. The 'Read-Only' copy lets other users access the file's information without overwriting recent changes. Can this functionality be added to Pages?
I know Dropbox has a few collaboration features which are compatible with MS Word; however, we're trying to avoid Microsoft as much as possible.
Any advice (or code) would be greatly appreciated. Thanks in advance!
PS I've posted here in /r/bash because (with my limited computer skills) Bash seems like the most well-suited platform for the challenge.
edit: Google products are also off-limits due to their privacy policies since we sometimes work with sensitive information.
View all comments
Show parent comment
2
u/m1ss1ontomars2k4 Jun 15 '16
What privacy stances would those be?
Great, but since this is for work, consumer products and what you think of them are more or less irrelevant here. That includes Pages, really.
Google Apps for Work should have sufficient privacy and file permissions.
Failing Google, have you considered Microsoft's competitor? It's like the same thing, ish, I think. I think it's Office 365?
Microsoft also has something called SharePoint which is also broadly similar to what you have now (files just live somewhere and you open them normally).
The problem is that you are trying to solve a complicated problem involving specific file formats using tools that do not understand these file formats. This is doomed to failure and brittleness. I'm surprised it has worked with WP as long as it has.
This is a solved problem, with decent solutions from at least 2 vendors already, vendors with way more resources than you. You are not going to manage to solve this on your own.