🚀 go-pugleaf

"Peter Below (TeamB)" <100113.1101@compuXXserve.com> wrote in message
news:VA.0000a8f6.0011729e@nomail.please...
> Actually the question fits in neither of these groups.

I do appologise. OpenToolsApi was my best guess, NativeApi was my mistake.

> What you need is a
> run-time interpreter for Delphi code. There are a number of scripting
support
> suites for Delphi you may want to look at.
>
>   Innerfuse Pascal Script (freeware): http://www.carlo-kok.com/ifs.php
>   Delphi Web Script (freeware): http://www.dwscript.com/
>   http://www.dreamcompany.com/ (commercial))
>   http.//www.vkarlsen.no/lvk
>   http://www.passcript.com/ (TPasScript))
>   http://www.gemini2k.com/sparksoft/

I'll check each of these. Thank you very much. Someone in OpenToolsApi
pointed out Delphi Web Script and I've already checked that one.

Delphi Web Script
- is a language that comes close to Delphi's ObjectPascal. But it isn't
entirely that same though.
- is missing an IDE. Or, more correctly, it's missing *the* IDE. One good
reason to interface with Delphi for this 'for applications' stuff is that
there's already a number of people, like myself, who really love the
language and the exact IDE, and who have extended it with wizards,
opentoolsapi usage, components, etc. So even if something like Delphi Web
Script would be extended with a Delphi IDE clone, it would still not be
*the* environment the Delphi programmer has build for himself through years
of writing and installing packages and such.
- apart from that, writing a good 'for application' specific IDE may be
feasable for a company like Borland or such, but I'm like just me or such.

I haven't yet checked out the other solutions you pointed out, and I will.
And it could go part of the way and get build to be a good solution,
probably... But do you consider it completely unfeasable to actually use
true original Delphi for this? I was thinking along the lines of
- storing macro's and hand-written 'procedures for applications' in a DLL
project linked with precompiled units that, amongst others, contain a
special flavor of 'DLLInitByHost' for passing pointers to what the host
exposes and such so that the precompiled units in turn can expose an
object-model of the host data to the macro code
- tracing through macro's and 'Delphi for applications' code could perhaps
be done by using opentoolsapi to mark breakpoints in that macro code,
attaching Delphi as a debugger to the host app, and running the macro from
the host app next, thus popping up the Delphi debugger.

Do you consider such a path remotely feasable or should I abort that
thinking?


Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be