jazzplusplus-devel — Discussion Forum for Jazz Developers

Re: [jazzplusplus-devel] Brief intro to the lists

[Kevin C. <ke...@co...>]

On 11 May 2008 at 2:50, "D.B. Moore" <db...@ho...> wrote:

> It would be in the order of 10years or so ago that I first became
> interested in the jazz++ application, and about that time I also
> joined jazzplusplus-user mailing list. Myself being a linux user,
> the building of jazz++ all that time ago was...'difficult' to say the
> least. I was initially going to ask list questions about this very
> difficultly...right about the the time project itself was in decline.

I've been there.  I think my jazz++ experience goes back to 4.0.  I 
was building on a Red Hat 5.0 system back then.

> As Kevin C. and others will attest, the jazzplusplus-user list
> has been a very quiet place, for a rather long time. 

Yup.  But, I don't want to miss any attempt to kick jazz++ back to 
life, so I lurk here waiting for messages.


> Okay...what do I hope to accomplish in my time here?

I like your agenda.


Thanks.... 
--
Kevin

Re: [jazzplusplus-devel] configure.ac update -please test-

[Kevin C. <ke...@co...>]

On 10 May 2008 at 12:31, Pete Stieber <pst...@ve...> wrote:

> Donald and Kevin, could I get you to try the Linux build and make sure 
> the jack/flsynth/qsynth is working.  I don't have access to a Linux 
> setup at the moment and that would really help me out.

I'm a bit busy at the moment, but I'll work on that ASAP.

> BTW I always seem to have a heck of a time with Mandriva.  Jazz++ can 
> hang it, it doesn't want to recognize my keyboard...

Hmmm.  I wonder what would happen with a Linus kernel on Mandriva?

Thanks.....
 
--
Kevin

Re: [jazzplusplus-devel] SF.net SVN: jazzplusplus: [515] tex2rtf

[D.B. M. <db...@ho...>]

Greetings,

> Subject: SF.net SVN: jazzplusplus: [515] tex2rtf
> Date: Sun, 11 May 2008 23:50:54 -0700
> 
> Revision: 515
>           http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=515&view=rev
> Author:   pstieber
> Date:     2008-05-11 23:50:53 -0700 (Sun, 11 May 2008)
> 
> Log Message:
> -----------
> Added a forked version of tex2rtf.  The code has a patch applied that allows
> it to build with a version of wxWidgets that is built using stl options.
> A complete build system is not in place and will have to be added.  The
> wxWidgets project is no longer using this code to build documentation
> and will not include it in post 2.8.* distributions.  The fork was OKed
> on the wxWidgets developer list by Julian Smart, the original author of
> this code.
> 

Do you  think we should announce this on the news page, and openly 
thank/acknowledge Julian for such a kind and co-operative gesture?

Regards,

Donald B 
_________________________________________________________________
Search for local singles online @ Lavalife - Click here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT

[jazzplusplus-devel] Initial considerations regarding inbuilt jazz++ documentation (jazz.tex)

[D.B. M. <db...@ho...>]

Greetings,

//for the benefit of list members ;- this posting is subsequent
//to some topics discussed between Pete and myself in private
//emails before I joined the list


               This content is now in my focus, however I've only
done a preliminary perusal of the existing (old..) documentation,
for the purpose of forming a rewrite stratagem. I'm hoping that
raising this discussion here will help form and clarify this process
*before* I actually start work in this area....so....

Quite obviously, the existing documentation is quite out-of-step
with what the eventual release of jazz++ will be - it will look different,
it may have different functions or do things in different ways than
previous releases of jazz - I have no real way of accurately forecasting
what these differences or changes might be - this is particularly so in
the linux case with the current status of 'minimal functionality'.

Questions: How disparate ..functionality wise...is the current Windows
build compared to the Mac & Linux positions? Are all the builds 'on
the same page' as it were?

In any event and as I infer here, updates to these areas of the
documentation will become apparent as functionality increases,
and will move in concert, with one area slightly behind the other.

Likewise, screen-shots are bound up in here somewhere as well.

That said, other sections of jazz.tex are really dated and out-of-sync
with the current linux position regarding audio/MIDI device options,
be that real hardware devices/cards, or 'pseudo' devices like the many
linux applicable 'softsynth' applications that exist today (which weren't
around when the original docs were drafted)...not to mention many
MIDI applications that have sprung up between then and now as well.

Seeing as we both agreed upon some form of 'how to use jazz++ with 'x''
(where 'x' is one of those applications I speak of above) section, I'll get
to a draft of that in the coming time. Remember though, interoperability
and functionality usually go hand in hand, and so I'm thinking everything
I've touched on so far will move forward at about the same rate...


Other sections, I want to fix right away....in particular, references to
'OSS' sound drivers for linux. I mean...even if one does want to use 
the old OSS API, you're going to use 'snd-*-oss' modules that plugin
to the alsasound API ...so I think OSS is fairly redundant stuff now. 

I think what I would like to do, is remove all references to the old
OSS modules altogether, and instead just touch upon same in a 
short introductory paragraph to this particular section, along the
lines of -- 'In the past, jazz++ relied on the now deprecated 'OSS'
sound drivers in linux, to......'  , following this up with a short
paragraph explaining the state of play now with linux and the 
alsasound drivers....and beyond that, the configuration details
focus entirely on what's current with linux today.

What do we think here? Comments? Thoughts?

Finally, I just want to say I'll be reliant on people running jazz++
on platforms other than linux, to supply  any documentation
and/or other material that's specific to the platform they use. 
I'm figuring there shouldn't be too much difference between 
the various builds...but where there is, be sure to let me know 
about it...(or submit same yourself).

Regards,


Donald B



_________________________________________________________________
Search for local singles online @ Lavalife - Click here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT

[jazzplusplus-devel] Query about Mac OSX builds

[D.B. M. <db...@ho...>]

Greetings,

                  I'm just wandering through the (website) documentation
fixing things, and my lack of experience with Mac OSX has just forced
me here.

In the 'buildingjazz++' documentation, a section describing the linux
build goes like this ;

The prefix option is used so that the make install step            
found later in these instructions, will not require root privileges.  It is          
also useful to run make install with this prefix option, so that the        
resulting install will create a copy of the jazz.cfg file that is           
independent of the one distributed in the source tree.  The configuration file       
is modified by the Jazz++ binary.  If the version of the jazz.cfg file      
in your svn working directory was altered, this could lead to update conflicts       
when updating the code using Subversion.  This may lead to problems using            
Jazz++ as a result.


The equivalent section in the Mac OSX instructions reads;


The prefix option is used so that the resulting install will not use        
the jazz.cfg file from the svn repository.  The configuration file is       
modified by the Jazz++ binary.  If the version in your svn working directory         
was altered, this could lead to update conflicts when updating the code.  This       
may lead to problems using Jazz++.


Obviously they are quite different. My question is, are the Mac OSX 
instructions here actually correct, or should they be more akin to the
linux instructions instead?


I'll hold-off diff'ing the next patch until some kind knowledgabe soul
clarifies this for me.


Regards,

