similar to: Status Update

I''ve downloaded wxPython and the demos and am trying to update our bigdemo. I can see some big differences in how wxRuby and wxPython interact on Windows. Our layout seems wrong. For example, I never knew the textctrl sample had more than two controls on it! I only ever saw the two. In the python version, the controls lay out close together. Secondly, on the ComboBox sample

I would like to tag and release 0.0.37 soon. I''m thinking of the next few days. We have good new stuff (Printing, Scintilla on OS X, other new classes) and have fixed some bugs. Also, would be good to put the early build probs with the last release behind us. Here''s the patches I think are outstanding: - Wx::App cleanup - rake HTML docs publishing - Scintilla OS X -

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

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

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

This patch fixes background color problems (at least on Windows). It uses the dreaded ''FIXME'' My plan for next weekend is to try building wxPython from the source to see how they manage to achieve several things with SWIG that we''re not (yet) able to. If I''m successful it might lead to wrapping a significant portion of wxWidgets more correctly than

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

I am attempting a text editor using wxRuby. I''m having character issues. Strings are not binary-safe. Some characters are not allowed. - newline / line feed (\n), tab (\t) are displayed - carraige return (\r) is stripped - Other control characters and high-ascii cause control values to become empty. Affected controls include: Wx::TextCtrl, Wx::StaticText, Wx::Clipboard, et al. Most

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.

Hi, I am trying out this example adapted from the wxpython book, but the mouse motion event does not seem to be captured right. What am I doing wrong? Thanks warrior # code below require ''wx'' class MyFrame < Wx::Frame def initialize super(nil, -1, "My Frame", :size => [300,300]) @my_panel = Wx::Panel.new(self, -1) evt_motion(){ |event|

Hello All, There seems to have been a lot of interest in getting wxScintilla incorperated, and I think most of us who want it, want it so we can create an editor, so to avoid multiple projects comming out with the same goal (Not really that bad of a problem....), I''m going to kick start this, and ask that anyone interested in developing a Editor with wxRuby and wxScintilla, to send

The previous TreeCtrl.i was very messy and just plain wrong, for instance it had GetFirstChild as depreciated when in fact only 1 version of it was depreciated not both. I changed GetFirstChild and GetNextChild to return an array of values to match the wxPython and wxPerl usage. I also noticed that wxTreeCtrl is inherited from wxControl on Windows and wxScrolledWindow on everything else so I #if

I''m trying to un-ignore TextCtrl#get_selection. The typemaps work fine, but in the process it breaks get_insertion_point. This is because (on Mac, tho not GTK), get_insertion_point calls get_selection internally and simply returns the first value. I think the return value is being converted from a long to a ruby int twice, because when get_selection is wrapped, it works fine but the

Hi Sean Thanks for the info on OS intel. Glad that at least it''s only broken on Scintilla, not generally. If you could upload a gem w/o Scintilla that would be great. Perhaps some library or framework that''s needed on 10.4 that 10.3 doesn''t need. I don''t know. cheers alex

Here''s a .zip file with the files and directory structure needed to try out my scintilla changes. It also included a help file. You''ll, of course, need to download wxScintilla from here: https://sourceforge.net/project/showfiles.php?group_id=51305&package_id=45182 Oh. Hmm, I just noticed he made a new build today. I guess I''ll have to go see what''s

Hi. Attached you find an attempt to adding MediaCtrl to WxRuby. It''s only tested on windows (compiled with msvc 6.0). Everything seems to be working fine except for a small problem with a few functions: wxFileOffset Seek(wxFileOffset where, wxSeekMode mode = wxFromStart); wxFileOffset Tell(); //FIXME: This should be const wxFileOffset Length(); //FIXME: This should be const

These patches implement wxRegion and the ShapedWindow sample. I stole the ruby image from ruby-lang.org. Shamelessly. Maybe someone has a better image we can use for the shaped window. It didn''t seem to make sense to use the Python image. I''d like something even bigger than what I stol^h^h^h^hmade, preferably. Image goes in icons. I had to %ignore one function in wxRegion.

Hi Seems that the last round of commits makes bigdemo crash fairly quickly. Guessing it''s something to do with either the Window or fixmodule change. Program received signal EXC_BAD_ACCESS, Could not access memory. 0x00034fbc in rb_obj_is_kind_of (obj=3825080, c=1839676) at object.c:523 523 object.c: No such file or directory. Any hints? alex

Thanks to everyone who voted in the API style survey. We had 10 votes altogether - we''re not electing the prime minister, after all - but it was decisively a yes. 90% (9/10) supported adding keyword constructors, and 77% (7/9) ruby-style accessors. The changes are summarised at the bottom of the email. We hope to have a 1.9.1 release incorporating these in the next week or two.