COM Automation in Classic99

[Willsy]

I thought this important enough to warrant it's own thread, not least to give Tursi a chance to see it.

 

So, here goes:

 

You know what would be nice?

 

COM automation in Classic99. (Probably not suitable for MESS, since MESS has to run in Linux too)

 

Classic99 could expose classes, methods, and properties allowing an external Windows program access into the TI's CPU memory, VDP memory, and GROM memory.

 

Thus, a program like grapefruit could *directly* drop an assembly language program into TI memory hosted by Classic99, and run it!

 

Something like (Visual Basic code):

Set TI=New Classic99.TI  ' get reference to TI top class
Set TMS9900=TI.Processor ' get reference to the Processor
Set CPUMem=TI.CPUMem     ' get reference to the CPU memory space
TMS9900.Halt             ' halt the processor
CPUMem.Dump(AddressOf MyProgramArray, A000h) ' drop executable code into the TI memory space
TMS9900.SetPC &A000h     ' point the program counter at our code
TMS9900.SetWP &8300h     ' set our workspace
TMS9900.Resume           ' classic99 is now running *our* code :-)

'release resources
Set CPUMem=Nothing
Set TMS9900=Nothing
Set TI=Nothing

 

How cool would THAT be? This would allow seamless interaction between an external Windows application, and Classic99 - and hence the "TI". For example, it would be possible to write an Assembler in Windows, and have it dump the assembled code into memory and run it in one click.

 

Nice.

 

I *think* COM is considered deprecated/legacy these days, but, there's so much COM out there that that shouldn't worry anyone. And the alternatives are ridiculous: SOAP/XML... Pah... If your transmitting data via the web, then ok. But internally, on the same box, COM is ok.

[sometimes99er]

I commented elsewhere, but would just like to say I find it interesting.

 

[+retroclouds]

Have you seen the openmsx emulator for MSX ?

 

From their specification list:

# Command interface via pipes or a (UNIX domain) socket: control openMSX with any external application

# Unique! TCL scripting: enhance openMSX with powerful scripts

# Unique! System ROMs are specified and found with their SHA1 sums or file names as a fall

 

They have some youtube videos up where they do crazy stuff with TCL scripts (add immortality, blend-in graphics, etc).

Something like that would be cool for the TI as well

[Tursi]

That's a neat idea. I haven't played with COM for about 8 years, setting it up really did kind of suck.

 

I wonder if things like messaging, named pipes, something like that might not be a better interface. Sure, it's not object oriented, but... (well, actually, that's all of it.) Also, the Bug99 interface is nearly done (Thierry and I hashed out some of the problems with the first release, I just need to finish implementing and testing the new one and let him know it's good to go).

[Opry99er]

Interesting thread.... I don't really quite understand how it all works, but I intend on doing a bit of research tonight after I finish up my coding for the evening.

[Willsy]

That's a neat idea. I haven't played with COM for about 8 years, setting it up really did kind of suck.

 

I wonder if things like messaging, named pipes, something like that might not be a better interface. Sure, it's not object oriented, but... (well, actually, that's all of it.) Also, the Bug99 interface is nearly done (Thierry and I hashed out some of the problems with the first release, I just need to finish implementing and testing the new one and let him know it's good to go).

 

The only issue with pipes is that they are not readily usable from languages that use COM (Visual Basic, .Net (through COM interop), Excel, Access, Even word!)

 

My preferences, if it were ever on the table would be:

1) COM

2) Sockets

3) Pipes

 

And yeah, I believe COM is a bitch to code for in C++, both on the client and server ends. Its a breeze in VB et al though, really nice.

 

Some system dependancies wuld be introduced: The com components (DLLs) would have to be registered in the reistry as ActiveX components, but there would be ni requirement for an installer: A simple batch file (calling RegSvr32.exe would do the job just fine).

 

Mark

[Willsy]

That's a neat idea. I haven't played with COM for about 8 years, setting it up really did kind of suck.

 

I wonder if things like messaging, named pipes, something like that might not be a better interface. Sure, it's not object oriented, but... (well, actually, that's all of it.) Also, the Bug99 interface is nearly done (Thierry and I hashed out some of the problems with the first release, I just need to finish implementing and testing the new one and let him know it's good to go).

Erm, whats the Bug99 interface?

[sometimes99er]

Erm, whats the Bug99 interface?

Have you read this/Do you know this one ? http://www.nouspikel.com/ti99/bug99.htm