User forums > Nightly builds
The 12 october 2006 build is out.
killerbot:
good idea Thomas, but we have made a few changes to the code ...
eranif:
I am up for it, I tried SVN (Takeshi convinced me for other project to use it) and I love it.
Any suggestion for a good repository place ?
Eran
thomas:
--- Quote from: eranif on October 13, 2006, 10:56:48 am ---Any suggestion for a good repository place ?
--- End quote ---
Uh... the same place where it is now? ;)
I figure that Sourceforge offers Subversion access now. I have never tried it, but they said they do. So you would expect they have a "convert your repository" button somewhere in the admin section.
If they don't, you'll have to run one of those cvs2svn conversion tools yourself (there is half a dozen of them available on the internet). It is quite harmless, worked nicely for the Code::Blocks repository.
But of course, you can also use BerliOS :)
Yiannis: Which tool was it we used back then?
--- Quote from: killerbot on October 13, 2006, 09:55:57 am ---good idea Thomas, but we have made a few changes to the code ...
--- End quote ---
If everything works as it should, that should even be not a problem. In theory, Subversion should simply merge our changes. However, I only experienced lately that merging isn't always working nicely :lol:
What do we need to change anyway, shouldn't it work out-of-the box, too?
From what I see while quickly scanning over the patch, it mostly changes include paths, registers one additional key event (for whatever it's good?), and replaces an awful lot of seemingly identical lines (--> changed indentation from tab to spaces?).
Is there no way we could get this to work otherwise?
mandrav:
--- Quote ---Yiannis: Which tool was it we used back then?
--- End quote ---
Yes, some perl script to convert it. I did it at home and then uploaded the (new) svn repository to berlios. I believe sourceforge has a more streamlined conversion process though.
--- Quote ---What do we need to change anyway, shouldn't it work out-of-the box, too?
From what I see while quickly scanning over the patch, it mostly changes include paths, registers one additional key event (for whatever it's good?), and replaces an awful lot of seemingly identical lines (--> changed indentation from tab to spaces?).
--- End quote ---
Our changes are not that simple ;).
For example, the latest patching I did in wxFNB was to move the EVT_PAGE_SELECTION_CHANGED and EVT_PAGE_SELECTION_CHANGING events to the SetSelection() function, instead of in the OnLeftDown(). The way it was, we were only informed about page selection changing only when the user used the mouse to change pages. But if you used Ctrl-Tab/Shift-Ctrl-Tab we never knew you changed the page, causing all kinds of side-effects for us...
thomas:
--- Quote from: mandrav on October 13, 2006, 12:13:17 pm ---Our changes are not that simple ;).
For example, the latest patching I did in wxFNB was to move the EVT_PAGE_SELECTION_CHANGED and EVT_PAGE_SELECTION_CHANGING events to the SetSelection() function, instead of in the OnLeftDown(). The way it was, we were only informed about page selection changing only when the user used the mouse to change pages. But if you used Ctrl-Tab/Shift-Ctrl-Tab we never knew you changed the page, causing all kinds of side-effects for us...
--- End quote ---
But why is the rum gone!
I mean, this is a change that would better be placed in the *real* codebase, as those problems will affect any application, not just ours. I think Arto won't object to adopt changes that are obviously advantageous to everybody ;)
Are there any other major changes that we need besides that?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version