jazzplusplus-devel

[jazzplusplus-devel] What's the latest on the WxWin 2.x port?

[Matt K. <ra...@ch...>]

Hi,

Sorry to post a noob-type question, but I've been out of the loop
for quite some time.

What is the current status of Jazz++?  I know the push is on to port
to that latest of everything, right?  Is the current code in CVS
getting close, or is there a ways to go?  What's left to do?

I might have some spare cycles to help out.

I also have some enhancements to the piano window.  I brought these
to the developer's group about a year ago, and they were well received,
but not committed to the repository.  Maybe it's time to re-address
these enhancements.  I'll do that in a separate message.

Thanks,

Matt K.

Re: [jazzplusplus-devel] What's the latest on the WxWin 2.x port?

[Patrick E. <pa...@pa...>]

On Sunday 21 March 2004 21:18, Matt Kelly wrote:
> Hi,
>
> Sorry to post a noob-type question, but I've been out of the loop
> for quite some time.
>
> What is the current status of Jazz++?  I know the push is on to
> port to that latest of everything, right?  Is the current code in
> CVS getting close, or is there a ways to go?  What's left to do?
>
> I might have some spare cycles to help out.
>
> I also have some enhancements to the piano window.  I brought these
> to the developer's group about a year ago, and they were well
> received, but not committed to the repository.  Maybe it's time to
> re-address these enhancements.  I'll do that in a separate message.

Jazz++ compiles and runs under Linux using wxWidgets 2.4.  There's 
still stuff that hasn't been ported properly.

Dave is working on separating things into three layers; you can see a 
description on the wiki:
    http://jazz.opensrc.org/

I've been working on divorcing tPianoWin from tEventWin. I'm nearly 
done that.  Once I'm done that, I'll be working on cleaning up the 
piano code as much as possible.  When Dave has commited his changes 
to the track window, the piano window will need to be hooked into 
that.

I've also been working on a new system to support XRC dialogs.  If 
you're looking for a specific task, one possibility is working on 
porting the the various dialogs over to the new system.

In my work with the CVS, I've been performing incremental changes, 
though they sometimes have their fingers in many files.  If you work 
on changes I'd suggest updating and commiting often so it doesn't 
lead to a huge integration mess afterwards.

As for your enhancements to the piano window, those should probably 
wait until the code has stabilized more.  We need the code to regain 
simplicity and to actually work before adding more stuff.

As far as I know, we could use somebody to go through the midi/audio 
stuff and fix anything that's not working.  With any luck, large 
chunks of the system can be replaced with portaudio and portmidi, 
though they seem to be lacking a few features like the ability to 
define midi thru, similar to alsa's aconnect.  If you're looking for 
a substantial job, you could put portmidi and portaudio in place and 
add any needed features to the libraries themselves.  For the time 
being, we could distribute changed versions of the libraries, but the 
enhancements could probably be added to the core libraries at some 
point.

There's also a number of memory bugs that need to be tracked down 
using valgrind.  For example, the piano window cannot be started and 
closed without causing jazz to crash.

Basically it comes down to finding something you want to work on and 
then doing it.  I've been assuming that the CVS is mostly current 
with the exception of the trackwin code, which I know Dave has ripped 
apart.

If you'd like access to the CVS, first grab the CVS anonymously, make 
some changes, then let me know and I can set you up with commit 
access.

        Patrick

Re: [jazzplusplus-devel] What's the latest on the WxWin 2.x port?

[Dave F. <dav...@co...>]

On Monday 22 March 2004 04:53 am, Patrick Earl wrote:
> As far as I know, we could use somebody to go through the midi/audio
> stuff and fix anything that's not working.  With any luck, large
> chunks of the system can be replaced with portaudio and portmidi,
> though they seem to be lacking a few features like the ability to
> define midi thru, similar to alsa's aconnect.  If you're looking for
> a substantial job, you could put portmidi and portaudio in place and
> add any needed features to the libraries themselves.  For the time
> being, we could distribute changed versions of the libraries, but the
> enhancements could probably be added to the core libraries at some
> point.

With the audio/midi, I strongly recommend just dropping wav playback for now.  
We can use softsynths like Timidity for wav playback, so this code doesn't 
*need* to be in Jazz at the moment.  I've no problems re-adding wav playback 
later, but in the push to simplify things, I strongly suggest dropping it now 
and working on a solid midi implementation.  The midi stuff that's there is 
already pretty good, but....

The current playback class (I forget what it's called, tPlayer?) is derived 
from wxTimer, so it needs to be completely rewritten.  Pretty much from the 
ground up.  ;)  I would suggest if you want to take a crack at this code, you 
might be better of just trashing the old code and rewriting the playback.  If 
you want a non-system dependency, I recommend PortMIDI, and at this moment I 
wouldn't suggest using anything else other than the Alsa and other driver 
code that's already in Jazz.  The problems with wxTimer for realtime midi 
applications are probably pretty obvious, but I'll be happy to write a 
diatribe for you if you want it.  :)

Dave

> There's also a number of memory bugs that need to be tracked down
> using valgrind.  For example, the piano window cannot be started and
> closed without causing jazz to crash.
>
> Basically it comes down to finding something you want to work on and
> then doing it.  I've been assuming that the CVS is mostly current
> with the exception of the trackwin code, which I know Dave has ripped
> apart.
>
> If you'd like access to the CVS, first grab the CVS anonymously, make
> some changes, then let me know and I can set you up with commit
> access.
>
>         Patrick
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> jazzplusplus-devel mailing list
> jaz...@li...
> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel

-- 
Visit my website!
http://www.davefancella.com/?event=em

I base my fashion taste on what doesn't itch.
		-- Gilda Radner

Re: [jazzplusplus-devel] What's the latest on the WxWin 2.x port?

[Joakim V. <jo...@ve...>]

Dave Fancella wrote:

>
>With the audio/midi, I strongly recommend just dropping wav playback for now.  
>We can use softsynths like Timidity for wav playback, so this code doesn't 
>*need* to be in Jazz at the moment.  I've no problems re-adding wav playback 
>later, but in the push to simplify things, I strongly suggest dropping it now 
>and working on a solid midi implementation.  The midi stuff that's there is 
>already pretty good, but....
>  
>
I agree with removin audio playback stuff. Modularity is the strength of
the linux audio plattform.

Regards
/Joakim