It's easier because someone implemented WINAPI and PRINTDLG classes before. You can do the same in Squeak. If you have too much time, that is.
Yes - I would like to see a WINAPI keyword (and a MACAPI, UNIXAPI, ...) in Squeak. It is true that the PRINTDLG Structure is predefined. But MT has a structure generator for easy defining an appropriate structure class. The only thing you have to do is to copy and paste the C structure from the MSDN documentation and run the generator.
Another thing I like is that the MT image wont crash if an API is called with a wrong parameter. (you get an Unhandled Exception then)
And it is easier because MT knows imported lib's so you dont have to write down the lib if you call an API. (But it's posssible to specify one if there are naming conflicts)
The only thing I disklike on MT is that I can rotate Win32 windows ;)
bye Torsten
On Fri, 30 Jun 2000 Torsten.Bergmann@phaidros.com wrote:
It's easier because someone implemented WINAPI and PRINTDLG classes before. You can do the same in Squeak. If you have too much time, that is.
Yes - I would like to see a WINAPI keyword (and a MACAPI, UNIXAPI, ...) in Squeak.
Go ahead, write one ;-) Still, I'd guess WINAPI is no keyword but a class in MT.
It is true that the PRINTDLG Structure is predefined. But MT has a structure generator for easy defining an appropriate structure class. The only thing you have to do is to copy and paste the C structure from the MSDN documentation and run the generator.
That's easy in Squeak, too. Just write a C struct parser that creates the field def array.
The only thing I disklike on MT is that I can rotate Win32 windows ;)
By turning your monitor upside down ;-)
-- Bert
squeak-dev@lists.squeakfoundation.org