Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: mandrav on July 09, 2005, 07:16:09 pm
-
I was thinking: maybe it's time to officially switch to wxWidgets-2.6.1?
The code is stable and I see no reason to delay it any longer.
Also, I 've added docking windows support using wxDockIt in my local sources. It's working great :lol:
(http://www.codeblocks.org/images/cb-wx26-thumb.png) (http://www.codeblocks.org/images/cb-wx26.png)
So, is it time to add all these changes in HEAD?
What do you all think?
Yiannis.
-
Wow! Look great! I think it is definitly must go to HEAD :)
-
I agree that we should switch.. :cry: now I have to compile wx 2.6.1 :cry: it takes to long... I am going to get a holliday. (probably not working on anything next for weeks (and last x weeks :oops:)
-
I think thats a good idea. Code::Blocks is heavily dependent on it, so why not move to the latest stable when possible?
The docked windows look awesome, a great feature IMHO
I agree that we should switch.. :cry: now I have to compile wx 2.6.1 :cry: it takes to long... I am going to get a holliday. (probably not working on anything next for weeks (and last x weeks :oops:)
I didnt count the exact time, but probably it took over 1 hour to build the library (shared, non-monolithic) and the samples (with plain mingw)
-
Absolutely, great improvement :)
-
I didnt count the exact time, but probably it took over 1 hour to build the library (shared, non-monolithic) and the samples (with plain mingw)
I know, but at 11:30 pm when I want to go to bed, it is a long time :P
-
I know, but at 11:30 pm when I want to go to bed, it is a long time :P
So just go to bed, but leave the compile running. Come back in the morning and it'll (hopefully) be finished. That's how I usually perform long compiles. (For "normal" long compiles. Compiling Gentoo from source may take longer (depending on computer speed), but that's not just a long compile but a LONG compile ;))
-
I can't sleep with the computer running :P
btw. mandrev? when will the project switch to 2.6.1 in the cvs? and wich projectfile will there be used?
-
Oh, the only problem I can see is the logo of the application (and @ home the problem that I could not see any open projects. When I open one, I could use my right mouse button to get the context menu..)
-
btw. mandrev? when will the project switch to 2.6.1 in the cvs? and wich projectfile will there be used?
That's what I 'm asking here. How people feel: should we switch now?
Yiannis.
-
yes - why not ?
-
Yes, we should switch. The problems I experience are probably my own problems :)
And the next release? when will that be :P
-
That's what I 'm asking here. How people feel: should we switch now?
IMHO you should switch, it's the next logical step!
-
Yes, it is time!
I wanna have that dockable version working here with wxWidgets 2.6.1 too :)
-
Wait, what happened with Ceniza's bug reports about the toolbar crash... oh wait, you're using wxDockit, right? :P
Well some minor details with the toolbar. There's a new debug icon (step out), but it's 32x32 only, and I have my C::B set to 16x16, so it looks kinda ugly.
Also, what changes are done to the sourcecode? Are they reversible, just in case something happens? A week of tests with the wxDockit library seem too short to me. (Then again, that's only MHO ).
Finally, i've exchanged a few mails with one of the people who reported the wx2.5+ bugs - he's not available for two weeks so we can close the bugs in question.
I'd say we should keep the wxdockit as a separate branch, so the devs can still download it and test it, while keeping and working on the current branch. (Just be careful of not committing to the wrong branch :roll: )
-
quote="rickg22"].
I'd say we should keep the wxdockit as a separate branch, so the devs can still download it and test it, while keeping and working on the current branch. (Just be careful of not committing to the wrong branch :roll: )[/quote]
I agree. I think we should start a new branch with wx2.6 as the official version of wx, and start working on adding the new features such as docking windows. Call this the development branch .. or whatever... I think the current branch we should release as 1.0 and leave it open. No new features should go to this branch.. just bug/security fixes and name somebody as a "maintainer" of this branch. This leaves the rest of the developers to start work on the 2.6 branch untill it becomes stable (read: production ready).
A "feature set" should be devised.. and once those features have all been implemented, then we make a branch again.. close the wx2.4 branch and leave the wx2.6 branch as stable.. and start another "feature set"...
just my opinion.
-
Thank you all for the feedback :)
CVS has been branched and the announcement is here (http://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&p=3089#3089).
Yiannis.
-
Perhaps it is a good idea to post a news item on sourceforge and the website. ;)
-
Thank you all for the feedback :)
CVS has been branched and the announcement is here (http://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&p=3089#3089).
Yiannis.
Thanks Yiannis. I think this will greatly enhance Code::Blocks development.