Re: [Shapefusion-devel] wx Compatibility Problems

[tiennou <tie...@gm...>]

Le 10 mars 07 =C3=A0 01:08, Tito Dal Canton a =C3=A9crit :

> On Fri, 2007-03-09 at 12:12 +0100, tiennou wrote:
>> I'm trying to find a solution to the ankward wx installation on =20
>> OSX...
>> I think that I'll add my frameworks to the Product page, and add a
>> note that they are needed for compilation, because it is much easier
>> to tell users to install wx.framework in /Library/Frameworks than =20
>> make
>> them twiddle with ShapeFusion precompiled headers settings, include
>> directories, and others...
> I don't think that's a great problem. Because we will release a
> statically linked binary, and if one wants to compile from Xcode, he
> will probably know how to tell the project where to find everything
> needed. And also, wx installations will be pretty the same =20
> everywhere I
> guess, so no changhe should be needed at all. Am I wrong?

This will mainly depend where people install their wx source...
For example, I put mine in /Volumes/myHD/Sources/Others/wxWidgets =20
which means that :
- Xcode project in /Volumes/myHD/Sources/Others/wxWidgets/src/=20
wxWindows.xcodeproj
- precompiled header is in /Volumes/myHD/Sources/Others/wxWidgets/=20
include/wx/wxprec.h
- bundled wx icon in /Volumes/myHD/Sources/Others/wxWidgets/src/mac/=20
carbon/wxmac.icns
Oh I guess we really need something more OSXyy from wx...
I'll add some info for MacOS X in the INSTALL file...

>
>> If you are fine with this, then I'll add my two frameworks somewhere
>> on the project page...
> I'm reluctant about this... Let's see if we can avoid it.
>
>> But I'm having compatibility problems ;-)
>> You are still using 2.6.*, and I'm using 2.8.2 for development... =20
>> When
>> using __WXDEBUG__ framework, I just have some warnings about the fact
>> that wxRect.Inside() is deprecated (can be changed to Contains()), =20=

>> but
>> when linking with the release framework, I get errors about this, and
>> the fact that wxOPEN is not defined (replaced by wxFD_OPEN in =20
>> 2.8). So
>> I would like to know if it is possible for you to upgrade...
> Damn it, I feared that. I'd need to either compile wx from source or
> reinstall a more recent ubuntu. I'd really like to avoid either, =20
> since I
> have a very robust, stable and strongly personalized system. =20
> Actually I
> begin to have quite a number of reason to upgrade, but I'm waiting =20
> until
> something happens (e.g. something VERY important to upgrade, or hard
> disk crash---let's hope the former). I'm quite conservative on =20
> upgrades,
> you see.

Hmm, guess I can downgrade instead, until you upgrade your distro...
(I'm wondering what was the wxMac support in wx2.6...)
Or I can release stuff using the wx debug version...

> I see that wxOPEN is used just 3 times in ShapesView (excluding
> ShapesEditor), so let's find a way to do the trick. #ifdef? As for
> Inside(), I don't seem to have Contains(). But WHY THE HELL do they =20=

> need
> to change such an API name!

That's right that I found this very *funny*. Guess they had a pretty =20
good reason...

>> In other news, I've bought the "Cross-platform GUI programming with
>> wxWidgets", so I will have more information on the Document/View
>> framework...
> That's cool.

(I think you're gonna laugh at me, but if you're looking for it, you =20
can go take a look to http://en.wikipedia.org/wiki/WxWidgets (Grr, I =20
should have looked better...)
But this wasn't really worth the effort... The chapter about Document/=20=

View is only the making-of of the docview sample, so there is not =20
really more information about it than that...)

tiennou=