| Build model change [message #595881] |
Fri, 12 February 2010 08:49  |
Eclipse User |
|
|
|
Hi,
I just checked in a slightly refactored build model.
The BuilderOutput construct was wrong.
The CompoundPathVector and PathVectorElement are now replaced by a
ConditionalPathVector (plays the role of old PathVector and
CompoundPathVector), and the old PathVectorElement is renamed to PathVector.
New structure is more straight forward, and allows the PathVectors to be
referenced when creating the evaluated output instead of having to
create new instances to get rid of expressions and conditionals in the
evaluated output.
Regards
- hnrik
|
|
|
| Re: Build model change [message #595906 is a reply to message #595881] |
Sat, 13 February 2010 18:12  |
| Eclipse User |
|
|
|
An additional model change:
The BeeModel (top level element in a b3 file) now has the ability to
have more than one BuildUnit. The name of the feature changed from
"body", to "buildUnits" as a consequence.
- henrik
On 2/12/10 2:49 PM, Henrik Lindberg wrote:
> Hi,
> I just checked in a slightly refactored build model.
> The BuilderOutput construct was wrong.
>
> The CompoundPathVector and PathVectorElement are now replaced by a
> ConditionalPathVector (plays the role of old PathVector and
> CompoundPathVector), and the old PathVectorElement is renamed to
> PathVector.
>
> New structure is more straight forward, and allows the PathVectors to be
> referenced when creating the evaluated output instead of having to
> create new instances to get rid of expressions and conditionals in the
> evaluated output.
>
> Regards
> - hnrik
|
|
|
Powered by
FUDForum. Page generated in 0.03368 seconds
Home