Organizer will allow Plugins menu organization by system folders - make a subfolder in your Plugins folder, then drop the desired .rb files into that subfolder. Organizer will create submenu items having the same name as the folder, and the submenus will contain the ruby scripts you placed there (I skipped a step or two in that description, but that's the basics).

Fletch,

The eventual goal is to wrap everything together. It's just that time isn't on my side right now...

Fletch: multiple columns is possible. I was just concerned about long scene names.

wrecknball: it should work on Mac (no reason to suspect otherwise).

Yep, I've been working on it off and on for a while. Nothing ready for prime-time, yet, though.

Susan,

I'm working on it.

The inactive scrollbars on the intial launch of the webDialog is a known SU bug. You can also right-click and select "refresh" to get the scrollbar to activate. I suppose I could shrink the text and/or make the rows shorter...

Since you asked nicely, I'll get one put in. Will post when it's ready.

Be careful, though, with groups. If you create an empty group in the definition and then add geometry to it, you'll be okay. But if you try to create the group with specified geometry, your group will end up in the main model entities space. That's because in ruby, things that are impossible when drawing manually become (theoretically) possible, such as using FollowMe on a path outside the current entities space (will work), or creating groups inside of groups when you aren't inside the group to begin with (won't work).

So, just be mindful when working with groups & nested geometry, that things may not happen the way you expect.

No progress yet. I've been swamped with my day job, and I want to investigate an alternative way of doing things for PageExIm...

I think if the last 4 lines are

vector = eye - target
vector.length = 2.m
eye = target + vector

camera.set eye, target, up

then you will get the desired result

@unknownuser said:

The idea would be to create new_comp_def = model.definitions.add
then create new_sub_comp_def = new_comp_def.definitions.add

Your second line will fail. There is no .definitions method for a definition. You will need to create the second definition exactly like the first, using model.definitions.add

Then, you can add an instance to the entities of your parent component:

new_comp_def.entities.add_instance(new_sub_comp_def, transformation)

In Geometry, a line is an infinitely long entity defined by a linear function [such as f(x)=2x, or y=2x], and a ray is like half a line, in that it is infinite in one direction, but has a specific start point [such as f(x)=2x where x>5].

In SketchUp, (as explained) a ray is an array consisting of the start point and the direction (a Point3d object and a Vector3d object), which corresponds to the Geometric ray.

http://groups.google.com/group/SketchUp-Plugins-Dev/web/Ruby-Model.html#raytest has an explanation of the ray as used in SketchUp ruby.

Ditto that.

Sorry to be the bearer of further bad news, but we can't delete scenes. I've made that request (plus others), so we'll see what happens...

Or use the Weld tool to join edges into a curve ("polyline").

I guess we don't...

Any more (or different) explanation of what you want to accomplish? Images often help get the point across.

Fletch: from the plugin's page:
@unknownuser said:

The default format is .jpg, but .bmp, .png, and .tif formats are also available.

Those are the available types in SU ruby. I'm looking into how to tie into the 3d exporters.

chango70: thanks, and glad it helped!

haynesc: If you have shadows turned on, try exporting with prompts at each scene. That will give SU time to generate the shadows for the scenes - something it might not do adequately if you have a complex model.

fletch: This plugin uses the scene settings to export image files. Unfortunately, it doesn't do CAD export. I could mod Didier's script to handle scene settings, or perhaps he could be persuaded to mod it himself IIRC, it was written before we had a pages.active_page= method available, so we had to do some gymnastics to get things to happen correctly. Now, a quick mod would fix the issues you're having.

Looks like Matt's problem was caused by SketchUp reporting the screen size prior to the toolbars loading, skewing the settings and causing the clipping issue. I've fixed that to check the screen size prior to the first run and then every time the dialog is refreshed, so if you change your SU window size, refresh the dialog (start it again from the menu bar) and you'll have accurate screen size settings.

I've also updated it to use the saved settings by default.

It might still be useful - say you try some different settings, then decide you don't like them - just "Restore from Model" and you don't have to try to re-create them.