From chauk.mean at gmail.com  Wed Dec  1 17:07:02 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Wed, 1 Dec 2010 23:07:02 +0100
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <4CF37548.1050901@pressure.to>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
	<4CF37548.1050901@pressure.to>
Message-ID: <AANLkTi=yUkuHdjWEq1+USN0Hmu1U5FW5jE1hiGOFVsoR@mail.gmail.com>

Hi all,

2010/11/29 Alex Fenton <alex at pressure.to>:
> Hi Carlo
>
> On 29/11/10 08:09, Carlo Bertini wrote:
>>
>> I wanted to know whether the development of the project is still active
>> or not.
>> many bugs in the bug tracker are open from 25/03/2009 ....
>
>
> I wouldn't call a project with a stable, complete release across half a
> dozen platforms 'dead' - but it's true that little or no new code has been
> committed in the past 12 months or so since the release of 2.0.1. I led the
> development of 2.0 but have been doing other non-programming things, but am
> around on the mailing list along with other devs. Hibernation maybe?
>
> cheers
> alex

Indeed, there have not been many bugfixes. We all have non-programming
activities :-)
Nevertheless, during the last months, I've committed fixes to the
stable branch to ensure that wxRuby builds properly with an up-to-date
environment :
- ruby-1.9.2 / rubygems-1.3.7
- SWIG-2.0
As Alex wrote, wxRuby is not dead but maybe in hibernation !

cheers,
Chauk-Mean.

From chauk.mean at gmail.com  Wed Dec  1 17:16:43 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Wed, 1 Dec 2010 23:16:43 +0100
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <AANLkTimJgH0X0of2X3wcbf3KHgr9iWW+PO-zB90Qrug3@mail.gmail.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
	<4CF37548.1050901@pressure.to>
	<AANLkTimJgH0X0of2X3wcbf3KHgr9iWW+PO-zB90Qrug3@mail.gmail.com>
Message-ID: <AANLkTimBA_NKS+KuxHHfqZijFr9PxBDX7H1ouA0Bx9p9@mail.gmail.com>

Hi Don,

2010/11/29 Don Wilde <dwilde1 at gmail.com>:
> On Mon, Nov 29, 2010 at 1:41 AM, Alex Fenton <alex at pressure.to> wrote:
>> I wouldn't call a project with a stable, complete release across half a
>> dozen platforms 'dead' - but it's true that little or no new code has been
>> committed in the past 12 months or so since the release of 2.0.1. I led the
>> development of 2.0 but have been doing other non-programming things, but am
>> around on the mailing list along with other devs. Hibernation maybe?
>>
> Alex, if that is the case it would be very good if we (and I include myself
> as a sacrificial offering) could get the docs updated to match the new code
> base. It is very frustrating to discover that half the 'overviews' are gone
> completely, and wxRuby is vastly different from wxC++ in the way things like
> Device Contexts and such are instantiated. I have been able to get my code
> to work well (after reading and re-RTFM-ing), but I'll bet it would be even
> better if I knew the little bits of tribal knowledge that you have stored in
> your collective brains.

I've seen that you faced some documentation issues.
Could you create some bug reports for tracking them ?
Also, documentation patches are always welcome
(http://wxruby.rubyforge.org/wiki/wiki.pl?DocumentingWxRuby).

cheers,
Chauk-Mean.

From alex at pressure.to  Wed Dec  1 17:33:04 2010
From: alex at pressure.to (Alex Fenton)
Date: Wed, 01 Dec 2010 22:33:04 +0000
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <AANLkTimJgH0X0of2X3wcbf3KHgr9iWW+PO-zB90Qrug3@mail.gmail.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>	<4CF37548.1050901@pressure.to>
	<AANLkTimJgH0X0of2X3wcbf3KHgr9iWW+PO-zB90Qrug3@mail.gmail.com>
Message-ID: <4CF6CD20.8030803@pressure.to>

Hi Don

On 29/11/10 15:13, Don Wilde wrote:
> Alex, if that is the case it would be very good if we (and I include 
> myself as a sacrificial offering) could get the docs updated to match 
> the new code base. It is very frustrating to discover that half the 
> 'overviews' are gone completely, and wxRuby is vastly different from 
> wxC++ in the way things like Device Contexts and such are 
> instantiated. I have been able to get my code to work well (after 
> reading and re-RTFM-ing), but I'll bet it would be even better if I 
> knew the little bits of tribal knowledge that you have stored in your 
> collective brains.

Yes, I agree a big part of a library's usefulness is whether it's well 
documented. I set up the current doc system for this reason, but it's 
certainly not what it could be. The tricky bit is documenting a very 
large library from scratch when about 90% of it (getter/setter 
methods...) is shared with wx C++. What's needed is something that can 
bring together 1) the existing, good documentation from wx C++ 2) the 
info SWIG provides about the C++ to Ruby mapping and 3) manual 
annotations, in a way that's manageable for a small development team.

I guess we've tended to prioritise adding samples to document the 
implementation of wxRuby, since these serve as test cases, demo code and 
partial docs at once. But additions to the current docs are also welcome 
(in Textile format). I think there's also a need to document SWIG 
knowledge - which is probably the really hard bit of 'tribal knowledge' 
I have stored in my brain.

a

From dwilde1 at gmail.com  Wed Dec  1 22:40:41 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Wed, 1 Dec 2010 19:40:41 -0800
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <4CF6CD20.8030803@pressure.to>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
	<4CF37548.1050901@pressure.to>
	<AANLkTimJgH0X0of2X3wcbf3KHgr9iWW+PO-zB90Qrug3@mail.gmail.com>
	<4CF6CD20.8030803@pressure.to>
Message-ID: <AANLkTi=BbGSJEvvM2by9AaEro04pY2rri+esmjOhnat+@mail.gmail.com>

Hi, Alex et al -

On Wed, Dec 1, 2010 at 2:33 PM, Alex Fenton <alex at pressure.to> wrote:

> Hi Don
>
>
> On 29/11/10 15:13, Don Wilde wrote:
>
>> Alex, if that is the case it would be very good if we (and I include
>> myself as a sacrificial offering) could get the docs updated to match the
>> new code base. It is very frustrating to discover that half the 'overviews'
>> are gone completely, and wxRuby is vastly different from wxC++ in the way
>> things like Device Contexts and such are instantiated. I have been able to
>> get my code to work well (after reading and re-RTFM-ing), but I'll bet it
>> would be even better if I knew the little bits of tribal knowledge that you
>> have stored in your collective brains.
>>
>
> Yes, I agree a big part of a library's usefulness is whether it's well
> documented. I set up the current doc system for this reason, but it's
> certainly not what it could be. The tricky bit is documenting a very large
> library from scratch when about 90% of it (getter/setter methods...) is
> shared with wx C++. What's needed is something that can bring together 1)
> the existing, good documentation from wx C++ 2) the info SWIG provides about
> the C++ to Ruby mapping and 3) manual annotations, in a way that's
> manageable for a small development team.
>
> I guess we've tended to prioritise adding samples to document the
> implementation of wxRuby, since these serve as test cases, demo code and
> partial docs at once. But additions to the current docs are also welcome (in
> Textile format). I think there's also a need to document SWIG knowledge -
> which is probably the really hard bit of 'tribal knowledge' I have stored in
> my brain.
>
> a
>
Anything that deals with multiple languages and interfaces is going to be
tough. While I've played with C++, I've never gone deep with it, so docs
that come from 'here's how it works in C++' as a starting point are
sometimes baffling especially WRT DeviceContexts. I have gotten insights
from the C++ wxWidgets book, and, in fact, figured out my re-paint on
exposure solution after digging there and thinking hard.

This is not in any way to say that it is your "fault" that the docs are the
way they are, except in a good way. :D

I love the examples from a 'neato' perspective, but some of them drive me
nuts because I have to erase all the loops and random color insertions.
Besides the fun toys, examples that demonstrate one thing at a time are
needed.

