Re: [jazzplusplus-devel] Re: jazzplusplus-devel digest, Vol 1 #43 - 4 msgs

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

Dave answered very aptly, I add some small further suggestions below:

Dave Fancella <dav...@co...> writes:

>> I tried to generate a Makefile with autoconf but got 3 different confusing
>> error messages with 3 different versions of these tools (2 cygwin on

please let us now these errors!



> Correct enough for MSVC++.  That's how Audacity solves this problem.  Now, in 
> config.h you must put all defines that are determined by the ./configure 
> script on GNU systems.

I include the config.h one my automake generates for reference, see below.


>
> You'll have to piece this one out, I think.  I don't know what it does.  ;)  
> Maybe someone else does?

for some reason the original developers chose to put the mswin midi
player in a dll. Maybe they had some different tools that used the
same dll?

Anyway, my suggestion is to simply disable playback altogether at
first. It will be complicated enough just to get jazz to compile
again under windows. And your area of interest doesnt really require
playback initially.


>> What are the wxProperty... things ? You can only use them if macro
>> "wxUSE_PROPSHEET" is not 0. In the file lib/msw/wx/setup.h it is #defined
>> to be 0! I had to add "$(WXWIN)/lib/msw" to my inlucde path - like in the
>> wxWidgets sample programs - to get things compiled. I had to change the
>> value to 1 in the wxWidgets source, but I guess it's not the way it is
>> meant by the inventors. But what is correct ? Not to use wxProperty...
>> classes in Windows programs ??

They are used in some dialogs. Why you need a special define to use
them is odd.

Anyway, we are moving away from this system to an xml resource based
system, so the dialogs using these proerties will go away, meaning
you can comment out those dialogs if you want. 

if you tell me which dialogs are giving you problems, I can port them
to the new system. Its not much work, and I will have time again next week.


>> The amount of specific code for Windows I saw up to now was frightening! I
>> had the hope that the OS interface is covered by wxWidgets (neary
>> completely). Isn't that the case ?

Remember that the old jazz core was built on wx1.68. There were tons
of windows specific things you had to do.

As we port more things to wx2, these windows specific hacks will go
away.

As an example, there were code that calculated heights of widgets and
stuff differently between mswin and linux. This stuff vanished(will
vanish) when dialogs are moved to the new xml based layout system,
which is the same for all platforms.


> I really appreciate you taking the time to work on this, I can't say enough 
> thank you.  :)

Me also! It will be very interesting to see your ideas in practice.



> Dave
>
>> Looking forward to your answers
>> Harald
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: GNOME Foundation
>> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
>> GNOME Users and Developers European Conference, 28-30th June in Norway
>> http://2004/guadec.org
>> _______________________________________________
>> jazzplusplus-devel mailing list
>> jaz...@li...
>> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel
>
> -- 
> Visit my website!
> http://www.davefancella.com/?event=em
>
> To whom the mornings are like nights,
> What must the midnights be!
> 		-- Emily Dickinson (on hacking?)
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> jazzplusplus-devel mailing list
> jaz...@li...
> https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel