Re: [Shapefusion-devel] status

[Tito D. C. <ti...@da...>]

On Mon, 2007-02-19 at 19:26 +0100, tiennou wrote:
> I guess you were right, changing to a wxDocument oriented approaches
> is a real pain, because Shapes and ShapesEditor must be separated, and
> much things have to be redone...
Doh! It's real!

> One of the things that bother me is that I could use what has been
> done, but I need to convert your BigEndianBuffer stuff to a
> wxDataStream to put reading and loading into the LoadObject/SaveObject
> methods of wxDocument... I haven't been able to find a tutorial on
> this (except in the wxWidgets book, which I don't have).
Yeah, wx documentation sucks. Tried to get the book with p2p? ;-)

I'll look at wxDocument too and try to produce some ideas, and will let
you know if I have some. In the meantime, maybe you could write your own
Sounds editor by starting a new wxDocument app, then we could "learn"
from it the best way to convert ShapeFusion. And eventually we could
merge your editor with ShapeFusion (that should be easy since we only
need to put the classes together). Once we understand how the whole
thing works I can recode BigEndianBuffer and all if you don't feel.

We could also go with your previous multi-document approach, but I'm not
sure it's a good way to do it... I prefer the wxDocument way (no matter
how difficult it could be to convert existing code) because I think the
code would be a lot nicer and more organized. Yeah, I should have
started with that already in mind.

Happy hacking
Tito
-- 
Physics is reverse engineering