On Sun, Mar 10, 2002 at 12:55:39AM -0700, Cliff L. Biffle wrote: > Before I start the reply process, I have some patches for coldsync 2.2.5 that > allow my Clie to sync all PDBs (for some reason, PRCs will sometimes work, > sometimes not). I don't remember if you were having trouble or not, but the > patch dramatically decreases the amount of link traffic during a sync (my > estimates are 16-32 bytes per DB during the listing process, which can be as > high as 20%) and thus might make your syncing experience faster.
Hmm.. Honustly, with my S320, I don't have any problem in syncing whatsover, and overall its fairly fast... can you direct me where I can pick up the patches though, so I can try them out? > Works great; jogdial is quite nice to have at the Library screen. I'd love > to have more control over the action of the jog dial, though. Scrolling half > a screen is too much for my poor brain to follow; three or four lines would > make continuity easier. Hmm. That would be nice.. the only problem is that the way how its setup. Its a bad UI method (imo) to have seperate options for, 1 one down, 1 line up, 2 lines down, 2 lines up, 3 lines down, 3 lines up.. etc etc. Instead it would be better to have another field there for the numerical value and multiply that by the function. The problem with that though is that not every option can make use of a numerical multiplicator, as well making that intuitive to the commoners would be a nightmare. > > Remember, test out jogdial support from the library page. Back doesn't do > > anything, but up/down/push/etc should browse your file list. > > Yup. Back should exit to the launcher, imho. I finally went and got the > Sony SDK, so I know how to do that! :-) Cool.. If you can make a patch for the sony branch, i'll be able to send it up to the cvs. > > Also try > > removing your memory stick with plucker running, it should dump back to > > your docs list and rebuild the listing. > > Yup, no crash. Nicely done. Is that a Notification Manager trick? > Several programs (gMovie comes to mind) can behave quite badly when surprised > by the loss of their mounted device. Kind of... Basically its saying, "If you ever notice anything in the external memory change, let me know and I can take care of it", and all its doing is going back to frmLibrary, and re-building a list of docs. > I've figured out what it is about the rendering that feels slow: the > rendering engine goes and fetches every image on a page as it comes to them, > rather than when they come into view. Depending on how it's doing that, that > can be a considerable speed hit (VFSMark suggests that database import/export Hmm.. I do know is that it hasn't really been optimized much in the way of image displaying, but what you're saying would make sence to speed things, up. I havn't really played with this area much so I cannot really offer much advice. I want to tackle hi-res support under the Clie next. > is MUCH slower on the Clie than it should be, while file-mode reads and seeks > are acceptably fast). It reminds me of the original Mosaic, which did the > same damn thing (and was why I switched to Netscape in the first place). > The solution, as I see it, is to store some 'hints' in the page at > compile-time. The width and height of the image would probably be > sufficient; the height might well be enough (since images don't seem to be I would agree... then as the image actually comes into view, it would grab it from memory and display it within that 'box' > able to be in-lined with text). The the rendering image would only go and > fetch images when they were on screen or very near to it. (Or, optionally, > images could be turned off, like I used to do over dialup, and a little > placeholder box would be left that could be tapped to display the image.) > I'm making a couple of assumptions with this tirade, of course: > --Images are in separate records or resources than the actual page text (I > think this is safe) Which is true. > --Width/height are not stored already. You know, im not 100% sure of that one. You might want to check the plucker specs. > (If they -are- stored, they should be being used! :-) > I guess this should really be posted to a mailing list instead of rambled > about in private, but perhaps you might have insights into this before I > publically embarass myself. :-) Too late, I'm already CCing the list :) -- Adam McDaniel Array Networks Calgary, AB, Canada
