>> It might not suck to have an optional API launch code such as 'choose link
>> target' so that one app, to create a link, could offer a 'link object' menu
>> choice, which would first list all apps which are 'linkable' then upon
>> choosing one, that app would be launched with a sub-launch and show a pick
>> list of items. Upon choosing the item, the original app would just plop in
>> the link. It makes for a more seamless user experience.
>>
>
>This would make things more seamless for the user, but it raises a lot of
>development issues. First and foremost, it means that adding
>'linkability' is a
>much more complicated task. Linking has to be simple enough that a
>sufficiently
>large number of apps will implement it, or else it is of little value.
>This idea
>could require changes to the UI of the program. If it is implemented as a
>sub-launch, then the second app would have much less memory than usual,
>which is
>quite likely to cause problems. If it is not implemented as a sub-launch,
>then
>the id of the calling app must be stored somewhere so the second app can
>return to
>it. The calling app would also have to save additional state so that it can
>process the link.
Well, that's true, but it would be an OPTIONAL thing for a given program...
it was just an idea. There's no reason the API shouldn't support it.
Alan
