> I'm working on a small game engine, and as such, I want to create a > level editor for the game. I love the old style Doom level editors, so > that's what I'm going for [1]. Notice in that screenshot the amount > the user can interact with - moving vertices on the grid, creating > lines between vertices, adding/removing objects, etc. > > At the moment, I have a main MapView control, which creates vertices > in an NSArrayController. I have 2 ways of viewing these vertices - one > is to handle rendering them directly in the MapView, and another > approach creates a new VertexView for each vertex, and adds it as a > subview of the MapView. From what I've read online, this is not going > to scale beyond maybe 50 vertices, so I don't think this is an > approach. However, handling *everything* in the MapView itself feels > like it drastically reduces the cohesion of the control.
You can handle everything in one view while still breaking up the handling. For instance, you can have Vertex objects which handle events, passed to them by the MapView, when they are selected. Having one view doesn’t require you to handle all the input in one place—your view just becomes a dispatcher. My 2¢. -Ben _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
