Just want to express my disappointment that you did not make your self imposed June 30th deadline. I am not going to threaten to stop using the software or call anyone names, or anything like that. I understand things come up and sometimes things don't work out as planned. And it is just software after all. However, this icloud compatible version is something that you have been espousing for over 6 months. I would think that wold be plenty of time for a crack software company like Barebones to accomplish. I have been following this closely, but from the sidelines. I suspect that I am not the only one who has been doing so and is also disappointed.
That said, please push an iCloud version of Yojimbo as soon as you can, or if you have other plans, please let us know as soon as possible so your users can make alternative plans.
+1 on the disappointment. The sun has set. I'm sure there are many people ready to blame Apple's app approval process, but this is Bare Bones dropping the ball and nothing less. I am shocked that they were not able to deliver within the stated time frame given the amount of time they had.
On Sunday, July 1, 2012 1:09:40 PM UTC-4, Rob Jackson wrote:
> To the Yojimbo Team:
> Just want to express my disappointment that you did not make your self > imposed June 30th deadline. I am not going to threaten to stop using the > software or call anyone names, or anything like that. I understand things > come up and sometimes things don't work out as planned. And it is just > software after all. However, this icloud compatible version is something > that you have been espousing for over 6 months. I would think that wold be > plenty of time for a crack software company like Barebones to accomplish. I > have been following this closely, but from the sidelines. I suspect that I > am not the only one who has been doing so and is also disappointed.
> That said, please push an iCloud version of Yojimbo as soon as you can, or > if you have other plans, please let us know as soon as possible so your > users can make alternative plans.
+ 1
_______________________________________
Terry J Fundak
Systems Engineer
Network Design and Security Solutions for SMBs
Tech Support - Client and Server Systems
TJSoftworks
1834 Chadwick Court
Santa Rosa, CA 95401
(707) 849-1000
(415) 877-1783
te...@tjsoftworks.com
> Just want to express my disappointment that you did not make your self imposed June 30th deadline. I am not going to threaten to stop using the software or call anyone names, or anything like that. I understand things come up and sometimes things don't work out as planned. And it is just software after all. However, this icloud compatible version is something that you have been espousing for over 6 months. I would think that wold be plenty of time for a crack software company like Barebones to accomplish. I have been following this closely, but from the sidelines. I suspect that I am not the only one who has been doing so and is also disappointed.
> That said, please push an iCloud version of Yojimbo as soon as you can, or if you have other plans, please let us know as soon as possible so your users can make alternative plans.
> Thanks.
> - Rob
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
> However, this icloud compatible version is something that you have been espousing for over 6 months. I would think that wold be plenty of time for a crack software company like Barebones to accomplish.
My gut feeling is that this is much more a reflection on the inadequacies of iCloud's sync support than it is of BB's programming skills. Apple created a situation that's bad for both BB and its users.
On Sun, 1 Jul 2012 10:09:40 -0700 (PDT), Rob Jackson
<rjackson...@gmail.com> wrote:
>However, this icloud compatible version is something >that you have been espousing for over 6 months. I would think that wold be >plenty of time for a crack software company like Barebones to accomplish.
I suspect the problem BB is running into has less to do with making
iCloud sync work and more to do with being forced into the App Store
and all the changes and limitations that entails. We need to be fair
to BB and acknowledge that the task at hand is much larger than
migrating from one sync solution to another. It might have helped if
they could have gotten into the MAS before the sandbox restrictions
went into place but they didn't so the pile of needed changes got even
higher.
OR... maybe what they've *really* been working on is Yojimbo 4 with
iCloud support and every new feature request anyone's ever asked for
implemented! ;)
Well: I bought Yojimbo in the MAS (january 2011) but it is not there right now, so there was no need to get it there in time for the sandboxing restriction. I have used some apps that sync through iCloud and have encountered some serious flaws so if the delay means Yojimbo will sync great I can live with this. Until then I will continue to use the Dropbox method, as I have used from the first moment I bought Yojimbo.
On Monday, July 2, 2012 3:39:19 PM UTC-5, GrumpyDave wrote:
> On Sun, 1 Jul 2012 10:09:40 -0700 (PDT), Rob Jackson > <rjackson...@gmail.com> wrote:
> >However, this icloud compatible version is something > >that you have been espousing for over 6 months. I would think that wold > be > >plenty of time for a crack software company like Barebones to accomplish.
> I suspect the problem BB is running into has less to do with making > iCloud sync work and more to do with being forced into the App Store > and all the changes and limitations that entails. We need to be fair > to BB and acknowledge that the task at hand is much larger than > migrating from one sync solution to another. It might have helped if > they could have gotten into the MAS before the sandbox restrictions > went into place but they didn't so the pile of needed changes got even > higher.
> OR... maybe what they've *really* been working on is Yojimbo 4 with > iCloud support and every new feature request anyone's ever asked for > implemented! ;)
We all want Yojimbo to work for us and all wish the best for BB, the company. However, BB has been assuring me ( I assume this is many of us) for a long time - way over 6 months ..... I needed the communication and to know the real date - not "before the sunset of MobileMe" - that is the real issue for me because I stupidly delayed my change from MobileMe to iCloud all the way 'till the very last day because I honestly needed ( wanted) the sync mechanism of Yojimbo... I have grown dependent on Yojimbo and the sync. I rely on it .... Without the sync, I will have to move to something else very shortly .... now as soon as I change - that is the end of Yojimbo's life for me.
Yes, Apple is moving the developers in "a direction" ( good or bad - YMMV ) and yes I'm sure Apple rules are forcing things, some I do not like and some which limit business decisions and developer methods .... Lion UI, in my case, and hidden sliders make me crazy for example, .... but again, BB needs to tell us ( the loyal users ) what the real problem/obstacle is, so that if we need to scream to Apple then we know what we are asking for...
The new limits of Yojimbo are a problem but the bigger problem was the promise and uncertainty of the delivery date and for me the inability to plan my move off MobileMe and find a new solution and change some of my work flows....
Terry
_______________________________________
Terry J Fundak
Systems Engineer
Network Design and Security Solutions for SMBs
Tech Support - Client and Server Systems
TJSoftworks
1834 Chadwick Court
Santa Rosa, CA 95401
(707) 849-1000
(415) 877-1783
te...@tjsoftworks.com
> On Sun, 1 Jul 2012 10:09:40 -0700 (PDT), Rob Jackson
> <rjackson...@gmail.com> wrote:
>> However, this icloud compatible version is something >> that you have been espousing for over 6 months. I would think that wold be >> plenty of time for a crack software company like Barebones to accomplish.
> I suspect the problem BB is running into has less to do with making
> iCloud sync work and more to do with being forced into the App Store
> and all the changes and limitations that entails. We need to be fair
> to BB and acknowledge that the task at hand is much larger than
> migrating from one sync solution to another. It might have helped if
> they could have gotten into the MAS before the sandbox restrictions
> went into place but they didn't so the pile of needed changes got even
> higher.
> OR... maybe what they've *really* been working on is Yojimbo 4 with
> iCloud support and every new feature request anyone's ever asked for
> implemented! ;)
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
David A. wrote:
> We need to be fair
> to BB and acknowledge that the task at hand is much larger than
> migrating from one sync solution to another.
I'm jsut relieved to be working with a company who don't ship until it's right. The inconvenience of the short delay compared to data corruption in a month...<shudder>. That's why I use all their stuff on a daily basis, because of those standards.
It was the right decision to wait. I can cope for a few days more;)
I do feel sorry for the BB team, and only indirectly does the missed
deadline affect me, but in the end, this will deeply affect how I store
data in the future, and it won't be in Yojimbo.
Basically, if Apple so severely restricts the solutions available
developers using its facilities (such as the appstore, iCloud, etc.) that a
competent developer with an established record like BB, fails in supporting
their own, currently working functionality, then I have to evaluate if
Apple is the right platform for me.
Apples hardware and on-board software is second to none in most aspects
(i.e., top of the line, and sexy as hell) and I think it is safe to say
that we all crave it to some degree. But when it comes to delivering
cloud/network based solutions, they suck.
The marginal .mac service was replaced with the even more marginal MobileMe
service, that have now been forcefully replaced with the better named, but
apparently less functional iCloud. At no point did Apple go out of its way
to help end-users by offering legacy support beyond the absolute
minimum... if that.
Anyway, the only reason I bring this up here, is that I hope that in the
future, BB will help its users to mitigate risk by not tying services
exclusively to services provided by Apple in the cloud/network area, where
Apple have a repeatedly deficient track record. IMNSHO, BB would do well in
separating its support for sync from its desire to run on the Apple
platform.
If such services as synchronization had been separated into a platform
neural layer, then I might have been able to use the Goole, Amazon, or
other third-party cloud service during the time it takes for Apple to get
iCloud fully functional.
Basically, the "cloud" (in its most extended meaning) is evolving so fast
that I can't be expected to lock down my supplier of sync services to
whomever I choose to provide the hardware platform for the UI.
To do so would be impractical and irresponsible.
I truly feel sorry that the BB team got caught on this cluster (cloud?)
"feature", and I don't hold it against them.
Now, all I have to do is extract myself gracefully from this mess and
select a solution based on the cloud provider(s) even though the UI is
bound to be inferior.
--j
PS I wish to underline that I'm not reacting like this because some petty
disagreement with BB or Apple (although the later is the party I blame for
pushing this wreck over the cliff.)
Here is how badly this has hit me:
Since a few month, I'm visiting Sweden for an extended time and had to
leave my primary Yojimbo DB back on a non-Lion compatible Mac back in
California. The machine I have here is Lion-only.
Thus I live in a [data] house divided.
How I'm going to re-integrate 6GB+ and just under 7K of items (many of them
over 50MB) I have no idea. So far the only solutions appear to be to write
a non trivial amount of custom software with separate versions for each
machine, and then re-integrate more or less by hand where there is
ambiguity.
As the metadata such as comments, tags, folders, and modification-,
creation-, and addition-dates are part of the metadata that I
*must*preserve, a simple export won't work.
Even simple things such as putting each item in a file with the title as
the name will fail as the titles often contain '/' and ':', so I have to
establish a dictionary just to do that.
Essentially I have a problem that is a miniature (and luckily one-of)
version of what BB had to deal with for the current iCloud migration.
I also have to figure out where to put all this when I'm done.
Clearly it is my fault for delaying cleaning this up until now, but as the
future is cloudy (sorry) as to where the best place to keep this, I had
hoped BB would buy me some time by pulling a rabbit out of a hat yet again.
As luck would have it, the s[omething] hit the fan when most inconvenient.
Sigh.
PPS [This spaced reserved for foul language generated by having to use the
AppleEvents data model to get the data out of Yojimbo.]
But, I still want to know exactly what I need to give as feedback to Apple so they don't continue down the apparently bad path - with respect to developers... BB help us help you..... what is the issue?
Terry
_______________________________________
Terry J Fundak
Systems Engineer
Network Design and Security Solutions for SMBs
Tech Support - Client and Server Systems
TJSoftworks
1834 Chadwick Court
Santa Rosa, CA 95401
(707) 849-1000
(415) 877-1783
te...@tjsoftworks.com
> I do feel sorry for the BB team, and only indirectly does the missed deadline affect me, but in the end, this will deeply affect how I store data in the future, and it won't be in Yojimbo.
> Basically, if Apple so severely restricts the solutions available developers using its facilities (such as the appstore, iCloud, etc.) that a competent developer with an established record like BB, fails in supporting their own, currently working functionality, then I have to evaluate if Apple is the right platform for me.
> Apples hardware and on-board software is second to none in most aspects (i.e., top of the line, and sexy as hell) and I think it is safe to say that we all crave it to some degree. But when it comes to delivering cloud/network based solutions, they suck.
> The marginal .mac service was replaced with the even more marginal MobileMe service, that have now been forcefully replaced with the better named, but apparently less functional iCloud. At no point did Apple go out of its way to help end-users by offering legacy support beyond the absolute minimum... if that.
> Anyway, the only reason I bring this up here, is that I hope that in the future, BB will help its users to mitigate risk by not tying services exclusively to services provided by Apple in the cloud/network area, where Apple have a repeatedly deficient track record. IMNSHO, BB would do well in separating its support for sync from its desire to run on the Apple platform.
> If such services as synchronization had been separated into a platform neural layer, then I might have been able to use the Goole, Amazon, or other third-party cloud service during the time it takes for Apple to get iCloud fully functional.
> Basically, the "cloud" (in its most extended meaning) is evolving so fast that I can't be expected to lock down my supplier of sync services to whomever I choose to provide the hardware platform for the UI.
> To do so would be impractical and irresponsible.
> I truly feel sorry that the BB team got caught on this cluster (cloud?) "feature", and I don't hold it against them.
> Now, all I have to do is extract myself gracefully from this mess and select a solution based on the cloud provider(s) even though the UI is bound to be inferior.
> --j
> PS I wish to underline that I'm not reacting like this because some petty disagreement with BB or Apple (although the later is the party I blame for pushing this wreck over the cliff.)
> Here is how badly this has hit me:
> Since a few month, I'm visiting Sweden for an extended time and had to leave my primary Yojimbo DB back on a non-Lion compatible Mac back in California. The machine I have here is Lion-only.
> Thus I live in a [data] house divided.
> How I'm going to re-integrate 6GB+ and just under 7K of items (many of them over 50MB) I have no idea. So far the only solutions appear to be to write a non trivial amount of custom software with separate versions for each machine, and then re-integrate more or less by hand where there is ambiguity.
> As the metadata such as comments, tags, folders, and modification-, creation-, and addition-dates are part of the metadata that I must preserve, a simple export won't work.
> Even simple things such as putting each item in a file with the title as the name will fail as the titles often contain '/' and ':', so I have to establish a dictionary just to do that.
> Essentially I have a problem that is a miniature (and luckily one-of) version of what BB had to deal with for the current iCloud migration.
> I also have to figure out where to put all this when I'm done.
> Clearly it is my fault for delaying cleaning this up until now, but as the future is cloudy (sorry) as to where the best place to keep this, I had hoped BB would buy me some time by pulling a rabbit out of a hat yet again.
> As luck would have it, the s[omething] hit the fan when most inconvenient.
> Sigh.
> PPS [This spaced reserved for foul language generated by having to use the AppleEvents data model to get the data out of Yojimbo.]
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
Johan,. I agree with you - migrating meta data is a huge hole!
On sync.
Can I suggest BB take a look at OwnCloud? This is self hosted and supports sync services and APIs for developers to do likewise. It has some dropbox like features and I found easy to install.
> I do feel sorry for the BB team, and only indirectly does the missed deadline affect me, but in the end, this will deeply affect how I store data in the future, and it won't be in Yojimbo.
> Basically, if Apple so severely restricts the solutions available developers using its facilities (such as the appstore, iCloud, etc.) that a competent developer with an established record like BB, fails in supporting their own, currently working functionality, then I have to evaluate if Apple is the right platform for me.
> Apples hardware and on-board software is second to none in most aspects (i.e., top of the line, and sexy as hell) and I think it is safe to say that we all crave it to some degree. But when it comes to delivering cloud/network based solutions, they suck.
> The marginal .mac service was replaced with the even more marginal MobileMe service, that have now been forcefully replaced with the better named, but apparently less functional iCloud. At no point did Apple go out of its way to help end-users by offering legacy support beyond the absolute minimum... if that.
> Anyway, the only reason I bring this up here, is that I hope that in the future, BB will help its users to mitigate risk by not tying services exclusively to services provided by Apple in the cloud/network area, where Apple have a repeatedly deficient track record. IMNSHO, BB would do well in separating its support for sync from its desire to run on the Apple platform.
> If such services as synchronization had been separated into a platform neural layer, then I might have been able to use the Goole, Amazon, or other third-party cloud service during the time it takes for Apple to get iCloud fully functional.
> Basically, the "cloud" (in its most extended meaning) is evolving so fast that I can't be expected to lock down my supplier of sync services to whomever I choose to provide the hardware platform for the UI.
> To do so would be impractical and irresponsible.
> I truly feel sorry that the BB team got caught on this cluster (cloud?) "feature", and I don't hold it against them.
> Now, all I have to do is extract myself gracefully from this mess and select a solution based on the cloud provider(s) even though the UI is bound to be inferior.
> --j
> PS I wish to underline that I'm not reacting like this because some petty disagreement with BB or Apple (although the later is the party I blame for pushing this wreck over the cliff.)
> Here is how badly this has hit me:
> Since a few month, I'm visiting Sweden for an extended time and had to leave my primary Yojimbo DB back on a non-Lion compatible Mac back in California. The machine I have here is Lion-only.
> Thus I live in a [data] house divided.
> How I'm going to re-integrate 6GB+ and just under 7K of items (many of them over 50MB) I have no idea. So far the only solutions appear to be to write a non trivial amount of custom software with separate versions for each machine, and then re-integrate more or less by hand where there is ambiguity.
> As the metadata such as comments, tags, folders, and modification-, creation-, and addition-dates are part of the metadata that I must preserve, a simple export won't work.
> Even simple things such as putting each item in a file with the title as the name will fail as the titles often contain '/' and ':', so I have to establish a dictionary just to do that.
> Essentially I have a problem that is a miniature (and luckily one-of) version of what BB had to deal with for the current iCloud migration.
> I also have to figure out where to put all this when I'm done.
> Clearly it is my fault for delaying cleaning this up until now, but as the future is cloudy (sorry) as to where the best place to keep this, I had hoped BB would buy me some time by pulling a rabbit out of a hat yet again.
> As luck would have it, the s[omething] hit the fan when most inconvenient.
> Sigh.
> PPS [This spaced reserved for foul language generated by having to use the AppleEvents data model to get the data out of Yojimbo.]
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
I don't want to seem like a wet blanket, but somehow, someway, other Apple developers have managed to make the transition.
I've used BB, originally BBEdit, then Yojimbo for a long time, and I want them to do well. However, I'm a developer myself and I really have to wonder why it's taking them so long. Yojimbo came out for the iPad in the late fall/early winter of 2010 as a read only app. My assumption at the time was that BB was just learning iPad programming and released a read only app as a stop gap measure. But it's been over a year and a half and no hint of a full functional app yet. Apple announced that MobleMe was going away and to program to iCloud a good 9 months ago. All this says to me that either BB is not willing to devote resources to the iPad app and considers it to be a hobby app that gets attention only when there is nothing else to do, or they have boxed themselves in with the design of the product and can't figure out how to make it work.
Seriously, iPad programming is not rocket science. Hundreds of thousands, if not millions of programmers have managed to figure it out. I sure hope that BB somehow manages to figure it out, but right now I'm frustrated with them.
On Jul 6, 2012, at 6:19 AM, Johan™Strandberg wrote:
> I do feel sorry for the BB team, and only indirectly does the missed deadline affect me, but in the end, this will deeply affect how I store data in the future, and it won't be in Yojimbo.
> Basically, if Apple so severely restricts the solutions available developers using its facilities (such as the appstore, iCloud, etc.) that a competent developer with an established record like BB, fails in supporting their own, currently working functionality, then I have to evaluate if Apple is the right platform for me.
> Apples hardware and on-board software is second to none in most aspects (i.e., top of the line, and sexy as hell) and I think it is safe to say that we all crave it to some degree. But when it comes to delivering cloud/network based solutions, they suck.
> The marginal .mac service was replaced with the even more marginal MobileMe service, that have now been forcefully replaced with the better named, but apparently less functional iCloud. At no point did Apple go out of its way to help end-users by offering legacy support beyond the absolute minimum... if that.
> Anyway, the only reason I bring this up here, is that I hope that in the future, BB will help its users to mitigate risk by not tying services exclusively to services provided by Apple in the cloud/network area, where Apple have a repeatedly deficient track record. IMNSHO, BB would do well in separating its support for sync from its desire to run on the Apple platform.
> If such services as synchronization had been separated into a platform neural layer, then I might have been able to use the Goole, Amazon, or other third-party cloud service during the time it takes for Apple to get iCloud fully functional.
> Basically, the "cloud" (in its most extended meaning) is evolving so fast that I can't be expected to lock down my supplier of sync services to whomever I choose to provide the hardware platform for the UI.
> To do so would be impractical and irresponsible.
> I truly feel sorry that the BB team got caught on this cluster (cloud?) "feature", and I don't hold it against them.
> Now, all I have to do is extract myself gracefully from this mess and select a solution based on the cloud provider(s) even though the UI is bound to be inferior.
> --j
> PS I wish to underline that I'm not reacting like this because some petty disagreement with BB or Apple (although the later is the party I blame for pushing this wreck over the cliff.)
> Here is how badly this has hit me:
> Since a few month, I'm visiting Sweden for an extended time and had to leave my primary Yojimbo DB back on a non-Lion compatible Mac back in California. The machine I have here is Lion-only.
> Thus I live in a [data] house divided.
> How I'm going to re-integrate 6GB+ and just under 7K of items (many of them over 50MB) I have no idea. So far the only solutions appear to be to write a non trivial amount of custom software with separate versions for each machine, and then re-integrate more or less by hand where there is ambiguity.
> As the metadata such as comments, tags, folders, and modification-, creation-, and addition-dates are part of the metadata that I must preserve, a simple export won't work.
> Even simple things such as putting each item in a file with the title as the name will fail as the titles often contain '/' and ':', so I have to establish a dictionary just to do that.
> Essentially I have a problem that is a miniature (and luckily one-of) version of what BB had to deal with for the current iCloud migration.
> I also have to figure out where to put all this when I'm done.
> Clearly it is my fault for delaying cleaning this up until now, but as the future is cloudy (sorry) as to where the best place to keep this, I had hoped BB would buy me some time by pulling a rabbit out of a hat yet again.
> As luck would have it, the s[omething] hit the fan when most inconvenient.
> Sigh.
> PPS [This spaced reserved for foul language generated by having to use the AppleEvents data model to get the data out of Yojimbo.]
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
On Fri, Jul 6, 2012 at 4:17 PM, Terry J Fundak <te...@tjsoftworks.com>
wrote:
> I still want to know exactly what I need to give as feedback to Apple
I doubt anything except pain in the bottom line will change Apple at this
point. I think it is up to developers like BB
(and ultimately customers like us) to vote by changing usage patterns. I
suspect that might be easier than it looks at the first glance. Who would
actually willingly choose iCloud as their primary cloud provider at this
point? Until proven otherwise, the storage and sync services are second
rate at best. Additional points must be deducted for the abysmal track
record and reliability of previous incarnations of Apple provided services.
Future will tell if they are actually committed to iCloud beyond what is
minimally needed to support the App Stores and iTunes and a few flagship
services. My gut feel is that iCloud will be replaced on a whim if other
needs demands it. But I have nothing firm to stand on here but my own not
so humble opinion, and we are drifting off topic.
---
On Fri, Jul 6, 2012 at 4:32 PM, Christian de Larrinaga <c...@firsthand.net>
wrote:
> migrating meta data is a huge hole
That would be the one thing that BB could have done for us -- adding a
simple metadata export option to the application. Something that wrote an
xml file containing all meta data and separate data files where needed for
binary data such as images, pdfs, etc..
At this point I have to do this myself some way as I can't wait for them to
do it for me. Suffice to say, I'm never putting data into a store that
won't provide this service for me in the future. Hit me hard enough times
and slowly I learn.
OwnCloud
I don't know anything about OwnCloud, but the idea sounds intriguing. As
long as it can export to a simple external format so I can move my data if
I need to, I'd be happy.
<walkerphill...@gmail.com> wrote:
>I don't want to seem like a wet blanket, but somehow, someway, >other Apple developers have managed to make the transition.
What currently shipping products are you aware of that are using iCloud to synchronize Core Data persistent stores at the object level? There are certainly applications shipping that use iCloud document ubiquity; but that's a completely different animal. (And it actually works.)
We're encountering challenges with iCloud that require firsthand intervention from the OS engineering staff. What's that tell you?
>Apple announced that MobleMe was going away and to program to >iCloud a good 9 months ago.
That the iCloud API itself was a moving target until roughly Mac OS X 10.7.3; or that there are bugs in the iCloud support in the currently shipping OS; that $AAPL has absolutely no insight into the business operations of our company (no more than you do, all due respect); none of these things have any bearing on the matter. Right?
>Hundreds of thousands, if not millions of programmers have managed to
>figure it out.
At 12:19 +0200 07/06/2012, Johan Strandberg wrote:
[...]
>Since a few month, I'm visiting Sweden for an extended time and had to
>leave my primary Yojimbo DB back on a non-Lion compatible Mac back in
>California. The machine I have here is Lion-only.
>Thus I live in a [data] house divided.
>How I'm going to re-integrate 6GB+ and just under 7K of items (many of
>them over 50MB) I have no idea. So far the only solutions appear to be to
>write a non trivial amount of custom software with separate versions for
>each machine, and then re-integrate more or less by hand where there is
>ambiguity.
[...]
Though perhaps there are other conditions I'm unaware of, if you have:
* Machine A: in California and inactive since you left
* Machine B: at hand and active
and if both machines contained the same data at the time you left CA, I'd
expect you can now consider machine B the 'master', and just copy its data
store back to machine A when you return.
Regards,
Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com>
P.O. Box 1048, Bedford, MA 01730-1048
Again, is there anything that we the effected loyal Yojimbo users ( some of us are developers too ) can do to help either Apple understand that they are creating pain or is there anything that we users can say that will help BB make a decision to move a different direction?
Terry
_______________________________________
Terry J Fundak
Systems Engineer
Network Design and Security Solutions for SMBs
Tech Support - Client and Server Systems
TJSoftworks
1834 Chadwick Court
Santa Rosa, CA 95401
(707) 849-1000
(415) 877-1783
te...@tjsoftworks.com
> On Friday, July 6, 2012, Phillip Walker <walkerphill...@gmail.com> wrote:
>> I don't want to seem like a wet blanket, but somehow, someway, other Apple developers have managed to make the transition.
> What currently shipping products are you aware of that are using iCloud to synchronize Core Data persistent stores at the object level? There are certainly applications shipping that use iCloud document ubiquity; but that's a completely different animal. (And it actually works.)
> We're encountering challenges with iCloud that require firsthand intervention from the OS engineering staff. What's that tell you?
>> Apple announced that MobleMe was going away and to program to iCloud a good 9 months ago.
> That the iCloud API itself was a moving target until roughly Mac OS X 10.7.3; or that there are bugs in the iCloud support in the currently shipping OS; that $AAPL has absolutely no insight into the business operations of our company (no more than you do, all due respect); none of these things have any bearing on the matter. Right?
>> Hundreds of thousands, if not millions of programmers have managed to
>> figure it out.
> Someday I'll look back on all this and laugh... until they sedate me.
> -- > You received this message because you are subscribed to the "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group.
At 07:17 -0700 07/06/2012, Terry J Fundak wrote:
[...]
>But, I still want to know exactly what I need to give as feedback to Apple
>so they don't continue down the apparently bad path - with respect to
>developers... BB help us help you..... what is the issue?
Though we do appreciate the offer, the key issues are technical, not
matters of feedback.
Regards,
Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com>
P.O. Box 1048, Bedford, MA 01730-1048
I'm not looking to pick a fight and I have no idea what specific technologies other companies use, but somehow, someway, they have managed to figure out how to achieve the effect of synchronization. Amazon, Evernote and Apple among others all managed to somehow produce apps that allow synchronization between devices, heck Amazon and Evernote even synchronize across different platforms. It doesn't much matter to me how they do it, I just care that it works.
I'm sure there are bugs in the technology, I have yet to work with a technology that doesn't have bugs. But I've never had a boss who was willing to accept there are bugs in the technology as a valid reason for not getting my project done on time. If one way doesn't work, then I figure out another way to achieve the same goal.
You are right, I don't have any knowledge of the inter workings of Bare Bones software. Bare Bones is well known for being very closed mouthed when dealing with customers. The problem is that if you aren't willing to be open with the customers, then they are going to fill in the details themselves and usually it won't be in a positive way. I'm sorry if that offends you, but that's a reality that all companies that have customers have to deal with.
Look, as I said, I'm not looking to pick a fight with you or anyone from Bare Bones. Yojimbo for the Mac is a fine product, I'm happy with it and the syncing work arounds work just fine for me. I'm frustrated that Yojimbo for the iPad is read only and that frustration is compounded by BB's unwillingness to discuss the matter.
> On Friday, July 6, 2012, Phillip Walker <walkerphill...@gmail.com> wrote:
>> I don't want to seem like a wet blanket, but somehow, someway, other Apple developers have managed to make the transition.
> What currently shipping products are you aware of that are using iCloud to synchronize Core Data persistent stores at the object level? There are certainly applications shipping that use iCloud document ubiquity; but that's a completely different animal. (And it actually works.)
> We're encountering challenges with iCloud that require firsthand intervention from the OS engineering staff. What's that tell you?
>> Apple announced that MobleMe was going away and to program to iCloud a good 9 months ago.
> That the iCloud API itself was a moving target until roughly Mac OS X 10.7.3; or that there are bugs in the iCloud support in the currently shipping OS; that $AAPL has absolutely no insight into the business operations of our company (no more than you do, all due respect); none of these things have any bearing on the matter. Right?
>> Hundreds of thousands, if not millions of programmers have managed to
>> figure it out.
> Someday I'll look back on all this and laugh... until they sedate me.
> -- > You received this message because you are subscribed to the "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group.
+ 1 to Phillip's and others comments.... I think we are really trying to communicate in a positive way.
BB, please keep us in the loop and in a "timely" way .... we are trying to remain loyal .... despite our pain.
Terry
_______________________________________
Terry J Fundak
Systems Engineer
Network Design and Security Solutions for SMBs
Tech Support - Client and Server Systems
TJSoftworks
1834 Chadwick Court
Santa Rosa, CA 95401
(707) 849-1000
(415) 877-1783
te...@tjsoftworks.com
> I'm not looking to pick a fight and I have no idea what specific technologies other companies use, but somehow, someway, they have managed to figure out how to achieve the effect of synchronization. Amazon, Evernote and Apple among others all managed to somehow produce apps that allow synchronization between devices, heck Amazon and Evernote even synchronize across different platforms. It doesn't much matter to me how they do it, I just care that it works.
> I'm sure there are bugs in the technology, I have yet to work with a technology that doesn't have bugs. But I've never had a boss who was willing to accept there are bugs in the technology as a valid reason for not getting my project done on time. If one way doesn't work, then I figure out another way to achieve the same goal.
> You are right, I don't have any knowledge of the inter workings of Bare Bones software. Bare Bones is well known for being very closed mouthed when dealing with customers. The problem is that if you aren't willing to be open with the customers, then they are going to fill in the details themselves and usually it won't be in a positive way. I'm sorry if that offends you, but that's a reality that all companies that have customers have to deal with.
> Look, as I said, I'm not looking to pick a fight with you or anyone from Bare Bones. Yojimbo for the Mac is a fine product, I'm happy with it and the syncing work arounds work just fine for me. I'm frustrated that Yojimbo for the iPad is read only and that frustration is compounded by BB's unwillingness to discuss the matter.
> On Jul 6, 2012, at 3:58 PM, Rich Siegel wrote:
>> On Friday, July 6, 2012, Phillip Walker <walkerphill...@gmail.com> wrote:
>>> I don't want to seem like a wet blanket, but somehow, someway, other Apple developers have managed to make the transition.
>> What currently shipping products are you aware of that are using iCloud to synchronize Core Data persistent stores at the object level? There are certainly applications shipping that use iCloud document ubiquity; but that's a completely different animal. (And it actually works.)
>> We're encountering challenges with iCloud that require firsthand intervention from the OS engineering staff. What's that tell you?
>>> Apple announced that MobleMe was going away and to program to iCloud a good 9 months ago.
>> That the iCloud API itself was a moving target until roughly Mac OS X 10.7.3; or that there are bugs in the iCloud support in the currently shipping OS; that $AAPL has absolutely no insight into the business operations of our company (no more than you do, all due respect); none of these things have any bearing on the matter. Right?
>>> Hundreds of thousands, if not millions of programmers have managed to
>>> figure it out.
>> Someday I'll look back on all this and laugh... until they sedate me.
>> -- >> You received this message because you are subscribed to the "Yojimbo Talk" discussion group on Google Groups.
>> To post to this group, send email to yojimbo-talk@googlegroups.com
>> To unsubscribe from this group, send email to
>> yojimbo-talk+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/yojimbo-talk?hl=en >> If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group.
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
ok, I'm to take one more stab at this and then I'm going to let it go.
A number of years ago, I read an interview with the owner of a restaurant. In that interview, the restaurant owner mentioned that one of her biggest frustrations is that Southerns tend not say when something is wrong, they just smile, say everything is fine and then never come back. She then said, how can she fix something if the customers aren't willing to say that there is a problem. I thought that she had a point.
I posted my comments because I saw a problem and thought it would be better to let BB software know what I saw as a problem rather than just simply not come back. As far as I know this is the only mechanism for given feedback to Bare Bones software. I'm not here to pick fights, I'm not here to start flame wars. I'm also not storming off in a huff because my feelings are hurt. I hope that Yojimbo for the iPad will eventually do what I want it to do. I will be quite happy if it does. I will leave it there.
On Jul 6, 2012, at 5:44 PM, Patrick Woolsey wrote:
> At 17:14 -0400 07/06/2012, Phillip Walker wrote:
>> I'm not looking to pick a fight [...]
> As in my experience :-), this is often the first thing someone who's trying
> to pick a fight says, please refrain.
> Regards,
> Patrick Woolsey
> ==
> Bare Bones Software, Inc. <http://www.barebones.com>
> P.O. Box 1048, Bedford, MA 01730-1048
> -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
At 18:25 -0400 07/06/2012, Phillip Walker wrote:
[...]
> I posted my comments because I saw a problem and thought it would
> be better to let BB software know what I saw as a problem rather
> than just simply not come back. As far as I know this is the only
> mechanism for given feedback to Bare Bones software. [...]
In hopes of clarifying the latter, we always appreciate feedback and the
most direct way to provide same is to contact us:
After reading over this thread and others related to the pending iCloud compatibility transition with Yojimbo, I thought I would chime in. I too was one of those folks who held onto their MobileMe account in the desperate hope that BB would nail this down prior to the sunset date. I too was one of those who was really angry for the semi-assurances that BB provided prior to the sunset date, only to be let down after it past without a new syncing solution available. But then I decided to look around at what is my alternative for similar apps that can syc across my Macs. After reading the blogs for other apps like Devonthink, and Soho notes, it is quickly apparent that no one has figured out how to nail this down in a timely fashion. What I get from my brief research on this topic is that straight document syncing over iCloud is easy to get rolling, but database syncing is a whole other enchilada. The fact that a lot of smart people with different developers have been working on this and that no one has cracked it speaks volumes to me about the way that Apple ultimately dropped the ball on this issue. Trust me guys, we are not alone, and I really think Apple should take a good piece of this beating that we are quick to dispense to BareBones. If you have bothered to post something or send an email to BB, I would encourage you to sit down at the keyboard once more and let Apple know how you feel.
> After reading over this thread and others related to the pending iCloud compatibility transition with Yojimbo, I thought I would chime in. I too was one of those folks who held onto their MobileMe account in the desperate hope that BB would nail this down prior to the sunset date. I too was one of those who was really angry for the semi-assurances that BB provided prior to the sunset date, only to be let down after it past without a new syncing solution available. But then I decided to look around at what is my alternative for similar apps that can syc across my Macs. After reading the blogs for other apps like Devonthink, and Soho notes, it is quickly apparent that no one has figured out how to nail this down in a timely fashion. What I get from my brief research on this topic is that straight document syncing over iCloud is easy to get rolling, but database syncing is a whole other enchilada. The fact that a lot of smart people with different developers have been working on this and that no one has cracked it speaks volumes to me about the way that Apple ultimately dropped the ball on this issue. Trust me guys, we are not alone, and I really think Apple should take a good piece of this beating that we are quick to dispense to BareBones. If you have bothered to post something or send an email to BB, I would encourage you to sit down at the keyboard once more and let Apple know how you feel. > -- > You received this message because you are subscribed to the > "Yojimbo Talk" discussion group on Google Groups.
> To post to this group, send email to yojimbo-talk@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/yojimbo-talk?hl=en > If you have a feature request or would like to report a problem, > please email "supp...@barebones.com" rather than posting to the group.
