Maybe a Local Sync to Mobile for PBB?What if Logos added a LOCAL sync to mobile device commend that did all of the work on your computer without going through the Logos servers? You attach your mobile device as a USB device and execute Sync Mobile. Then we could do it ourselves, not as convent but gets the job done, no server space problems for Logos, no copyright problems for Logos. [And no backup on the Cloud]
Many requests to get PBBs on mobile devices such as:http://community.logos.com/forums/p/61021/432803.aspx#432803 http://community.logos.com/forums/p/72400/504108.aspx#504108 http://community.logos.com/forums/p/49739/367841.aspx#367841 Others
Maybe a Local Sync to Mobile for PBB?What if Logos added a LOCAL sync to mobile device commend that did all of the work on your computer without going through the Logos servers?
The last I have seen from Logos - http://community.logos.com/forums/p/66838/467269.aspx#467269 - states that this is not in their plans.
Yes, that is their statement. [And I had seen it] BUT something [from our point of view] is holding their plans up.
[and we have not been told what the hold up is]
And Yes, having our PBB sync as does every thing else is the best fix.
The question here is: If their planed way will not be ready soon [if ever] will we accept a local, and yes limited, work a round so that we can read our PBBs in Logos Mobile? By letting them know that we would [or would not] accept a local option they can modify their plans as needed.
[[Then we need to define 'soon': End of 2013, late 2014, Logos 6 (2015/18?) ]
In David Mitchell's words (http://community.logos.com/forums/p/66838/466886.aspx#466886): "there's a lot to do".
Sorry that this isn't very descriptive, but it's difficult to go into much more detail without requiring knowledge of a number of our internal systems.
The question here is: If their planed way will not be ready soon [if ever] will we accept a local, and yes limited, work a round so that we can read our PBBs in Logos Mobile?
A local sync option would not be significantly less code for us to write. That is, while local sync may appear simple, it would actually take a lot of work to make it function correctly, so we're planning to spend that effort implementing the server-based solution instead.
[and we have not been told what the hold up is] A local sync option would not be significantly less code for us to write. That is, while local sync may appear simple, it would actually take a lot of work to make it function correctly, so we're planning to spend that effort implementing the server-based solution instead.
Local sync option is the LAST choice. Only as a LAST resort when nothing else will get the job done.
Am I correctly understanding your statement "we're planning to spend that effort implementing the server-based solution" to mean that there are no known BLOCKING issues such as Server space and capacity; copyright restrictions; etc.?
[[Was a programmer for 30 years - even 'Hello World' programs are not simple. [return of zero to let the system know that there were no errors gets skipped] ]]
Well that sucks...
