… OKAY… we’re just testing the poll system in time for the popularity vote of the Widget Challenge.
Don’t take this poll too seriously.
But here it is anyway. Don’t complain about missing options – it’s just a test.
… OKAY… we’re just testing the poll system in time for the popularity vote of the Widget Challenge.
Don’t take this poll too seriously.
But here it is anyway. Don’t complain about missing options – it’s just a test.
I personally liked the WWW class, made online high scores really really easy!
Yes… my favourite too.
You forgot the “all of the above” option!
And “I don’t have a Mac, you insensitive clod”
:lol: :lol:
I voted for Windows publishing, but only narrowly over the WWW class, Davy’s scripting tutorial, and the docs. The Windows publishing won out for future potential. The WWW class is really nice and well done, but it, or some other class, still needs to be a little more comprehensive in some areas, IMO. Let me know if you need any ideas, especially if you ever plan on supporting services Davy’s tutorial is awesome, and the docs are much nicer now. I could have gone any of the 4 ways. The other choices are still well beyond me at this point.
Is there any information on the plug-in SDK?
Well, I guess that is a duh on my part Thanks.
Are the Objective-C plugins cross-platform, or only the C and C++? Or is Objective-C cross-platform only if you install GNUStep on the Windows machine.
No C++ plugin is cross platform by itself.
You always need to compile two plugins for it to work on windows / mac os x.
One “.bundle”, one “.dll”.
If you write straight C++ code it is easier to port it to windows.
But as soon as you do something with GUI, you will either have to write completely different code for the two platforms or use an available library to do it for you. Eg. QT or one of the various open source libraries.