Donald B  
_________________________________________________________________
Search for local singles online @ Lavalife - Click here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT

Re: [jazzplusplus-devel] Tex2RTF for online documentation building

[Pete S. <pst...@gm...>]

PS = Pete Stieber
PS>> You'll probably see a fork of tex2rtf showing up
PS>> in the Jazz++ source tree by the end of the week.
PS>> Maybe I can get you to create a web page
PS>> describing it's history including this discussion
PS>> and describing the build and install procedure ;-)

DM = Donald B. Moore
DM> Not a problem - once tex2rtf is incorporated into
DM> the tree, I'll set about generating this content.

Well, I just go a positive reply from my wxWidgets developer list post...

<wxWidgets dev list>
PS = Pete Stieber
PS>> Quite a while ago I submitted a patch for tex2rtf
PS>> to get it building with stl options turned on in
PS>> wxWidgets (patch number 1755801).  IIRC the patch
PS>> caused problems with the stock wxWidgets build.
PS>>
PS>> Now that you all are no longer using tex2rtf would
PS>> you mind if I forked it?  I want to use it for the
PS>> help system of an open source project I'm working
PS>> on (Jazz++ at http://jazzplusplus.sourceforge.net/)
PS>> and I use it at my place of employment.

JS = Julian Smart
JS> No problem as far as I'm concerned - I'd be happy
JS> to see it have a life elsewhere.

Thanks for the quick reply Julian.  I may attempt to stick a version of
it under the Jazz++ source tree by the end of the week.  It probably
should be turned into it's own project, but I just don't have the time
at this point.

Pete
</wxWidgets dev list>

So I'm confirming my patched version builds with the Jazz++ build of 
wxWidgets and will put the code under jazzplusplus/tex2rtf in the Jazz++ 
subversion repository.

Pete

Re: [jazzplusplus-devel] Tex2RTF for online documentation building

[D.B. M. <db...@ho...>]

----------------------------------------
> Date: Sun, 11 May 2008 22:43:31 -0700

 

> 
> You'll probably see a fork of tex2rtf showing up in the Jazz++ source 
> tree by the end of the week.  Maybe I can get you to create a web page 
> describing it's history including this discussion and describing the 
> build and install procedure ;-)
> 
> Pete
> 

Not a problem - once tex2rtf is incorporated into the tree, I'll set
about generating this content.

Regards,

Donald B




_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT

Re: [jazzplusplus-devel] Tex2RTF for online documentation building

[Pete S. <pst...@gm...>]

PS = Pete Stieber
PS>> You correctly surmised that a tex2rtf binary is
PS>> not included with a wxWidgets distribution.  It
PS>> is considered a utility that is not required to
PS>> to use wxWidgets.  It was used to generate the
PS>> documentation for wxWidgets itself, but I believe
PS>> that will not be the case for future versions
PS>> (2.9.* and 3.*) of wxWidgets.
PS>>
PS>> It was lucky for you that you attempted to build
PS>> tex2rtf from a stock build.  Given the options we
PS>> use to build wxWidgets for use with Jazz++, you
PS>> would have run into trouble with the non-stock
PS>> build of tex2rtf.  We use the stl in our wxWidgets
PS>> build, and tex2rtf is not compatible with the stl
PS>> build of wxWidgets.
PS>>
PS>> I have created a patched tex2rtf, that does build
PS>> with our wxWidgets options.  I submitted it to the
PS>> wxWidgets sourceforge patch manager (number 1755801)
PS>> quite a while ago, but the patch caused a problem
PS>> with the stock build.
PS>>
PS>> I guess I have the following options...
PS>>
PS>> 1. Since wxWidgets is switching to a different
PS>> documentation build system, I could try submitting
PS>> the patch again, but the process will take up a lot
PS>> of my Jazz++ development time.
PS>> 2. I could create a fork of tex2rtf in our development
PS>> tree so I could change it in any way I like.  This is
PS>> my favorite option at this point.
PS>> 3. I could make binaries available for download.  I
PS>> don't like this idea because there might be some
PS>> platforms I have difficulty generating and testing a
PS>> binary on.

DM> Yeah...don't do option 3, it's perilous considering
DM> how many platforms are out there. When we get around
DM> to doing binary packages, the documentation will have
DM> already been built and included there - this infers
DM> the source tree compiles the documentation. If there's
DM> a future wherein jazz++ is supposed to compile from
DM> source tarball release on a package-managed system
DM> against a *stock* wxwidgets tree, the only way that's
DM> going to happen is if tex2rtf is available, and
DM> by the sounds of it this might not be the case.
DM>
DM> Do we know of anything else dependent on tex2rtf in
DM> the real world?

I use it at my place of work.  BTW, the wxWidgets documentation is for 
the wxWidgets library.  They switched to doyxgen, which makes sense for 
a code library.  User documentation for an application like Jazz++ is a 
different story.

DM> I like option 2.  - it neatly gets around all this
DM> conjecture by being part of the jazz++ tree, and
DM> offers the most flexibility overall (without need
DM> to rework things already done).

I found the following pose on the wxWidgets list from 3/22/2008...

<wxWidgets Developers List>
 >   4) tex2rtf => I don't know if someone is using this outside
 > wxWidgets... but I think that if this is the case, the version
 > in the 2.8 branch could be enough (I don't see future
 > developments for this tool likely to happen)

Yes, I had already asked about it and Julian agreed with this.
</wxWidgets Developers List>

So I just made a post on the list asking if anyone would mid a fork of 
the project.

PS>> I do like tex2rtf's capabilities, and I do want to
PS>> use it for online HTML help.  What do you all think?

DM> It generates correct HTML, it's quick, and you've a
DM> history with it.  In my country, we have a saying -
DM> "When you're on a good thing - stick to it!" -- I
DM> believe that idiom applies here.  (-;

You'll probably see a fork of tex2rtf showing up in the Jazz++ source 
tree by the end of the week.  Maybe I can get you to create a web page 
describing it's history including this discussion and describing the 
build and install procedure ;-)

Pete

Re: [jazzplusplus-devel] Patch -- htdocs fixups

[Pete S. <pst...@gm...>]

DM = D.B. Moore
DM> This patch corrects (hopefully) all outstanding
DM> typos, spelling, and other grammatical issues in
DM> the content of the following;
DM>
DM> web/htdocs/index.php
DM> web/htdocs/download/index.php
DM> web/htdocs/subversion/index.php
DM>
DM> Apart from simple corrections, some wording has
DM> been slightly changed/rearranged to facilitate
DM> paragraph formatting. A bit more 'user encouragement'
DM> has been added to the subversion content regarding
DM> svn builds. These are the only deviations from the
DM> content of the original texts at this time.
DM>
DM> See attached:-  htdocs-20080512-fixups.patch.gz

Thanks.  Applied in svn and moved up to the web site.  You should check 
the web site to make sure I didn't foul anything up ;-)

Thanks for your editing efforts.
Pete

Re: [jazzplusplus-devel] Tex2RTF for online documentation building

[D.B. M. <db...@ho...>]

----------------------------------------
> Date: Sun, 11 May 2008 21:38:40 -0700



