Explicit History Plugin for Rhino4 外在的历史记录插件

来之 https://shaper3d.5d6d.com/viewth ... 1&extra=#pid770Rhino Wiki Shaper3d 整理
____________________________________________________________________


下载这个插件
注意这个插件只能在Rhino4.0 SR2上运行.
_________________________________________________________________________________________
安装介绍
1 下载这个Zip文件,然后解压到你想放的任何地方
2 你必须确定文件夹内的文件结构没有变动,放置位置没有关系
3 启动Rhino
4 拖跩文件 ExplicitHistory.rhp到你的Rhino窗口
5 _ExplicitHistoryEditor命令将会被激活
__________________________________________________________________________________________
为什么需要外在的历史记录?
Rhino4.0本身具有内建的基础历史记录特征,这是一种非插入式的伴随可以自动更新某些建模步骤工作流程,
当前Rhino4.0的历史记录功能的执行是比较隐藏的,你执行了就会记录.这样意味着建模时并不需要额外的动
作,正是这样我们想看到在Rhino中有更多没有额外限制的更多功能,然而,隐藏的历史记录不能做一 些基于
约束的造型的工作.

首先对于Rhino用户来说历史记录结构树是隐藏的.不同的历史记录步骤是不能调整.例如,是不是只有一次
机会来设置loft命令的历史记录属性,一旦这个面完成了,想修改这个loft的面就只有重建这个面,这将会
打断所有下游的历史纪律,因此是个非常大的限制,从当前的历史记录你既不可能增加也不可以替换loft线,
另一个限制是，缺乏数学关系。

外在的历史记录解决好这两个问题但是是个大的牺牲.现在不能透明的记录历史记录,但历史记录结构树
对于用户来说是个特别的结构,历史树必须由用户具体地修建,这是不可能利用现有的命令,因为他们不能
揭示需要运行的选项和设置.这意味着，对大多数人来说，一个外在的历史功能不会有用。

然而，优势不言自明：
模型树是清楚表现的,并且能够全部或者部分的重新使用所有的模型.
模型树的所有组成部分都是清楚外显的,并且这样就可以重新替换和调试.这个操作对于模型的任何几何部
分都不受限制,几个数字符号就可以组建一个模型树,数学和逻辑关系都可以购置.对于Rhino外部的资源都
可以使用和保存数据.

在第一个SR版本并不是所有的特征都可以使用,我们讲会花费一些时间来完成这个插件的所有特征

看看这个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

来之Rhino Wiki

[ 本帖最后由 jessesn 于 2007-10-26 19:22 编辑 ]

谢谢斑竹   下来看看

呵呵　　有深入研究吗？