similar to: wxScintilla

There is a contribution called ''stc'' (StyledTextControl) that comes with wxWidgets. It appears that this is -also- a wrapper around Scintilla. I can''t tell if one or the other of these two is a better choice or if there''s a particular reason to favor one over the other. I can see that having the source available right there in the contrib directory would

wxScintilla already comes with a SWIG friendly header file. I modified the rakewx and the Scintilla.i file to include it directly from the wxScintilla install. This means it''s an odd-ball compared to our other classes. Does anyone see a problem with this? I think it''s best to use the one supplied with the installation to avoid problems of the header file getting out of

Two patches here: First one removes virtual from a function that shouldn''t have been virtual. Second one applies a typemap to catch GetRectFromChildWindow. For reasons that are completely beyond me the standard ruby OUTPUT typemaps don''t define directorargouts. I will take a stab at patching SWIG''s default typemaps someday so we get this fixed for free on all our

Here''s the last piece of the puzzle you''ll need to get this working (other than modifying the platform specific stuff like rakemswin.rb). Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

The latest cvs version of SWIG breaks a few things. I have patched common.i to fix most of it. There will be some other things later that should be compatible with all versions. Can someone test to see if this compiles with the old version? Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: common.i.patch Url:

Seems the gems and tarball have been downloaded a bit with no reported problems. I suggest we do an alpha release incorporating Roy''s useful recent fixes and announce it more publicly e.g. on the mailing list. It''s not perfect, but again we have made a lot of progress since late July and we should build on it; it was our dev goal. I now personally have to put some effort

Small patch to correct spelling of lemonade. Should ask Sean if he really wanted it to be lemonaid. If not, here''s the patch. On another note... This sample works! Kudos. It is odd that the textbox doesn''t scroll. I suppose I may patch that, too. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

Hi I just tagged 0.0.37 in Subversion. I also added a note on the Wiki on how to do this, and how to checkout a clean version: http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo For the build, I''m just about to upload a tarball, and will add a powerpc gem once the compiler''s chugged away. Please upload for your platform as you''re ready. I suggest we announce

Hi Should we look to do a 0.0.38 release soon? I think we should get an updated set of gems out there to show we are making progress. So if you have a moment over the next couple of days, please could you post how stable a release gem from SVN HEAD is on your OS? Linux seems OK on release, crashes in debug mode - which seem to relate to the same failed assertion from wx/event.h.

I''m posting this for a friend who is having trouble with this and here is his message. "Heya! I''m working on a script editor application, but it''s missing one key feature: Syntax highlighting. Seeing this, I looked around in the sample directory and came across scintilla.rb. I attempted a run, however Ruby reported Wxruby2::Scintilla as an uninitialized

Hi Now we''ve got the download problems nailed, shall we do an announcement on comp.lang.ruby? I can do it if you''re really busy, but Kevin I think you have first refusal as you''re owed the biggest chunk of kudos for getting us this far. re patch backlog: no worries - just clearing the decks before having another go at integrating wxScintilla - but I can''t

I decided to try my hand at hacking SWIG and successfully produced a patch that fixes the error I demonstrated. I''m not -positive- it''s correct for all cases but I''ll re-run my version of SWIG over the library and see how things turn out. Roy

http://visualwx.altervista.org/ A visual builder for wxWindows that purports to support Ruby. I''ll play with this some and see if I can design projects that work with wxRuby2. Roy

I feel like I''ve mostly been banging my head against header file issues for the last couple weeks. I don''t feel like I''ve gotten any actual ''work'' done on fixing wrapping problems, adding new classes or improving the samples. I''m searching for any but haven''t found ''em. Some things I''ve noticed: 1) Some

Hi A gemspec for installation of wxuby-swig via rubygems. It assumes the end-users will compile the pre-swigged .cpp files & that that the main require file will be wx.rb (as per Kevin''s suggestion). runrake.rb is just a helper script that runs rake correctly within the rubygems installation process. # to build the gem gem build wxruby2.gemspec # to build & install the

I just re-integrated fixdeleting.rb, the last of the post-processors. Running minimal.rb no longer segfaults on exit. Running dialogs.rb and immediately exiting doesn''t segfault, but bringing up a dialog and then exiting does. So there are still memory problems, but fewer than yesterday :-/ I''m not sure how it compares to last week. I probably won''t have much time

This patch implements a more generic solution to the problem that will work for all our integer types at least. Use this instead of the last version I sent, please. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

These files add the virtual function AcceptFocus that was missing from wxWindow.h. In order to make things right I had to make sure it was also declared in all the places where wxWindows also changes it. Also, in wxTextCtrl on Windows GetDefaultAttributes needs to be redeclared. I haven''t downloaded the Unix and Mac headers for 2.6.3 so I couldn''t see if it also applies

About a year ago (ouch!), Robert Carlin submitted a ported version of the wxPython demo/sample. I hoped to include it in wxruby2, but it relies on SplitterWindow, which isn''t in wxruby2 yet. I tried to implement SplitterWindow myself, but got such strange results that I''m thinking I did something wrong. Even though the generated C++ code specified a variable number of

SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until 1.3.30, unless I can hack together a nasty workaround for a problem with the object tracking. It seem that each SWIG module gets its own hash for tracking objects. This means that, for example, you create a find dialog (in FindReplaceDialog.cpp) events you get from it (from FindDialogEvent.cpp)