Like patches, maquettes be used as autonomous programs, or within other patches and maquettes, like blue and red patches. Consequently, OM also offers two types of maquettes :
|
|
|
|
General maquettes can be :
Local maquettes can be added directly into a patch like an internal abstraction.
Maquettes can also be used within other maquettes, according to similar principles :
Last, like blue and red patches again, general maquettes can be converted into local maquettes, and vice-versa.
General maquettes are equivalent to standard blue patches. Like them, they can be created in the workspace, or one of its folders. To add a maquette in a workspace :
|
General maquettes are persistent files that can be manipulated like patches. They can be :
Once a maquette is added in a workspace, it can be dropped in a patch, on the same basis as an abstraction : like a "global" abstraction, or blue patch, the maquette keeps it original reference, which means any modification will affect all of its representations.
Internal maquettes are the equivalent to internal – red – patches .They can be created inside a patch. To add a maquette in a patch :
|
General maquettes can be converted into internal maquettes, and reciprocally, internal maquettes can be converted into global abstractions.
|
This use of maquettes mostly sets forth a number of specificities dealing with the use of TemporalBoxes[1].
To save a maquette :
Cmd
+ s
File / Save
Ctrl
/ right click in the maquette and choose Last Saved
in the contextual menu.The Last Saved
command allows to reset the maquette to its last saved version.
A TemporalBox refers to an object in a maquette : an instance, a patch, or another maquette.