Svend Erix wrote:
> My application may consist og 100Kb code and 800 Kb Database content.
> If I include a datafile with the 800Kb data and import it into an
> SQLite database under the initial run of the applcation, I cannot
> delete the data file afterwards and my application will take up 800 Kb
Thanks for the clear answer - yes the restriction mentioned is
important to me :-)
On Jan 22, 1:52 am, Mark Murphy wrote:
> Svend Erix wrote:
> > My application may consist og 100Kb code and 800 Kb Database content.
> > If I include a datafile with the 800Kb data and import it into an
> > SQLit
Even if you had the import feature, the user would still need to get
the 800k data...from somewhere either online or from the device?
Sorry if I did not understand your problem...
On Jan 22, 6:59 am, Svend Erix wrote:
> Thanks for the clear answer - yes the restriction mentioned is
> important
Not the best solution, but may save your users some memory:
Have 2 versions of the software, one with the database and
one without. After the database is installed, have the user
download the new version wothout the database. You could have a menu
item in the large application that downloads the
It is important that the application is fully functioning imeediately
after download. The user should not need to do anything further to use
it - so no second downloads.
On Jan 22, 8:40 pm, "info.sktechnol...@gmail.com"
wrote:
> Not the best solution, but may save your users some memory:
> Have
I just got an idea: Anyone know if and how the following could be
done:
Can I create the SQLite DB (a single SQLite file) and then include it
in my APK and connect to it? - or is the SQLite DBs in an android
application shielded from such a solution.
On Jan 22, 1:52 am, Mark Murphy wrote:
> Sve
I'm not sure I understand your problem. You have 100K app code and
800K initialization data - that's below 1 MB. If the app is worth it I
don't see any user would complain about your app's size. Most
(non-trivial) games will be bigger than that.
Cheers,
Stoyan
On Thu, Jan 22, 2009 at 12:52 AM, S
1) it is a matter of principle - if we all take up twice as much space
as we needed, it would matter eventually
2) I would like the user to download more applications of this type of
mine :-) Depending on the type of user (and on my succes), the user
may choose to download and use more than ten of
OK, I found a thread dealing with this option ("Including SQLite
database with application")
On Jan 22, 10:37 pm, Svend Erix wrote:
> I just got an idea: Anyone know if and how the following could be
> done:
>
> Can I create the SQLite DB (a single SQLite file) and then include it
> in my APK an
How about a link to the thread, so other people who having same
problem can read the solution too?
On Jan 22, 11:32 pm, Svend Erix wrote:
> OK, I found a thread dealing with this option ("Including SQLite
> database with application")
>
--~--~-~--~~~---~--~~
You
Sorry, Odessa.
I tried to include a link, but I don't know how to do that. So I just
specified the thraed's title in brackets ("Including SQLite database
with application")
The full URL is:
http://groups.google.com/group/android-developers/browse_frm/thread/72c189caaed48c/a7a4fa964ba36f92?hl=en&l
HA :-)
Ok I see now :-)
On Jan 23, 10:51 pm, Svend Erix wrote:
> Sorry, Odessa.
> I tried to include a link, but I don't know how to do that. So I just
> specified the thraed's title in brackets ("Including SQLite database
> with application")
>
> The full URL
> is:http://groups.google.com/grou
On Jan 22, 1:31 pm, Svend Erix wrote:
> It is important that the application is fully functioning imeediately
> after download. The user should not need to do anything further to use
> it - so no second downloads.
>
Why don't you download and then execute the .sql file from a file
server w
13 matches
Mail list logo
