Displaying 20 results from an estimated 10000 matches similar to: "New release of wxruby-swig"
2004 Jul 20
0
Progress on wxruby-swig
Greetings,
I wanted to give you all a progress report on wxruby-swig, the next
generation of wxruby.
As most of you know, we are in the process of rewriting wxruby from
scratch, using SWIG instead of the custom wxpp template tool in the
current version. Using SWIG will make it easier for more people to add
support for new classes and methods, and will make it easier to optimize
(and fix)
2004 Apr 22
0
wxruby-swig 0.0.4
REMINDER: This news is about the swig-based prototype. The main wxRuby
release is still current at 0.3.0.
I just pushed the latest wxruby-swig code to:
http://qualitycode.com/repos/wxruby-swig
Thanks to Nick for reminding me about the Window#paint method that
wxRuby 0.3 supports. I had forgotten all about it. There may be other
features that we manually added to wxRuby that I will need to
2004 Apr 10
5
wxRuby-SWIG 0.0.3 is available
REMINDER: wxruby-swig is an experimental rewrite of wxRuby, using SWIG.
It is not yet useful. The official wxRuby is still at 0.2.1.
The 0.0.3 release of wxruby-swig is able to run the "minimal.rb" sample,
which includes menu event handling. As always, it is available at:
http://qualitycode.com/repos/wxruby-swig/
I also created a tarball this time, so you can just download that and
2003 Dec 07
0
New non-cvs repository of wxruby code is available
As I have mentioned on this list before, my goal is to switch entirely
away from CVS for managing the wxRuby source code. CVS is fundamentally
broken in several ways, including:
- Each developer needs write access to contribute effectively
- Tagging and branching are weak
- Checkins are file-based instead of patchset-based
- Moving files or directories loses the history
For me, the first one
2004 Apr 04
5
SWIG update
I have a minimal working version of a SWIG-based wxRuby that can bring
up an empty Frame with a title.
On my system, it crashes on exit. I suspect this is the same problem
that I mentioned months ago when I first upgraded to wxWindows 2.4.2.
The problem mysteriously vanished at some point, but now it is back. I
fiddled with this new code for several frustrating hours, and couldn''t
2004 Jul 20
6
The great MSVC wxruby-swig bug hunt!
Hi everyone,
As Kevin has just announced, wxruby-swig has been moved into CVS as a
toplevel project. It still is not in a "releasable" form yet, but it now
builds on more systems than it doesn''t, and is moving towards stability.
Because of the complexity of the build environment, we''re using rake
(http://rake.rubyforge.org) as a build system instead of the standard
2006 Nov 21
0
[ wxruby-Bugs-6809 ] Weird SWIG error when constructing statusbar
Bugs item #6809, was opened at 2006-11-21 22:05
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=218&aid=6809&group_id=35
Category: Incorrect behavior
Group: None
Status: Open
Resolution: None
Priority: 4
Submitted By: Alex Fenton (brokentoy)
Assigned to: Kevin Smith (qualitycode)
Summary: Weird SWIG error when constructing statusbar
Initial Comment:
A
2005 Oct 09
0
[Fwd: Re: [Swig] Re: Object return problem]
Forwarded from the SWIG mailing list, so we have a copy in our archives.
Kevin
-------- Original Message --------
Subject: Re: [Swig] Re: Object return problem
Date: Sun, 09 Oct 2005 18:31:40 -0400
From: Kevin Smith <wxruby@qualitycode.com>
To: Charlie Savage <cfis@interserv.com>
CC: Swig@cs.uchicago.edu
References: <4347277E.1030700@mindspring.com>
2007 Jul 23
0
[1142] trunk/wxruby2/README: Updated README with latest version info and Kevin credit
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2004 Apr 24
1
wxruby-swig 0.0.7
I just pushed a new wxruby-swig, which includes the known MSWin rakefile
changes. It also has some significant internal improvements that will
make it easier to add classes, and it includes support for one new class
(wxEvent).
wxruby-swig is now licensed under the "MIT license". wxRuby will remain
under the wxWindows license as long as we are releasing the old code
base. When we
2004 Jun 01
2
New wxRuby code is in CVS
I just checked in some good fixes. You can see the (full) Changelog
here: http://qualitycode.com/repos/wxruby/ChangeLog
Notable items:
- Added shanko''s grid sample (thanks!)
- Added support for ComboBox#get_value
- Fixed *all* the known crashing bugs.
The way I "fixed" the problems with get_client_data was to remove the
set_client_data and get_client_data implementations. I
2004 Aug 08
7
wxruby-swig progress report
Hey everybody,
I''ve made some progress on wxruby-swig, and have some good news and some bad
news.
The good news is that the MSVC version finally can run all of the samples provided in
CVS. I''m using the same solve-by-ignore solution to the GC problem that wxruby uses,
so there is far less crashing goin'' on. Depending on the next few weeks, we might be
able to
2004 Jun 10
2
Building wxruby-swig on WinXP
Sorry for the lameness, but I need things explained to me very slowly...
-----Original Message-----
Subject: RE: [Wxruby-users] wxGrid Question
>
> Yes, grab the latest tarball from the above location. Then, you should
> install rubygems if you haven''t already:
> http://rubyforge.org/projects/rubygems/
>
> That should allow you to easily install rake:
>
2005 Jul 19
5
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
2008 Jan 25
0
[ wxruby-Feature Requests-17477 ] wxruby fails with SWIG 1.3.33
Feature Requests item #17477, was opened at 2008-01-25 01:57
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=221&aid=17477&group_id=35
Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: wxruby fails with SWIG 1.3.33
Initial Comment:
Using SourceMage GNU/Linux. Stable recently upgraded to
2004 Sep 01
2
wxruby swig progress
I''ve checked a number of new .i files into the wxruby-swig tree. Not all
of them are fully tested, but I thought it would be better for them to
be there than to have somebody start duplicating the work. I''ve also
added the ''caret'' and ''image'' samples, as well as the generic etc/test.rb.
These need the unreleased SWIG-1.3.22. The current
2005 Jul 20
3
Plans to rename wxruby-swig to wxruby2
Greetings all,
Over the last few months, while I have been busy on other projects, Nick
and other folks have built wxruby-swig up to where it now supports about
120 classes, compared to the 139 in wxruby 0.6. When you include the
fact that wxruby 0.6 had a few classes that really weren''t needed
(because non-wx ruby versions work fine), it looks like wxruby-swig is
actually very
2005 Feb 04
0
wxruby-swig update
> Great news!! So is the swig-version going to be first released with 2.5
> support? The documentation I''m working on parses the 2.4 xml file. Will
> the original parser create a xml file in the same format for 2.5 ?
Thankfully, the XML hasn''t changed - I''m using the same file and
removing the stripped methods.
> I think a while back there was some talk
2005 May 03
2
Making it easier to contribute wxRuby-SWIG code
After seeing contributions from Dmitry and Alex, I''m wondering how we
can better organize and encourage user contributions.
ORGANIZING
Maybe identifying what is still missing in wxRuby-SWIG and publishing a
prioritized todo list could useful to contributors.
GETTING NOTICED
It might be useful to post a link to the unassigned todo list each month
to comp.lang.ruby and ask for
2006 Dec 06
0
[ wxruby-Bugs-7131 ] Stock colours (eg Wx::WHITE) are not available before App#on_init
Bugs item #7131, was opened at 2006-12-06 19:13
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=218&aid=7131&group_id=35
Category: Incorrect behavior
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Alex Fenton (brokentoy)
Assigned to: Kevin Smith (qualitycode)
Summary: Stock colours (eg Wx::WHITE) are not available before App#on_init