[Ken Case]

Originally Posted by whpalmer4

Okay, just a word of caution -- the stuff contained by the "No Context" bin is NOT filtered by the view bar settings, despite what my previous message suggested.

This has been fixed for v1.6: the action filters now apply to the "No Context" list, and actions can now become available whether or not they have a context.

(By the way, we'd love to start sharing daily sneaky peeks of v1.6. But first we have to release a new version of the iPhone app which can handle syncing with 1.6. And since we can't release sneaky peeks builds of the iPhone app, we have to make sure that work is stable.)

[whpalmer4]

Originally Posted by Ken Case

This has been fixed for v1.6: the action filters now apply to the "No Context" list, and actions can now become available whether or not they have a context.

(By the way, we'd love to start sharing daily sneaky peeks of v1.6. But first we have to release a new version of the iPhone app which can handle syncing with 1.6. And since we can't release sneaky peeks builds of the iPhone app, we have to make sure that work is stable.)

Interesting -- can you characterize what changed about the sync protocol?

Nice to see you taking care of the people who cannot bring themselves to use contexts, even though I cannot fathom doing not using contexts with a workload large enough to spur one to use a powerful task management tool....

Do the action filters now also apply to the Inbox?

[Ken Case]

Originally Posted by whpalmer4

Interesting -- can you characterize what changed about the sync protocol?

The protocol itself hasn't changed, but we want the iPhone app to understand the changes to the data model (such as the new "autocomplete when children are complete" setting on projects and groups).

Do the action filters now also apply to the Inbox?

Yes.

[whpalmer4]

I think you can expect a rising chorus of "is it ready yet?" "can we get the sneaky peek now?" "how about now, is it ready yet?" with answers like those :-)

[curt.clifton]

Originally Posted by Ken Case

(such as the new "autocomplete when children are complete" setting on projects and groups).

Sneaking in that hotly debated feature in a parenthetical?

Woot! This is a true best-of-both-worlds solution to challenging design question from the good old original sneaky peek days. Can't wait to put it to good use.

[Obyor]

Hopefully, metadata columns are coming in v1.6 too :-)

As I recently mentioned in the Tags thread, our plan all along has been to allow people to create their own columns of metadata, which they can use however they want: with generic tags, or with specific columns for priority, people, etc. (We have this capability in OmniPlan, OmniOutliner, and OmniGraffle.) We just didn't have time to do it for 1.0, and we won't for 1.1 (which has to focus on synchronization so it can be ready to synchronize with the iPhone).

Hopefully in 1.6.

http://forums.omnigroup.com/showpost...&postcount=155

[pinky]

Here are some things to concentrate on in version 1.6:

From version 1.0- still unable to drag simple documents into OF without them loosing their name. One year on and still waiting.

The whole style preferences is just infuriating. For example it works some of the time and then not at all.

Omnifocus, as far as I'm concerned, has been a HUGE disappointment because of these two issues. Tech support say it's on the list but guess what-I DON'T HAVE AN IPHONE! So while you have been doing all that development some very basic things have still not been fixed.

Any chance of a refund if you don't fix these issues in say 3 months time?

[Greg Jones]

Originally Posted by Ken Case

(By the way, we'd love to start sharing daily sneaky peeks of v1.6. But first we have to release a new version of the iPhone app which can handle syncing with 1.6. And since we can't release sneaky peeks builds of the iPhone app, we have to make sure that work is stable.)

My question is not OF-specific, but I've been curious as to how developers of iPhone applications are required to handle betas of their programs. Is there no provision to allow developers to beta test an application externally, short of providing the program to users with a jail broken phone (which probably violates Apple's guidelines)?

[JKT]

Originally Posted by Greg Jones

Is there no provision to allow developers to beta test an application externally, short of providing the program to users with a jail broken phone (which probably violates Apple's guidelines)?

That wouldn't even be proper beta testing - gaol broken phones are not the same as default ones and are very prone to crashing where a non-gaol-broken one isn't (due in part to people running more than one app at a time). A good proportion of the "this app sucks because it crashes all the time" reviews on the App store are from gaol breakers for this very reason.

[sfkeydel]

Developers are able to provision their apps to beta testers who are using non-jail/gaol-broken phones, so it's a moot point. Regardless, it's the Omni Group's prerogative as to how they beta test their apps, and they clearly do so, whether it's in-house or via provisioning.