@unknownuser said:
Can you give some examples of what you script so we can get some ideas of what to add to a scripting interface?
I am not familar with Layout and it capabilitys since I am evaluating the specs for a possible future use.
When I undertstand it right Layout is a separte EXE/Modul and not running in the same process then SketchUp.
In Autocad the modellviews in modellspace are similar to the modellviews in paperspace.
Both can be reached from autolisp and automated/scripted.
So what I would expect from scripting layout:
Inserting forms/templates and filling their data-fields.
Drawing primitives (lines,arrows,text and whatever layout supports) in Paperspace
Placing views and set them up with view-points, camera-settings, rendermodes etc.
Iterating (reading propertys) through all elements in paperspace.
Interfacing with the SketchUp main-modul. (Starting a layout/print process in Sketchup/Ruby, doing the job (passing a ruby call to layout) in layout/Ruby and return back to the calling point in SketchUp)
Control (filenames/printers) the output (Printing/Exporting) with Ruby in Layout.
So be able to give a customer a cadalog with Sketchup Components and ready made forms/templates and custom ruby code/toolbars to allow him easy product customising.
(I hope I make it clear so far, since I am not native english)
Greetings from germany
Regards
Hans-Peter