We are still working on this, and will have a future version of Yojimbo
with iCloud support prior to the MobileMe sunset date (of Jun 30, 2012).
Regards,
Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com>
P.O. Box 1048, Bedford, MA 01730-1048
>It's mid-March. How much longer do we have to wait? Give us a hint.
>March, April, May
>
>I have to move to iCloud by the second week of May as I'm leaving on a
>six week ride to Canada & Alaska.
As of today I can only say with surety what I have before, i.e. that we
will have a version of Yojimbo with iCloud support ready prior to the
Tomball sez:
Sorry but I can't offer you specific advice here since I don't have enough
background; I'll follow up separately.
On 11/04/12 at 6:47 AM -0700, Bryan Bagwell <bbag...@gmail.com> wrote:
>The sun sets in 80 days! I hope you guys come up with a solid,
>tested solution and not some patchwork stab at it. I have not
>used Yojimbo since the day I moved to iCloud last year and will
>not use it again until it works the way it is supposed to.
That's a bit agro, Yojimbo *does* work the way it's supposed to,
just not the way you *want* it to.
What makes you think BBSW would make "some patchwork stab at
it"? When have you *ever* seen anything like that from them. For
decades they have been producing quality software. They have
said an iCloud solution is coming; give them a chance to fulfil that.
Charlie
PS. I doubt anyone will lose sleep over your choice not to use Yojimbo.
--
Ꮚ Charlie Garrison ♊ <garr...@zeta.org.au>
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
〠 http://www.ietf.org/rfc/rfc1855.txt
In 80 days this will no longer be true -- what many people consider
one of Yojimbo's essential features will stop working. The OP's
question was a fair one. It will take some time to find and
transition to an alternative solution if one of Yojimbo's key features
stops working in 80 days and many of us would like to know if we
should start that transition now. Fair question.
> What makes you think BBSW would make "some patchwork stab at it"? When have
> you *ever* seen anything like that from them. For decades they have been
Uhm, the iPad app...
> PS. I doubt anyone will lose sleep over your choice not to use Yojimbo.
Seriously dude, why do most people on this list feel the need to
attack any poster who isn't crazy in love with Barebones? This isn't
the Yojimbo-fan-boyz list, it's Yojimbo-talk and talking about
Yojimbo's shortcomings (yes, there are some) should be OK. Let's all
be polite and civil to each other.
Cheers,
Rhet
> --
> 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 yojimb...@googlegroups.com
> To unsubscribe from this group, send email to
> yojimbo-talk...@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 "sup...@barebones.com" rather than posting to the group.
That's why I now use evernote. I don't like the fact that it uses remote servers, but at least I can enter information into it. I guess I might be a bit more understanding if I understood why Barebones refuses to allow me to enter info on the iPad. But they refuse to talk about it. Let's face it, Yojimbo for the iPad is priced as a premium iPad app, but it doesn't have the functionality of a premium iPad app. After I first bought it, I thought, well, this is just an interim solution, they'll release a fully function version real soon, but that was a long time ago and I've just about given up hope that Bare Bones has any plans to enhance Yojimbo for the iPad. It's too bad. I think that Yojimbo for the iPad could have been a real winner.
On 11/04/12 at 9:23 PM -0600, Rhet Turnbull
<rtur...@gmail.com> wrote:
>> That's a bit agro, Yojimbo *does* work the way it's supposed to, just not
>
>In 80 days this will no longer be true -- what many people consider
>one of Yojimbo's essential features will stop working. The OP's
>question was a fair one. It will take some time to find and
>transition to an alternative solution if one of Yojimbo's key features
>stops working in 80 days and many of us would like to know if we
>should start that transition now. Fair question.
Fair question, which has already been answered. The OP didn't
acknowledge the question had been answered, other than by
quoting one answer and then ignoring it.
>> What makes you think BBSW would make "some patchwork stab at it"? When have
>> you *ever* seen anything like that from them. For decades they have been
>
>Uhm, the iPad app...
Never seen it, so can't really comment. I thought the only real
problem with it was lack of reverse sync, which was clearly
stated in product description. People may not have been happy
with that, but I wouldn't call it a "patchwork stab".
>> PS. I doubt anyone will lose sleep over your choice not to use Yojimbo.
>
>Seriously dude, why do most people on this list feel the need to
>attack any poster who isn't crazy in love with Barebones? This isn't
>the Yojimbo-fan-boyz list, it's Yojimbo-talk and talking about
>Yojimbo's shortcomings (yes, there are some) should be OK. Let's all
>be polite and civil to each other.
To me; it felt the OP was not being civil and was threatening.
For very many years I've heard users threaten to "never use XYZ
product again", or some variation. It achieves nothing other
than to attempt a call to action via threats. Few people respond
well to such threats; I've heard/read BBSW staff politely
respond to such threats by even suggesting other products which
may suit user better, but never has it made them jump and react.
Had the OP stated a specific problem (or shortcoming) and
requested assistance or solutions, we'd be having a *very*
different conversation right now. Isn't talking about solutions
heaps more productive than moaning and whinging? If preferring
production conversation makes me a fan-boy, then send me a
t-shirt to wear proudly.
Granted, I started my reply saying the OP sounded a bit agro. I
accept that's my personal opinion which happens when I see
threatening behaviour. I should have refrained since all I did
was add to the problem. This list is to discuss Yojimbo and how
best to use it; not to whinge/threaten/react.
Signing off (this is straying too far OT),
Charlie
PS. As summary for those who may have missed it:
On 5/03/12 at 9:43 AM -0500, Patrick Woolsey
<pwoo...@barebones.com> wrote:
>We are still working on this, and will have a future version of Yojimbo
>with iCloud support prior to the MobileMe sunset date (of Jun 30, 2012).
On 19/03/12 at 8:43 AM -0400, Patrick Woolsey
<pwoo...@barebones.com> wrote:
>As of today I can only say with surety what I have before, i.e. that we
>will have a version of Yojimbo with iCloud support ready prior to the
>MobileMe sunset date (of Jun 30, 2012).
If pressed, I bet someone could get Patrick to repeat himself
(again). Personally, I think his time is better spent with the codebase.
I don't use MobileMe or iCloud (as I am on Snow Leopard). I sync Yojimbo to my iPad using wifi. Does this sunset thing affect users like me or only MobileMe users?
Shaun
We regret that we will not have iCloud support ready in time for the MobileMe shutoff. The technical issues of the last few days will take a bit longer to resolve, and test. These issues can be worked around; and we are working as hard as we can. Nonetheless, it will take time to implement and test the necessary changes; and to ensure that our support for iCloud meets the standard that our customers have come to expect from us.
The amount of time required is more than remains before Apple turns off MobileMe; and we think you need to know this now.
Please note that Yojimbo will continue to work except for syncing between multiple Macs. When the new release is ready, once you have installed it, your changes will resynchronize using iCloud.
We apologize for the inconvenience these delays are causing, and we know they make your work harder. Thanks again for your continued patience and understanding while we get this job done.
Well, given Apple’s lack of timely communication in many regards with their development community, and the general economy, it’s not too surprising and at least they are offering to make sure that when the syncing starts up again they will resync.