Hi! I''m using winxp, wxwindows 2.4.2, mingw, msys: droptarget.o(.data$_ZTV18wxDropTargetHelper+0x20):droptarget.cpp: undefined reference to `wxDropTargetHelper::OnData(int, int, wxDragResult)'' textdroptarget.o(.text+0x26a):textdroptarget.cpp: undefined reference to `wxTextDropTargetHelper::wxTextDropTargetHelper()'' dataobject.o(.text+0x306):dataobject.cpp: undefined reference to `wxDataObjectHelper::wxDataObjectHelper()'' make: *** [wxruby.so] Error 1 -- +-[ Kontra, Gergely<kgergely@mcl.hu> PhD student Room IB113 ]---------+ | http://www.mcl.hu/~kgergely "Olyan langesz vagyok, hogy | | Mobil:(+36 20) 356 9656 ICQ: 175564914 poroltoval kellene jarnom" | +-- Magyar php mirror es magyar php dokumentacio: http://hu.php.net --+
KONTRA Gergely wrote:> I''m using winxp, wxwindows 2.4.2, mingw, msys: > > droptarget.o(.data$_ZTV18wxDropTargetHelper+0x20):droptarget.cpp: > undefined reference to `wxDropTargetHelper::OnData(int, int, > wxDragResult)'' > textdroptarget.o(.text+0x26a):textdroptarget.cpp: undefined reference to > `wxTextDropTargetHelper::wxTextDropTargetHelper()'' > dataobject.o(.text+0x306):dataobject.cpp: undefined reference to > `wxDataObjectHelper::wxDataObjectHelper()'' > make: *** [wxruby.so] Error 1 >Sorry about those. I just checked in a set of changes from Nick Kral that (hopefully) will fix them. Unfortunately, I have no way to test MS Windows builds, so I rely on you folks to report (and fix) problems like these. Thanks, Kevin
KONTRA Gergely wrote:> On 1120, Kevin Smith wrote: > >>KONTRA Gergely wrote: >> >>>I''m using winxp, wxwindows 2.4.2, mingw, msys: >>> > > > After successful compilation: > > kgergely@OJJEKTUM /d/tmp > $ irb > irb(main):001:0> require ''wxruby'' > require ''wxruby'' > => true > irb(main):002:0> Wx::FileDropTarget > Wx::FileDropTarget > NameError: uninitialized constant Wx::FileDropTarget > from (irb):2 > irb(main):003:0> > > So it seems, that FileDropTarget is not even created. Surprisingly the > filedroptarget.cpp is very short.Yes. In filedroptarget.t, the RB_IMPLEMENT_CLASS line is commented out (an extra set of //). I don''t have time to try uncommenting it right now, but it is definitely an untested class. This confused me for a while, because earlier I had done a make install, so I was running an old copy of the library. I couldn''t see any of the new classes. Finally I figured it out, and now I can see Wx::DropTarget but not Wx::FileDropTarget. Kevin
Kontra, We''re not ignoring you, but you''re going to have to give the DnD development a little bit of time. Unlike many of the widgets, where ruby calls into wxWindows and then returns back, the DnD classes require subclasses of the DataObjects and DropTargets to be developed which requires Ruby to call Wx to call Ruby then return then return. This is a lot more sophisticated, and may require either a lot of hand coded subclasses or a huge extension to wxpp. Either way, this is going to have to be put on a development schedule. If you''re familiar with ruby and wxWindows you could help with the development. Nick Kevin Smith wrote:> KONTRA Gergely wrote: > >> On 1120, Kevin Smith wrote: >> >>> KONTRA Gergely wrote: >>> >>>> I''m using winxp, wxwindows 2.4.2, mingw, msys: >>>> >> >> >> After successful compilation: >> >> kgergely@OJJEKTUM /d/tmp >> $ irb >> irb(main):001:0> require ''wxruby'' >> require ''wxruby'' >> => true >> irb(main):002:0> Wx::FileDropTarget >> Wx::FileDropTarget >> NameError: uninitialized constant Wx::FileDropTarget >> from (irb):2 >> irb(main):003:0> >> So it seems, that FileDropTarget is not even created. Surprisingly the >> filedroptarget.cpp is very short. > > > Yes. In filedroptarget.t, the RB_IMPLEMENT_CLASS line is commented out > (an extra set of //). I don''t have time to try uncommenting it right > now, but it is definitely an untested class. > > This confused me for a while, because earlier I had done a make > install, so I was running an old copy of the library. I couldn''t see > any of the new classes. Finally I figured it out, and now I can see > Wx::DropTarget but not Wx::FileDropTarget. > > Kevin > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >
My only Q: how to be a developer of this project? Gergo -- +-[ Kontra, Gergely<kgergely@mcl.hu> PhD student Room IB113 ]---------+ | http://www.mcl.hu/~kgergely "Olyan langesz vagyok, hogy | | Mobil:(+36 20) 356 9656 ICQ: 175564914 poroltoval kellene jarnom" | +-- Magyar php mirror es magyar php dokumentacio: http://hu.php.net --+
KONTRA Gergely wrote:> My only Q: how to be a developer of this project?A very good question. And I don''t have a simple answer, but we can talk about it. Being a developer could mean one of several things: 1. You contribute code. Well, by that definition, you''re already a wxruby developer, Gergely! Seriously, I am happy to take code submissions from anyone who is willing to send them in. As we have discovered, the current CVS diff/patch situation is a bit of a problem, but so far it has worked. 2. You are listed on the wxruby project page as being a ''developer''. You''ll need to be added that way before you can do administrative tasks like marking bugs fixed. If you want to be added to the project this way, let me know and we can probably do it. But that won''t give you... 3. CVS commit access. Ah, the big one, and probably what you were asking about. Although I don''t have a firm policy, my preference would be for someone to submit a few good code patches first. Once I am confident in your ability to write and submit well-written, well-tested code, you can start checking directly into CVS. I think this is the way most projects work. Sometime within the next few months, there is a chance that wxruby might move to a more advanced revision control system. Unlike CVS, it would allow each developer to work locally, without requiring server write access. You would easily be able to keep your tree up to date with the "official" repository while you work. When you''re ready, you would submit your patch(es) to me, and I would easily be able to merge them in and add them to the official repository. I am already experimenting with a system like this, called darcs. If you are interested in testing it with me, send me an email off-list and we can coordinate it. Thanks, Kevin