vjoel at path.berkeley.edu
Thu Feb 9 15:57:17 EST 2006
Hm, I remember 1.0->1.2 was a bit painful, but 1.2->1.4 was almost no
effort, so the API seems to have settled down.
Meinrad Recheis wrote:
> i *guess* it's due to the massive changes of the fxruby api. please
> dont take it as an offence, lyle ;)
> every time a new version of fox is released, the fxruby api changes a
> lot. a big gui application can become totally broken and it may
> require days to port it to the new fxruby version. i know it from my
> own experience @ work ;) until now we stayed with fxruby 1.0.28 at
> work because nobody wanted to pay the porting time. i am working for 2
> days now on it and its still not completed.
> On 2/9/06, Russell Fulton <r.fulton at auckland.ac.nz> wrote:
>> Antti Karanta wrote:
>>> So I compiled fox 1.2 and now the images look fine.
>> I notice that there are several important apps that only work with
>> fox1.2 (including freeride). What is the issue that prevents these apps
>> being moved to 1.4?
>> fxruby-users mailing list
>> fxruby-users at rubyforge.org
> fxruby-users mailing list
> fxruby-users at rubyforge.org
vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407
More information about the fxruby-users