> You correctly surmised that a tex2rtf binary is not included with a 
> wxWidgets distribution.  It is considered a utility that is not required 
> to use wxWidgets.  It was used to generate the documentation for 
> wxWidgets itself, but I believe that will not be the case for future 
> versions (2.9.* and 3.*) of wxWidgets.
> 
> It was lucky for you that you attempted to build tex2rtf from a stock 
> build.  Given the options we use to build wxWidgets for use with Jazz++, 
> you would have run into trouble with the non-stock build of tex2rtf.  We 
> use the stl in our wxWidgets build, and tex2rtf is not compatible with 
> the stl build of wxWidgets.
> 
> I have created a patched tex2rtf, that does build with our wxWidgets 
> options.  I submitted it to the wxWidgets sourceforge patch manager 
> (number 1755801) quite a while ago, but the patch caused a problem with 
> the stock build.
> 
> I guess I have the following options...
> 
> 1. Since wxWidgets is switching to a different documentation build 
> system, I could try submitting the patch again, but the process will 
> take up a lot of my Jazz++ development time.
> 2. I could create a fork of tex2rtf in our development tree so I could 
> change it in any way I like.  This is my favorite option at this point.
> 3. I could make binaries available for download.  I don't like this idea 
> because there might be some platforms I have difficulty generating and 
> testing a binary on.

Yeah...don't do option 3, it's perilous considering how many platforms
are out there. When we get around to doing binary packages, the 
documentation will have already been built and included there - this
infers the source tree compiles the documentation. If there's a future
wherein jazz++ is supposed to compile from source tarball release
on a package-managed system against a *stock* wxwidgets tree,
the only way that's going to happen is if tex2rtf is available, and
by the sounds of it this might not be the case. 

Do we know of anything else dependent on tex2rtf in the real world?

I like option 2.  - it neatly gets around all this conjecture by being
part of the jazz++ tree, and offers the most flexibility overall (without
need to rework things already done). 
> 
> I do like tex2rtf's capabilities, and I do want to use it for online 
> HTML help.  What do you all think?
> 

It generates correct HTML, it's quick, and you've a history with it.
In my country, we have a saying - "When you're on a good thing -
stick to it!" -- I believe that idiom applies here.  (-;
 
Regards,

Donald B


> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> jazzplusplus-devel mailing list
> jaz...@li...
> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel

_________________________________________________________________
It's simple! Sell your car for just $30 at CarPoint.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT

[jazzplusplus-devel] Patch -- htdocs fixups

[D.B. M. <db...@ho...>]

Greetings,


This patch corrects (hopefully) all outstanding typos, spelling,
and other grammatical issues in the content of the following;

web/htdocs/index.php
web/htdocs/download/index.php
web/htdocs/subversion/index.php


Apart from simple corrections, some wording has been slightly
changed/rearranged to facilitate paragraph formatting. A bit
more 'user encouragement' has been added to the subversion
content regarding svn builds. These are the only deviations
from he content of the original texts at this time.


See attached:-  htdocs-20080512-fixups.patch.gz


The building{wx/jazz++} content will be subject of another
patch, which will follow in a few hours time.


Regards,

Donald B

_________________________________________________________________
It's simple! Sell your car for just $30 at CarPoint.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT

[jazzplusplus-devel] Tex2RTF for online documentation building

[Pete S. <pst...@gm...>]

In a separate thread (Subject: online help build system update) I 
mention the use of tex2rtf to generate HTML help.

"For the HTML help you will need the tex2rtf code that is provided with 
wxWidgets."

I have a bit of a history with tex2rtf, and I felt this history, and its 
relationship to Jazz++ development, was worth a separate topic.  In the 
old thread, Donald B. Moore wrote...

DM> In your previous posting about this, you signified
DM> that the 'tex2rtf' utility was distributed with the
DM> wxwidget tarball. My stock installation of wx is
DM> version 2.8.4, however 'tex2rtf' wasn't in $PATH.
DM> I'd only just updated wx a week or so ago, so I
DM> still had the source/build tree handy. Checking
DM> that was when I discovered 'tex'2rtf' hadn't been
DM> built (in my 2.8.4 wx tree) - nor had it been
DM> built in the non-stock wx-2.8.7 build used for
DM> jazz++ ; apparently the cause is common.
DM>
DM> I chose to sort this on my *stock* wx installation
DM> (to make tex2rtf available systemwide, not just for
DM> jazz++). The full path to tex2rtf in the wx source
DM> tree is -- wxGTK-2.8.4/utils/tex2rtf/
DM>
DM> Changing to that directory, issuing make && make
DM> install was how I ended up with a working tex2rtf.
DM> Strangely, it had all been previously configured,
DM> all the Makefiles were present, but for whatever
DM> reason the build process skips right over the utils
DM> section and why is something I would need look closer
DM> at ....if you want me to that is. Let me know...

You correctly surmised that a tex2rtf binary is not included with a 
wxWidgets distribution.  It is considered a utility that is not required 
to use wxWidgets.  It was used to generate the documentation for 
wxWidgets itself, but I believe that will not be the case for future 
versions (2.9.* and 3.*) of wxWidgets.

It was lucky for you that you attempted to build tex2rtf from a stock 
build.  Given the options we use to build wxWidgets for use with Jazz++, 
you would have run into trouble with the non-stock build of tex2rtf.  We 
use the stl in our wxWidgets build, and tex2rtf is not compatible with 
the stl build of wxWidgets.

I have created a patched tex2rtf, that does build with our wxWidgets 
options.  I submitted it to the wxWidgets sourceforge patch manager 
(number 1755801) quite a while ago, but the patch caused a problem with 
the stock build.

I guess I have the following options...

1. Since wxWidgets is switching to a different documentation build 
system, I could try submitting the patch again, but the process will 
take up a lot of my Jazz++ development time.
2. I could create a fork of tex2rtf in our development tree so I could 
change it in any way I like.  This is my favorite option at this point.
3. I could make binaries available for download.  I don't like this idea 
because there might be some platforms I have difficulty generating and 
testing a binary on.

I do like tex2rtf's capabilities, and I do want to use it for online 
HTML help.  What do you all think?

Pete

Re: [jazzplusplus-devel] online help build system update

[Pete S. <pst...@gm...>]

DM> Pete -- I've posted this reply to
DM> jazzplusplus-user as well, just to help
DM> remove any confusion generated there.

That's fine.  I'm going to stick with the developer list.

PS>>>> You will need certain tools available to make this
PS>>>> work. For the HTML help you will need the tex2rtf
PS>>>> code that is provided with wxWidgets.

DM>>> I did forget to mention that 'tex2rtf' doesn't
DM>>> seem to get built here as part of the wx-2.8.7
DM>>> build instructions. I have no idea if that's an
DM>>> expected result (it may well be)....

PS>> If you don't have tex2rtf, how did you build the
PS>> HTML help?

DM> Sorry, I should have been a bit clearer about this.
DM> Here's the detail ;

I'm going to start a new thread concerning tex2rtf on the developer list 
and copy some of your post to that thread.

PS>>>> For PDF generation, you will need a LaTeX
PS>>>> installation and the pdflatex converter.

