Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="todo">
<title>To-do list</title>
<itemizedlist mark="bullet">
<listitem>
<para>I haven't yet paid much attention to some of the more esoteric
issues such as multithreaded applications, or interactions with other
popular Ruby extensions. FXRuby seems to cooperate well with Ruby's
thread scheduler on all platforms, although threading support for the
mswin32 build of Ruby was broken for Ruby versions 1.6.7 and earlier.
For best results, use Ruby versions 1.6.8 or later.</para>
</listitem>
<listitem>
<para>More examples are always good. Instead of (or in addition to)
merely cloning the C++ examples from the standard FOX distribution, it
would be nice to have original example programs that demonstrate
Ruby's special strengths.</para>
</listitem>
<listitem>
<para>Documentation is of course a big weakness at this point. I am
slowly building up a set of "pseudo-sources" with RDoc-style
comments that can be used to generate API documentation but this is far
from complete (see the <filename class="directory">rdoc-sources</filename>
directory in the standard source distribution).</para>
</listitem>
<listitem>
<para>Many people have expressed interest in a framework similar to
Tk's <classname>Canvas</classname> widget that allows you to draw
and drag 2-D shapes around, etc. Should be able to implement this kind
of thing directly in Ruby code (i.e. no need to write it in C++ first
and then "wrap" it).</para>
</listitem>
<listitem>
<para>There is no native Mac OS X port of FOX, but many people are
successfully building and running FOX and FXRuby applications on Mac OS
X using Apple's X11 server implementation. For more information,
please see the <ulink
url="http://www.fox-toolkit.net/cgi-bin/wiki.pl?Mac_OS_X">Mac OS X</ulink>
page at the <ulink url="http://www.fox-toolkit.net">FOX Community Wiki</ulink>
site.</para>
</listitem>
<listitem>
<para>Need to investigate how well FXRuby-based applications work with
<ulink url="http://exerb.sourceforge.jp/index.en.html">exerb</ulink>,
and perhaps add a section to the documentation about how to do this.</para>
</listitem>
<listitem>
<para>As of this writing, FOX doesn't provide any support for
internationalization (I18N) or Unicode text and so FXRuby doesn't
either. It is possible that FOX 1.2 will include some I18N support (see
the <ulink url="http://www.fox-toolkit.net/cgi-bin/wiki.pl?FAQ">FAQ</ulink>
at the <ulink url="http://www.fox-toolkit.net">FOX Community Wiki</ulink>
site), and if so, appropriate changes will be made to FXRuby at that
time.</para>
</listitem>
<listitem>
<para>FOX's list-like widgets (such as <classname>FXList</classname>)
behave differently from Ruby container objects (such as
<classname>Array</classname>) in the sense that when a list widget is
destroyed, it typically destroys all of its contained items at the same
time. One consequence of this behavior is that you can end up with Ruby
objects that refer to dead C++ objects (a variation of the dangling
pointer problem familiar to C/C++ programmers). I would like to see if
this behavior can be modified for FXRuby so that it's impossible to
end up with these "dangling references".</para>
</listitem>
</itemizedlist>
</chapter>