Now that I've swum through the seaweed, I'll see if I can extract a simple
example and submit that as a start.

AFA doc patches, usually where I get bitten is where there is no ruby-side
doc at all (such as the evt_xyz names and what class they inherit from). I'm
not good enough yet to be able to surf the C++ and SWIG interfaces to figure
it out, but I'll keep learning.

I love using this Wx library with Ruby; I'm blowing the boss's mind and he's
stopped muttering about Intel's commitment to C++ and Qt, at least for the
moment.
-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101201/87774453/attachment.html>

From dwilde1 at gmail.com  Mon Dec 13 13:16:23 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Mon, 13 Dec 2010 10:16:23 -0800
Subject: [wxruby-users] layers
Message-ID: <AANLkTikgH+YyKSo11UVkzU6bp59ST=o00bNf-a-=sVga@mail.gmail.com>

Is there a way to stack windows in Z dimension? I find that quite useful in
Android, and it would be useful here. I don't see it in the docs or the C++
book, so perhaps it's a wish list item.

For example, I have a gauge to display with a moving dial pointer. Due to
the fact that the pointer crosses several colors, simply "un-writing" the
pointer before moving it will not work, so I need to redraw the underlying
gauge which often hiccups even on my 4-core Ubuntu system.

If sizers could stack in Z, the top pane would be transparent except for the
dial pointer and it would be the only thing redrawn.
-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101213/0dcf600d/attachment.html>

From chauk.mean at gmail.com  Sat Dec 18 06:07:38 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Sat, 18 Dec 2010 12:07:38 +0100
Subject: [wxruby-users] layers
In-Reply-To: <AANLkTikgH+YyKSo11UVkzU6bp59ST=o00bNf-a-=sVga@mail.gmail.com>
References: <AANLkTikgH+YyKSo11UVkzU6bp59ST=o00bNf-a-=sVga@mail.gmail.com>
Message-ID: <AANLkTimtJWJv4wALormriXEzDEG=SGt5jRxJ3aABc80y@mail.gmail.com>

Hi,

2010/12/13 Don Wilde <dwilde1 at gmail.com>:
>
> Is there a way to stack windows in Z dimension?

I haven't used them yet , but there are two methods that control the
z-hierarchy of a window.
Window#bring_to_front and Window#send_to_back.

Cheers,
Chauk-Mean.

From dwilde1 at gmail.com  Sat Dec 18 13:39:46 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Sat, 18 Dec 2010 10:39:46 -0800
Subject: [wxruby-users] layers
In-Reply-To: <AANLkTimtJWJv4wALormriXEzDEG=SGt5jRxJ3aABc80y@mail.gmail.com>
References: <AANLkTikgH+YyKSo11UVkzU6bp59ST=o00bNf-a-=sVga@mail.gmail.com>
	<AANLkTimtJWJv4wALormriXEzDEG=SGt5jRxJ3aABc80y@mail.gmail.com>
Message-ID: <AANLkTik254OeuTHcvYznTFDLt5+54nTAMRD1d5auy0UN@mail.gmail.com>

On Sat, Dec 18, 2010 at 3:07 AM, Chauk-Mean Proum <chauk.mean at gmail.com>wrote:

> Hi,
>
> 2010/12/13 Don Wilde <dwilde1 at gmail.com>:
> >
> > Is there a way to stack windows in Z dimension?
>
> I haven't used them yet , but there are two methods that control the
> z-hierarchy of a window.
> Window#bring_to_front and Window#send_to_back.
>
> Hi, Chauk-Mean -

I suspect that that refers to the window / frame relative to the window
manager hierarchy, the OS.  What I want to do is to stack panels  inside a
sizer such that they overlap. I haven't seen anything on that.

-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101218/b784d601/attachment.html>

From chauk.mean at gmail.com  Sun Dec 19 17:03:21 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Sun, 19 Dec 2010 23:03:21 +0100
Subject: [wxruby-users] layers
In-Reply-To: <AANLkTimAyxjDYfoimRiJ+8hpTdn_TkujSnGpnXXQFZO7@mail.gmail.com>
References: <AANLkTikgH+YyKSo11UVkzU6bp59ST=o00bNf-a-=sVga@mail.gmail.com>
	<AANLkTimtJWJv4wALormriXEzDEG=SGt5jRxJ3aABc80y@mail.gmail.com>
	<AANLkTik254OeuTHcvYznTFDLt5+54nTAMRD1d5auy0UN@mail.gmail.com>
	<AANLkTimAyxjDYfoimRiJ+8hpTdn_TkujSnGpnXXQFZO7@mail.gmail.com>
Message-ID: <AANLkTikNn39Wwp3wCaDZQVn+NhccCW5Nn55sBF=aPccC@mail.gmail.com>

Hi Don,

2010/12/18 Don Wilde <dwilde1 at gmail.com>:
>> I haven't used them yet , but there are two methods that control the
>> z-hierarchy of a window.
>> Window#bring_to_front and Window#send_to_back.
>>
> Hi, Chauk-Mean -
>
> I suspect that that refers to the window / frame relative to the window
> manager hierarchy, the OS.? What I want to do is to stack panels? inside a
> sizer such that they overlap. I haven't seen anything on that.
>
> -- Don Wilde

