Components, Layers and Component Collections

plot-paris

or you can do it the dirty way...

create a component within the component. place this inner component on the correct layer. call the inner component by the correct name (e.g. toilet) and call the outer component something like 'toilet_container'.
now you've got everything you want:

when hiding the layer 'toilets' all the toilet components will become invisible.
if you check, how many of those toilets are in the model, it will show you the right amount
when placing the component, you don't have to mess around with layers. they are already placed

there are two downsides though. firstly, you've got an unnecessary component in you browser (the 'toilet_container' component); and you actually have to expand your view in the component browser in order to see the ones you want, which clatters the browser with all the nested components as well. good thing is though, that it won't increase the file size too much, for the content of the container component is just another component.
secondly, if you press Ctrl + A to select everything within your scene, even with the toilet layer switched off you will select the container components (even if they are not visible). that may cause some unwanted deletions if you are not careful.

you could of course always explode the container components. but then its not too much of an effort to simply place the component on the right layer manually in the first place...

aadbuild

Oh and Tig I am not disputing that layer 0 is not the correct layer for componets to be placed on. I am simply asking if it were possible to have it on the layer I decide not the layer Sketchup decides.

aadbuild

@unknownuser said:

If you explain exactly where you want to end up, and where you are starting from, then the solution might be more obvious, or at least clearer...

Sorry if I sound a little vaigue. basically, from start to finish:

I have my own library of components that I use for all my models.
2.I place the components in new models and I report the components by layer ( with a ruby).
The problem for me is: when I import a new component from my collection I have to go and manually change from layer 0 (the "correct" layer thanks TIG) to the layer I initially saved it on so that the component is where I want it to be in the report.

There could be 500 components which takes some time to adjust even If I do it in outliner. It also brings a lot of human error into the mix.

A 'component-inserter' browser is above our ability and probably more complex than I have time to tackle. Thanks I appreciate the suggestion though.

oh and plot paris I like the dirty idea, thanks. it will get me out of trouble until I come up with some thing new

chrisglasier

Andrew, please consider this what you might call low tech solution.

Use the word joist to indicate you need a joist. Add dimensions, either exact or for later adjustment. Make a component say 50 x 175 x 1000mm and save it in a file called joist.skp. Arrange it so that when you click on the word joist you can also click on other words that link up to functions to import it into your model, scale it, make arrays, and so on.

When you have made more components in this way, you can collect them together under another name, say structure or floor 12 or timber. One component can belong to as many collections or groupings you care to name. Dimensions and labels would need to go on layers because they are part of drawing rather than components, but everything else can go any place because you are able to generate only the components you wish using the collection, grouping or component names you have selected.

Rather than extract a BOM a BOM generates** the model ... and with other devices just about anything else you need to support physical activities.

You and I have talked about this for more than a year, but now my cavalier attempts at coding have been taken in hand by Jim and we now have a Web Dialog/HTA/In browser operating system that we both consider stable, extensible and of universal application. You can see the first application here, but probably of more interest to you will be the machine that is suitable for more "horizontal" associative indexing - e.g. from project through to door hinges rather the long "vertical" lists of Classes and Methods in the API device.

The problem lots to do makes it difficult to know what to do first - the API devices like plugins index to show off the functionality or, for me the more interesting, general purpose machine

early stage

and building industry devices that I think are of interest to a few here.

My regards

Chris
edit ** or modifies - can just hide/show

aadbuild

Thanks Chris I do like the way name sets makes it easy to organise components, layers and variable tasks. I am still trying to figure out where the web dialogue box fits in. I guess my need for a BOM is to know which components are in the model and have them in a way they can easily be grouped acording to supplier and the job progress. I do this by using layers (more of a named group) as the job stage. It would probably be easier to do this with namesets but I have not spent enough time lookig at how it would go together . I guess the only way would be to give it a go...
would you lke a model example? and we can compare notes. Your way verses mine?

chrisglasier

@aadbuild said:

... I am still trying to figure out where the web dialogue box fits in.

machine nov 51.png
This little thing can sit inside a web dialog to make it easy to give Sketchup commands like in the .rb file attached. The function of the machine is to knit a nset (nameset) of all the things you associate with yourself in a top down hierarchy. So one trail from the name office would go:

Office>Projects>Project 1>Building>Ground floor>Space> Sanitary ware>WC suite.

Of course there would be many trails like this with inherent and custom cross links. For example, sanitary ware is an inherent link you can use to pick up all the sanitary ware but you might also set up a "week1" name and link all planned deliveries (possibly including sanitaryware). The menus on the right pick up devices both to build the nset and use it to assemble models, purchase orders and so on. So Add is obviously the first device I need to make.

@aadbuild said:

I do this by using layers (more of a named group) as the job stage.

I understand but plain text is king if you want to use it for many different tasks. Doming plain text (making into HTML) means you can automate what you otherwise have to do by hand (in Excel for example).

@aadbuild said:

I guess the only way would be to give it a go...
would you lke a model example? and we can compare notes.
.

Yes of course and I am working towards that. I already have one of your models but I don't think it sensible for me to strip out its attributes into a plain text list (for converting to json) better to get on with the machine. But a snapshot of your components subdirectory would be useful to see whether we can easily adapt and incorporate your naming system.

@aadbuild said:

Your way verses mine?

Actually we both have similar aims so I think it's more like pushing the thing to a natural and satisfying conclusion. But a little rivalry is healthy!

Chris

Namesets3.rb

chrisglasier

@chrisglasier said:

But a snapshot of your components subdirectory would be useful to see whether we can easily adapt and incorporate your naming system.

I wonder, Andrew, instead of a screenshot, you could copy six of your component files into a folder, zip it and send it to me. I hope these pics and notes will help to show where I'm at and why such a folder made by someone else would be a good design prop.

Showing part of the hierarchy that leads to the components (columns slide vertically and horizontally to reveal the rest)
New component name in nameAdd device (name and menu panel slide to accommodate device panel)
new component instance name (resize machine to see all of long names)
Instance added to nset ready for import into Sketchup (Changed device background)

What I want to do next is to get the machine to read the file names of your components, strip them of .skp and populate the product (component) names slider with the results. So after this step the machine will be a component importer and instance namer. At the same time of course it keeps a tally of the numbers. After that I will make it into a kind of super measurement box, and then a means to hide and show components by entity (location), grouping (purchases), headers (subjects) or individual component. I am not intending to get involved with positioning and rotations as before, but I have some code worked out for tracking resizing in Sketchup (so actions are bilateral).

My regards

Chris

aadbuild

HI Chris Christmas has come upon me and I have had no time to do any more work but I will get to it as soon as I can. I have spoken to mIke and we will have a seperate forumn for the estimating ruby in the new years. Ther ewill be a preliminary beta test. I am alos working on a yotube ppresentation to show what we are doing and how we are doing it. I hope to get much feed back from yourself and the Sketchup community.