wxruby users - Jul 2005 - More wxruby-swig changes

I just checked in several changes from Sean Long that should make 
wxruby-swig work with wx 2.6 as well as 2.5.

I also committed his changes to extconf.rb. But could someone please 
explain to me why anyone would prefer to use extconf.rb instead of rake? 
It just seems like one more piece of code to maintain, and I don''t like
extra code.

Sean: The other diffs in the patch you sent were all due to changes I 
checked in recently that weren''t in your baseline. As far as I know, I 
have incorporated all the changes you have sent me so far. You have also 
added some classes and samples, right? Can you send those as patches too?

Next up for me: Make xrc non-optional, and try to figure out how to get 
rid of the WXRUBY_SWIG environment variable by just detecting whether or 
not SWIG is available.

Thanks much,

Kevin

> I also committed his changes to extconf.rb. But could someone please 
> explain to me why anyone would prefer to use extconf.rb instead of rake? 
> It just seems like one more piece of code to maintain, and I don''t
like
> extra code.
I much prefer Rake too. It''s either bundled or easy-to-install these 
days, so reducing the argument for extconf.rb as a standalone.

It may be worth looking at the install stage (OS X only) of the Rakefile 
if dumping extconf.rb:

http://rubyforge.org/pipermail/wxruby-users/2005-February/001166.html

Also I don''t know how well Rakefiles play with Rubygems - but the
manual
entry seems to suggest it''s possible.

http://docs.rubygems.org/read/chapter/20#extensions

I can look at these latter two once your work''s stabilised and i have
my
laptop back

a

> Sean: The other diffs in the patch you sent were all due to changes I
> checked in recently that weren''t in your baseline. As far as I
know, I
> have incorporated all the changes you have sent me so far. You have also
> added some classes and samples, right? Can you send those as patches too?
I am attaching a small patch and the missing files, the xrc.zip is for
the samples/ folder.


Sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff.list
Type: application/octet-stream
Size: 8191 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/wxruby-users/attachments/20050720/8919ca01/diff-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xrc.zip
Type: application/zip
Size: 1867 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/wxruby-users/attachments/20050720/8919ca01/xrc-0001.zip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ProgressDialog.i
Type: application/octet-stream
Size: 256 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/wxruby-users/attachments/20050720/8919ca01/ProgressDialog-0001.obj

Sean Long wrote:
> I am attaching a small patch and the missing files, the xrc.zip is for
> the samples/ folder.
I tried to apply these last night, but encountered several problems that 
seem to be due to changes between wx 2.5 and 2.6. I can''t think of a 
clean way to support both, so I plan to upgrade myself to 2.6 and then 
change wxruby2 to only support that version.

However, I definitely do not want to impose a binary dependency on wx 
2.6 since it is not available for Ubuntu (and perhaps others). For this 
reason and others (e.g. unicode support), I plan to link wx statically 
into wxruby2, at least on Linux. It probably makes sense on other 
platforms, but I''m not in a good position to decide that. I do not plan
to support dynamic linking at all for Linux, and suggest the same for 
other platforms, to keep everything as simple as possible.

I will upgrade my system to 2.6, and then will apply Sean''s latest 
changes. After that, I plan to begin the naming changes to wxruby2. 
However, this is a busy week for me, so I''ll probably only have a
little
time each day to make a little progress.

Kevin

Kevin Smith wrote:
> 
> I tried to apply these last night, but encountered several problems that 
> seem to be due to changes between wx 2.5 and 2.6. I can''t think of
a
> clean way to support both, so I plan to upgrade myself to 2.6 and then 
> change wxruby2 to only support that version.
I''m changing my mind again.

I have been experimenting with wx 2.6 today. I got it to link 
statically, but I''m really not sure that''s the best option
after all. It
seems like it introduces more complexity and more dependencies, rather 
than less.

At this point, I am again leaning toward trying to support 2.5+.
> I will upgrade my system to 2.6, and then will apply Sean''s latest
> changes. 
I have not yet attempted (again) to apply Sean''s latest patches in a
way
that lets them work with wx 2.5. On the other hand, the code that is 
currently checked into the head compiles with both 2.5 and 2.6 on my 
system, so I am more optimistic that the problems are not due to 
differences between 2.5 and 2.6.

Kevin

Kevin Smith wrote:
> I have not yet attempted (again) to apply Sean''s latest patches in
a way
> that lets them work with wx 2.5. On the other hand, the code that is 
> currently checked into the head compiles with both 2.5 and 2.6 on my 
> system, so I am more optimistic that the problems are not due to 
> differences between 2.5 and 2.6.
I just checked in code that integrates Sean''s patches, and tagged a 
0.0.20 version. My next step is to make the switch to wxruby2 naming, 
including having the wx.rb wrapper in the lib/ directory. I''m not sure 
how this will affect the MSWin and Mac build/install processes.

I have only found one true difference between 2.5 and 2.6 so far, and 
that is the addition of a "skip" parameter to ProgressDialog#update.
So,
for now, I have left that parameter off. We''ll have to try to figure
out
a clean way to support it.

Sean: Please try the latest HEAD (or v0-0-20) as-is. If you find any 
problems, please let me know so we can work together to find ways to 
solve them that are compatible with both 2.5 and 2.6.

Kevin