In article <slrnmaa9rp.2ff.empty.bu...@Ferrycy.localdomain>,
empty-buffers <
empty.buffersYO...@gmail.NEITHER-THIS.com> wrote:
>In comp.lang.forth,
visua...@rocketmail.com wrote:
>
>> Additional answer: There is a chance to be a pioneer!
>> I waited ten years for a VisualFORTH. Nothing happened. So I did it myself.
>> You are asking for access to "native" Windows' widgets?
>
>"Native" widgets are the ones provided by OS (and his environment) - and
>which are not built by the "tool" (VisualFORTH in this case).
Actually most Forths on MS-Windows can use DLL's. The only requirement is
that you have the documentation in detail (which requires that the size of
fields within structs are known by their byte count.).
Those spec's are partly in c-type include file and some Forths
do a good job interpreting those files.
If you've the documentation and perseverance, you can use all DLL's
from a simplistic Forth like wina, with only the words
LOAD-DLL DLL-ADDRESS ICALL CALL
and maybe one screen of auxiliary words.
(I was surprised to find this out. It is actually easier than using
shared object libraries -- .so -- in linux).
>
>> Don't wait!
>> Take the chance!
>> Be a pioneer!
>> [..]
>> So, don't be shy. I am sure, it can be done.
>> One more step into the future.
>
>The problem is I'm Linux user (since 1994; since about 2005 almost
>exclusively), and I rather seldom use Windows. That's why I was hoping for
>"something ready to use".
It may be much simpler than you expect.
>--
>May the Forth be with you!