Well ginge, personally I really love COM, I'm just thinking about all the others
. There's a big difference between telling people that they can do scritps and telling people that for most stuff they'll have to create COM objects. Also, I disagree with the idea of two different versions, it would make scripts useless for most people.
I hope there will be a mximum number of posts today about this matter, I can't develop anything until we've decided somthing final on this important question. Also, I think that some of you didn't understood the problem correctly.... my firs goal was to move most of my built-in features (QuickTexts, loggin, different text transformations, etc...) into scripts. Now that I see the limitations, I'm not sure I want to do that anymore. Of course, I could do as ginge says and create COM objects (for those who do not know really what it means... it's ActiveX, or any kind of object you generally use in VB). If I do that, however, the script will contain pratically nothing except for an object creation and a mthod call, as all the code will be encapsulated in the COM object itself. So... what's the point? If I do that, I'd better expose com COM interfaces directly so that people can interact with them using VB, as they already do with Messenger itself.
Waiting for your posts and ideas,
Patchou.