Posts made by AdrianM

The eDrawings publisher will let you export a Sketchup file to an exe file.

@unknownuser said:

To use the component later on, or make DC changes to it, you want to import it. I tend to do this using drag and drop from a file browser (nice and easy on my mac), but if you prefer using the component manager thing, then you want to go to the menu and select "Open a local collection...", then you can navigate to wherever you keep your components.

It must be different on a Mac as importing a DC on the PC in either of those ways loses the attributes.

Unless I'm completely misunderstanding something which is usually a safe bet.

IF you create the component and then save it so it can be imported via the Component window then it will lose attributes. The documentation does imply that DC's can't be imported via the browser.

I save them and open them as normal Sketchup files which seems to work fine, nowhere near as convenient as importing though.

Not sure what you mean by adding attributes, if I'm modifying an existing DC or creating a new from scratch or from a normal component I just highlight it and choose attributes off the context menu.

If you're using Pro then you can do what that script does in a Dynamic Component. They're fantastic for woodworking, I can't believe the difference they're making to my workflow.

If you don't have Pro you can still do it, you just need someone with Pro to make the basic box/plank DC first.

Made all my Ruby scripts pretty much redundant!

There is also a set of DC's in the "Google Sketchup 7\Components\Dynamic Components Training" folder as part of the installation.

However the best way to learn I found was to download this one (http://sketchup.google.com/3dwarehouse/details?mid=ce5eddf19a1cd04d4af4635b6ebb0145) from the warehouse, loads of examples all in one file.

The SU bonus component packs have been moved onto the warehouse but the download page does have a link to the original SU6 packs which work fine in SU7.

For some reason they've taken the bonus texture packs off at the moment.

My system isn't state of the art but I regularly run very large models as I design boat interiors which means I have a model of the whole boat to scale with each individual room drawn inside. Due to the nature of a boat having a lot more curves than the average house and because I have to make these models from the 2D cad files they tend to be a lot bulkier than most house designs.

The OP's file, however, is unusable on my system. Any operation takes several seconds to achieve. A few minutes spent on setting up and hiding layers (as I do all the time in my models) and it's fine.

The moral of the story is that working smarter is a lot cheaper.

I have a dual-core Athlon 64 4400+ with a Quadro FX3500 and 4gb of memory (for Vista although I've gone back to XP for work).

Yes, four scripts, plus two supports classes. No real reason why they couldn't all be in one Ruby but it makes the code too big for my tastes.

I've been rushed off my feet the last couple of days (hence the lateness in replying) but I'll see if I can get then posted on here ASAP.

I have a set of scripts that I developed for frameless European style cabinets.

It does wall cabinets, base cabinets and corner cabinets for both. Just about every parameter is adjustable via dialogs both before and after placing the cabinets.

At the moment it's integrated into my SU environment rather than being something I could just post here. If you think it might be of some use then I could spend an evening or two making it stand-alone.

I reach for SU everytime unless it's for something very, very quick in the workshop and the CNC pc is turned off.

I've been using computers everyday since the age of 11 so I find it far more intuitive to reach for the mouse and keyboard than pencil and paper.

Writing more than a sentence or two these days give me terrible cramp. Mind you that may be more to do with the RSI from too much keyboard use!