From: Leland <ja...@ho...> - 2008-03-16 02:50:44
|
I'd be interested in a Jazz revival too. I have the CVS code from about about September '07 running on wxWidgets 2.6/2.8 on the Mac. It even plays via the latest portmidi. I've gotten a lot of the incomplete dialogs "working" but not necessarily correctly...I just wanted to get them to compile and accept input. While I develop on the Mac, my intentions of getting Jazz++ working was actually targeting Windows with the main goal of making it accessible to visually impaired users. I haven't gotten to the point of integrating accessibility yet though and thought contributing to the revival might be more productive to begin with. For background, I currently participate in Audacity development and was responsible for making it more accessible to VI users. Holler, if y'all need some help. I will be finishing another project on March 31st and I'll be starting back up on my Jazz work as I hope to have something at least partially usable by June for my wife's birthday. Leland |
From: Pete S. <pst...@ve...> - 2008-03-16 03:14:16
|
L = Leland L> I'd be interested in a Jazz revival too. I have the CVS L> code from about about September '07 running on wxWidgets L> 2.6/2.8 on the Mac. I converted the CVS repository to Subversion in January. You can access it by following the instructions at http://jazzplusplus.sourceforge.net/subversion/ L> It even plays via the latest portmidi. I've gotten a lot L> of the incomplete dialogs "working" but not necessarily L> correctly...I just wanted to get them to compile and accept L> input. L> L> While I develop on the Mac, my intentions of getting L> Jazz++ working was actually targeting Windows with the L> main goal of making it accessible to visually impaired L> users. The current Subversion trunk compiles on a Windows box using XP or Vista using either Visual Studio .NET 2005 (VS8) or Visual Studio .NET 2008 (VS9) and works with wxWidgets 2.8.7. I have the same source building on Fedora 8 using GCC 4.1.2 and the WX_2_8_BRANCH of wxWidgets. The trunk is only partially implemented, but has the ability to read and play a MIDI file. L> I haven't gotten to the point of integrating accessibility L> yet though and thought contributing to the revival might L> be more productive to begin with. Sounds good. L> For background, I currently participate in Audacity L> development and was responsible for making it more L> accessible to VI users. I am a frequent user of Audacity on Windows and Linux boxes. L> Holler, if y'all need some help. I will be finishing L> another project on March 31st and I'll be starting back L> up on my Jazz work as I hope to have something at least L> partially usable by June for my wife's birthday. Do you have access to a Windows box? Today I made a post on the users list looking for "innocent victims" to attempt to build the version of the code in the trunk so that I can add decent build instructions on the web site. If you get an opportunity to try this I would be willing to help you. Leland, thanks for your interest in Jazz++, Pete |
From: Leland <ja...@ho...> - 2008-03-16 03:24:11
|
On 3/15/08 10:14 PM, "Pete Stieber" <pst...@ve...> wrote: > Do you have access to a Windows box? > Actually, I work on Windows, Linux, and Mac. I just prefer to do initial work on the Mac and then migrate it to the others. I've recently been working with OpenSolaris as well, but don't intend to do much with that after March 31st. > Today I made a post on the users list looking for "innocent victims" to > attempt to build the version of the code in the trunk so that I can add > decent build instructions on the web site. If you get an opportunity to > try this I would be willing to help you. > I'll give it a try. I too have VS8 (Pro) and VS9 (Express) installed, so I'll try VS8 first. Leland |
From: Pete S. <pst...@ve...> - 2008-03-16 03:37:33
|
PS = Pete Stieber PS>> Today I made a post on the users list looking for PS>> "innocent victims" to attempt to build the version PS>> of the code in the trunk so that I can add decent PS>> build instructions on the web site. If you get PS>> an opportunity to try this I would be willing to PS>> help you. L = Leland L> I'll give it a try. I too have VS8 (Pro) and VS9 L> (Express) installed, so I'll try VS8 first. Great. I appreciate it. The VS8 solution is under jazzplusplus/trunk/jazz/vc8 and it called JazzPlusPlus-VC8.sln. It uses an environment variable called EXT_PKGS to find the wxWidgets package. I typically create C:\ExternalPackages and put the wxMSW version of wxWidgets in this directory. You will see $(EXT_PKGS)\wxMSW-2.8.7-VC8 in the project setting in various places. Let me know if you have any difficulties. Thanks again, Pete |
From: Leland <ja...@ho...> - 2008-03-16 03:52:14
|
On 3/15/08 10:37 PM, "Pete Stieber" <pst...@ve...> wrote: > > jazzplusplus/trunk/jazz/vc8 > > and it called JazzPlusPlus-VC8.sln. It uses an environment variable > called EXT_PKGS to find the wxWidgets package. I typically create > C:\ExternalPackages and put the wxMSW version of wxWidgets in this > directory. You will see $(EXT_PKGS)\wxMSW-2.8.7-VC8 in the project > setting in various places. > > Let me know if you have any difficulties. > Will do. Leland |
From: Leland <ja...@ho...> - 2008-03-16 04:20:45
|
On 3/15/08 10:37 PM, "Pete Stieber" <pst...@ve...> wrote: > > Let me know if you have any difficulties. > Awesome...plays like a charm. I see you took the smart approach (unlike me) and pulled most of the incomplete dialogs and wound up with a decent base. There were a couple of build problems. The first was related to "cout" not being defined. Just added an include for iostream to get around it. The other was a few of these: 1>------ Build started: Project: A JazzPlusPlus Application, Configuration: Debug GUI VC8 Win32 ------ 1>Compiling... 1>Audio.cpp 1>..\src\Audio.cpp(956) : error C2666: 'wxDialog::wxDialog' : 2 overloads have similar conversions 1> C:\Documents and Settings\Administrator\My Documents\wxMSW-2.8.7\wxMSW-2.8.7-VC8\include\wx/msw/dialog.h(105): could be 'wxDialog::wxDialog(wxWindow *,const wxString &,bool,int,int,int,int,long,const wxString &)' 1> C:\Documents and Settings\Administrator\My Documents\wxMSW-2.8.7\wxMSW-2.8.7-VC8\include\wx/msw/dialog.h(33): or 'wxDialog::wxDialog(wxWindow *,wxWindowID,const wxString &,const wxPoint &,const wxSize &,long,const wxString &)' 1> while trying to match the argument list '(wxWindow *, , const char [16])' 1>Build log was saved at "file://c:\Documents and Settings\Administrator\My Documents\jazzplusplus\trunk\jazz\vc8\Debug GUI VC8\BuildLog.htm" 1>A JazzPlusPlus Application - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Just wrapped the title in a wxString() to get it to build. Leland |
From: Pete S. <pst...@ve...> - 2008-03-16 15:35:22
|
PS = Pete Stieber PS>> Let me know if you have any difficulties. L = Leland L> Awesome...plays like a charm. I see you took the L> smart approach (unlike me) and pulled most of the L> incomplete dialogs and wound up with a decent base. L> L> There were a couple of build problems. The first L> was related to "cout" not being defined. Just L> added an include for iostream to get around it. I don't have this problem. I just did a clean build and didn't get any complaints. Could you let me know where (which source module) you had to add the include? L> The other was a few of these: L> L> 1>------ Build started: Project: A JazzPlusPlus Application, L> Configuration: Debug GUI VC8 Win32 ------ L> 1>Compiling... L> 1>Audio.cpp L> 1>..\src\Audio.cpp(956) : error C2666: 'wxDialog::wxDialog' : 2 L> overloads have similar conversions L> 1> C:\Documents and Settings\Administrator\My L> Documents\wxMSW-2.8.7\wxMSW-2.8.7-VC8\include\wx/msw/dialog.h(105): L> could be 'wxDialog::wxDialog(wxWindow *,const wxString L> &,bool,int,int,int,int,long,const wxString &)' L> 1> C:\Documents and Settings\Administrator\My L> Documents\wxMSW-2.8.7\wxMSW-2.8.7-VC8\include\wx/msw/dialog.h(33): or L> 'wxDialog::wxDialog(wxWindow *,wxWindowID,const wxString &,const wxPoint L> &,const wxSize &,long,const wxString &)' L> 1> while trying to match the argument list '(wxWindow *, , const L> char [16])' L> 1>Build log was saved at "file://c:\Documents and L> Settings\Administrator\My Documents\jazzplusplus\trunk\jazz\vc8\Debug L> GUI VC8\BuildLog.htm" L> 1>A JazzPlusPlus Application - 1 error(s), 0 warning(s) L> ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== L> L> Just wrapped the title in a wxString() to get it to build. After looking at all of the errors and warnings you posted, I believe I know what is causing the problem. I'm guessing I built wxWidgets with different options than you. I change some settings in setup.h before running nmake with the Microsoft tools. Here's how I build wxWidgets... 1. Download wxMSW-2.8.7.zip from the wxWidgets web site. 2. Extract the zip file to C:\ExternalPackages. Extracting creates a wxMSW-2.8.7 directory directly under C:\ExternalPackages. 3. Change the name of the top-level wxWidgets directory to wxMSW-2.8.7-VC8 so I can have other versions of wxWidgets built with other compilers in parallel with this directory. 4. Download wxWidgets-2.8.7-CHM.zip from the wxWidgets web site. 5. Extract the zip file to C:\ExternalPackages\wxMSW-2.8.7-VC8. This installs the compiled HTML help files for wxWidgets and tex2rtf. 6. Download wxWidgets-2.8.7-HTML.zip from the wxWidgets web site. 7. Extract the zip file to C:\ExternalPackages\wxMSW-2.8.7-VC8. This installs the HTML help files for wxWidgets and tex2rtf. 8. Make the following changes to C:\ExternalPackages\wxMSW-2.8.7-VC8\include\wx\msw\setup.h: Macro From To WXWIN_COMPATIBILITY_2_6 1 0 wxUSE_STD_IOSTREAM 0 1 wxUSE_IOSTREAMH 1 0 wxUSE_GLCANVAS 0 1 We don't really need the OpnGL code for this project, but I use it on other projects. I want to eventually change wxUSE_STL from 0 to 1, but a while ago there was a bug reported in this implementation on the wxWidgets developers list. 9. Edit C:\ExternalPackages\wxMSW-2.8.7-VC8\include\wx\msw\wx.rc and comment out the following line. #include "wx/msw/wince/wince.rc" 10. Use Start | All Programs | Microsoft Visual Studio .NET 2005 | Visual Studio .NET Tools | Visual Studio .NET 2005 Command Prompt to start a console session. 11. Ensure that the command-line compiler and tools (including nmake) are installed and ready to run. 12. Change directory to C:\ExternalPackages\wxMSW-2.8.7-VC8\build\msw. 13. Build the debug static version of the wxWidgets libraries by typing: nmake BUILD=debug SHARED=0 USE_OPENGL=1 -f makefile.vc 14. Build the release static version of the wxWidgets libraries by typing: nmake BUILD=release SHARED=0 USE_OPENGL=1 -f makefile.vc 15. Remove the build directories (vc_msw and vc_mswd) under c:\ExternalPackages\wxMSW-2.8.7-VC8\build\msw. 16. Change directory to C:\ExternalPackages\wxMSW-2.8.7-VC8\utils\tex2rtf\src. 17. Build the release static version of tex2rtf by typing: nmake BUILD=release SHARED=0 -f makefile.vc 18. Create a directory for the tex2rtf binaries under the wxWidgets distribution (c:\ExternalPackages\wxMSW-2.8.7-VC8\bin). 19. Move the tex2rtf binaries from c:\ExternalPackages\wxMSW-2.8.7-VC8\utils\tex2rtf\src \vc_msw. to c:\ExternalPackages\wxMSW-2.8.7-VC8\bin. 20. Remove the build directory (vc_msw) under c:\ExternalPackages\wxMSW-2.8.7-VC8\utils\tex2rtf\src. Leland, I hope you had the patience to follow all of that ;-) I really appreciate your attempt to build the code and report the problems you had. This is exactly what I'm looking for in terms of build feedback. I need to post the instructions listed above on the Jazz++ web site so others understand what I'm up to. I know this is asking a lot, but if you could build version 2.8.7 of wxWidgets described above and try it with the code in SVN I would really appreciate it. Thanks again for the very useful feedback, Pete |
From: Leland <ja...@ho...> - 2008-03-16 18:40:57
|
On 3/16/08 10:35 AM, "Pete Stieber" <pst...@ve...> wrote: > I don't have this problem. I just did a clean build and didn't get any > complaints. Could you let me know where (which source module) you had > to add the include? These needed the include: Dialogs.cpp EventWindow.cpp MouseAction.cpp Player.cpp PropertyListDialog.cpp And these needed the wxString(): Audio.cpp GuitarSettingsDialog.cpp Harmony.cpp This was with a stock Widgets build. After rebuilding according to your instructions (which worked perfectly), these changes were not needed. Leland |
From: Pete S. <pst...@ve...> - 2008-03-16 19:13:49
|
PS = Pete Stieber PS>> I don't have this problem. I just did a clean build PS>> and didn't get any complaints. Could you let me know PS>> where (which source module) you had to add the include? L = Leland L> These needed the include: L> L> Dialogs.cpp L> EventWindow.cpp L> MouseAction.cpp L> Player.cpp L> PropertyListDialog.cpp L> L> And these needed the wxString(): L> L> Audio.cpp L> GuitarSettingsDialog.cpp L> Harmony.cpp L> L> This was with a stock Widgets build. After rebuilding L> according to your instructions (which worked perfectly), L> these changes were not needed. Thank you for trying this. I really appreciate it. Today I'm working on preventing flicker in the track window when updating. I'm going to start a separate thread to see if I can get the projects mailing list maintainer to create another list for SVN commit messages. If that actually happens, you can subscribe to the new list to track my progress. I have extensive experience developing in Linux and Windows, but none on the Mac. What would you recommend for a Mac development system? Thanks again for trying the described wxWidgets build. Pete |
From: Leland <ja...@ho...> - 2008-03-16 19:38:09
|
On 3/16/08 2:14 PM, "Pete Stieber" <pst...@ve...> wrote: > > I have extensive experience developing in Linux and Windows, but none on > the Mac. What would you recommend for a Mac development system? > I would expect a Mac Mini would be sufficient as a build/test platform since you'd do doing development on your main machine(s). Leland |
From: Pete S. <pst...@ve...> - 2008-03-16 19:44:17
|
PS = Pete Stieber PS>> I have extensive experience developing in Linux PS>> and Windows, but none on the Mac. What would PS>> you recommend for a Mac development system? L = Leland L> I would expect a Mac Mini would be sufficient as L> a build/test platform since you'd do doing L> development on your main machine(s). Thanks for the suggestion. I have some questions about this, but this is getting far enough off-topic that I think I'll email you directly. Is that OK? Pete |
From: Leland <ja...@ho...> - 2008-03-16 19:50:47
|
Sure, that'd be fine. On 3/16/08 2:44 PM, "Pete Stieber" <pst...@ve...> wrote: > PS = Pete Stieber > PS>> I have extensive experience developing in Linux > PS>> and Windows, but none on the Mac. What would > PS>> you recommend for a Mac development system? > > L = Leland > L> I would expect a Mac Mini would be sufficient as > L> a build/test platform since you'd do doing > L> development on your main machine(s). > > Thanks for the suggestion. I have some questions about this, but this > is getting far enough off-topic that I think I'll email you directly. > Is that OK? > > Pete > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel > |