> how about putting it in the .prc compressed and you extract into a > .pdb or onto the VFS card upon installation; based on a user option? > you can detect if VFS is present, and, ask - and, if it isn't, > just create the file stream (dont need hostcontrol then)
That's clever. That may be the way to go about it. Then toast the resource(s) from the .prc > for what it is worth, using VFS direct and palm filestream databases > renders little different in performance in regards to accessing the > data stored within a file :) we did a number of tests, accessing > a .mpg file on a sony clie for playback with both techniques.. maybe > 2-3% difference (faster in ram) Not really worreid about performance so much as size in this case. > how big is this .gam file? is it feasible to have an installer which > generates it as appropriate? Probably in the neighborhood of 512k...which is obviously why we want it on VFS as possible. I'm not too hot on the idea of doing it at install time because it still doesn't solve the issue of actually *getting* it on to the card. Can someone enlighten me on this point? My only VFS device is a Clie, so I can use Sony's MS Import utility to move files around. But, how does it work for the SD-enabled Palms? Assuming a file extension hasn't been registered on the Palm side, there's no way to just put a file on a card form Hotsync, right? Combine that with my lack of Mac-installer experience and I think this is a problem best solved elsewhere. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
