From: tiennou <tie...@gm...> - 2007-02-21 14:16:54
|
Le 21 f=C3=A9vr. 07 =C3=A0 13:50, ti...@da... a =C3=A9crit : >> Hmm, my approach had the >> advantage of not separating the Shapes/ ShapesEditor > Actually, I see this separation as a good thing... > >> =46rom my point of view, I'm not really fond of the >> wxDocument way, but it can be enhanced by subclassing >> stuff, so that's not really a problem... > There are many things I don't like about wx, too. But from > experience I think that the final result is good if you try > to follow wx accurately. Let's see if this holds also with > this wxDoc stuff... I'm commiting right now. I've made some progress... I think reusing the ShapeEditor code won't =20= be a problem, but as I need loading Shapes file to continue, I moved =20 to trying to actually load data the wxDoc way... I'm in a big need of help there, because I'm thinking of Object-=20 Orienting the Marathon structs so I could just write =20 ShapesDocument::LoadObject(), and it will issue =20 ShapesChunk::LoadObject(), which will work as a a chain... I need =20 some help from you to (re)do that. I'm also trying to remove everything std (vectors principally) and =20 changing them into wxList subclasses to ensure portability... It =20 won't be a problem for you ? tiennou |