Hey!
Ive begun writing my own level editor in python. Im kind of new to programming, but Im making progress. But I have two of questions on how to structure an application like this.
First question:
Im torn between making a brush class that holds all the data for a brush, and a more fluid data structure where a brush object has poly objects, that has three or more vertex objects and so on.
Or possibly making a simple list for the vertexes and then have the polys refering to it. The latter would simplify OBJ export which is the format Im looking to make the default.
What kind of data structure would an exprienced 3d programmer make?
Second question:
The TK canvas widget is not 100% acurate in terms of scale and pan factors so I had to wrap it in a class that resets it and redraws that grid/geometry when needed. This worked out surprinsingly well. (I had a genuine YAY moment when it worked)
Question is, how much functionality should go into this class. Im having a hard time drawing the line between where the display ends and the data begins.
Fuzzy, I know.
In practical terms, what I cant get clear on is whether its best to have the data and display talking directly with eachother, or have all their communicating mediated by the event handlers. On the one hand, the Display class might get messy and the data would be less safe if hooked up directly to the display. One the other hand, the display always redraws based on whats in the data class so why bother with a middle man (and lots of extra typing)?
Any insights appreciated