DM>>> Using tetex under linux (which supplies the tool
DM>>> 'pdftex'), jazz.pdf generation also works fine.
DM>>> The tool 'pdftex' is also maintained separately
DM>>> (http://www.pdftex.org) and seems more current
DM>>> than the version shipping with tetex.
DM>>>
DM>>> Both versions work.

PS>> Maybe I can check for existence of pdflatex or
PS>> pdftex in the build system.

DM> Yeah, I think you'll have to. AFAICT 'pdflatex'
DM> is not specific to linux -

I'm not sure what you mean by "specific to Linux".  It's part of my 
Fedora 8 install.  It came with the tetex-latex-3.0-44.9.fc8.x86_64 
package.  I determined this using...

rpm -qf /usr/bin/pdflatex
tetex-latex-3.0-44.9.fc8.x86_64

pfdtex is also on the system.

rpm -qf /usr/bin/pdftex
tetex-3.0-44.9.fc8.x86_64

DM> the equivalence is 'pdftex' to the best of
DM> my knowledge. It probably make sense to
DM> include a check in configure for both these
DM> tool sets (including tex2rtf), and like other
DM> projects I've seen issue a warning at the end
DM> of configure 'documentation will not be built
DM> - please install <> if you wish to build a
DM> local copy of the documentation'
DM> ....blabla...

I think that's what we'll do...  Require tex2rtf since it is used for 
online help, but make the PDF build optional via --enable-pdfdocs.  If 
the developer uses --enable-pdfdocs, we'll check for a pdflatex install.

DM> I should also point out, although the 'tetex'
DM> distribution does include it's own (working)
DM> version of 'pdftex', the variant downloaded from
DM> http://www.pdftex.org is meant to replace the one
DM> distributed in tetex.

DM>>> I just need to clarify something here -- when you say;
DM>>>
DM>>> 'in your svn working'
DM>>>
DM>>> I construe this as ;
DM>>>
DM>>> 'in your svn working directory'
DM>>>
DM>>> Is that correct?

PS>> Yes. Sorry about the missing noun and the
PS>> related confusion. I just committed a fix
PS>> for this one. You update your web source
PS>> tree (i.e. your svn web working directory)
PS>> and svn will merge the changes with any
PS>> you have made.

DM> I should have patches for the rest of the
DM> web docs sorted over the next few days.

Excellent!  I'll be looking for them.

Next, I'm going to start that tex2rtf thread.

Pete

Re: [jazzplusplus-devel] online help build system update

[D.B. M. <db...@ho...>]

Greetings,

Pete -- I've posted this reply to jazzplusplus-user as well,
just to help remove any confusion generated there.

----------------------------------------
> Date: Sun, 11 May 2008 13:49:37 -0700

> PS>> You will need certain tools available to make this
> PS>> work. For the HTML help you will need the tex2rtf
> PS>> code that is provided with wxWidgets.
>
> DM> I did forget to mention that 'tex2rtf' doesn't
> DM> seem to get built here as part of the wx-2.8.7
> DM> build instructions. I have no idea if that's an
> DM> expected result (it may well be)....
>
> If you don't have tex2rtf, how did you build the HTML help?
>
> tex2rtf will probably be the topic of a separate thread, but it can be
> generated from the wxWidgets distribution. Unfortunately, due to the
> way wxWidgets is built for Jazz++, there are some potential problems.
>

Sorry, I should have been a bit clearer about this. Here's the detail ;

In your previous posting about this, you signified that the 'tex2rtf'
utility was distributed with the wxwidget tarball. My stock installation
of wx is version 2.8.4, however 'tex2rtf' wasn't in $PATH. I'd only
just updated wx a week or so ago, so I still had the source/build tree
handy. Checking that was when I discovered 'tex'2rtf' hadn't been
built (in my 2.8.4 wx tree) - nor had it been built in the non-stock
wx-2.8.7 build used for jazz++ ; apparently the cause is common.

I chose to sort this on my *stock* wx installation (to make tex2rtf
available systemwide, not just for jazz++). The full path to tex2rtf in
the wx source tree is -- wxGTK-2.8.4/utils/tex2rtf/

Changing to that directory, issuing make && make install was how
I ended up with a working tex2rtf. Strangely, it had all been previously
configured, all the Makefiles were present, but for whatever reason
the build process skips right over the utils section and why is something
I would need look closer at ....if you want me to that is. Let me know...


> PS>> For PDF generation, you will need a LaTeX
> PS>> installation and the pdflatex converter.
>
> DM> Using tetex under linux (which supplies the tool
> DM> 'pdftex'), jazz.pdf generation also works fine.
> DM> The tool 'pdftex' is also maintained separately
> DM> (http://www.pdftex.org) and seems more current
> DM> than the version shipping with tetex.
> DM>
> DM> Both versions work.
>
> Maybe I can check for existence of pdflatex of pdftex in the build system.
>

Yeah, I think you'll have to. AFAICT 'pdflatex' is not specific to linux -
the equivalence is 'pdftex' to the best of my knowledge. It probably
make sense to include a check in configure for both these tool sets
(including tex2rtf), and like other projects I've seen issue a warning
at the end of configure 'documentation will not be built - please install
<> if you wish to build a local copy of the documentation'
....blabla...

I should also point out, although the 'tetex' distribution does include
it's own (working) version of 'pdftex', the variant downloaded from
http://www.pdftex.org is meant to replace the one distributed in
tetex.


> PS>> Would you like me to send you the current PDF
> PS>> file in a private email?
>
> DM> A kind offer, however I'm eager to checkout
> DM> as much of source build process as is possible
> DM> here - test, test and test again...
>
> PS>> Since you can build the HTML help using
> PS>> "make html" feel free to start editing jazz.tex
> PS>> and send me patches. Replacement screen shots
> PS>> are welcome too. We may end up with different
> PS>> sets of screen shots for each platform and I
> PS>> can change the Makefile to build the docs for
> PS>> different platforms. I'm going to make one
> PS>> commit to jazz.tex before I go to bed, but
> PS>> after that it's "open season" for you.
>
> DM> ....now, where did I put my hunting cap?... (;
>
> PS>> I would prefer many smaller patches than one
> PS>> big patch, and please include a note
> PS>> summarizing the changes you made. I'll use
> PS>> this in commit message and give you credit.
> PS>> The first change you should make is make
> PS>> yourself a coauthor. I changed the original
> PS>> author names because they have been out of
> PS>> the picture for over 8 years. The commit
> PS>> messages will look like...
> PS>>
> PS>> "Applied a patch provided by Donald B. Moore.
> PS>> Your description here.
> PS>> A description of anything I changed here."
>
> DM> All understood, I'll keep my submissions
> DM> small and descriptive ...
>
> Thanks.
>
> PS>> I see you signed up for the
> PS>> jazzplusplus-updates list. Excellent!
>
> DM> I try to please.
>
> DM> I just need to clarify something here -- when you say;
> DM>
> DM> 'in your svn working'
> DM>
> DM> I construe this as ;
> DM>
> DM> 'in your svn working directory'
> DM>
> DM> Is that correct?
>
> Yes. Sorry about the missing noun an the related confusion. I just
> committed a fix for this one. You update your web source tree (i.e.
> your svn web working directory) and svn will merge the changes with any
> you have made.
>
> Pete
>

No problem...I guess that's what we're supposed to do though - confuse each
other then clear up that confusion before the user audience finds themselves confused...

I should have patches for the rest of the web docs sorted over the next
few days.

Regards,

Donald B

>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> jazzplusplus-devel mailing list
> jaz...@li...
> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel

_________________________________________________________________
Never miss another e-mail with Hotmail on your mobile.
http://www.livelife.ninemsn.com.au/article.aspx?id=343869

Re: [jazzplusplus-devel] online help build system update

[Pete S. <pst...@gm...>]

DM = D.B. Moore
PS>> jazzplusplus/trunk/jazz/doc.  On my x86_64 Fedora 8
PS>> box, if I run "make" in the referenced directory, it
PS>> will generate HTML help files you can view with your
PS>> favorite web browser and a jazz.pdf file.
PS>>
PS>> You will need certain tools available to make this
PS>> work.  For the HTML help you will need the tex2rtf
PS>> code that is provided with wxWidgets.

DM> I did forget to mention that 'tex2rtf' doesn't
DM> seem to get built here as part of the wx-2.8.7
DM> build instructions. I have no idea if that's an
DM> expected result (it may well be)....

If you don't have tex2rtf, how did you build the HTML help?

tex2rtf will probably be the topic of a separate thread, but it can be 
generated from the wxWidgets distribution.  Unfortunately, due to the 
way wxWidgets is built for Jazz++, there are some potential problems.

PS>> For PDF generation, you will need a LaTeX
PS>> installation and the pdflatex converter.

DM> Using tetex under linux (which supplies the tool
DM> 'pdftex'), jazz.pdf generation also works fine.
DM> The tool 'pdftex' is also maintained separately
DM> (http://www.pdftex.org) and seems more current
DM> than the version shipping with tetex.
DM>
DM> Both versions work.

Maybe I can check for existence of pdflatex of pdftex in the build system.

PS>> Would you like me to send you the current PDF
PS>> file in a private email?

DM> A kind offer, however I'm eager to checkout
DM> as much of source build process as is possible
DM> here - test, test and test again...

PS>> Since you can build the HTML help using
PS>> "make html" feel free to start editing jazz.tex
PS>> and send me patches.  Replacement screen shots
PS>> are welcome too.  We may end up with different
PS>> sets of screen shots for each platform and I
PS>> can change the Makefile to build the docs for
PS>> different platforms.  I'm going to make one
PS>> commit to jazz.tex before I go to bed, but
PS>> after that it's "open season" for you.

DM> ....now, where did I put my hunting cap?...  (;

PS>> I would prefer many smaller patches than one
PS>> big patch, and please include a note
PS>> summarizing the changes you made.  I'll use
PS>> this in commit message and give you credit.
PS>> The first change you should make is make
PS>> yourself a coauthor.  I changed the original
PS>> author names because they have been out of
PS>> the picture for over 8 years.  The commit
PS>> messages will look like...
PS>>
PS>> "Applied a patch provided by Donald B. Moore.
PS>> Your description here.
PS>> A description of anything I changed here."

DM> All understood, I'll keep my submissions
DM> small and descriptive ...

Thanks.

PS>> I see you signed up for the
PS>> jazzplusplus-updates list.  Excellent!

DM> I try to please.

DM> I just need to clarify something here -- when you say;
DM>
DM> 'in your svn working'
DM>
DM> I construe this as ;
DM>
DM> 'in your svn working directory'
DM>
DM> Is that correct?

Yes.  Sorry about the missing noun an the related confusion.  I just 
committed a fix for this one.  You update your web source tree (i.e. 
your svn web working directory) and svn will merge the changes with any 
you have made.

Pete

Re: [jazzplusplus-devel] online help build system update

[D.B. M. <db...@ho...>]

Greetings,

----------------------------------------
> Date: Sat, 10 May 2008 22:26:58 -0700
> From: pst...@gm...

> PS>> jazzplusplus/trunk/jazz/doc.  On my x86_64 Fedora 8
> PS>> box, if I run "make" in the referenced directory, it
> PS>> will generate HTML help files you can view with your
> PS>> favorite web browser and a jazz.pdf file.
> PS>>
> PS>> You will need certain tools available to make this
> PS>> work.  For the HTML help you will need the tex2rtf
> PS>> code that is provided with wxWidgets.

I did forget to mention that 'tex2rtf' doesn't seem to get built
here as part of the wx-2.8.7 build instructions. I have no idea
if that's an expected result (it may well be)....

> PS>>
> PS>> For PDF generation, you will need a LaTeX
> PS>> installation and the pdflatex converter.
> PS>>

Using tetex under linux (which supplies the tool 'pdftex'),
jazz.pdf generation also works fine. The tool 'pdftex' is
also maintained separately (http://www.pdftex.org) and
seems more current than the version shipping with tetex.

Both versions work.

> 
> Would you like me to send you the current PDF file in a private email?
> 

A kind offer, however I'm eager to checkout as much of source
build process as is possible here - test, test and test again... 

> 
> Since you can build the HTML help using "make html" feel free to start 
> editing jazz.tex and send me patches.  Replacement screen shots are 
> welcome too.  We may end up with different sets of screen shots for each 
> platform and I can change the Makefile to build the docs for different 
> platforms.  I'm going to make one commit to jazz.tex before I go to bed, 
> but after that it's "open season" for you.
>

....now, where did I put my hunting cap?...  (;
 
> I would prefer many smaller patches than one big patch, and please 
> include a note summarizing the changes you made.  I'll use this in 
> commit message and give you credit.  The first change you should make is 
> make yourself a coauthor.  I changed the original author names because 
> they have been out of the picture for over 8 years.  The commit messages 
> will look like...
> 
> "Applied a patch provided by Donald B. Moore.
> Your description here.
> A description of anything I changed here."

All understood, I'll keep my submissions small and descriptive ...

> 
> I see you signed up for the jazzplusplus-updates list.  Excellent!
> 

I try to please.


I just need to clarify something here -- when you say;

'in your svn working'

I construe this as ;

'in your svn working directory'

Is that correct? Or does the paraphrase ' in your svn working'
refer to some subversion terminology that is unknown to me?

    Regards,

Donald B



 
_________________________________________________________________
Be part of history. Take part in Australia's first e-mail archive with Email Australia.
http://emailaustralia.ninemsn.com.au

Re: [jazzplusplus-devel] online help build system update

[Pete S. <pst...@gm...>]

D.B. Moore wrote:
DM> Apologies for not observing 'PCYMTNQREAIYR'
DM> previously..fixed..

No problem.  Happens all of the time.  Thanks for fixing it.

PS>> Donald or anyone else wishing to help with
PS>> documentation,
PS>>
PS>> If you update your subversion source tree, I have
PS>> modified the jazz/doc directory.  If you have
PS>> checked out the entire subversion repository so
PS>> you can create patches for the web content, the path
PS>> to the documentation directory is
PS>> jazzplusplus/trunk/jazz/doc.  On my x86_64 Fedora 8
PS>> box, if I run "make" in the referenced directory, it
PS>> will generate HTML help files you can view with your
PS>> favorite web browser and a jazz.pdf file.
PS>>
PS>> You will need certain tools available to make this
PS>> work.  For the HTML help you will need the tex2rtf
PS>> code that is provided with wxWidgets.
PS>>
PS>> For PDF generation, you will need a LaTeX
PS>> installation and the pdflatex converter.
PS>>
PS>> If you have trouble with either of these build, you
PS>> can perform them separately by using
PS>>
PS>> make html
PS>>
PS>> for HTML help generation or
PS>>
PS>> make pdf
PS>>
PS>> for PDF file generation.
PS>>
PS>> Keep in mind I'm discussing and working on the build
PS>> process, not the content of the help.  The screen
PS>> shots used in the docs are from an old Jazz++ build
PS>> and it looks like the Motif Window manager (mwm) was
PS>> used.

DM> ....and possibly Lesstif widgets were used for linux
DM> builds IIRC

Yes, LessTif is the "open source" Motif (http://www.lesstif.org/).

PS>> They should be replaced.  I'm hoping the image format
PS>> (Portable Network Graphics or PNG -
PS>> http://www.libpng.org/pub/png/) will stick.
PS>>
PS>> I'll be counting on you to fix up the content;-)
PS>> Before I help you with that, let's see if you can
PS>> build the docs in either of the formats described
PS>> above.  Let me know and I enjoyed your "biography post".

DM> Manual (separate) generation of HTML docs works fine.

Excellent!  Then you have a working tex2rtf!

DM> I'll need grab & install 'pdflatex' to checkout the
DM> PDF build.  I'll do a full 'inline' build
DM> of the tree a bit later and check all is
DM> working as expected.

Would you like me to send you the current PDF file in a private email?

DM> Glad my bio-post wasn't too far off topic ;-)

Considering the amount of traffic on these lists (almost none) any post 
related to Jazz++ is welcome.

PS>> BTW, It appears my service provider (verizon.net)
PS>> is blocking email from the Jazz++ lists, so I may
PS>> end up replying using some other email account...
PS>> What a pain.

DM> Indeed...why on earth would they do that?

I don't know, but thank goodness for gmail.

Since you can build the HTML help using "make html" feel free to start 
editing jazz.tex and send me patches.  Replacement screen shots are 
welcome too.  We may end up with different sets of screen shots for each 
platform and I can change the Makefile to build the docs for different 
platforms.  I'm going to make one commit to jazz.tex before I go to bed, 
but after that it's "open season" for you.

I would prefer many smaller patches than one big patch, and please 
include a note summarizing the changes you made.  I'll use this in 
commit message and give you credit.  The first change you should make is 
make yourself a coauthor.  I changed the original author names because 
they have been out of the picture for over 8 years.  The commit messages 
will look like...

"Applied a patch provided by Donald B. Moore.
Your description here.
A description of anything I changed here."

I see you signed up for the jazzplusplus-updates list.  Excellent!

Looking forward to your web content and documentation patches.

TIA,
Pete

Re: [jazzplusplus-devel] online help build system update

[D.B. M. <db...@ho...>]

Greetings,


----------------------------------------
> Date: Sat, 10 May 2008 20:56:49 -0700


Apologies for not observing 'PCYMTNQREAIYR' previously..fixed..


> Donald or anyone else wishing to help with documentation,
> 
> If you update your subversion source tree, I have modified the jazz/doc 
> directory.  If you have checked out the entire subversion repository so 
> you can create patches for the web content, the path to the 
> documentation directory is jazzplusplus/trunk/jazz/doc.  On my x86_64 
> Fedora 8 box, if I run "make" in the referenced directory, it will 
> generate HTML help files you can view with your favorite web browser and 
> a jazz.pdf file.
> 
> You will need certain tools available to make this work.  For the HTML 
> help you will need the tex2rtf code that is provided with wxWidgets.
> 
> For PDF generation, you will need a LaTeX installation and the pdflatex 
> converter.
> 
> If you have trouble with either of these build, you can perform them 
> separately by using
> 
> make html
> 
> for HTML help generation or
> 
> make pdf
> 
> for PDF file generation.
> 
> Keep in mind I'm discussing and working on the build process, not the 
> content of the help.  The screen shots used in the docs are from an old 
> Jazz++ build and it looks like the Motif Window manager (mwm) was used.

....and possibly Lesstif widgets were used for linux builds IIRC
 
>   They should be replaced.  I'm hoping the image format (Portable 
> Network Graphics or PNG - http://www.libpng.org/pub/png/) will stick.
> 
> I'll be counting on you to fix up the content;-)  Before I help you with 
> that, let's see if you can build the docs in either of the formats 
> described above.  Let me know and I enjoyed your "biography post".
>

Manual (separate) generation of HTML docs works fine. I'll need grab &
install 'pdflatex' to checkout the PDF build. I'll do a full 'inline' build
of the tree a bit later and check all is working as expected. 

Glad my bio-post wasn't too far off topic ;-)
 

> BTW, It appears my service provider (verizon.net) is blocking email from 
> the Jazz++ lists, so I may end up replying using some other email 
> account... What a pain.

Indeed...why on earth would they do that?


Regards,

Donald B
_________________________________________________________________
Never miss another e-mail with Hotmail on your mobile.
http://www.livelife.ninemsn.com.au/article.aspx?id=343869

[jazzplusplus-devel] online help build system update

[Pete S. <pst...@ve...>]

Donald or anyone else wishing to help with documentation,

If you update your subversion source tree, I have modified the jazz/doc 
directory.  If you have checked out the entire subversion repository so 
you can create patches for the web content, the path to the 
documentation directory is jazzplusplus/trunk/jazz/doc.  On my x86_64 
Fedora 8 box, if I run "make" in the referenced directory, it will 
generate HTML help files you can view with your favorite web browser and 
a jazz.pdf file.

You will need certain tools available to make this work.  For the HTML 
help you will need the tex2rtf code that is provided with wxWidgets.

For PDF generation, you will need a LaTeX installation and the pdflatex 
converter.

If you have trouble with either of these build, you can perform them 
separately by using

make html

for HTML help generation or

make pdf

for PDF file generation.

Keep in mind I'm discussing and working on the build process, not the 
content of the help.  The screen shots used in the docs are from an old 
Jazz++ build and it looks like the Motif Window manager (mwm) was used. 
  They should be replaced.  I'm hoping the image format (Portable 
Network Graphics or PNG - http://www.libpng.org/pub/png/) will stick.

I'll be counting on you to fix up the content;-)  Before I help you with 
that, let's see if you can build the docs in either of the formats 
described above.  Let me know and I enjoyed your "biography post".

BTW, It appears my service provider (verizon.net) is blocking email from 
the Jazz++ lists, so I may end up replying using some other email 
account... What a pain.

Pete

[jazzplusplus-devel] Brief intro to the lists

[D.B. M. <db...@ho...>]

G'day all,

             This is merely a short(?)  email letting everyone know
a little about myself, how I ended up here, and what I hope
to accomplish in my time here.

In case you missed it, I am an Australian. I am actually a
qualified motor-mechanic, have tickets in quality assurance
and control operations, and I like to study human sociology
in my spare time. I've also worked in electronics R&D and
production arenas. I am '50-something' years old (;

It would be in the order of 10years or so ago that I first became
interested in the jazz++ application, and about that time I also
joined jazzplusplus-user mailing list. Myself being a linux user,
the building of jazz++ all that time ago was...'difficult' to say the
least. I was initially going to ask list questions about this very
difficultly...right about the the time project itself was in decline.

As Kevin C. and others will attest, the jazzplusplus-user list
has been a very quiet place, for a rather long time. When Pete's
request for power-users to test out new builds hit the list, I was
actually in the throws of moving house...so I was a bit late getting
onto that testing. However, I did get around to it, and I might say
that I was both amazed and enthused to discover that everything
compiled correctly. I sent an email to Pete recounting that very
experience, along with a small critique of website instructions
given to achieve this.

Since then, Pete and myself have had a detailed private email
discussion about the website content, documentation in general,
and right about the time I thought 'can I help?' , Pete had a very
similar notion...'would you like to help?'....and here I am! We have
of course moved that private discussion onto the lists as we get
things co-ordinated between us.

Pete was hoping that I join the developers list as well as the users
list, and I have now made that so. I will primarily be working on
documentation generation & proofing tasks. If anyone has any
comments or requests about this area of the project, feel free to
raise a hand -- comments and critiques both good and bad very
welcome.

I can also do any (linux..) testing required on ix86 in both 32 and
64 bit flavors, using Debian 4.0 installations. I can also test on
this station, a non-mainstream linux 64bit x86 with no 32bit-compat
system. In a happy future where a sanctioned release of jazz++
becomes available, I could produce binary packages for Debian.

Okay...what do I hope to accomplish in my time here?

First off the rank, is to straighten and correct the jazz++ website
texts. The aim is for correctness and clarity within the website. I
believe this task is almost complete.

Secondly...and as expounded to Pete in one of our private emails,
users of jazz++ on the Windows platform have really got it easy.
That is to say, no matter what soundcard hardware these systems
have fitted, the user will have a MIDI 'softsynth' as part of that
system makeup. Even the most inexperienced Windows user will
have little trouble downloading and installing jazz++, and having
it create sound first up 'out of the box' as it were.

The linux experience is not so straight forward....in fact, getting
and compiling jazz++ from svn is actually the -easy- part now.

Getting it to actually make any sound, is another matter again,
and unless the user has a hardware-based MIDI/synth soundcard
(or 'real' MIDI hardware), then they will have to setup their own
'softsynth' implementation before they can hear the replay of....
..ie; 'jazz.mid' (or any other MIDI track for that matter).

I am of the belief that normal, average and inexperienced users
of linux have no idea about such things - they expect their linux
systems to have a builtin MIDI 'softsynth'  just like a Windows
system has.

I am also of the belief that the lack of this 'native' MIDI 'softsynth'
support in linux, has in some way been participle to jazz++ (and
other linux/MIDI projects) falling by the wayside.  Does anyone
else share this belief?

Ergo, I plan to create some documentation for inclusion on the
jazz++ website, to explain these things to potential users who
might not know about such things. I plan to write a set of
instructions that hopefully enables such inexperienced/casual
users of linux to build, install and setup their own 'softsynth'
implementation as quickly and simply as possible. My aim here
is to make the linux experience with jazz++ as closely akin to
the Windows experience as possible -- the linux path might
require a bit more work, but I want that work as easy as
possible for (inexperienced) linux users to complete successfully.

Beyond that, I want to test and document jazz++'s setup
and interoperability with -other- linux MIDI based applications.

Beyond that...(??)...who knows, but I'm always open to suggestions!!

Finally, I wish to thank those jazzplusplus-user list members who
responded to my call for a listening head-count -- it's comforting
to know I'm not totally alone on that list!!


Kind regards to all,

Donald B

_________________________________________________________________
Never miss another e-mail with Hotmail on your mobile.
http://www.livelife.ninemsn.com.au/article.aspx?id=343869

[jazzplusplus-devel] configure.ac update -please test-

[Pete S. <pst...@ve...>]

I think I finally have configure.ac setup to build on a Mac and a Linux 
box with ALSA.  I tested the Mac build with the current svn repository 
and it works on my Max mini.

Leland, I noticed your Midible commits.  How's it going?

I need to look at the use of portmidi/portaudio in your version to get 
the Mac playing Midi files.

Donald and Kevin, could I get you to try the Linux build and make sure 
the jack/flsynth/qsynth is working.  I don't have access to a Linux 
setup at the moment and that would really help me out.

BTW I always seem to have a heck of a time with Mandriva.  Jazz++ can 
hang it, it doesn't want to recognize my keyboard...

Pete

[jazzplusplus-devel] Web Content and Documentation

[Pete S. <pst...@ve...>]

DM>>> interest to check jazzplusplus out, along
DM>>> with some (realistic) estimation of when
DM>>> userland type tarballs are expected to be
DM>>> available....

PS>> That estimate will be tough for me to come up with.
PS>> What do you think of this version...
PS>>
PS>> http://jazzplusplus.sourceforge.net/download/

DM> Yeah, the release time estimation consideration
DM> is always tough. Mind you, the actual value might
DM> change at any time, and could be updated when so.
DM> For example, 'now' that estimation might be 'before
DM> the end of 2009', but in 3months time it might be
DM> 'by the end of this year'....it's a mobile target.

Let me think about this one...

DM> There's a small typo here and there on the
DM> download page, there's a few more likewise on
DM> other pages which I've caught on the 3rd pass.
DM>
DM> Rather than load you up with all these minor
DM> corrections,  I'll ask first if these fixups
DM> will be better served by me having a working
DM> setup of whatever documentation generation
DM> process you prefer to use?
DM>
DM> I'll hold these little corrections in check
DM> until I hear back on that....

OK.  What do you think about the following.

1. I'll put the web content in subversion so you can send me patches.
2. I make this weekend's goal the setting up of the online help/web 
user's manual build system.  It will be similar to building code.

I want to separate the two for a while.  Seem reasonable?

DM>>> ....and, if it were there, pointers to other
DM>>> docs on the site of other software already
DM>>> known to be working with devel versions
DM>>> of jazzplusplus, screenshots --

PS>> Currently I have the screen shot page commented out.

DM> Ah, okay...noted...

DM>>> I'll wait for your reply to this before
DM>>> reposting ....oh, and if you'd rather this
DM>>> private, that's fine too....

PS>> No.  I prefer a public discussion to get others interested.

DM> Agreed -- open discussion of such things on
DM> *this* list, gives every possible opportunity
DM> for the intended users of jazzplusplus to have
DM> some say in what happens next.

I did move this discussion over to the developers list because it is 
going to get into how the documentation is built instead of what it 
contains.  Feel free to keep a thread alive on the user list.

DM>>> let me know, but like that the record
DM>>> shows that there's some depth of thought
DM>>> going into the revitalized jazzplusplus

PS>> Exactly! :-)

DM>>> fork...

PS>> Keep in mind, this isn't a fork
PS>>
PS>> http://en.wikipedia.org/wiki/Fork_(software_development)
PS>>
PS>> I'm just building on the work of others without
PS>> splitting off.

DM> ...oops! I'll make sure to get that right from now on....

I just don't want to tick off the kind folks that let me have a go at 
this.  Thanks again, Pat, Dave, Kevin...

DM>>> I'll do a 3rd pass over things in the interim.

PS>> Great.  Thanks.

DM> Yep, as I mentioned above, 3rd pass revealed a few
DM> small oversights, but if the correcting/editing
DM> process is going to be streamlined by my using
DM> your preferred document generation method, then
DM> I would rather move to that method sooner than
DM> later.

If you approve of the idea, I'll put the web content in subversion and 
you can send me patches.

DM>>> ps: excuse my impoliteness, I didn't ask if
DM>>> you wanted American, or British spelling,
DM>>> sorry. You would have received Australian
DM>>> spelling by default -- please advise which
DM>>> english varient you prefer so I avoid
DM>>> spelling 'bolour' with a 'k'....

PS>> American English please.  Thanks for asking.

DM> No problem,,,,

Thanks,
Pete

Re: [jazzplusplus-devel] Building Jazz with GCC 4.2.3 on Ubuntu (Hardy)

[Pete S. <pst...@ve...>]

BS = Bruno Schödlbauer wrote:
BS> gives me:
BS>
BS> [..]
BS> ../../jazz/src/AboutDialog.cpp: In constructor
BS> »JZAboutDialog::JZAboutDialog(wxWindow*)«:
BS> .
BS> .
BS> .
BS> So g++ insists that 'wxString("About Jazz++")' is
BS> ambiguous. Heh?! ^^
BS>
BS> My intuition says it's supposed to interpret this as
BS> wxString::wxString(wxChar, size_t). Therefore, can
BS> someone give me a hint on what went wrong?

Hello Bruno,

I believe you need to build wxWidgets with STL compatibility.  I have 
posted instructions for building wxWidgets for use with Jazz++ at

http://jazzplusplus.sourceforge.net/buildingwx/

Look at the "Building wxWidgets for Linux" section.  The stock install 
on you system probably doesn't use the --enable-std_string configure option.

Hope that helps.  Let us all know,
Pete

[jazzplusplus-devel] Building Jazz with GCC 4.2.3 on Ubuntu (Hardy)

[Bruno S. <bru...@gm...>]

Hello!

 > make

gives me:

[..]
../../jazz/src/AboutDialog.cpp: In constructor
»JZAboutDialog::JZAboutDialog(wxWindow*)«:
../../jazz/src/AboutDialog.cpp:54: Error: Aufruf des überladenen
»wxString(const char [13])« ist mehrdeutig
/usr/include/wx-2.8/wx/string.h:722: Anmerkung: Kandidaten sind:
wxString::wxString(const wxWCharBuffer&) <nahe Übereinstimmung>
/usr/include/wx-2.8/wx/string.h:692: Anmerkung:
wxString::wxString(wxChar, size_t) <nahe Übereinstimmung>
/usr/include/wx-2.8/wx/string.h:690: Anmerkung:
wxString::wxString(const wxString&) <nahe Übereinstimmung>
/usr/include/wx-2.8/wx/string.h:682: Anmerkung:
wxString::wxString(int) <nahe Übereinstimmung>
[..]

("<nahe Übereinstimmung>" = possible candidate)

Lines 53 to 56 are:

JZAboutDialog::JZAboutDialog(wxWindow* pParent)
  : wxDialog(pParent, wxID_ANY, wxString("About Jazz++")),
    mpLogo(0),
    mpBitmap(0)

So g++ insists that 'wxString("About Jazz++")' is ambiguous. Heh?! ^^

My intuition says it's supposed to interpret this as
wxString::wxString(wxChar, size_t). Therefore, can someone give me a
hint on what went wrong?

Regards,
Bruno S.

Re: [jazzplusplus-devel] "Floating exception"

[Pete S. <pst...@ve...>]

PS = Pete Stieber
PS>> Would you be willing to post the offensive MIDI file
PS>> to the list or send it directly to me?

KC = Kevin Cosgrove
KC> Gosh, I forgot to send you the file!  My inbox
KC> filled up recently (90 messages)

You should see my email setup.  I subscribe to several mailing lists 
(fedora, wxWidgets...) and have thousands of unread emails, so I can 
relate...

KC> and I'm getting ready for 3 gigs this weekend,
KC> hand drums in one,

I'm not a "hand drums guy", but have you ever looked at the Roland 
HandSonic 
(http://www.rolandus.com/products/productdetails.aspx?ObjectId=765)?

I'm not a Roland rep either, but I do love my TD-20 electronic kit :-)

KC> drumkit in another, and sound tech in
KC> another -- yes, 3 bands.
KC>
KC> I'm attaching the file.  It's a demo song from the
KC> old Jazz++ 4.1.3 release from years back.

I actually have that version compiled on Windows.  It's under the 
branches directory.  I had to resurrect an ancient version of wxWidgets 
to get it built and convert the project file from Visual Studio 5 to 
Visual Studio 6, but I got it built and working.

KC> You might want to try to play a few of those.
KC> I have all the old demos, if you want some.

Your right, I should try to play more samples.  I was just excited to 
get Jazz++ built and playing anything.  I'm also trying to focus on 
getting other features to work.  You still can't select or edit events. 
  I just need some time to work on it.

I think some (if not all) of the old demo files are in the subversion 
repository.  When I posted instructions for you to build the code, I 
only had you checkout the trunk, but there is also a branches directory 
structure.  There are MIDI files in the repository in both locations. 
There are probably redundant MIDI files in the various versions.

Maybe the file you sent me is the same as the one under jazz/song/demo1.mid?

KC> Actually, I have hundreds of MIDI files.

Maybe I should create a separate directory for sample MIDI files that is 
independent of the code.  We could put samples in that directory and 
point to the directory on the web site.

PS>> I could run it using a debugger on a different
PS>> OS (the Windows version works too) and see what
PS>> is causing the problem.  No application should
PS>> cause the machine to lockup.  Core dump for
PS>> sure, but not lockup the kernel.

KC> Agreed.

PS>> I could also try playing the file using gdb on
PS>> Fedora 8.  I've never had Jazz++ (or any other
PS>> application) lockup Fedora.

KC> The only time I've had an application on Linux
KC> lock up a system is when it turned out that I
KC> was using the wrong RAM for my vintage of
KC> motherboard.  Was that EVER hard to figure out;
KC> it took me over a year.

I had it happen here with Mandriva 2008, but not on any other OS using 
the same machine.

PS>> I'll be heading off to work soon, but if you can
PS>> send me the file, I'll look at it tonight.
PS>>
PS>> Thanks again for the testing,

KC> Sorry again to be so delinquent.....

No problem.  I'll look at this when I get the time.  I know you can 
relate to that ;-)

Pete