Daniel McCarty wrote:
>
> What about using something similar to the
> sysAppLaunchCmdPanelCalledFromApp and sysAppLaunchCmdReturnFromPanel
> launch codes? To make this a "seamless" user experience, as someone
> else said, it would probably be best if the called application
> provided a "Done" button that would take the user back to the calling
> app.
> In essence, this is a type of *puke* OLE for Palm devices.
My apologies,
My mailer sent out this half-finished letter before I was done.
What I was trying to say wasn't that I didn't like the idea--which
I do--but that this sort of reminds me of OLE for Windows.
Anyway, that's not the point I was trying to make, which is
that this idea will only catch on if it's as simple as possible
for the end-user. I think C.E. has made this clear.
The idea of a "LinkMaster" isn't a bad one. Bringing a third-
party into the communication between two apps would solve some
of the clean up problems and also eliminate the need for duplicated
code in every app that wants to support record linking. I think it's
important that if someone were to create an app like this (or if
someone already is), the app should be 1) free and 2) open source.
This way no one person would control the app, and we wouldn't be stuck
on version 0.9 for 2 years. <g>
(BTW, Ben, bringing a third application into this would eliminate
the need for both a shared library _and_ take care of the problem of
broadcasting launch codes. Your "gut feeling" is evident in the "Set
Time" and "Set Date" actions that take so long on a device that
has any third-party apps on it, because of the system-wide launch-
code broadcast they do.)
Regards,
Daniel.
