View Single Post
Old 06-18-2008, 04:32 PM   #100
=X=
Wizard
=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.
 
=X='s Avatar
 
Posts: 3,671
Karma: 12205348
Join Date: Mar 2008
Device: Galaxy S, Nook w/CM7
Quote:
Originally Posted by lisak View Post
Well, at the moment I have to have dictionary itself in the internal memory of the Reader - it's the only way I can access it from the internal shell so far. And if it's really a fact that reading from the card drains battery, it would be probably wiser to let it stay there. Some installer would be probably possible, though (eg. copy everything onto card and move dictionaries to the internal memory at the first start) but I am still wondering whether it's worth the effort, especially when we're able to help people with installation problems here in forum.
Ops the complete thought was in my head I just forgot to write it all down.

My thought is during the loading of the program, all files that must reside on the internal memory are "Installed" (e.g. copied) during to the internal memory. This would make this process invisible to the user. They would just notice a large load time for the very first time they run the program.

We can minimize the load time by performing a "file exist" (getFileInfo) check for each file. Or write a flag to a file when the a successful install was completed therefore we write a true flag. Then check for the flag.

Last edited by =X=; 06-18-2008 at 04:36 PM.
=X= is offline   Reply With Quote