1. RE: EuCOM 2.01
Matt Lewis wrote:
> Exciting news! I've updated EuCOM (fixed a couple of bugs related to
events
> and implemented interfaces) and added two new demos:
EXCELLENT work! I'm so glad that I can finally use web browsers in my
Euphoria applications! This has been on my wish list ever since I moved
from Visual Basic to Euphoria. Your browser demo is very clean and easy
to understand. Way to go!
Does this work with other Visual Basic custom controls?
~Tom
2. RE: EuCOM 2.01
> From: thomas at columbus.rr.com [mailto:thomas at columbus.rr.com]
> Matt Lewis wrote:
> > Exciting news! I've updated EuCOM (fixed a couple of bugs
> related to
> events
> > and implemented interfaces) and added two new demos:
>
> EXCELLENT work! I'm so glad that I can finally use web browsers in my
> Euphoria applications! This has been on my wish list ever
> since I moved
> from Visual Basic to Euphoria. Your browser demo is very
> clean and easy
> to understand. Way to go!
Thank you.
> Does this work with other Visual Basic custom controls?
"Visual Basic custom controls" are usually just ActiveX controls, so, yes,
it should. A word of caution, however: Every COM/ActiveX object I've
worked with has done things slightly differently (requiring named
parameters, hooking up event interfaces, etc), so it might not work "right
out of the box".
The challenge of building EuCOM has been that I don't have all the nice
supporting structure that C++ or VB have, and it's somewhat difficult to
figure out what's going on under the hood with some controls, so I've
written EuCOM as I've gone along, and each time I run into something new,
the lib gets a little more general and better able to handle diverse
circumstances.
If you're using an ActiveX control, it's probably enough to use tbrowse to
generate a wrapper for you (although you'll probably want the docs that came
with the control if it's very complicated). For other objects, you'll also
want the C/C++ .h header files or IDL (Interface Definition[?] Language)
files in order to hand wrap interfaces that aren't included in the typelib.
An example of this is for SAPI. For some reason, the default event
interface crashes after it's invoked. I was able to successfully use events
when using the IEventWhatever interface directly, however. Of course, this
is probably something to do with how EuCOM takes the call to invoke (or some
memory allocation problem), but I haven't been able to track it down yet.
Hmmm, that looks like something that should go into a FAQ. I think I'm
going to start building one, since there's a lot to EuCOM that's pretty
opaque, but might solve some people's problems pretty quickly if they
understood better.
Matt Lewis
3. RE: EuCOM 2.01
> From: Matthew Lewis [mailto:matthewwalkerlewis at YAHOO.COM]
<snip>
> Hmmm, that looks like something that should go into a FAQ. I
> think I'm
> going to start building one, since there's a lot to EuCOM
> that's pretty
> opaque, but might solve some people's problems pretty quickly if they
> understood better.
OK, I've started an 'official' EuCOM FAQ:
http://www14.brinkster.com/matthewlewis/eucom_faq.htm
Let me know what you think, or if you have other questions that should be
included.
Matt Lewis
