Re: [Pyobjc-dev] Developing on 10.5, targeting 10.4u

[David B. <db3...@gm...>]

Ronald Oussoren <ron...@ma...> writes:

> On 26 Mar, 2008, at 18:36, David Bolen wrote:
(...)
>> Is it also still true that things will break if the WebKit framework
>> gets updated on a 10.4 system to the latest version?  (...)
>
> That's true for PyObjC 1.4. I definely won't fix that, I really don't
> have time for that. PyObjC 2.x uses a completely different method for
> wrapping frameworks.

Yep, I've followed that.  And currently 2.x can't be used on a 10.4
system (barring further resources on it), correct?

> The good news is that it should be possible to update the problematic
> wrappers using tools included with PyObjC 1.4, "Tools/CodeGenerators/
> cocoa_generator.py" is the script that I used to create the framework
> wrappers in PyObjC 1.4. The main portion of that is a Python script
> that parses header files using regular expressions and generates the
> Python and ObjC code for the wrappers. Running that on a 10.4.11
> system should get you working wrappers for that version of webkit.

Thanks - I'm in a little catch-22 in that I've only one primary system
for development, so if the above didn't work, I'd be upgraded but
couldn't build the app any more.  I'll have to see if I can find a
sacrificial system to try to build the new wrapper on.

If you've currently got an application developed on 10.4 that is used
on 10.4 and 10.5 clients, is there a view on what the most robust
current development approach is?  To date I've just stuck with my
existing PyObjC 1.4, and limited OSX to 10.4.10.  The choices of
moving to 10.5 with PyObjC 2 on the development machine, or using 1.4
with 10.4.11, seemed likely to be more risky and/or problematic than
just staying with what I had.  Though of course I can't stay in that
state forever.

I was hoping PyObjC 2 might make it back to 10.4 to then provide an
upgrade path where I didn't have to change two systems (PyObjC and
OSX) simultaneously, but I completely understand that the resources to
do so haven't been (and may never be) available.

-- David