[Plugin] VisMap - Layer/Scene Visibility Map

fredo6

Freeze panes have been requested for both the layer list and the scene list. This is almost possible with frames. Issue: how to synch vertical scroll in the layers list with vertical scroll in the main array. I don't know that JS has scroll listeners.

That means, writing a custom scrollbar widget, a feasible project in any browser that supports <canvas>. That's every browser except MSIE, of course.

Freeze Panes is relatively easy to do with DIV in pure HTML with constant column width.
For non constant column width, the horizontal scrolling with freeze of first column is more complex, but doable with JavaScript in a portable way.
All this said, I am still wondering why these natural and simple requirement is not a default part of the HTML table specifications. Hope that HTML 5 will do something about it.

Fredo

PS: For sorting, I don't understand the issue you mention. Data should be independent from their display.

MartinRinehart

@unknownuser said:

For sorting, I don't understand the issue you mention. Data should be independent from their display.

You click a checkbox in row 3. This is the third layer in the model, as is. If I sort the layers, row 3 may be model layer 17. Solution: hash with key = layer name, value = original row number. Something like:


var hash = [];
for ( i in layerNames ) { 
    hash[ layerNames[i] ] = i; 
}

fredo6

Sure, you need an indirection to keep track of the original index in the model.layers array. But that's just a little bit of code, not a limitation.

Fredo

chrisglasier

@unknownuser said:

Chris,

I agree with your remarks, but then, you don't need a plugin, as it should be enough to show the SU Layers dialog, and click on the scene Tabs to see which layers are visible in the current scene.

...

Fredo

Of course I would prefer to use cgScenes so I could manipulate many aspects. But, whereas I do see a matrix as also useful I still think it should be easy to use it with reference to several layers and the SU display simultaneously.

Chris

Bob James

@chrisglasier said:

I think the option to have layers and scenes in alphabetical/sequential order is important.

Chris

Layers in alphabetical order is a must, but I wouldn't want the scenes in alphabetical order. I name my scenes to be applicable to their content and in the order I want them to appear. This is rarely alphabetical.

Also, it needs to stay on top.

Bob James

Martin,

I realize that the existing Layers Tool can be used to create scenes, but your tool is MUCH simpler to use. Why? Because I can look at all of the scenes at once. With the Layers Tool I have to open the scene, then go through and pick the layers I want, then save the scene. With your tool I can do several, if not all, layers at once. Much better.

Why do I press for this tool? We have a satellite processing facility and a launch facility at Vandenberg AFB, CA. I have built models of both of these facilities. When a new user comes I need to model their process through the facility. This requires the basic model, then certain layers of both their equipment and ours turned on/off for each stage of the process. Each stage of the process is a new scene with their and our equipment at different locations and attitudes (open/closed, up/down, etc.). I model their equipment and, for the pieces that will appear at different places in each scene, I make a new location-sensitive instance. Once all of this is done I can then, with your tool, turn on the applicable location-sensitive pieces of equipment at the appropriate location in the appropriate scene.

But to be useful it is (absolutely essential) to have the layers sorted.

It would also help a lot if:

Somehow the numbers representing the scenes need to stay fixed at the top when scrolling down. I can remember the scene number(s) I'm changing or, more likely, I can refer to a print out of the scene numbers/names.
The VisMap dialog stayed on top.

VisMap still does not capture the model data for a very large model/scene combination. If I copy the entire model (60 or 70 layers) and put it into a new instance of SU, VisMap can then read the data. But, of course, I've lost all the scenes.

Thank you very much for working on this Plugin.

chrisglasier

@bob james said:

...

I model their equipment and, for the pieces that will appear at different places in each scene, I make a new location-sensitive instance. Once all of this is done I can then, with your tool, turn on the applicable location-sensitive pieces of equipment at the appropriate location in the appropriate scene. ...

That's very interesting. Am I right in thinking each layer configuration is saved in a client specific file? As VisMap is in a webdialog what would you think about saving configurations as JavaScript arrays, so that you need not open and close files and quickly move through the configurations, and, with further devices, compare selected parts/costs/status and suchlike in different configurations? If the Sketchup Viewer had plugin facilities, clients could access your configurations via the Net as a normal part of their business operation.

If the Sketchup Viewer had plugin facilities ... now that's definitely another topic ... sorry!

Chris

SHAHEEN

thanks mr. martin

Bob James

@chrisglasier said:

Am I right in thinking each layer configuration is saved in a client specific file?
Chris

Not quite. Each scene in the process has its own layer configuration. The process (movement of their satellite through the facility) may take 10 or 15 scenes. This client-specific SU file is then saved. In most cases each scene is rendered using IDXRenditioner, the result saved, each picture touched up in Photoshop (if necessary), and the result put into a PowerPoint presentation. Sometimes the entire set of scenes is made into an SU animation.

During the development process I also use new version of Layer Manager to save the layer configurations (great plugin - use it and its associated Layer Tools all the time).

MartinRinehart

@chrisglasier said:

If the Sketchup Viewer had plugin facilities

<sketchup src='my_slick_model.skp'> If you had a better browser, you'd see My Slick Model here </sketchup>

Right?

MartinRinehart

Like so?

Or should Layer0 always be at the top?

Bob James

Super!!
Can I download this version? I'm just beginning a new project.

@martinrinehart said:

Or should Layer0 always be at the top?

My vote would be for Layer(0) to be at the top.

Jim

Like this:

Bob James

I like Jim's layout better, but would still prefer Layer(0) at the beginning (but that's not a show stopper).

chrisglasier

@bob james said:

I like Jim's layout better, but would still prefer Layer(0) at the beginning (but that's not a show stopper).

Forgive me if I have missed something but isn't layer0 always going to have to be the active layer and should not appear at all? If not it seems there will be lots of complications with reassignment/hiding.

Both seem to ignore the scene name problem!

Chris

TIG

'Layer0' is most often used as the current layer - you then put 'assembled' groups/components/etc on other layers to control visibility. However, you can set any layer as the 'active' one BUT it's not recommended without a good reason... An example would be you are puttings dimensions on the model and want them all to be on layer 'DIMS' - make that the active layer, add the dimensions [you can then switch them on and off separated from everything else] BUT remember to go back to active=Layer0 afterwards otherwise chaos will ensue...

chrisglasier

@tig said:

'Layer0' is most often used as the current layer - you then put 'assembled' groups/components/etc on other layers to control visibility. However, you can set any layer as the 'active' one BUT it's not recommended without a good reason...

Ah yes I should have written ... "always going to have to be the active layer" when using VisMap

MartinRinehart

@chrisglasier said:

"always going to have to be the active layer" when using VisMap

Actually, Chris, I'd turn Layer0 off, if I could. In my tutorial I teach the common gospel re Layer0, but I don't believe it. I consider a model incomplete until Layer0 is empty.

chrisglasier

@martinrinehart said:

@chrisglasier said:

"always going to have to be the active layer" when using VisMap

Actually, Chris, I'd turn Layer0 off, if I could. In my tutorial I teach the common gospel re Layer0, but I don't believe it. I consider a model incomplete until Layer0 is empty.

Yes I agree, empty, active and not an option in VisMap! Otherwise if you try and hide another layer that is active you will get an alert "You cannot hide an active layer" or something like that.

MartinRinehart

Sorted layer names.

These two are not in the .zip yet. Please rename "vismap.txt" to "vismap.js", try them in .../Plugins/Vismap and let me know.

Thanks.

vismap.txt

vismap.rb