CgScenes version 2 - WIP Reform
-
I see it is quite popular to post model wips. I thought I might get away with doing the same for a less glamorous subject like cgScenes because what I want to do in this stage includes other members' ideas, plugins and snippets that I have found when grazing the forum.
cgScenes Version 1.04 I released here just used the web dialog as a machine to handle several standard SU features. Now I want to reform and structure information (the names of collections, groupings, components, scene sets and scenes) to be usable on the web as well as locally. The immediate advantage for Sketchup users will be unlimited combinations of visible entities for easy to manage sets of scenes.
For example, a bath that is part of a bathroom collection, is also part of a grouping of sanitaryware requiring containerisation and appears in several scenes in 3D, in plan, section, elevation, in different styles, in a schedule and perhaps in an animated set tracing its distribution path. By unhitching elements other than dimensions and labels from SU layer and group restraints, component and group elements (as with their real life counterparts) are moved in and out of different associations. It will be possible, for example, to plan and monitor a project with a dedicated set of scenes each representing the projected status at each week's end. Components can be moved independently within each scene to help identify sequence as well as design clashes.
The first task is to reform existing models to accommodate a new web-compatible data structure for the existing 1.04 machine, and here is what I have come up with:
Of course all this is pretty much experimental especially not knowing how much will need to be done manually (hence options in the top menu to examine each element separately). But I have been quite surprised that much of the ruby code already exists - for example, Chris Fullmer's geometry to groups and TIG's layer.delete, as well as discussion and snippets like of the Transformation array, that will be needed later on.
One thing always in the back of my mind is how to efficiently relate the javascript "master" array to SU entities array, the biggest problem being the children in the collection, groupings and scene set hierarchies. I understand observers better now but I don't think they offer the solution. The last reform on the list is where this will be set down.
Any suggestions or comments about any of this welcomed. I would also like to hear from anyone who is concerned about the web dialog/Mac frustration.
My regards
Chris
-
Maybe if you change the name you'll get more response. hmmm... what about Outganizer
-
@xrok1 said:
Maybe if you change the name you'll get more response. hmmm... what about Outganizer
Yes thanks I'm open to all suggestions. Perhaps a name that captures the idea of nesting sets of scenes and components as shown in this "Reform" part of the machine? Don't think Outganiser does that really.
Advertisement