[whpalmer4]

Originally Posted by c.nick

I can't understand why people keep discribing all sorts of WORKAROUNDS to cope with missing features of the product. After all we love our OmniGroup products because they offer great FUNCTIONALITY instead of the hassle with workarounds in the first place.

Because most of us don't have the ability to make changes to Omni's source code to implement that functionality, and yet are interested in using the product, we do what we can — discuss workarounds, and encourage others to send in feedback requesting changes.

I'm sure most of us figure out their own workarounds for whatever they feel missing on the feature list so far.

And yet, there are numerous posts asking "how do I do X?" and often only small differences in X change the answer from a matter of describing how a feature works to suggesting a workaround. Allow me to apologize for the many posters who thought they may have missed something while learning the program and didn't realize they would pollute the purity of the forum experience by talking about workarounds rather than page numbers where the answer could be found!

Heaven forbid anyone should be interested in learning how to approximate some desired functionality with the resources at hand while waiting for Omni to deliver a native version.

I engage here not to discuss workarounds but to find the leanest and meanest possible ways how to implement and enhance features.

If I wanted to discuss all the needs and possibilities of workarounds over workarounds of workarounds I'd have more food for thought on the Things forums ;-)

As long as we are here, let's hear some of your ideas for lean and mean ways to implement richer repeat options. Can you offer any improvements on iCal's custom repeats? Any unusual repeat patterns that you would like supported?