I'm way behind on my e-mail due to a business trip,
but I've scanned the responses to this and haven't
seen either the concept of a runtime engine or the
concept of shared libraries mentioned.
A runtime engine would be something like cBaspad
or PocketC or Waba. The apps would be "data" to
the interpreter.
A shared library is a resource database with a
known entry point. Take a look at the concept
of "Desk Accessory" and the DA launchers. Right
now they all use their own creator code and a "type"
of "DAcc" but it should be possible to invert
the relationship and use a common creator "Aplt"
and different "type" to distinguish among them. There
is nothing magic about the type of "DAcc" except
that DA launchers recognize them. Your Applet Launcher
could recognize resource databases w/ the creator
code of "Aplt" and any type code other than "appl"
(which would be the type code of your launcher).
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Tim Hewitt [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 16, 1999 4:17 PM
> To: [EMAIL PROTECTED]
> Subject: "Running" a database entry
>
>
> I have an interesting, though somewhat academic question.
>
> Is it possible to write an application that is not loaded as
> an application, but
> rather is stored as a database entry on the Palm, then when
> selected by a "host"
> application, the "database-based" application runs? When it
> finishes, it would
> launch the parent application with a custom launch code and
> the user would be
> returned to where they started - sort of.
>
> The problem I'm trying to solve is one of having hundreds of
> "applets" available
> to be run on the Palm at one time. These programs are very
> small, and there are
> potentially 1000's of them. It would be a shame to burn up
> 1000 creator ids for
> these guys, yet I am intrigued by the idea of having each one
> a totally self
> contained program.
>
> I'd tell you what I have in mind for them to do, but then I'd
> have to kill you :).
>
> -Tim
> --
> Tim Hewitt
> Principal Software Engineer
> Fairchild Semiconductor
>
