I arrived a little late to this thread: I notice the discussion has meandered, which is normal, in forums.
For those reading this thread, I have already donated 2 Ruby scripts to this forum which I wrote:
I didn't claim copyright nor did I obfuscate the code so others could not read it, and anyone is free to use the code and alter it.
Window Tools:
http://forums.sketchucation.com/viewtopic.php?f=323&t=14394&p=109705&hilit=window+tools#p108868
Door Tool:
http://forums.sketchucation.com/viewtopic.php?f=323&t=14008&p=105538&hilit=doortools#p105538
My investigation into Ruby coding lead me to believe that it was impossible to cut an opening into a wall, because a SketchUp wall is not actually a wall, its only to planes separated by a given distance, with 4 more planes defining the thickness, unlike a real 3d object which would require a Boolean operation to cut holes into it, or Nurb objects. However my 2 ruby scripts will cut openings into walls as long as the user enters the wall thickness into the dialog box prior to cutting the holes. SketchUp is a surface modeling program NOT a solid modeling program like ArchiCad, Maya, XIS, Max, C4D, or Rhino. Its also one of the main problems facing developers trying to produce workable export plugins from SketchUp to other 3d platforms.
I found schedules the 3rd item on the list, to which not much attention has been paid.
When I was creating AutoCad window and Door schedules many years ago, I could get them to print out via an Excel spreadsheet. So they could be incorporated in 8.5x 11 format into the back of a specification manual(s) I had to create a Dialog box consisting of some 15 attribute tags that needed to by filled out before a door could be inserted onto a AutoCad drawing file. So whats wrong with that!
Nothing except AutoCad would change its menu structure each year. And with each newer version, it became impossible to keep up making changes to the menu structure, and to incorporate those Attribute and Lisp coded functions. And it got even harder, for the Firm, after I left. I heard later that they were making schedules the old fashioned way, which was much faster in the long run.
I've been there just like Atl-Arch describing his attempt to build a stone cap parapet. I recall Working with a $3000.00 program from AutoDesk called Architectural Desktop, which was supposed to be used to draw repetitive floor plans, except they forgot to include an actual floor in the program that you could insert and which had actual thickness.
I hope Revit users wont go through the same dilemma, now that AutoDesk bought them.
Regardless, I'm looking forward to the schedule, good luck, Al