I'd go this way if you don't need to edit their styles or line weights later. Open an SU file drag in ALL your SU components and arrange to a rough grid. Look down on the model with persective off and set with "ground" off to ensure no background in LO. Drag and drop this file or reference into a layout doc and scale as needed. Export the whole page at good resolution PNG so the transparency again sticks. Delete the SU object from the doc, drag in the PNG, scale out to fit the page. Then on a new layer draw an open square or circle over each item on the page. Select back to the lower layer and do a CTRL+C of the PNG object, then select the image and the first square and "make clipping mask", Ctrl+V to paste a new instance of the image and repeat with the next square till complete! Looks like a long process but I've spelt it step by step (actually probably the quickest). Nice thing is you get nice clean non too sticky objects - if you use a circle as the clip you can position it so the centre matches what you want to be the insertion of the object so it snaps in place as desired.

@dave r said: How about this? Color the wall with the color of the paint and name the material "drywall" Paint the box blue and rename the blue material "20 ga. sheet metal" Paint the piece of furniture with a woodgrain material the color of the stained cherry and name it "cherry" A simple note can identify the finish. +1 I always try to name my material so I can find and reuse them. A model becomes messy if you keep picking the same colour from the material browser - ending up with many materials of the exact same colour. That just lead to a pain when you want to change it later on. Give material a semantic meaning and make sure you use the correct one for the correct place. Managing materials becomes so much easier that way.

I just corrected the link in the above post. Here it is for easy reference. http://forums.sketchucation.com/viewtopic.php?f=15&t=39846

@adamb said: you sure, TIG? I'm certain I tried doing a html+js progress bar and found its actually run from inside the Ruby execution loop. Yes I've just done it! Sleeping will slow the changes to the displayed dialog but it won't stop it loading as it is currently set...