frog-o,
I 'm really having a hard time to understand your posts. Maybe it's not your fault but my poor English. Nevertheless, I can't understand much of what you 're saying OR you can't understand much of what I 'm saying.
This will be my last post on the subject. I 'm tired of explaining it in so many different threads AND in the mail I sent you.
Here goes then:
I had no problem leaving wxSashLayoutWindow in it. I just did not know you wanted to keep it I think it crap and was i side efect of mdi i did not know any better. I will just say the following on why i want to get rid of it and leave it go at that. wxSashLayoutWindow seem messy for the folowing reson. I mite be wrong if so please correct me if i am.
1. It need an onsizeevent
2. you need to manualy place all windows.
3. you need to call doupdatelayout fuction or equivilent. evertime something need painted or relayed out.
4. alot more code is add becuse of this.
5 it harder to implement xrc mabe imposible.
The creation happens in CreateIDE(), just a small function.
DoUpdateLayout() is called when the frame is resized.
Now, why you keep thinking this is a lot of work is beyond me...
XRC is good for dialogs that don't change, like
all dialogs in C::B. But the main frame needs to be customizable at run-time, like the recently added feature of repositioning the manager tree (how would you do that with XRC without too much effort???).
XRC is
not good for dialogs that change at run-time. Is there something obvious I 'm missing?
Example: Launch C::B and press F2 and then Shift-F2. Wow! An empty frame! What do I need the XRC for???
That's what I mean when I say "change at run-time".
And when a docking library is added, XRC will have no place in the main frame anyway...
That's all I 'm going to say about using XRC in the main frame. Please don't ask me again on this subject. Unless you have a good explanation of what (
and how) we 'll gain.
This project is just to big for one person and i think we need cvs to do it
when i say this project I did not mean for codeblock i ment the conversion of cbeditor wxMDIchildwindow to wxnotebook (as my title said). and the one person is anyone who try
When *I* read "project", I think of C::B. But I guess that's just me.
converting cbeditor to wxnotebook
. I think it need it own workspace in the cvs tree and is the conversion need, is to big to do all at once
For someone who doesn't know the codebase as well as I do, it may be hard to do the conversion.
I converted it earlier today, in less than two hours (including debugging it). I will commit my changes tomorrow.
PLEASE MANDRAV TRY TO UNDERSTAND ME A LITTLE MORE AND TRY TO LOOK AT THING FROM A DIFFERT POINT OF VIEW. If something dose not sound right it is probbly not.
And why
exactly are you shouting at me??? This is
not polite at all :evil:
Anyway, I see that Rick is understanding you better than I do, so please ask him any questions you might have. As I said, I seem to misunderstand you too often and then you shout at me. Thank you very much...
Yiannis.