Legacy Class Catalog¶
Class names and schemas below are values recorded in controlled files. They are
wire identifiers, not Python implementation names. Public mappings refer to
the data returned by skppy.
Class families¶
Wire classes |
Public mapping |
Key role |
|---|---|---|
|
Geometry classes in |
Shared topology and directed face boundaries |
|
|
Ordered edge ownership and circular parameters |
|
Component/entity classes |
Reusable geometry and placement |
|
|
Appearance, physical scale, and image bytes |
|
|
Visibility and ownership |
|
Construction classes |
Guides and sections |
|
|
View and saved-page state |
|
Model metadata |
Display, geolocation, and axes |
|
Annotation classes |
Text, anchors, dimensions, and fonts |
|
Dictionaries and relationships |
Typed metadata and graph links |
Style, line-style, watermark managers |
Shared style classes |
Named presentation resources |
Manager objects normally collapse into their public collections; they are not duplicated as model objects.
SketchUp 8 version map¶
# |
Class |
Schema |
# |
Class |
Schema |
|---|---|---|---|---|---|
1 |
|
1 |
29 |
|
1 |
2 |
|
0 |
30 |
|
2 |
3 |
|
0 |
31 |
|
4 |
4 |
|
1 |
32 |
|
1 |
5 |
|
10 |
33 |
|
12 |
6 |
|
5 |
34 |
|
4 |
7 |
|
11 |
35 |
|
1 |
8 |
|
5 |
36 |
|
0 |
9 |
|
10 |
37 |
|
0 |
10 |
|
4 |
38 |
|
0 |
11 |
|
0 |
39 |
|
36 |
12 |
|
1 |
40 |
|
2 |
13 |
|
0 |
41 |
|
7 |
14 |
|
4 |
42 |
|
1 |
15 |
|
0 |
43 |
|
0 |
16 |
|
3 |
44 |
|
22 |
17 |
|
1 |
45 |
|
1 |
18 |
|
6 |
46 |
|
1 |
19 |
|
2 |
47 |
|
2 |
20 |
|
4 |
48 |
|
9 |
21 |
|
9 |
49 |
|
5 |
22 |
|
2 |
50 |
|
6 |
23 |
|
1 |
51 |
|
1 |
24 |
|
3 |
52 |
|
0 |
25 |
|
3 |
53 |
|
12 |
26 |
|
4 |
54 |
|
1 |
27 |
|
0 |
55 |
|
2 |
28 |
|
1 |
56 |
|
0 |
Schema differences, SketchUp 3–8¶
A dash means that the class is absent from the target’s version map.
Class |
V3 |
V4 |
V5 |
V6 |
V7 |
V8 |
|---|---|---|---|---|---|---|
|
- |
0 |
0 |
0 |
0 |
0 |
|
- |
0 |
0 |
0 |
0 |
0 |
|
- |
0 |
0 |
0 |
1 |
1 |
|
- |
- |
- |
1 |
9 |
10 |
|
- |
4 |
4 |
5 |
5 |
5 |
|
3 |
4 |
4 |
4 |
5 |
5 |
|
3 |
3 |
4 |
4 |
4 |
4 |
|
0 |
1 |
1 |
1 |
1 |
1 |
|
3 |
4 |
4 |
4 |
4 |
4 |
|
2 |
2 |
2 |
3 |
3 |
3 |
|
0 |
0 |
0 |
1 |
1 |
1 |
|
4 |
4 |
4 |
6 |
6 |
6 |
|
8 |
8 |
9 |
9 |
9 |
9 |
|
2 |
3 |
3 |
3 |
3 |
3 |
|
- |
4 |
4 |
4 |
4 |
4 |
|
1 |
2 |
2 |
2 |
2 |
2 |
|
- |
1 |
1 |
1 |
1 |
1 |
|
22 |
25 |
28 |
32 |
35 |
36 |
|
0 |
0 |
0 |
1 |
1 |
1 |
|
10 |
12 |
12 |
18 |
22 |
22 |
|
- |
- |
- |
1 |
1 |
1 |
|
- |
- |
- |
2 |
2 |
2 |
|
4 |
4 |
4 |
5 |
5 |
5 |
|
4 |
4 |
4 |
6 |
6 |
6 |
|
0 |
1 |
1 |
1 |
1 |
1 |
|
6 |
9 |
9 |
11 |
11 |
12 |
|
- |
- |
- |
2 |
2 |
2 |
Explicit schema boundaries¶
Version-aware readers use the per-file map. Classes with a single confirmed layout accept only the schemas below and fail before consuming an unknown body.
Class |
Accepted schemas |
|---|---|
|
10 |
|
11 |
|
10, 11 |
|
4, 6 |
|
0 |
|
0 |
|
1 |
|
6 |
|
2 |
|
0 |
|
1 |
|
0 |
|
0 |
|
2 |
|
9 |
|
1 |
|
1 |
|
2 |
Some newer applications write a later class tag while down-saving an older body. The archive tag still participates in object identity, but the file’s version map selects the body layout. Confirmed target-specific exceptions are documented in field layouts.