On May 21, 9:49 pm, Roelf Toxopeus <these3rt0o...@[EMAIL PROTECTED]
>
wrote:
> Mmm, some rethinking.
> If I'm right in assuming you want to access functions from your
> turnkeyed MacForth from the outside.
Yep. I wish to do this as an intermediate step in my ****ting. Just
so I don't have to rewrite all the computational code as well as user
interface stuff. This makes it a shorter journey to getting an app
that uses the user interface widgets of OSX.
> I can think of 3 possible alternatives, all three needing a running
> MacForth, not necessarily in the foreground.
>
I have experimented with AppleEvents in this manner. In the test
another application was handling user interface interactions and I
wrote an add-on for that application (ArchiCAD) which would simply
send an AppleEvent message to my application running in the
background. This was really fast. As part of this test I also
****ted my app to windows using ProForth - well just the engine of the
app, so that used ANSI forth, and so the code was mostly unchanged.
The part that needed complete rewriting was the message despatching
which on Windows used DDE.
But I was hoping for a way that didn't need MacForth app to be
running.
I will try to understand better your suggestion for the intermediate
shared bundle. Forgive me for my slowness, I'll need to tinker with
this to understand it.
back later
Chris
|
