search

tt-acm / Spectacles.GrasshopperExporter

A Spectacles Exporter for Grasshopper
MIT License
7 stars 12 forks source link

Attribute names should not have to be unique #23

Open mnaugle-tt opened 9 years ago

mnaugle-tt commented 9 years ago

@anagpuyol

We should allow an attribute name to be repeated, this would be my hacky way of getting around issue #22 (which I shouldn't have to do, but we should allow what is shown in the screen shot if someone wanted to do it this way for some reason).

image

anagpuyol commented 9 years ago

@bhowes-tt do you think that adding more than one value to the same attribute name could be an issue on the web side? I'm thinking in terms of retrieving values by key (attribute name)...?

bhowes-tt commented 9 years ago

@anagpuyol - I'm not 100% sure but I think it would be fine on the web side.

In general I think this is weird... @mnaugle-tt --- why do we need to allow multiple attributes of the same name? Is the component just less error prone that way?

I can't imagine a useful scenario, but if you just want the components to solve, I might be able to stomach it. But, let the record show that it feels like pushing :hankey: downhill to me ;]

mnaugle-tt commented 9 years ago

yes this was mainly about having it solve more easily for those that don't understand grasshopper iteration (and especially datatree's if that is the way to handle this per #22 )