Drowning in email? Try Inbox Zero to learn sane tips for dealing with high-volume email. And don’t miss the free Inbox Zero video. »
Register for free on 43 Folders to comment on articles, post to our forum, customize your visits, and much more. Current users can login now.
OmniOutliner3, Omnishadow and Shadow on palm - help please
joej | Feb 14 2007
I am trying to get Omnioutliner to export my outlines to ShadowPlan on my palm. I installed Omnishadow and all went well. I am using Omnioutliner3 Pro (demo) since the non-Pro version is what came on my Mac and I read the Pro version is needed. When I have an OO outline open in front of me, I go to the applescript menu, select the "Shadow-Plan Save" option to try to export the outline and nothing happens except for a tone sounds. I look and there is no file in the "Files to Install" directory of the Palm user directory. In fact, I cannot find a file of the name of the OO file anywhere except for the original. No pdb, xml, or other file is exported anywhere. I emailed the author of Omnishadow but have had no reply to date (and he is clear that the scripts are not necessarily supported). I verified the Omnishadow prefs 3x. Questions: -Does OO3 Pro need to be registered for this to work? Any ideas? Thanks very much... 3 Comments
POSTED IN:
Sorry to see you haven't...Submitted by yucca on February 17, 2007 - 5:37pm.
Sorry to see you haven't gotten a useful reply. I can't help you with your exact requirements, but I do have question. Have you considered going the OO3 (with KGTD) <-> iCal <-> Palm'sTasks app sync route? It works for me, but I did have to do some troubleshooting a few years ago to get the sync between iCal and Palm Tasks to work. Of course, I don't actually want to do planning on my Palm . . . so this might not be much of an option for you. Hope this at least gives you an option if you don't get anything concrete re: Omnishadow and ShadowPlan. Good luck, and do let us know how things go! » POSTED IN:
Error converting Shadow XMl to pdbSubmitted by writerati on March 25, 2007 - 5:11pm.
Hi JoeJ-- joej;8144 wrote:
In my experience, that's exactly what you have to do. I haven't used OmniShadow in a while, but I do remember that the "Shadow Plan Save" option didn't work for me. I saved as Shadow XML, opened in Shadow Desktop, and it worked fine. The error (I think) has to do with a bug when Shadow Desktop converts an XML file to a .pdb. In my command-line tests, if I converted a file using
and then hotsynced the pdb file, I got an error in HotSync Manager. However, if I opened the same XML file in Shadow Desktop and manually saved as a .pdb, it worked fine. I was able to sync the file without issues. OmniShadow tries to run the same -xlate converstion, so that *might* be where the problem lies. Try saving as XML and then converting it manually, and see if that works. » POSTED IN:
hold on a second...Submitted by writerati on April 15, 2007 - 8:28am.
I just had a thought... Apparently some people (like me) are having this problem with the OmniShadow "Save" function, while others say it works fine. JoeJ: Is your copy of Shadow Desktop registered? Mine isn't, and I'm getting the error. I wonder if this would work if I were using a registered copy? The OmniShadow home page states that the script "requires you to have a licensed copy of the Shadow Desktop for part of the background conversion." That might be our problem. Can anyone confirm this? Forgive me if I'm hesitant to slap down some $ to register and test this theory. =) » POSTED IN:
About joej |
|
| EXPLORE 43Folders | THE GOOD STUFF |