How to start with Visual studio 2005(VC 8) with OCC6.2

Hi everybody,
i have downloded OCC6.2 knowing that it now supports microsoft visual studio 2005. but i dont know how to begin with..

Previously it was easy in VC 6 just to add .awx file to a specific (template) folder. But what to do in case of vc8. because the folder names and files are very much different than incase of vc6..

so can any body just tell me how to add the OCC wizard in vc 8 (2005) so that i can try out something

bhimesh

bhimesh's picture

please any one tell that how to begin with Visual studio 2005 without VC++ 6.0

P Dolbey's picture

I can see you're struggling with this one so I'll throw in my 3 ha'pence and let others in. If you haven't already done this, I suggest you recompile all the OCC code under VS2005 - the 7.1 projects under version 6.2 migrate easily. The only major gothca is the DRAWEXE.exe for which you need a separate Tcl/tk distro, such as ActiveSte. However when I use the batch builder I leave this out as I never use it. I would also recommend you apply the simple patch described in http://www.opencascade.org/org/forum/thread_11016/ in Jan's update on 2007-04-18. Re-compile all the examples in VS2005 as well - there's a single sln file to help you with this.

The version 6.0 awx wizard files are pretty useless these days as Nair commented in another thread ( see http://www.opencascade.org/org/forum/thread_11234/ ). But assuming you want to remain decicated to MFC, you have 2 possibilities for going forward.

1. If you're just exploring some of the features of OCC, take a copy of one the samples which is closest to your needs, copy it into a new folder and use that as your starting point.

2. If you want to see the code emitted from the old wizards, then run them under VC 6.0 and migrate the projects to VS2005. Build a few variants through the wizards and save them as "templates" However my experience is that these projects have not been updated with either OCC or MFC, but they provide useful referneces, such as the IGES/STEP file readers. If you don't have a VC6.0 environment, let me know and I can build some templates for you to download.

Have a good look into the inner workings of the source code, then design your own master template. Theortically you should be able to leverage this template via inheritance, but I have found this is not always so easy with the MFC interaction model. When you design your template, consider carefully whether you want the MDI or SDI model. Personally I prefer the SDI model these days, but most of the examples are MDI which adds an addtional layer of complexity into the Document/View model - I always think I'm writing an AutoCAD interface, not a (pre Office 2003) MS Word interface. Salome for instance uses an SDI model - unfortunately not on Windows (yet).

I can't re-emphasise the importance of a object design enough, but there are very few designs in the open source world - most people just Doxygen their code afterwards (even me)! Again its worth re-engineering a design from one of the examples (Doxygen again). This will help you consider what the important features you're trying to implement should be - trust me I'm a s/w architect .

For another view of how to get started, head over to Stephane's exoTK project on http://www.exotk.org and link to sourceforge. However the version 0.2beta from sourceforge has some problems with both OCC 6.2 and VS2005 SP1 - Marc Britten and I have working versions on both Linux and XP, but we should really ask Stephane's permission before making them more widely available - he mave already have his own unpublished updates.

If your not attached to MFC, then you can can consider other GUI frameworks to look at, using VS2005. My own humble attempts at a Qt4 viewer are available via links through this forum, but other projects worthy of research are FreeCAD on sourceforge (uses OCC with Qt3, Python and Coin3d), cam-occ http://cam.occ.googlepages.com/home and the Netgen mesh generator (Tcl/tk interface with VS2005).

One of my main problems these days is spending far too much looking for other projects and not doing anything myself - it can become addictive. The main point is - don't expect to have a simple solution delivered on a plate, you have to work at it. And if you suceed let us know!

Hope this helps

Pete

bhimesh's picture

hi sir,
thanks for ur reply....
it was realy encouraging..
i will try it out .. and let u know ..

thanks once again..

bhimesh