It seems that you're right.
Window#bring_to_front and Window#send_to_back correspond respectively
to wxWidgets Window#raise and Window#lower. The methods have been
renamed for consistency and to avoid name conflict with Kernel#raise.
And raise and lower work only for top level windows (see
http://trac.wxwidgets.org/ticket/4717).
According to the ticket, overlapping windows/controls are not advised.
Unfortunately the wxWidgets documentation has not been updated
accordingly (http://docs.wxwidgets.org/stable/wx_wxwindow.html#wxwindow).
Regarding wxRuby, I'll fix the documentation to clarify this point.

Cheers,
Chauk-Mean.

From dwilde1 at gmail.com  Sun Dec 19 19:28:27 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Sun, 19 Dec 2010 16:28:27 -0800
Subject: [wxruby-users] layers
In-Reply-To: <AANLkTimAyxjDYfoimRiJ+8hpTdn_TkujSnGpnXXQFZO7@mail.gmail.com>
References: <AANLkTikgH+YyKSo11UVkzU6bp59ST=o00bNf-a-=sVga@mail.gmail.com>
	<AANLkTimtJWJv4wALormriXEzDEG=SGt5jRxJ3aABc80y@mail.gmail.com>
	<AANLkTik254OeuTHcvYznTFDLt5+54nTAMRD1d5auy0UN@mail.gmail.com>
	<AANLkTimAyxjDYfoimRiJ+8hpTdn_TkujSnGpnXXQFZO7@mail.gmail.com>
Message-ID: <AANLkTi=MLYduxed-xx41HLrk3ESJrpQknWVAvqMfEXf_@mail.gmail.com>

On Sun, Dec 19, 2010 at 2:00 PM, Chauk-Mean Proum <chauk.mean at gmail.com>wrote:

> Hi Don,
>
> 2010/12/18 Don Wilde <dwilde1 at gmail.com>:
> >> I haven't used them yet , but there are two methods that control the
> >> z-hierarchy of a window.
> >> Window#bring_to_front and Window#send_to_back.
> >>
> > Hi, Chauk-Mean -
> >
> > I suspect that that refers to the window / frame relative to the window
> > manager hierarchy, the OS.  What I want to do is to stack panels  inside
> a
> > sizer such that they overlap. I haven't seen anything on that.
> >
> > -- Don Wilde
>
> It seems that you're right.
> Window#bring_to_front and Window#send_to_back correspond respectively
> to wxWidgets Window#raise and Window#lower. The methods have been
> renamed for consistency and to avoid name conflict with Kernel#raise.
> And raise and lower work only for top level windows (see
> http://trac.wxwidgets.org/ticket/4717).
> According to the ticket, overlapping windows/controls are not advised.
> Unfortunately the wxWidgets documentation has not been updated
> accordingly (http://docs.wxwidgets.org/stable/wx_wxwindow.html#wxwindow).
> Regarding wxRuby, I'll fix the documentation to clarify this point.
>
>
Yes, it does appear to be a design decision. Very useful 'would be nice',
though! :D

Thanks, Chauk-Mean.
-- 
-- Don Wilde
ph: 512-394-8896 skype: donwilde1
e: dwilde1 at gmail.com
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101219/ea97408d/attachment-0001.html>

From lists at ruby-forum.com  Mon Dec 20 02:34:57 2010
From: lists at ruby-forum.com (Fred L.)
Date: Mon, 20 Dec 2010 08:34:57 +0100
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
Message-ID: <fcd75e175f3a63f026a16db16b5840ac@ruby-forum.com>

Hello,
I'm a beginner with Ruby and even more with wxRuby and it was a question 
I was planning to ask too, because the "news" on wxRuby website are 
rather old and the roadmap is dated from 2009.

wxWidgets 2.9.2 is about to come shortly (as to the wxWidgets roadmap) 
and the "main release goals" of v3.0 are all marked "done" or "almost 
done".

there are nice things in the wxRuby Roadmap, but maybe it could be 
actualised and a message could be add about that "paused" progression of 
wxRuby.. at least to let the newcomers know exactly what to expect.

of course I completely understand that you can't keep all your time on 
wxRuby development, I also got very little time to learn Ruby/wxRuby 
right now. but maybe a message could also be add to ask some help or new 
developpers...?

Fred

-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Tue Dec 21 05:03:46 2010
From: lists at ruby-forum.com (Fred L.)
Date: Tue, 21 Dec 2010 11:03:46 +0100
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
Message-ID: <305d9116399fc63b1d09d5b97cc635b0@ruby-forum.com>

just to let you see what we could get with wxWidgets 3.0 :
(sorry if it's an "old" info, but I just discovered it yesterday)
http://www.wxdesigner-software.de/WoWoW30.html

-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Wed Dec 22 01:28:08 2010
From: lists at ruby-forum.com (Ridge McGhee)
Date: Wed, 22 Dec 2010 07:28:08 +0100
Subject: [wxruby-users] OS X Snow Leopard + wxRuby 2.0.1 gem - WORKING
In-Reply-To: <4C344B85.6000808@pressure.to>
References: <4C344B85.6000808@pressure.to>
Message-ID: <32957dcaa6087e7ff290cbb1e73bb5dc@ruby-forum.com>

Some good news...

Alex, your method didn't work for me immediately but I found a method
that works for me and may help others.

I have a MacBook Pro (64-bit) running OS X 10.6.
Like others, I wanted to run Ruby 1.9.2 (latest) and wxRuby 2.0.1 
(latest).

I use RVM to install Ruby 1.9.2 (and manage my ruby versions).
(See http://pragmaticstudio.com/blog/2010/9/23/install-rails-ruby-mac)

By default, RVM builds the Ruby 64-bit version (only).
I finally found a post that indicates how to build both 32-bit and 
64-bit versions of Ruby.

Briefly, here's how to get both built:
rvm install ruby-1.9.2-head -C --with-arch=x86_64,i386

Here's how to check what you have:
file `which ruby` | perl -pe 's|^.*/||'

(Which will produce output like this:)
ruby: Mach-O universal binary with 2 architectures
ruby (for architecture x86_64): Mach-O 64-bit executable x86_64
ruby (for architecture i386):   Mach-O executable i386

Visit:
http://rubyforge.org/frs/?group_id=35

And, download this gem:
wxruby-ruby19-2.0.1-x86-darwin-9.gem

Now, install the gem (no sudo required):
(Note, you may want to cd to your Downloads folder.)
gem install wxruby-ruby19-2.0.1-x86-darwin-9.gem
Successfully installed wxruby-ruby19-2.0.1-x86-darwin-9

Create a wxruby test script (wxtest.rb):
------------------------------------
#!/usr/bin/env arch -i386 ruby

require 'wx'
include Wx

App.run do
  frame = Frame.new(nil, :title => 'So far, so good...')
  frame.show
end
------------------------------------

And run it:
> ruby wxtest.rb


Ok, so this particular working set produced a window.
So, we (or I anyway) have a way to proceed.

Alex - I hope this somehow helps you find out what the problem
(32-bit vs 64-bit) might be.  Any thoughts?

Cheers,
Ridge


Alex Fenton wrote in post #923756:
> Hi
>
> It is possible to use the standard wxRuby 2.0.1 gem with the standard
> system ruby in /usr/bin/ruby in OS X 10.6
>
> 1) download the gem
>
> http://rubyforge.org/frs/download.php/63386/wxruby-2.0.1-universal-darwin-9.gem
>
> 2) install it from the downloaded file
>
> sudo gem install wxruby-2.0.1-universal-darwin-9.gem
>
> 3) run ruby like this, forcing 32-bit mode
>
> arch -i386 ruby -rubygems <scriptfile.rb>
>
>
> Have tested with a couple of samples and this works fine. Appreciate any
> feedback. Of course, we are still aiming to get full compatibility, but
> for various reasons this is quite difficult.
>
> Thanks to some advice on this page (comment #4)
> http://weblog.rubyonrails.org/2009/8/30/upgrading-to-snow-leopard
>
> alex

-- 
Posted via http://www.ruby-forum.com/.

From alex at pressure.to  Wed Dec 22 07:10:49 2010
From: alex at pressure.to (Alex Fenton)
Date: Wed, 22 Dec 2010 12:10:49 +0000
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <fcd75e175f3a63f026a16db16b5840ac@ruby-forum.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
	<fcd75e175f3a63f026a16db16b5840ac@ruby-forum.com>
Message-ID: <4D11EAC9.3080108@pressure.to>

On 20/12/2010 07:34, Fred L. wrote:
> I'm a beginner with Ruby and even more with wxRuby and it was a question
> I was planning to ask too, because the "news" on wxRuby website are
> rather old and the roadmap is dated from 2009.
>
> wxWidgets 2.9.2 is about to come shortly (as to the wxWidgets roadmap)
> and the "main release goals" of v3.0 are all marked "done" or "almost
> done".

That's really handy to know - part of the reason I got stalled was b/c I 
couldn't get a development environment working on OS X after upgrading 
to 10.6. But it sounds like 3.0 is much closer and should be usable now.

Like you say, there are a lot of things that are exciting in there; some 
of the architectural changes will help the redesign of wxruby 3.0 
(though I'm not promising I have time to get started on this immediately).
> there are nice things in the wxRuby Roadmap, but maybe it could be
> actualised and a message could be add about that "paused" progression of
> wxRuby.. at least to let the newcomers know exactly what to expect.

That's a good idea - as per this thread, perhaps it's worth saying that 
it's not abandoned, just snoozing.

happy xmas to all
alex

From alex at pressure.to  Wed Dec 22 07:07:18 2010
From: alex at pressure.to (Alex Fenton)
Date: Wed, 22 Dec 2010 12:07:18 +0000
Subject: [wxruby-users] OS X Snow Leopard + wxRuby 2.0.1 gem - WORKING
In-Reply-To: <32957dcaa6087e7ff290cbb1e73bb5dc@ruby-forum.com>
References: <4C344B85.6000808@pressure.to>
	<32957dcaa6087e7ff290cbb1e73bb5dc@ruby-forum.com>
Message-ID: <4D11E9F6.5030805@pressure.to>

Hi Ridge

On 22/12/2010 06:28, Ridge McGhee wrote:
> I have a MacBook Pro (64-bit) running OS X 10.6.
> Like others, I wanted to run Ruby 1.9.2 (latest) and wxRuby 2.0.1
> (latest).
That sounds similar to my setup.

> I use RVM to install Ruby 1.9.2 (and manage my ruby versions).
> (See http://pragmaticstudio.com/blog/2010/9/23/install-rails-ruby-mac)
>
> By default, RVM builds the Ruby 64-bit version (only).
> I finally found a post that indicates how to build both 32-bit and
> 64-bit versions of Ruby.

I hadn't come across RVM - this looks great.

> Ok, so this particular working set produced a window.
> So, we (or I anyway) have a way to proceed.
>
> Alex - I hope this somehow helps you find out what the problem
> (32-bit vs 64-bit) might be.  Any thoughts?

I'm just headed off for xmas so won't have a go at this til new year - 
but it sounds very promising as a way to restart development on the 
stable branch with 10.6. What I'll need to test is that I can use this 
ruby to compile against wxWidgets 2.8 - which is what has been the 
headache so far.

best wishes
alex

From dwilde1 at gmail.com  Wed Dec 22 19:29:19 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Wed, 22 Dec 2010 16:29:19 -0800
Subject: [wxruby-users] linking gem to wx on Linux
Message-ID: <AANLkTikWsyTKxobrVRt0k2sesX-P22dDUAHDjn3u4pT4@mail.gmail.com>

Hi, Alex and Chauk-Mean -

I see that holidays are happening, so I may have to bull my way through
this, but here goes.

On some systems, we get

/usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so:
/usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so: symbol
_ZN13wxAuiNotebook14ShowWindowMenuEv, version WXU_2.8.5 not defined in file
libwx_gtk2u_aui-2.8.so.0 with link time reference -
/usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wxruby2.so
(LoadError)
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
        from /usr/lib/ruby/gems/1.8/gems/wxruby-2.0.1-x86-linux/lib/wx.rb:12
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in
`gem_original_require'
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in
`require'
        from smarttvmark.rb:11

... after installing wxruby from the gem and the libwxbase libraries from
apt-get. I know I solved this on my system after going back and forth
between gem and source distros, and the procedure works fine on some
systems, but I'd like to know what works and what I can do that'll work on
all (Linux) systems.
-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101222/8b1e3261/attachment.html>

From dwilde1 at gmail.com  Thu Dec 23 11:59:24 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Thu, 23 Dec 2010 08:59:24 -0800
Subject: [wxruby-users] linking gem to wx on Linux
Message-ID: <AANLkTi=ENFjTS6e19nOJ0i+DcEydCYi5=mTFppMJZzR8@mail.gmail.com>

By compiling wxWidgets from source, enabling the shared library option and
using 2.8.11 wxGTK as follows:

../configure --enable-shared --with-gtk --enable-monolithic \
 --enable-unicode --disable-debug --enable-catch_segvs --enable-graphics_ctx
\
 --enable-mediactrl --with-opengl --with-libjpeg=builtin
--with-libpng=builtin \
 --with-libtiff=builtin --with-zlib=builtin --with-expat=builtin
--enable-gui \
 --enable-xrc --enable-mdi --enable-gif \
 --enable-pcx --enable-iff --enable-pnm --enable-xpm

I now get this error on my own machine (Ubuntu 9,10) which was working:

/usr/local/lib/ruby/site_ruby/1.8/i686-linux/wxruby2.so:
/usr/local/lib/ruby/site_ruby/1.8/i686-linux/wxruby2.so: undefined symbol:
_ZN8wxWindow12ApplyToolTipEP12_GtkTooltipsPKc -
/usr/local/lib/ruby/site_ruby/1.8/i686-linux/wxruby2.so (LoadError)
    from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
    from /usr/local/lib/ruby/site_ruby/1.8/wx.rb:12
    from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
    from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
    from ./smarttvmark.rb:11

I know I had it working, so I'll keep pushing forward. :D
-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101223/a2631199/attachment.html>

From dwilde1 at gmail.com  Thu Dec 23 16:05:32 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Thu, 23 Dec 2010 13:05:32 -0800
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
Message-ID: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>

On Thu, Dec 23, 2010 at 8:59 AM, Don Wilde <dwilde1 at gmail.com> wrote:

> By compiling wxWidgets from source, enabling the shared library option and
> using 2.8.11 wxGTK as follows:
>

I was able to get my system going again by forcing Synaptic to re-install
the libwxgtk2.8 packages in the Debian tree. This wipes out the source
install, so there must be some ubuntuism that isn't handled properly.

HOWEVER... now my system hangs on close() Any ideas?

-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101223/800dde1a/attachment-0001.html>

From lists at ruby-forum.com  Sun Dec 26 13:42:06 2010
From: lists at ruby-forum.com (Ken Spyce)
Date: Sun, 26 Dec 2010 19:42:06 +0100
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
Message-ID: <2ddbe14a28841ea467936e8217cb6415@ruby-forum.com>

I was wondering if we're going to have the PropertyGrid class anytime 
soon...

-- 
Posted via http://www.ruby-forum.com/.

From chauk.mean at gmail.com  Tue Dec 28 20:03:16 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Wed, 29 Dec 2010 02:03:16 +0100
Subject: [wxruby-users] Building wxRuby for Ubuntu (update)
Message-ID: <AANLkTi=O-2i6rf_xJSQEEiE7pQZq0=5CFjrvEZoinbLP@mail.gmail.com>

Hi all,

There have been several messages regarding the build of wxRuby on Ubuntu.

I've written previously the detailed steps for building wxRuby on top
of linux distribution's wxWidgets packages.
(http://rubyforge.org/pipermail/wxruby-users/2009-November/005089.html
or the direct link
http://wxruby.rubyforge.org/wiki/wiki.pl?BuildingOnTopOfLinuxDistroPackages.).

I've updated these detailed steps to cover :
- the custom build of wxWidgets.
- the build of upcoming wxRuby release
(http://wxruby.rubyforge.org/wiki/wiki.pl?BuildingForUbuntu).
This page is more clearly linked from the installation page
(http://wxruby.rubyforge.org/wiki/wiki.pl?Installation).

Cheers,
Chauk-Mean.

From chauk.mean at gmail.com  Tue Dec 28 20:08:26 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Wed, 29 Dec 2010 02:08:26 +0100
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
In-Reply-To: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
References: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
Message-ID: <AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>

Hi Don,

2010/12/23 Don Wilde <dwilde1 at gmail.com>:
> On Thu, Dec 23, 2010 at 8:59 AM, Don Wilde <dwilde1 at gmail.com> wrote:
>>
>> By compiling wxWidgets from source, enabling the shared library option and
>> using 2.8.11 wxGTK as follows:
>
> I was able to get my system going again by forcing Synaptic to re-install
> the libwxgtk2.8 packages in the Debian tree. This wipes out the source
> install, so there must be some ubuntuism that isn't handled properly.
>
> HOWEVER... now my system hangs on close() Any ideas?
>
> -- Don Wilde

Could you try the detailed steps in the following message/link ?
(http://rubyforge.org/pipermail/wxruby-users/2010-December/005773.html)

Cheers,
Chauk-Mean

From alex at pressure.to  Tue Dec 28 20:12:53 2010
From: alex at pressure.to (Alex Fenton)
Date: Wed, 29 Dec 2010 01:12:53 +0000
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <2ddbe14a28841ea467936e8217cb6415@ruby-forum.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
	<2ddbe14a28841ea467936e8217cb6415@ruby-forum.com>
Message-ID: <4D1A8B15.8020209@pressure.to>

Hi Ken

On 26/12/2010 18:42, Ken Spyce wrote:
> I was wondering if we're going to have the PropertyGrid class anytime
> soon...
>

I did have a go at porting this class a while ago but I ran into 
difficulties - can't quite remember what the problem is but I couldn't 
work round it. It might be worth another go with the newest version of 
SWIG if there's interest in the class.

alex



From dwilde1 at gmail.com  Tue Dec 28 20:16:04 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Tue, 28 Dec 2010 17:16:04 -0800
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
In-Reply-To: <AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>
References: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
	<AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>
Message-ID: <AANLkTikZ8vWDWsYzv+WcsP84ztoWocG8ZxC083u-aonA@mail.gmail.com>

Will do, Chauk-Mean, tomorrow morning. Thanks!

I do not use 1.9 yet, so I'll be working with parallel steps on 1.8.

On Tue, Dec 28, 2010 at 5:08 PM, Chauk-Mean Proum <chauk.mean at gmail.com>wrote:

> Hi Don,
>
> 2010/12/23 Don Wilde <dwilde1 at gmail.com>:
> > On Thu, Dec 23, 2010 at 8:59 AM, Don Wilde <dwilde1 at gmail.com> wrote:
> >>
> >> By compiling wxWidgets from source, enabling the shared library option
> and
> >> using 2.8.11 wxGTK as follows:
> >
> > I was able to get my system going again by forcing Synaptic to re-install
> > the libwxgtk2.8 packages in the Debian tree. This wipes out the source
> > install, so there must be some ubuntuism that isn't handled properly.
> >
> > HOWEVER... now my system hangs on close() Any ideas?
> >
> > -- Don Wilde
>
> Could you try the detailed steps in the following message/link ?
> (http://rubyforge.org/pipermail/wxruby-users/2010-December/005773.html)
>
> Cheers,
> Chauk-Mean
>



-- 
-- Don Wilde
ph: 512-394-8896 skype: donwilde1
e: dwilde1 at gmail.com
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101228/e23d0d01/attachment.html>

From chauk.mean at gmail.com  Tue Dec 28 20:26:48 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Wed, 29 Dec 2010 02:26:48 +0100
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <4D1A8B15.8020209@pressure.to>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>
	<2ddbe14a28841ea467936e8217cb6415@ruby-forum.com>
	<4D1A8B15.8020209@pressure.to>
Message-ID: <AANLkTi=-dd9=3rtU4L-AT46RYHjzRN7t8ix7FnV8+b0p@mail.gmail.com>

Hi Alex,

2010/12/29 Alex Fenton <alex at pressure.to>:
> It might be worth another go with the newest version of SWIG if
> there's interest in the class.

Have you tried wxRuby with SWIG-2.0.0/2.0.1 on OS X ?

Cheers,
Chauk-Mean.

From alex at pressure.to  Wed Dec 29 04:57:33 2010
From: alex at pressure.to (Alex Fenton)
Date: Wed, 29 Dec 2010 09:57:33 +0000
Subject: [wxruby-users] wxruby is dead?
In-Reply-To: <AANLkTi=-dd9=3rtU4L-AT46RYHjzRN7t8ix7FnV8+b0p@mail.gmail.com>
References: <93bd3b430de4f0be66b323fd601da903@ruby-forum.com>	<2ddbe14a28841ea467936e8217cb6415@ruby-forum.com>	<4D1A8B15.8020209@pressure.to>
	<AANLkTi=-dd9=3rtU4L-AT46RYHjzRN7t8ix7FnV8+b0p@mail.gmail.com>
Message-ID: <4D1B060D.3070609@pressure.to>

Hi Chauk-Mean

On 29/12/2010 01:26, Chauk-Mean Proum wrote:
> Have you tried wxRuby with SWIG-2.0.0/2.0.1 on OS X ?

No, not yet. After upgrading to OS X 10.6 I found it hard to get a ruby 
+ wxWidgets build that would work together for wxruby. Having seen your 
new instructions for Ubuntu I'm going to have a sweep through the bug 
list in the new year - catch up with you on -dev soon.

alex

From dwilde1 at gmail.com  Wed Dec 29 13:30:45 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Wed, 29 Dec 2010 10:30:45 -0800
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
In-Reply-To: <AANLkTikZ8vWDWsYzv+WcsP84ztoWocG8ZxC083u-aonA@mail.gmail.com>
References: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
	<AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>
	<AANLkTikZ8vWDWsYzv+WcsP84ztoWocG8ZxC083u-aonA@mail.gmail.com>
Message-ID: <AANLkTimCqrPQvXWs-ZYRifoK3fidqkUeqb7qADBTFRrn@mail.gmail.com>

Hi, Chauk-Mean -

I installed everything from source, adding the switches you specified, and
it still hangs on close. I found the wxWidgets-2.8.11 tarball, used SWIG
1.3.40, and wxruby-2.0.1. I'm using patchlevel 302 of Ruby 1.8.7. I don't
have git or svn access from within Intel's firewalls.

I recompiled everything in the sequence you suggested, and everything else
functions very well. It just locks up on close(). I've verified that
everything else is executed up to close().

I am extremely reluctant to move to Ruby 1.9 because that will break other
things. I do use a number of other Ruby extensions.

On Tue, Dec 28, 2010 at 5:16 PM, Don Wilde <dwilde1 at gmail.com> wrote:

> Will do, Chauk-Mean, tomorrow morning. Thanks!
>
> I do not use 1.9 yet, so I'll be working with parallel steps on 1.8.
>
>
> On Tue, Dec 28, 2010 at 5:08 PM, Chauk-Mean Proum <chauk.mean at gmail.com>wrote:
>
>> Hi Don,
>>
>> 2010/12/23 Don Wilde <dwilde1 at gmail.com>:
>> > On Thu, Dec 23, 2010 at 8:59 AM, Don Wilde <dwilde1 at gmail.com> wrote:
>> >>
>> >> By compiling wxWidgets from source, enabling the shared library option
>> and
>> >> using 2.8.11 wxGTK as follows:
>> >
>> > I was able to get my system going again by forcing Synaptic to
>> re-install
>> > the libwxgtk2.8 packages in the Debian tree. This wipes out the source
>> > install, so there must be some ubuntuism that isn't handled properly.
>> >
>> > HOWEVER... now my system hangs on close() Any ideas?
>> >
>> > -- Don Wilde
>>
>> Could you try the detailed steps in the following message/link ?
>> (http://rubyforge.org/pipermail/wxruby-users/2010-December/005773.html)
>>
>> Cheers,
>> Chauk-Mean
>>
>
>
>
> --
> -- Don Wilde
> ph: 512-394-8896 skype: donwilde1
> e: dwilde1 at gmail.com
> "If you are creative and add value to the world, sleep well. You've earned
> it."
>
>


-- 
-- Don Wilde
ph: 512-394-8896 skype: donwilde1
e: dwilde1 at gmail.com
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101229/d52fbf78/attachment-0001.html>

From dwilde1 at gmail.com  Wed Dec 29 14:06:42 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Wed, 29 Dec 2010 11:06:42 -0800
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
In-Reply-To: <AANLkTimCqrPQvXWs-ZYRifoK3fidqkUeqb7qADBTFRrn@mail.gmail.com>
References: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
	<AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>
	<AANLkTikZ8vWDWsYzv+WcsP84ztoWocG8ZxC083u-aonA@mail.gmail.com>
	<AANLkTimCqrPQvXWs-ZYRifoK3fidqkUeqb7qADBTFRrn@mail.gmail.com>
Message-ID: <AANLkTinLDGyFL3kG__Hue-5S6Ow9GOETR_gvtycB0PTT@mail.gmail.com>

Hi, Chauk-Mean -

Well, that was interesting. I had

                 evt_close { exit }

in my code and I commented it out.

The next time I ran it I got the following backtrace:

*** glibc detected *** ruby: free(): invalid pointer: 0x002f93d0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0x2220d1]
/lib/tls/i686/cmov/libc.so.6[0x2237d2]
/lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x2268ad]
/usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb936f1]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_ZN19wxGnomePrintLibraryD1Ev+0x40)[0x6245270]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_ZN18wxGnomePrintModule6OnExitEv+0x29)[0x62452c9]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_ZN8wxModule16DoCleanUpModulesERK12wxModuleList+0x2b)[0x61497fb]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_Z14wxEntryCleanupv+0x80)[0x6135df0]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_Z14wxUninitializev+0x40)[0x6135e90]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_Z7wxEntryRiPPw+0xa4)[0x6136204]
/usr/local/lib/ruby/site_ruby/1.8/i686-linux/wxruby2.so[0x11b7108]
/usr/local/lib/libruby.so.1.8[0x3e57cd]
/usr/local/lib/libruby.so.1.8[0x3ef7fa]
/usr/local/lib/libruby.so.1.8[0x3ef989]
/usr/local/lib/libruby.so.1.8[0x3ecf72]
/usr/local/lib/libruby.so.1.8[0x3ef6c1]
/usr/local/lib/libruby.so.1.8[0x3ef989]
/usr/local/lib/libruby.so.1.8[0x3ecf72]
/usr/local/lib/libruby.so.1.8[0x3ed7ed]
/usr/local/lib/libruby.so.1.8[0x3fa81d]
/usr/local/lib/libruby.so.1.8(ruby_exec+0x16)[0x3fa856]
/usr/local/lib/libruby.so.1.8(ruby_run+0x25)[0x3fa885]
ruby[0x8048711]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x1cdb56]
ruby[0x8048641]
======= Memory map: ========
00110000-00117000 r-xp 00000000 08:06 3014919    /lib/tls/i686/cmov/
librt-2.10.1.so
00117000-00118000 r--p 00006000 08:06 3014919    /lib/tls/i686/cmov/
librt-2.10.1.so
00118000-00119000 rw-p 00007000 08:06 3014919    /lib/tls/i686/cmov/
librt-2.10.1.so
00119000-00120000 r-xp 00000000 08:06 3226
/usr/lib/libpangoxft-1.0.so.0.2600.0
00120000-00121000 r--p 00006000 08:06 3226
/usr/lib/libpangoxft-1.0.so.0.2600.0
00121000-00122000 rw-p 00007000 08:06 3226
/usr/lib/libpangoxft-1.0.so.0.2600.0
00122000-0015e000 r-xp 00000000 08:06 3778
/usr/lib/libgobject-2.0.so.0.2200.3
0015e000-0015f000 r--p 0003b000 08:06 3778
/usr/lib/libgobject-2.0.so.0.2200.3
0015f000-00160000 rw-p 0003c000 08:06 3778
/usr/lib/libgobject-2.0.so.0.2200.3
00160000-00163000 r-xp 00000000 08:06 3779
/usr/lib/libgmodule-2.0.so.0.2200.3
00163000-00164000 r--p 00002000 08:06 3779
/usr/lib/libgmodule-2.0.so.0.2200.3
00164000-00165000 rw-p 00003000 08:06 3779
/usr/lib/libgmodule-2.0.so.0.2200.3
00165000-00181000 r-xp 00000000 08:06 637        /lib/libgcc_s.so.1
00181000-00182000 r--p 0001b000 08:06 637        /lib/libgcc_s.so.1
00182000-00183000 rw-p 0001c000 08:06 637        /lib/libgcc_s.so.1
00183000-00185000 r-xp 00000000 08:06 2472
/usr/lib/libXinerama.so.1.0.0
00185000-00186000 rw-p 00001000 08:06 2472
/usr/lib/libXinerama.so.1.0.0
00186000-0018d000 r-xp 00000000 08:06 2441       /usr/lib/libSM.so.6.0.0
0018d000-0018e000 r--p 00006000 08:06 2441       /usr/lib/libSM.so.6.0.0
0018e000-0018f000 rw-p 00007000 08:06 2441       /usr/lib/libSM.so.6.0.0
00191000-001b5000 r-xp 00000000 08:06 3014749    /lib/tls/i686/cmov/
libm-2.10.1.so
001b5000-001b6000 r--p 00023000 08:06 3014749    /lib/tls/i686/cmov/
libm-2.10.1.so
001b6000-001b7000 rw-p 00024000 08:06 3014749    /lib/tls/i686/cmov/
libm-2.10.1.so
001b7000-002f5000 r-xp 00000000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
002f5000-002f6000 ---p 0013e000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
002f6000-002f8000 r--p 0013e000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
002f8000-002f9000 rw-p 00140000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
002f9000-002fc000 rw-p 00000000 00:00 0
002fc000-00323000 r-xp 00000000 08:06 3220
/usr/lib/libpangoft2-1.0.so.0.2600.0
00323000-00324000 r--p 00027000 08:06 3220
/usr/lib/libpangoft2-1.0.so.0.2600.0
00324000-00325000 rw-p 00028000 08:06 3220
/usr/lib/libpangoft2-1.0.so.0.2600.0
00325000-00350000 r-xp 00000000 08:06 2747
/usr/lib/libfontconfig.so.1.3.0
00350000-00351000 r--p 0002a000 08:06 2747
/usr/lib/libfontconfig.so.1.3.0
00351000-00352000 rw-p 0002b000 08:06 2747
/usr/lib/libfontconfig.so.1.3.0
00352000-00375000 r-xp 00000000 08:06 8279       /usr/lib/libpng12.so.0.37.0
00375000-00376000 r--p 00022000 08:06 8279       /usr/lib/libpng12.so.0.37.0
00376000-00377000 rw-p 00023000 08:06 8279       /usr/lib/libpng12.so.0.37.0
00377000-0038b000 r-xp 00000000 08:06 673        /lib/libz.so.1.2.3.3
0038b000-0038c000 r--p 00013000 08:06 673        /lib/libz.so.1.2.3.3
0038c000-0038d000 rw-p 00014000 08:06 673        /lib/libz.so.1.2.3.3
0038d000-00479000 r-xp 00000000 08:06 21499
/usr/local/lib/libruby.so.1.8.7
00479000-0047a000 r--p 000eb000 08:06 21499
/usr/local/lib/libruby.so.1.8.7
0047a000-0047b000 rw-p 000ec000 08:06 21499
/usr/local/lib/libruby.so.1.8.7
0047b000-0048b000 rw-p 00000000 00:00 0
0048b000-004ad000 r-xp 00000000 08:06 3080       /usr/lib/libjpeg.so.62.0.0
004ad000-004ae000 r--p 00021000 08:06 3080       /usr/lib/libjpeg.so.62.0.0
004ae000-004af000 rw-p 00022000 08:06 3080       /usr/lib/libjpeg.so.62.0.0
004af000-004bd000 r-xp 00000000 08:06 6760
/usr/lib/libgstinterfaces-0.10.so.0.18.0
004bd000-004be000 r--p 0000d000 08:06 6760
/usr/lib/libgstinterfaces-0.10.so.0.18.0
004be000-004bf000 rw-p 0000e000 08:06 6760
/usr/lib/libgstinterfaces-0.10.so.0.18.0
004bf000-004c1000 r-xp 00000000 08:06 2454
/usr/lib/libXcomposite.so.1.0.0
004c1000-004c2000 r--p 00001000 08:06 2454
/usr/lib/libXcomposite.so.1.0.0
004c2000-004c3000 rw-p 00002000 08:06 2454
/usr/lib/libXcomposite.so.1.0.0
004c5000-004e0000 r-xp 00000000 08:06 3540       /lib/ld-2.10.1.so
004e0000-004e1000 r--p 0001a000 08:06 3540       /lib/ld-2.10.1.so
004e1000-004e2000 rw-p 0001b000 08:06 3540       /lib/ld-2.10.1.so
004e2000-00533000 r-xp 00000000 08:06 9116       /usr/lib/libtiff.so.4.2.1
00533000-00534000 ---p 00051000 08:06 9116       /usr/lib/libtiff.so.4.2.1
00534000-00536000 r--p 00051000 08:06 9116       /usr/lib/libtiff.so.4.2.1
00536000-00537000 rw-p 00053000 08:06 9116       /usr/lib/libtiff.so.4.2.1
0053a000-00552000 r-xp 00000000 08:06 17138
/usr/lib/libgdk_pixbuf-2.0.so.0.1800.3
00552000-00553000 r--p 00017000 08:06 17138
/usr/lib/libgdk_pixbuf-2.0.so.0.1800.3
00553000-00554000 rw-p 00018000 08:06 17138
/usr/lib/libgdk_pixbuf-2.0.so.0.1800.3
00554000-0055f000 r-xp 00000000 08:06 3218
/usr/lib/libpangocairo-1.0.so.0.2600.0
0055f000-00560000 r--p 0000a000 08:06 3218
/usr/lib/libpangocairo-1.0.so.0.2600.0
00560000-00561000 rw-p 0000b000 08:06 3218
/usr/lib/libpangocairo-1.0.so.0.2600.0
00561000-00565000 r-xp 00000000 08:06 2464       /usr/lib/libXfixes.so.3.1.0
00565000-00566000 r--p 00003000 08:06 2464       /usr/lib/libXfixes.so.3.1.0
00566000-00567000 rw-p 00004000 08:06 2464       /usr/lib/libXfixes.so.3.1.0
00567000-0056a000 r-xp 00000000 08:06 666        /lib/libuuid.so.1.3.0
0056a000-0056b000 r--p 00002000 08:06 666        /lib/libuuid.so.1.3.0
0056b000-0056c000 rw-p 00003000 08:06 666        /lib/libuuid.so.1.3.0
0056d000-0056e000 r-xp 00000000 00:00 0          [vdso]
0056e000-00676000 r-xp 00000000 08:06 15275
/usr/local/lib/libwx_gtk2u_stc-2.8.so.0.7.0
00676000-00679000 r--p 00107000 08:06 15275
/usr/local/lib/libwx_gtk2u_stc-2.8.so.0.7.0
00679000-0067a000 rw-p 0010a000 08:06 15275
/usr/local/lib/libwx_gtk2u_stc-2.8.so.0.7.0
0067a000-0067b000 rw-p 00000000 00:00 0
0067b000-006aa000 r-xp 00000000 08:06 2772
/usr/lib/libgconf-2.so.4.1.5

-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101229/84e0dfe0/attachment.html>

From chauk.mean at gmail.com  Thu Dec 30 14:22:41 2010
From: chauk.mean at gmail.com (Chauk-Mean Proum)
Date: Thu, 30 Dec 2010 20:22:41 +0100
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
In-Reply-To: <AANLkTimCqrPQvXWs-ZYRifoK3fidqkUeqb7qADBTFRrn@mail.gmail.com>
References: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
	<AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>
	<AANLkTikZ8vWDWsYzv+WcsP84ztoWocG8ZxC083u-aonA@mail.gmail.com>
	<AANLkTimCqrPQvXWs-ZYRifoK3fidqkUeqb7qADBTFRrn@mail.gmail.com>
Message-ID: <AANLkTik2aAaUoHvXZ_csBJrZQxafSNig-CE4oUd1q4Ui@mail.gmail.com>

Hi Don,

2010/12/29 Don Wilde <dwilde1 at gmail.com>:
> Hi, Chauk-Mean -
>
> I installed everything from source, adding the switches you specified, and
> it still hangs on close. I found the wxWidgets-2.8.11 tarball, used SWIG
> 1.3.40, and wxruby-2.0.1. I'm using patchlevel 302 of Ruby 1.8.7. I don't
> have git or svn access from within Intel's firewalls.
>
> I recompiled everything in the sequence you suggested, and everything else
> functions very well. It just locks up on close(). I've verified that
> everything else is executed up to close().

Do the samples from wxRuby work ?
Could you post an example script (just a minimal script) where your
'close' issue occurs ?

> I am extremely reluctant to move to Ruby 1.9 because that will break other
> things. I do use a number of other Ruby extensions.

Ruby-1.8.7 should work but I'll try with the example script you will provide.

Cheers,
Chauk-Mean

From dwilde1 at gmail.com  Thu Dec 30 15:26:30 2010
From: dwilde1 at gmail.com (Don Wilde)
Date: Thu, 30 Dec 2010 12:26:30 -0800
Subject: [wxruby-users] linking gem to wx on Linux NEW BUG
In-Reply-To: <AANLkTik2aAaUoHvXZ_csBJrZQxafSNig-CE4oUd1q4Ui@mail.gmail.com>
References: <AANLkTimeK24YzOFu6MA-4VR98Tzo-GWekKkBxD3NHL8W@mail.gmail.com>
	<AANLkTikrtoLuXUMHZ-CV-+eDfGyA-1B6uvvpteVrjbO0@mail.gmail.com>
	<AANLkTikZ8vWDWsYzv+WcsP84ztoWocG8ZxC083u-aonA@mail.gmail.com>
	<AANLkTimCqrPQvXWs-ZYRifoK3fidqkUeqb7qADBTFRrn@mail.gmail.com>
	<AANLkTik2aAaUoHvXZ_csBJrZQxafSNig-CE4oUd1q4Ui@mail.gmail.com>
Message-ID: <AANLkTimVfsK9fq+8THfvgKU88cp=uQA+RTS7BAidPE3s@mail.gmail.com>

On Thu, Dec 30, 2010 at 11:22 AM, Chauk-Mean Proum <chauk.mean at gmail.com>wrote:

> Hi Don,
>
> Hi, Chauk-Mean -


> 2010/12/29 Don Wilde <dwilde1 at gmail.com>:
> > Hi, Chauk-Mean -
> >
> > I installed everything from source, adding the switches you specified,
> and
> > it still hangs on close. I found the wxWidgets-2.8.11 tarball, used SWIG
> > 1.3.40, and wxruby-2.0.1. I'm using patchlevel 302 of Ruby 1.8.7. I don't
> > have git or svn access from within Intel's firewalls.
> >
> > I recompiled everything in the sequence you suggested, and everything
> else
> > functions very well. It just locks up on close(). I've verified that
> > everything else is executed up to close().
>
> Do the samples from wxRuby work ?
>

When I run the examples that have no menu item, I get the segfault I posted
in my last email when I press X. When I run one which does have a menu
item,  I get the big long error dump, as below. It seems that it is my
system that is bollixed, but it would be nice to identify the dependency
that we aren't catching because the way I have my machine set up here is
fairly common. It is Ubuntu 9.10 with the Pre-Released Updates enabled.

I haven't done any crazy stuff on the machine, other than what I've done
with wxRuby and its dependencies. If you don't have time to pursue this
further let me know, and I'll wipe the machine and reload. I have
successfully installed and run wxruby-2.0.1 on several other boxes, but I
think this is the only one with Pre-Release Updates enabled. If I do that,
I'll see if it runs on a normal 9.10 setup then enable the updates and see
if it crashes again.

*So, okay. Let me know if you want more info off my system or if you'd
rather I get the data from restarting on a clean box?*

# ./controls.rb
*** glibc detected *** ruby: free(): invalid pointer: 0x0027a3d0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0x1a30d1]
/lib/tls/i686/cmov/libc.so.6[0x1a47d2]
/lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x1a78ad]
/usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0x9196f1]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_ZN19wxGnomePrintLibraryD1Ev+0x40)[0x8867270]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_ZN18wxGnomePrintModule6OnExitEv+0x29)[0x88672c9]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_ZN8wxModule16DoCleanUpModulesERK12wxModuleList+0x2b)[0x876b7fb]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_Z14wxEntryCleanupv+0x80)[0x8757df0]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_Z14wxUninitializev+0x40)[0x8757e90]
/usr/local/lib/libwx_gtk2u-2.8.so.0(_Z7wxEntryRiPPw+0xa4)[0x8758204]
/usr/local/lib/ruby/site_ruby/1.8/i686-linux/wxruby2.so[0x12fc108]
/usr/local/lib/libruby.so.1.8[0x2acc78]
/usr/local/lib/libruby.so.1.8[0x2b7b3e]
/usr/local/lib/libruby.so.1.8[0x2b7cda]
/usr/local/lib/libruby.so.1.8[0x2b4fbb]
/usr/local/lib/libruby.so.1.8[0x2c3eb6]
/usr/local/lib/libruby.so.1.8(ruby_exec+0x22)[0x2c3f02]
/usr/local/lib/libruby.so.1.8(ruby_run+0x35)[0x2c3f45]
ruby[0x804871d]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x14eb56]
ruby[0x8048641]
======= Memory map: ========
00110000-00112000 r-xp 00000000 08:06 21701
/usr/local/lib/ruby/1.8/i686-linux/etc.so
00112000-00113000 r--p 00001000 08:06 21701
/usr/local/lib/ruby/1.8/i686-linux/etc.so
00113000-00114000 rw-p 00002000 08:06 21701
/usr/local/lib/ruby/1.8/i686-linux/etc.so
00114000-0011f000 r-xp 00000000 08:06 14891
/usr/local/lib/libwx_gtk2u_gl-2.8.so.0.7.0
0011f000-00120000 ---p 0000b000 08:06 14891
/usr/local/lib/libwx_gtk2u_gl-2.8.so.0.7.0
00120000-00121000 r--p 0000b000 08:06 14891
/usr/local/lib/libwx_gtk2u_gl-2.8.so.0.7.0
00121000-00122000 rw-p 0000c000 08:06 14891
/usr/local/lib/libwx_gtk2u_gl-2.8.so.0.7.0
00122000-00132000 r-xp 00000000 08:06 24569
/usr/local/lib/libwx_gtk2u_media-2.8.so.0.7.0
00132000-00133000 r--p 0000f000 08:06 24569
/usr/local/lib/libwx_gtk2u_media-2.8.so.0.7.0
00133000-00134000 rw-p 00010000 08:06 24569
/usr/local/lib/libwx_gtk2u_media-2.8.so.0.7.0
00134000-00136000 r-xp 00000000 08:06 2472
/usr/lib/libXinerama.so.1.0.0
00136000-00137000 rw-p 00001000 08:06 2472
/usr/lib/libXinerama.so.1.0.0
00137000-00138000 r-xp 00000000 00:00 0          [vdso]
00138000-00276000 r-xp 00000000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
00276000-00277000 ---p 0013e000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
00277000-00279000 r--p 0013e000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
00279000-0027a000 rw-p 00140000 08:06 3014915    /lib/tls/i686/cmov/
libc-2.10.1.so
0027a000-0027d000 rw-p 00000000 00:00 0
0027d000-0027f000 r-xp 00000000 08:06 2458
/usr/lib/libXdamage.so.1.1.0
0027f000-00280000 rw-p 00001000 08:06 2458
/usr/lib/libXdamage.so.1.1.0
00280000-0034d000 r-xp 00000000 08:06 21492
/usr/local/lib/libruby.so.1.8.7
0034d000-0034e000 r--p 000cd000 08:06 21492
/usr/local/lib/libruby.so.1.8.7
0034e000-00350000 rw-p 000ce000 08:06 21492
/usr/local/lib/libruby.so.1.8.7
00350000-00360000 rw-p 00000000 00:00 0
00360000-00468000 r-xp 00000000 08:06 15275
/usr/local/lib/libwx_gtk2u_stc-2.8.so.0.7.0
00468000-0046b000 r--p 00107000 08:06 15275
/usr/local/lib/libwx_gtk2u_stc-2.8.so.0.7.0
0046b000-0046c000 rw-p 0010a000 08:06 15275
/usr/local/lib/libwx_gtk2u_stc-2.8.so.0.7.0
0046c000-0046d000 rw-p 00000000 00:00 0
0046d000-004b3000 r-xp 00000000 08:06 3216
/usr/lib/libpango-1.0.so.0.2600.0
004b3000-004b4000 r--p 00045000 08:06 3216
/usr/lib/libpango-1.0.so.0.2600.0
004b4000-004b5000 rw-p 00046000 08:06 3216
/usr/lib/libpango-1.0.so.0.2600.0
004b5000-004b9000 r-xp 00000000 08:06 3783
/usr/lib/libgthread-2.0.so.0.2200.3
004b9000-004ba000 r--p 00003000 08:06 3783
/usr/lib/libgthread-2.0.so.0.2200.3
004ba000-004bb000 rw-p 00004000 08:06 3783
/usr/lib/libgthread-2.0.so.0.2200.3
004bb000-004d7000 r-xp 00000000 08:06 637        /lib/libgcc_s.so.1
004d7000-004d8000 r--p 0001b000 08:06 637        /lib/libgcc_s.so.1
004d8000-004d9000 rw-p 0001c000 08:06 637        /lib/libgcc_s.so.1
004d9000-00500000 r-xp 00000000 08:06 3220
/usr/lib/libpangoft2-1.0.so.0.2600.0
00500000-00501000 r--p 00027000 08:06 3220
/usr/lib/libpangoft2-1.0.so.0.2600.0
00501000-00502000 rw-p 00028000 08:06 3220
/usr/lib/libpangoft2-1.0.so.0.2600.0
00502000-00509000 r-xp 00000000 08:06 2441       /usr/lib/libSM.so.6.0.0
00509000-0050a000 r--p 00006000 08:06 2441       /usr/lib/libSM.so.6.0.0
0050a000-0050b000 rw-p 00007000 08:06 2441       /usr/lib/libSM.so.6.0.0
0050b000-0050d000 r-xp 00000000 08:06 2454
/usr/lib/libXcomposite.so.1.0.0
0050d000-0050e000 r--p 00001000 08:06 2454
/usr/lib/libXcomposite.so.1.0.0
0050e000-0050f000 rw-p 00002000 08:06 2454
/usr/lib/libXcomposite.so.1.0.0
0050f000-00510000 r-xp 00000000 08:06 1704610
/usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
00510000-00511000 r--p 00001000 08:06 1704610
/usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
00511000-00512000 rw-p 00002000 08:06 1704610
/usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
00512000-0052d000 r-xp 00000000 08:06 3540       /lib/ld-2.10.1.so
0052d000-0052e000 r--p 0001a000 08:06 3540       /lib/ld-2.10.1.so
0052e000-0052f000 rw-p 0001b000 08:06 3540       /lib/ld-2.10.1.so
0052f000-00552000 r-xp 00000000 08:06 8279       /usr/lib/libpng12.so.0.37.0
00552000-00553000 r--p 00022000 08:06 8279       /usr/lib/libpng12.so.0.37.0
00553000-00554000 rw-p 00023000 08:06 8279       /usr/lib/libpng12.so.0.37.0
00554000-00568000 r-xp 00000000 08:06 673        /lib/libz.so.1.2.3.3
00568000-00569000 r--p 00013000 08:06 673        /lib/libz.so.1.2.3.3
00569000-0056a000 rw-p 00014000 08:06 673        /lib/libz.so.1.2.3.3
0056a000-0056e000 r-xp 00000000 08:06 2464       /usr/lib/libXfixes.so.3.1.0
0056e000-0056f000 r--p 00003000 08:06 2464       /usr/lib/libXfixes.so.3.1.0
0056f000-00570000 rw-p 00004000 08:06 2464       /usr/lib/libXfixes.so.3.1.0
00573000-0058e000 r-xp 00000000 08:06 2533
/usr/lib/libatk-1.0.so.0.2809.1
0058e000-0058f000 r--p 0001b000 08:06 2533
/usr/lib/libatk-1.0.so.0.2809.1
0058f000-00590000 rw-p 0001c000 08:06 2533
/usr/lib/libatk-1.0.so.0.2809.1
00590000-00645000 r-xp 00000000 08:06 3776
/lib/libglib-2.0.so.0.2200.3
00645000-00646000 r--p 000b4000 08:06 3776
/lib/libglib-2.0.so.0.2200.3
00646000-00647000 rw-p 000b5000 08:06 3776
/lib/libglib-2.0.so.0.2200.3
00647000-0064a000 r-xp 00000000 08:06 21754
/usr/local/lib/ruby/1.8/i686-linux/thread.so
0064a000-0064b000 r--p 00002000 08:06 21754
/usr/local/lib/ruby/1.8/i686-linux/thread.so
0064b000-0064c000 rw-p 00003000 08:06 21754
/usr/local/lib/ruby/1.8/i686-linux/thread.soAborted


-- 
-- Don Wilde
"If you are creative and add value to the world, sleep well. You've earned
it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/wxruby-users/attachments/20101230/97ef509d/attachment-0001.html>