Right as most of you are already aware I have 2 books out for SW API, that are still very popular, and I get so many requests now for an API coverage of Drawing Automation as it is so undocumented at present that I am going to try and fit it in shortly.
My original plan was to create Draftsman, a tool that automatically creates drawings from scratch for you... cool aye? However, due to certains reasons I will not be doing this for now. However, the better idea is to write the first of the second series of books on SolidWorks API for drawing automation and SW2010 so you guys can do it all yourself.
I am likely to get started on the book later this year once other projects are finished, so now is a perfect time to voice your opinions and requests again like before - what you would like to see, have included, code coverage, ideas etc....
Here is the current thinking:
1. Book will focus on one language to best consolidate pages and to fit more code and less duplication of code. Current language of choice is likely C#, and where needed any specific differences that are not obvious to VB.Net will be covered. For all other code, the free Developer Fusion Conversion tool can be used easily (http://www.developerfusion.com/tools/convert/vb-to-csharp/).
2. Code samples will be via Download not CD. All samples in the book will be included, in BOTH C# and Vb.Net
3. Books will be Thermal bound instead of wire to allow more pages
What I plan to do for this book to instead of covering specific scenarios is to start off from scratch and create one single application. That application will effectively mimic the SolidWorks drawing environment entirely, from getting all of the drawing sheets, views, notes, boms, information etc... to then manipulating any and all of it, or to add/remove drawing items, views or sheets etc... This way the user will learn how to obtain, manipulate and add anything to do with drawings. What I picture is that the end application (which will be a fully integrated add-in) will have a display canvas showing the currently open drawing, and re-drawing it to show that it has successfully obtained the information. The user can then use the add-in to position, update, add/delete views and annotations and tables, can change sheet, can inspect objects for their values and re-reference views. All-in-all, anything I can think of to do with manipulating a drawing will be covered.
Of course this is just the current thought process so is up for suggestions at this stage, that is just what I am thinking, feel free to let me know what you guys would like from this one.
Luke
SolidworksApi macros