@ToneZone
I’m going to ignore your snarky comments and your ignorance based confidence. I’m neither a blind fanatic nor did I lie about my professional occupation. I hope we can leave such immaturities aside going forward.
Although I disagree with most of your statements, I do agree with some of them, such as the following:
managing the file location would be nice but really isn't part of the main issue
I never claimed you needed access to the native file system, but some part of the file system will need to be opened or created for general consumption
the sandbox created by MS is the true problem
Those statements nicely address the idiocy of this discussion. With the unfortunate exception of you being unable to download and view PDF's on WP8, which generally works just fine, we all agree what the problems are. You and I also agree that managing files isn’t one of them. As you yourself stated, the “true” problem is the sandboxing of apps, or more precisely:
- WP’s concept of isolated (WP7) or local (WP8) storage, meaning:
- Every app has its own dedicated space on the filesystem, which is entirely inaccessible to any and every other app.
- 3[SUP]rd[/SUP] party apps can write to and modify only those files which reside in their own dedicated space on the filesystem. Even the SD card and WP’s library folders (documents, videos and music folders) are off limits.
- WP’s insistence that an app must have associated itself with a particular file type, say a *.3ds file, if the app expects to be able to do anything with a *.3ds file. Want to upload a *.3ds file to DropBox from your SD card? Currently impossible, unless DropBox is associated with *.3ds files (and every other conceivable file extension), which is just silly.
The above are the root causes of all the problems people have expressed so far.
I’m
not saying that a file manager is a terrible idea, or that a file manager can under no circumstances be part of a solution. I
am saying that invoking the word “file manager” doesn’t say anything about how the above issues would be addressed. Hence, doing so contributes nothing towards stating how the problems mentioned would be resolved.
I’ll concede that those ignorant enough to suggest Microsoft throw all of their security measures overboard and programmatically expose the entire filesystem actually have found a solution (I know you aren’t suggesting such nonsense, but others have implied as much). However, again, that has nothing to do with a file manager… that suggestion simply takes a sledge hammer to WP’s security architecture and removes all restrictions, thereby allowing any app to do anything. At that point DropBox would work great without a dedicated file manager app, though any person seriously insisting on such an approach is really just disqualifying themselves from the discussion.
- Do you understand the problems MS created with their isolated storage model?
- Do you understand the problems MS created with WP security model?
- Do you understand how these limitations discourage app development on the platform? (especially for top tier apps)
- Do you understand how a secure environment is inconsequential with a dwindling 3% market share?
- Yes. We’ve been discussing them here this whole time. Useless question.
- No. Explain.
- Yes. However, it doesn’t affect a lot of apps. Unfortunately, it does make developing an app that aims to work with arbitrary file types an impossibility at this time.
- No. I would in fact argue the opposite, namely that a secure environment is essential in order for these devices to gain market share, as they are poised to replace our credit cards in our not too distant future. You can always relax security policies, but tightening them is extremely difficult without causing revolts amongst users and developers. Microsoft is doing the right thing by starting out extremely restrictive and then tweaking where needed going forward… Microsoft just needs to finally shift out of first gear (preferably find fourth and not second).
Let's hear what your solution is
As I said, I can think of a few solutions that don’t require a dedicated file manager app. I’ll give you just one example:
First, Microsoft should add a single shared folder that is programmatically and fully accessible by any app. I’ll call it the “Shared” folder. I imagine it would also show up when the device is plugged into a USB host (as do the other library folders). IE would also require a slight tweak, as to save downloaded files of an unassociated type in this folder. Apps like DropBox would do the same, and could also upload files from here. This solves all our download problems and some of the upload problems without a dedicated file manager app.
Second, Microsoft should introduce a new component to the SDK and encourage developers to use it wherever lists of files are displayed. Since PDF files are all the rage in this thread, I’ll use Acrobat Reader (from WP7) as an example of how users would interact with this new component:
- Launch Acrobat. Acrobat opens to the same two-page panorama view it always has, listing various PDF files (the files are displayed using this new component).
- Press to the left of one or more PDF file names. A checkmark appears to their left, similar to WP’s e-mail app.
- Press the ellipsis. This opens the app menu which includes the entry "send to..."
- Press "send to..." and then select the desired send-to-target. Examples of send-to-targets may be “Shared folder”, “SkyDrive”, “FTP” and “DropBox” (assuming DropBox is installed)
- Select DropBox. The DropBox app is launched. DropBox opens to the upload page and is temporarily given permission to read the selected PDF files (and only them) from Adobe Acrobat’s isolated storage.
- Optionally change the DropBox folder to which the PDF files are uploaded, then press upload. The file transfer commences and continues in the background until complete.
- Press the back button at any time. This returns the user to Acrobat.
This solves all the issues related with apps not being able to handle arbitrary file types and all remaining upload problems, as it allows us to hand off files from isolated storage to apps like DropBox in a controlled fashion.
Notes:
- I imagine any app could register itself as a send-to-target with the OS. Some send-to-targets like “Shared folder”, “SkyDrive”, “FTP” and “WebDAV” would hopefully ship as part of WP.
- Since it is the OS which implements the component and the “send to…” app menus, usage would be consistent across all apps once incorporated. It would work identically for any file types and in any app.
- Apps storing confidential information (like banking apps) probably shouldn’t support “send to…” functionality, in which case the developer just wouldn't use the component.
- The “send to…” mechanism essentially allows apps to exchange files of any type amongst themselves. Any app that acts as a send-to-target is effectively saying: “you can send me multiple files of any file type you want, I can do something useful with it”.
I’m not claiming that this is the best solution or even a realistic solution. Since I don’t have access to Microsoft’s internal security specifications for WP I can’t even say if it is a secure one. What I am saying is that this solves all the problems previously mentioned without:
- requiring a dedicated file manager app and
- making mincemeat of WP’s current security mechanisms which are extremely important, despite one ignorant fool claiming otherwise