> > any pointers on creating this "self-extracting" archive? I still need to
> > support < 3.5.
>
> It's an idea that's been floating around for a while on this forum - check
> the archives. I was going to say that the implementation was left as an
> exercise for the reader. :) Ideally, the self-extracting archive should
> gradually delete itself as it expands. You shouldn't need twice as much free
> memory as the data actually consumes. This is one of the tricky parts.
> Another trick is deleting the final "stub" when you're all done - how do you
> delete yourself? Fun, fun!
>
I have searched the archives... but havent really gained any insight ;) I
just need a point in the right direction I think. how can a palm
application create another palm application (the sefl extracting part) on
the fly? or, if I create a new database, dump all of my other databses
into it, and then beam that over, how does the receiving palm 'know' to
'run' it? I'm grasping here...
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
