wxruby users - Dec 2003 - Font support, MS Windows binaries, Mac status (?)

Wx::Font now supports almost all the methods of wxFont, which should be 
good news for anyone interested in rich text editing (FreeRIDE anyone?). 
These changes are checked in to CVS and my darcs repository.

Thanks to Nobuaki Arima for submitting font support code. Although I 
didn''t actually use that font code, I did directly use the included 
sample file, and the changes to const.cpp. It was great to have a 
working sample, and to know that font support was possible.

I took advantage of this opportunity to switch font over to be generated 
from a .t template (font.t), so it will be easier to maintain in the 
future. To do that, I had to make some minor changes to wxpp.rb.

Oddly, underlining does not work on my GTK system. The screen shot that 
Nobuaki Arima sent shows it working under MS Windows.

Over the weekend, I finally had a chance to borrow a Windows machine and 
experiment with Gour''s MinGW binary build. It works great! I''m
really
excited that any MS Windows system can run wxruby apps just by 
installing Ruby itself, plus two dll''s and wxruby.so.

Questions: Do the licenses of those dll''s require us to distribute 
source code? Or are they LGPL or apache style? I''m pretty sure you can 
ship wxWindows itself without source code. Also, we''ll need a readme 
that describes where you should put the .so and .dll files, and how to 
make sure they are in your path.

Question: Are we going to be able to have Mac OS X support in our 0.2 
release, or will that have to wait for a future version?

Cheers,

Kevin

Kevin Smith wrote:
>
> Over the weekend, I finally had a chance to borrow a Windows machine and
> experiment with Gour''s MinGW binary build. It works great!
I''m really
> excited that any MS Windows system can run wxruby apps just by
> installing Ruby itself, plus two dll''s and wxruby.so.
>
> Questions: Do the licenses of those dll''s require us to distribute
> source code? Or are they LGPL or apache style? I''m pretty sure you
can
> ship wxWindows itself without source code. Also, we''ll need a
readme
> that describes where you should put the .so and .dll files, and how to
> make sure they are in your path.
>
> Question: Are we going to be able to have Mac OS X support in our 0.2
> release, or will that have to wait for a future version?
This is all good news! I''m trying again to get a native windows (VC++)
build
with an installer that would integrate with Andy''s windows installer
for
Ruby. Gour said that he had problems with a static build and that''s why
he
chose the dll route. So, this time, I''m going to try that also.

Curt

>
> Question: Are we going to be able to have Mac OS X support in our 0.2 
> release, or will that have to wait for a future version?
0.2 builds just fine on OS X. I''m a little behind on bundling it 
together (spent a bit too much time at home over the Holidays and not 
nearly enough on the computer) but I''ll have it built soon.

Nick

Kevin Smith (wxruby@qualitycode.com) wrote:
> Over the weekend, I finally had a chance to borrow a Windows machine and 
> experiment with Gour''s MinGW binary build. It works great!
I''m really
> excited that any MS Windows system can run wxruby apps just by 
> installing Ruby itself, plus two dll''s and wxruby.so.
Glad to hear that :-)
> Questions: Do the licenses of those dll''s require us to distribute
> source code? Or are they LGPL or apache style? I''m pretty sure you
can
> ship wxWindows itself without source code. 
I don''t know about that. Let''s someone more copetent in legal
issues speak up.
> Also, we''ll need a readme that describes where you should put the
.so and
> .dll files, and how to make sure they are in your path.
Well, wxruby.so goes into standard Ruby directory, and as far as wxWindows dll
it is explained in old README.mingw (though it needs some update for newer
versions :-)

When are you planning to have a 0.2 release?

(I can update README.mingw and send you mine extconf.rb if there is some
difference - this time I did a build with non-debug version.)

Sincerely,
Gour


-- 
Gour
gour@mail.inet.hr
Registered Linux User #278493

Nick wrote:
> 0.2 builds just fine on OS X. I''m a little behind on bundling it 
> together (spent a bit too much time at home over the Holidays and not 
> nearly enough on the computer) but I''ll have it built soon.
That''s great news. My hope is to have the 0.2 release ready within a 
week or so, but it''s ok if the OS X version isn''t quite ready
by then. I
expect to set up the rubyforge files such that we can add more platform 
binaries later, as they become available.

Kevin

Gour wrote:
> Kevin Smith (wxruby@qualitycode.com) wrote:
>>Questions: Do the licenses of those dll''s require us to
distribute
>>source code? Or are they LGPL or apache style? I''m pretty sure
you can
>>ship wxWindows itself without source code. 
> 
> I don''t know about that. Let''s someone more copetent in
legal issues speak up.
I just checked. The MinGW stuff seems to be public domain, so we 
apparently don''t need to include any source or license information. The
wxWindows dll can be distributed without source code, but we do need to 
include a copy of the wxWindows license.

Anyone building a tarball, even  a "beta", should include that license
file, along with the wxRuby license file. It''s not that the legal
danger
is huge. It''s that it is the proper and moral thing to do. If someone 
out there ends up with a copy, they should know the license terms.
> Well, wxruby.so goes into standard Ruby directory, and as far as wxWindows
dll
> it is explained in old README.mingw (though it needs some update for newer
> versions :-)
Ah. I didn''t think to look in the old readme, since it wasn''t
in the
tarball :-)
> When are you planning to have a 0.2 release?
I would like to have a pre-release version by January 4. It would be 
great if we could release within a week after that.

I hope to post a Linux binary tarball within a couple days. Will someone 
out there be able to test it? Preferably on a non-Debian box. I may also 
try to create a simple .deb package. If anyone out there can create a 
.rpm, that would be great.
> (I can update README.mingw and send you mine extconf.rb if there is some
> difference - this time I did a build with non-debug version.)
Yes, please do.

Kevin