From: Björn P. <bjo...@gm...> - 2008-12-23 23:35:30
|
Hi eberybody, I just recently stumpled upon this project looking for a simple midi-recorder for windows. Looks like something I'd like to get involved in. I am working with a mingw (tdm-4.3) and codeblocks workbench on XP here (not too keen on setting up vc for this) so i tried to go along importing the vc projects in codeblocks, adjusting the compiler-settings, patching the source. I found that this is a pure ansi project, while my wx2.8 being built unicode. So having read about the new wxString implementation in wx2.9 - that has unicode/ansi merged with fancy constructors from char*, std::string etc - I continued with that, patching the source (mostly char* <> wxString conversions). But after some time I had to stop short on this (marked deprecated) proplist thing, that just doesn't want to compile for 2.9 anymore. Long story, just a few questions: - Are there efforts for a mingw port/setup? I do not mean to switch and not for releases (for executable size is pretty bad compared to vc), just as an alternative for the devs. - Could anybody upload a binary (windows)? I'd like to get an idea of what the prop-thing practically does (plan to replace it with something else). - Why no intermediate nightly builds for win32? - What about migrating the wx-version to 2.9 => wx30? Maybe (probably) in a separate branch. Big hello for a start. Looking forward to your opinions on these ideas. But for now: Happy Xmas everybody ! - Björn Pfeiffer |
From: Pete S. <pst...@gm...> - 2008-12-24 00:33:06
|
BP = Björn Pfeiffer BP> Hi everybody, BP> I just recently stumbled upon this project BP> looking for a simple midi-recorder for windows. We're not recording yet, but I'm starting to work with the portmedia/portmidi project to make this happen. BP> Looks like something I'd like to get involved in. Sounds great. BP> I am working with a mingw (tdm-4.3) and codeblocks BP> workbench on XP here (not too keen on setting up BP> vc for this) so i tried to go along importing the BP> vc projects in codeblocks, adjusting the BP> compiler-settings, patching the source. I found BP> that this is a pure ansi project, while my wx2.8 BP> being built unicode. I would be interested in an ANSI + STL wxWidgets 2.8.9 build using MinGW for CodeBlocks. Would you like to take a crack at that? BP> So having read about the new wxString implementation BP> in wx2.9 - that has unicode/ansi merged with fancy BP> constructors from char*, std::string etc - I BP> continued with that, patching the source BP> (mostly char* <> wxString conversions). We don't need this. Note that we build wxWidgets with wxUSE_STL and it gets around this problem. BP> But after some time I had to stop short on this BP> (marked deprecated) proplist thing, that just BP> doesn't want to compile for 2.9 anymore. For now we are sticking with wx 2.8.* until 3.0.* is out and is stable w.r.t. the API. BP> Long story, just a few questions: BP> - Are there efforts for a mingw port/setup? No, but this would be welcome. BP> I do not mean to switch and not for releases BP> (for executable size is pretty bad compared to vc), BP> just as an alternative for the devs. I like the idea because the more platforms/compilers you build a code with, the better the code gets because each platform/compiler highlights different issues. BP> - Could anybody upload a binary (windows)? BP> I'd like to get an idea of what the prop-thing BP> practically does (plan to replace it with BP> something else). I might take a crack at this over the weekend or possibly email you a version directly. BP> - Why no intermediate nightly builds for win32? The code just isn't ready for this. BP> - What about migrating the wx-version to BP> 2.9 => wx30? Maybe (probably) in a separate BP> branch. I would prefer to skip 2.9 and wait until 3.0 is out and stable. To many other problems with Jazz++ to deal with this at the moment. BP> Big hello for a start. Same here :-) BP> Looking forward to your opinions on these ideas. BP> BP> But for now: BP> Happy Xmas everybody ! Merry Christmas to you Björn. Pete |
From: Björn P. <bjo...@gm...> - 2008-12-24 02:31:33
|
Meanwhile I have compiled wx with vc9 according to instructions on the website. That VC was idling around on my harddisk. BTW: I had to give them my e-mail for registering!!! ;-) but... I could not wait to see something. Fine. And: I found a #BUG! :-) ...in MetronomeSettingsDialog.cpp +85 (constructor) Menu: Settings->Metronome << mIndexToName is used (indexed [0]) but empty. As for ansi/unicode: I'll give it a try. Gcc on windows is basically the same as on linux but the mingw/codeblocks approach wo wx has recently gained much momentum on windows, so this might attract more people to jazz++ (how many active devs are around here actually?) On the other hand... I don't know what release-plans are, but by the time jazz++ will be ready for prime-time we might also see wx-2.9 -> 3.0 around. So maybe I'd vote for an intermediate branch, but that's not really important for now, as you stated. As for the deprecated proplist-thingy, what are your plans on this? Ok, enough now. I will spend some time looking into the source, that will keep me busy enough for the next time. Greetings, Björn Am 24.12.2008 01:32 schrieb Pete Stieber: > BP = Björn Pfeiffer > BP> Hi everybody, > BP> I just recently stumbled upon this project > BP> looking for a simple midi-recorder for windows. > > We're not recording yet, but I'm starting to work with the > portmedia/portmidi project to make this happen. > BP> Looks like something I'd like to get involved in. > > Sounds great. > > BP> I am working with a mingw (tdm-4.3) and codeblocks > BP> workbench on XP here (not too keen on setting up > BP> vc for this) so i tried to go along importing the > BP> vc projects in codeblocks, adjusting the > BP> compiler-settings, patching the source. I found > BP> that this is a pure ansi project, while my wx2.8 > BP> being built unicode. > > I would be interested in an ANSI + STL wxWidgets 2.8.9 build using MinGW > for CodeBlocks. Would you like to take a crack at that? > > BP> So having read about the new wxString implementation > BP> in wx2.9 - that has unicode/ansi merged with fancy > BP> constructors from char*, std::string etc - I > BP> continued with that, patching the source > BP> (mostly char* <> wxString conversions). > > We don't need this. Note that we build wxWidgets with wxUSE_STL and it > gets around this problem. > > BP> But after some time I had to stop short on this > BP> (marked deprecated) proplist thing, that just > BP> doesn't want to compile for 2.9 anymore. > > For now we are sticking with wx 2.8.* until 3.0.* is out and is stable > w.r.t. the API. > > BP> Long story, just a few questions: > BP> - Are there efforts for a mingw port/setup? > > No, but this would be welcome. > > BP> I do not mean to switch and not for releases > BP> (for executable size is pretty bad compared to vc), > BP> just as an alternative for the devs. > > I like the idea because the more platforms/compilers you build a code > with, the better the code gets because each platform/compiler highlights > different issues. > > BP> - Could anybody upload a binary (windows)? > BP> I'd like to get an idea of what the prop-thing > BP> practically does (plan to replace it with > BP> something else). > > I might take a crack at this over the weekend or possibly email you a > version directly. > > BP> - Why no intermediate nightly builds for win32? > > The code just isn't ready for this. > > BP> - What about migrating the wx-version to > BP> 2.9 => wx30? Maybe (probably) in a separate > BP> branch. > > I would prefer to skip 2.9 and wait until 3.0 is out and stable. To > many other problems with Jazz++ to deal with this at the moment. > > BP> Big hello for a start. > > Same here :-) > > BP> Looking forward to your opinions on these ideas. > BP> > BP> But for now: > BP> Happy Xmas everybody ! > > Merry Christmas to you Björn. > > Pete > > ------------------------------------------------------------------------------ > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel > |
From: Pete S. <pst...@gm...> - 2008-12-24 05:41:34
|
BP = Björn Pfeiffer BP> Meanwhile I have compiled wx with vc9 according BP> to instructions on the website. That VC was BP> idling around on my harddisk. BTW: I had to BP> give them my e-mail for registering!!! ;-) Wonderful. Enjoy the Microsoft spam. BP> but... I could not wait to see something. Fine. BP> BP> And: I found a #BUG! :-) BP> ...in BP> MetronomeSettingsDialog.cpp +85 (constructor) BP> Menu: Settings->Metronome BP> << mIndexToName is used (indexed [0]) but empty. Update. BP> As for ansi/unicode: I'll give it a try. BP> Gcc on windows is basically the same as on linux BP> but the mingw/codeblocks approach wo wx has BP> recently gained much momentum on windows, so BP> this might attract more people to jazz++ (how BP> many active devs are around here actually?) I'm it. BP> On the other hand... I don't know what BP> release-plans are, There aren't any. BP> but by the time jazz++ will be ready for BP> prime-time we might also see wx-2.9 -> 3.0 BP> around. So maybe I'd vote for an BP> intermediate branch, but that's not BP> really important for now, as you stated. BP> BP> As for the deprecated proplist-thingy, what BP> are your plans on this? Replace user interface components that use it with modern wxWidgets controls. Pete |
From: Björn P. <bjo...@gm...> - 2008-12-24 15:44:06
|
Am 24.12.2008 06:41 schrieb Pete Stieber: > BP = Björn Pfeiffer > BP> Meanwhile I have compiled wx with vc9 according > BP> to instructions on the website. That VC was > BP> idling around on my harddisk. BTW: I had to > BP> give them my e-mail for registering!!! ;-) > > Wonderful. Enjoy the Microsoft spam. > > BP> but... I could not wait to see something. Fine. > BP> > BP> And: I found a #BUG! :-) > BP> ...in > BP> MetronomeSettingsDialog.cpp +85 (constructor) > BP> Menu: Settings->Metronome > BP> << mIndexToName is used (indexed [0]) but empty. > > Update. Did that. Fine. > BP> As for ansi/unicode: I'll give it a try. The CB projects are ready to go. It took some patches in the source to make it compile and run but the vc-build is still fine. I will pm you the patch and the new project-files soon. > BP> Gcc on windows is basically the same as on linux > BP> but the mingw/codeblocks approach wo wx has > BP> recently gained much momentum on windows, so > BP> this might attract more people to jazz++ (how > BP> many active devs are around here actually?) > > I'm it. That's fine, the lonesome-cowboy-story. ;-) While Jazz++ is not 'exactly' the tool I was looking for (and maybe never will be) I am really eager to get my hands on some music/midi software project. And this really matches my profile, so to say. Think I might be in it too now, joining the ride for some part of the way at least. > BP> On the other hand... I don't know what > BP> release-plans are, > > There aren't any. Excellent. No schedule, no stress, no panic. A wide open space of possibilities. > BP> but by the time jazz++ will be ready for > BP> prime-time we might also see wx-2.9 -> 3.0 > BP> around. So maybe I'd vote for an > BP> intermediate branch, but that's not > BP> really important for now, as you stated. > BP> > BP> As for the deprecated proplist-thingy, what > BP> are your plans on this? > > Replace user interface components that use it with modern wxWidgets > controls. I might take a look into this. Can you give me a quick overview of the widgets affected? XMas-Greetings, Björn |
From: Pete S. <pst...@gm...> - 2008-12-31 05:06:12
|
BP = Björn Pfeiffer BP> The CB projects are ready to go. It took some BP> patches in the source to make it compile and BP> run but the vc-build is still fine. I will BP> pm you the patch and the new project-files soon. I got them. I noticed you patched some code that isn't built in the VS version. This got me looking where the deprecated wx prop* stuff was used and what it would take to update those UI components. I just uploaded an old version of Jazz++ so you (and anyone else listening who uses a Windows box) could download it to see how the code used to work. Do you think you'll have time to convert any dialog boxes for me? I'm going to convert the event filter dialog tomorrow. Maybe that can be an example for the conversion process. Any help converting dialog boxes would be welcome. Hope everyone has a great new year, Pete |