看看这个GIF 动画的简单演示. 下载一些例子设置+ Rhino文件。
_______________________________________________________________________________________________ 更进一步的阅读
[$nbsp] [$nbsp] 历史记录构成说明
[$nbsp] [$nbsp] 界面说明
[$nbsp] [$nbsp] 管理持久性的数据记录
[$nbsp] [$nbsp] 管理挥发性数据继承
[$nbsp] [$nbsp] 数据流匹配算法
__
翻译如有出入请参考以下原文
__________________________________________________________________________________________________
原文
Why explicit history?
Rhino4 came with a basic history feature build-in, which is a non-intrusive layer around the workflow that allows for automatic updates of certain modeling steps. The current implementation of History in Rhino4 is implicit; it is recorded as you go. This means there is no additional overhead required at model-time which is exactly the sort of thing we would like to see in Rhino: more features, no additional limitations. However, implicit history cannot do some things which are possible with a constraint based modeler.
First of all, the history tree is hidden from the user. The behaviour of the different history stages cannot be adjusted. For example, there is only one chance to set the properties of a history based loft. Once the surface exists, the only way to change the loft settings is to recreate the surface. This will break all downstream history records and is thus potentially an extremely expensive limitation. It is also impossible to add or replace curves from a history loft. Another limitation is the lack of mathematical relationships.
Explicit history tackles these two issues, but at a great expense. It is no longer possible to record it transparently, the history tree has to be specifically constructed by the user. It is impossible to use available commands since they do not expose the options and settings they need to run. This means that for most people, an Explicit History feature will not be useful.
However, the advantages speak for themselves:
The tree is exposed, and can thus in whole or in part be re-used throughout different models.
The components on the tree are exposed and can thus be replaced and adjusted.
The operations are not tied to geometry in the model, it is possible to make a tree which only deals with numbers.
Mathematical and logical relationships can be constructed.
External (to Rhino) sources can be used to retrieve and store data.
Not all of these features are available in the first release, it will take time (lots of time) to expand the feature set of the plugin.
Watch an example animation of the plugin in action.
Download some example Definitions + Rhino files.
Further reading
History components explained
Interface widgets explained
Managing the persistent data records
Managing volatile data inheritance
Data stream matching algorithms
