Symbolic links will work if the app is looking at the file structure directly when selecting their files to open. It appears Docs2Go only recognizes the files it can open (and NOT the symbolic link).
Alternatively, if you have GoodReader and make your link to the external media /var/mnt/mount1 in my case, you can open the file in Docs2Go when selecting it and Open With... Not quite as convenient but it would get the doc in for editing. I tried this, and GoodReader also does not see the symbolic link.
Getting a file with changes back out again is the problem as you won't be able to save out to the media from Docs2Go. Right now, that seems to be the weakest link along with printing when using an iPad for editing/creating documents.
As for video playback, OPlayer and yxplayer (from the app store) both can work with the symbolic link to the external media. But both seem to suffer when playing back some formats/files. From what I've heard, the video playback for MP4 files using their built-in Video Player uses the onboard chip's ability to decode and therefore offloads the playback from the regular processes. The API to do this is probably locked up, and it wouldn't support the AVI and other formats or codecs anyhow.
So my guess is, for non-MP4 files we may be limited to the software decoding that is resulting in poor performance.
Alternatively, if you have GoodReader and make your link to the external media /var/mnt/mount1 in my case, you can open the file in Docs2Go when selecting it and Open With... Not quite as convenient but it would get the doc in for editing. I tried this, and GoodReader also does not see the symbolic link.
Getting a file with changes back out again is the problem as you won't be able to save out to the media from Docs2Go. Right now, that seems to be the weakest link along with printing when using an iPad for editing/creating documents.
As for video playback, OPlayer and yxplayer (from the app store) both can work with the symbolic link to the external media. But both seem to suffer when playing back some formats/files. From what I've heard, the video playback for MP4 files using their built-in Video Player uses the onboard chip's ability to decode and therefore offloads the playback from the regular processes. The API to do this is probably locked up, and it wouldn't support the AVI and other formats or codecs anyhow.
So my guess is, for non-MP4 files we may be limited to the software decoding that is resulting in poor performance.