Re: Need help understanding desktop/handheld relationship
"Mark Einersen" <[email protected]>
| Newsgroups | gmane.comp.handhelds.palm.shadow |
|---|---|
| Message-ID | <[email protected]> |
Thanks for your reply, Jeff. Just to make sure I understand correctly... 1. I could keep all my outlines on a memory card on the HH side. Then when I want to edit them I could simply insert the card into my PC and "Open raw..." directly from the card? I guess the only disadvantage of this scenario is that I would NOT be able to categorize the outlines on the HH, correct? 2. When I look at the info in the Expert console, where should the index be looking? Can I change this path or is it automatically set? I see the following path descriptions: -Registration file path -Filter file path -Tag file path -Refreshing outline directory 3. Should the path that the index is looking for be the location where I store the corresponding files I have on my HH? If so, how do I make that the default location where they are stored upon sync (or at least how do I get the HH files to sync to the corresponding files in the DT directory)? 4. Theoretically, I should "Open..." the same directly that the index is looking for, right (at least on a "normal" basis)? Thanks again! This is very helpful. Mark --- In [email protected], Jeff Mitchell <skeezix@...> wrote: > > On Fri, 2 Jan 2009, Mark Einersen wrote: > > # 1. Am I correct that files on my memory card have NO ASSOCIATION > # whatsoever with what is backed up on and/or synced with the desktop? > > More-or-less correct; there was a time when I had planned to have > the desktop do some really tricky things so you could edit files on the > card after hotsync, but in the end.. devices started to get a lot of RAM, > Palm made the tricky stuff really buggy to pull off, and I added Open Raw > which would let you edit the card-side files directly (via a USB flash > reader say, or mounting the files via the Palm evice as a card reader, > etc.) > > So to sync it is easiest to keep files in RAM. > > # 3. On the DT my visual list of outlines shows 8 outlines, including a > # new one I created a couple weeks ago that appears to have been synced > # properly onto my HH. Yet when I choose "Open..." I see a list of 10 > # outlines (8 are the same as what I see on the DT UI, plus two others > # that I have previously used). Why? > > Could check the Exprt -> Console option and read through (its > cryptic) to see where it is looking.. essentially, the left-side index > shows from one directory the files it could find; the Open could be > looking in another place (it tries to remember the last palced you've > opened a file, and you could have opened somewhere else). > > The DT can open files anyplace on your computer, the trick is what > it is showing in the index and File -> Open. > > # 4. I have also created a "test" outline on the HH and upon sync it is > # not visible in EITHER of the aforementioned list of files. However, > # when I click on the last outline listed on the DT UI, it opens the > # "test" list--although it is an old outline with a totally different > # name!! What the heck? > > Simialr to (3). Theres probably a mixup of where it is seeing. > (Which could also be complicated by some of Vista's odd behaviours, if > you're using that OS.) > > # 5. When on choose "Open raw..." all I see are 3 files, all three of > # which are presently in internal memory on the HH (other files with > # corresponding names on the DT are presently on my HH memory card). > # When/why would I want to open/modify on the DT a "raw" file (PDB) vs. > # a "normal" file (XML)? > > Open Raw is provided for those who need it, but it is generally > not needed much for Windows users. (It is mostly used by Mac and Linux > users, or Windows folks who need to recover based on a pdb file, or who > want to edit on an SD card, or other crazy tricks :) Generally the XML > file is the way to go, but as always.. I like to provide tools so people > can work how they see fit. > > jeff > > -- > If everyone would put barbecue sauce on their food, there would be no war. >