[Moose-dev] Re: Blueprint diagrams

I think that we should stick to builders. Because you anyway have some questions open like should script create view or populate existing one and so on. If we create a builder, then potential users will work with familiar interface + will be able to combine your work with other visualisations and so on. I was really frustrated with Roassal 1 because everyone was creating his own thing, and then one builder returned a view, another one - view stack, and some of them required you to provide a view. Uko On 01 Sep 2014, at 06:51, Tudor Girba &lt;tudor(a)tudorgirba.com&gt; wrote: Hi, Exactly. A builder offers an API with which for the same input you can produce multiple outputs. If you can only produce one output then you probably have a script in your hand. On the other hand, if you do not place the script in the class of the input object, then you probably want to have a separate class for the visualization. In that case, it might still make sense to have this class be a subclass of builder. What do you think? Doru On Mon, Sep 1, 2014 at 12:02 AM, Alexandre Bergel < alexandre.bergel(a)me.com&gt; wrote: -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev