Custom visible objects with editable parameters

I am developing a tools for making design process in our company easier since some time but i hit the wall with possibilities of improvement. My tool is placing curves, circles, hatches, texts and another objects on our models and everything is fine until some additional external requirements appear, that require editing of the design.When I am generating objects, I have a lot of structured data generated by algorithms about how everything should behave and be placed. When python script is finished, all this data is lost. I have just curves and hatches. Then it is hard to edit design, only possibility is to use commands designed for curves, not my earlier structures. I was thinking about ways of handling it. One of them is to have database always attached to rhino model, but this solution would require to exchange multiple files instead of just one rhino file and this is not the easiest for everyone. Second idea is to code my structures into internal variables of curves, for example store info inside names of curves and then rebuild structure in memory based on this names, but this needs a lot of work and probably is not the best solution.
I want to ask of this is possibility to define custom objects in rhino like curves, or another default objects that I can create, that have their own variables, methods, and that I can put into 3d space and then select as input when using some script. I should have still access to it’s variables, so I can edit them.

And second question is about if such objects can be hierarchical, for example if I can make object “zone”, which will have inside “lines” with “circles” attached to them.

I don’t know if I am clear, but the result I want to achieve is having object on drawing which can store custom data, for example number of circles in a row, distance from another object, direction of arrows and so on, so it can be edited and object will change

I believe object attributes and Elefront would be your friend.

I’m thinking myself about conversion to this approach.


Its pretty awesome & i will certainly help where i can if you have any questions.

Have to say I’m not that smart and it took me some time to understand philosophy behind it but man…this is just mind blowing. At the moment I’m having a bit of the fight with Rhino to stop crashing every time when I attach attributes from csv to rhino geometry with grasshopper opened and looking for value and key.

Thank you a lot.
There is answer to my question. I will have to switch from normal rhino python to grasshopper but i think I will manage to do it and find a lot of ways to improve.