OpenGL Or Win32 Api
-
We are developing an application for process modelling. The end users require a Visio like tool for modelling. Which is the way to go Win32 Api or OpenGl or something else. The intial version will have very little modelling features, but it is expected that we might add lot more. Thanks
-
We are developing an application for process modelling. The end users require a Visio like tool for modelling. Which is the way to go Win32 Api or OpenGl or something else. The intial version will have very little modelling features, but it is expected that we might add lot more. Thanks
It depends on what you want to display really. If you need to draw in 3 dimensions, you have a choice between Direct3D (COM based) or OpenGL (procedural). Either will quite happily do the job, although MS are naturally pushing Direct3D rather than OpenGL. If you only need 2D views, you have a choice between DirectDraw (COM based), GDI or GDI+. Which is best for you will depend upon speed, platform and flexibility:
- DirectDraw can be hardware accelerated but has a limited implementation on NT (and probably Win95) - it's only well supported on Win98, Win2k and WinXP. DirectDraw has a lot in common with Direct3D, which could be useful if you have to do both.
- GDI is a pain. I'd avoid it if at all possible, unless you have a good reason to use it.
- GDI+ is promising - it's easier and more flexible than GDI, but with an easier learning curve than DirectDraw. However, it isn't hardware accelerated (yet!) and requires you to redistribute the installer with your app. It will work on all 32 bit flavours of Windows (except Win95) though.
Your best bet is probably to write some demo apps and see which suits your product. Good luck. :) Andy Metcalfe - Sonardyne International Ltd
Trouble with resource IDs? Try the Resource ID Organiser Add-In for Visual C++ 5.0/6.0
"I'm just another 'S' bend in the internet. A ton of stuff goes through my system, and some of the hairer, stickier and lumpier stuff sticks." - Chris Maunder (I just couldn't let that one past ;)) -
It depends on what you want to display really. If you need to draw in 3 dimensions, you have a choice between Direct3D (COM based) or OpenGL (procedural). Either will quite happily do the job, although MS are naturally pushing Direct3D rather than OpenGL. If you only need 2D views, you have a choice between DirectDraw (COM based), GDI or GDI+. Which is best for you will depend upon speed, platform and flexibility:
- DirectDraw can be hardware accelerated but has a limited implementation on NT (and probably Win95) - it's only well supported on Win98, Win2k and WinXP. DirectDraw has a lot in common with Direct3D, which could be useful if you have to do both.
- GDI is a pain. I'd avoid it if at all possible, unless you have a good reason to use it.
- GDI+ is promising - it's easier and more flexible than GDI, but with an easier learning curve than DirectDraw. However, it isn't hardware accelerated (yet!) and requires you to redistribute the installer with your app. It will work on all 32 bit flavours of Windows (except Win95) though.
Your best bet is probably to write some demo apps and see which suits your product. Good luck. :) Andy Metcalfe - Sonardyne International Ltd
Trouble with resource IDs? Try the Resource ID Organiser Add-In for Visual C++ 5.0/6.0
"I'm just another 'S' bend in the internet. A ton of stuff goes through my system, and some of the hairer, stickier and lumpier stuff sticks." - Chris Maunder (I just couldn't let that one past ;))1. You can use OpenGL for 2D graphics, although it's not really meant for that. It's probably better to use that than use straight GDI. 2. It depends on your target OS. If you have any Windows NT 4.0 users, forget Direct3D, becuase AFAIK, it is not supported on NT. 9X, 2000, and beyond, though, I believe are OK. The early bird may get the worm, but the second mouse gets the cheese.