Hi Chris, @chris fullmer said: Well then, the bigger question is does you component need to be compatible with the built in dynamic component webdialog, like for others to interact with it. I didn't think of that since I assumed the way of doing this was through Dynamic Components. So I'm not sure what being compatible with implies the DC webdialog implies either way. @unknownuser said: There is no need to actually make a "dynamic component" to do what you are asking. There is a lot that goes on behind the scenes of dynamic components. If all you want to do is manipulate components using your own webdialog, I'd recommend not using the term dynamic component a that confuses the question with the actual dynamic components. Gotcha, knowing that now, yes that's exactly what I'd like to do is being able to manipulate the created components. eg: height, width, depth... along with other variables I have. And being able to do so to all the components or just selected ones. @unknownuser said: The way I see it is that you have 2 main issues to tackle here. 1 - You need to learn how to work with components, and scale them or manipulate their geometry. You can learn this without the trouble of a webdiloag first. I have a pretty good handle on creating components already but manipulating tham after they've been created is another story which is what my original question should of been. @unknownuser said: 2 - You need to master is how to converse freely back and forth from ruby and your web dialog. Once you get them talking, and you know what you need to do to your components, then its easier to understand how to put your webdialog together so it can reach into the model and make changes. I've got the initial communication between WD and ruby working just fine. Actually My plugin is built with WD and also works great, well it needs a few 'fixes' but I'm able to get all that done, as best as I can for a newbie at lest. But getting my WD to then modify or manipulate as you say the components I create is a whole other story! I fugured integrating DCs was the way to go but seems like there are other ways of doing so. That being said, from your reply maybe I should look into scaling my components? Or resending new values and some how applying them to existing components and redrawing? Am I even close in my assumptions? Thanks, Frank

Thanks TIG, I haven't gotten around to trying what you suggested but I will soon enough.

Thanks for the link Dan... that's the kind of info that seems trivial till you run into a problem. Yeah Komodo does all that good stuff plus the pro version does a bunch of other stuff and even debugging for ruby, I think. But I tried it and it had too many bells and whistles for a newbie like me and was confusing!

Hi Keith, Thanks for the input. As stated some features aren't working yet... as you found out right now you can't mix and match doors and drawers. Which in turn is why you're not asked anything about drawer size... when adding drawers to base cabinets they automatically divided equally in the size of the cabinet entered. Ecepth when selecting 3 drawers then the top is smaller then the bottom 2... I'll be adding the option to have 3 equally sized drawers. Like I said this was for personal use with the way I build cabinets so I understand that some deatures seem limited... but I figured it was hard enough to get what I wanted without adding options I would never use. But I'm kinda getting the hang of this and add different features as I go along and have the time. So far it's proven very useful in getting exact measurements for things like stile and rails which I use to have to calculate individually for different cabinets, now it's all done automatically which to me is a huge time saver. As per Dan's suggestions I'm working 'standardizing' the pluggin and when I'm done with that I'll start a new thread dedicated to the plugin with updated. I guess till then this thread can be used for suggestions. Frank @ktkoh said: Tested your cabinet plug-in and was impressed. However I was trying to design a base cabinet with 2 drawers at the top and then doors on the lower part of the cabinet. What I got was a 30" tall base cabinet with 2 doors and then 2 drawers on top of the base cabinet with a total height of about 50". Also when I specified drawers I was not asked anything about size. I'm sure there are too many options to please all cabinet designs but I would think this would be able to get a kitchen design started and the individual could add/change some details with less work than starting from scratch. Keith

Just a note to remind all.. ... that now with Ruby in the 1.8.6 branch, we have both a ceil() and a floor() method defined for the Float class.

Dan, I stand corrected - clearly the skethcup.rb's 'inputbox' is to be preferred to the UI. version...

And depending upon version, either the relative or absolute path, or both script path(s), (sometimes downcased,) were pushed into the $LOADED_FEATURES array. Sometimes we need a table to keep track of things like this from version to version.