GNU Smalltalk ideas

[Paolo Bonzini]

Here are they.

<ul>
<li>GnuTLS bindings, including adding to Swazoo support for serving
HTTPS.  Other common libraries, such as GD, GSL or Expat would be
interesting.  In a project application you probably want to propose a
coherent set of libraries to work on, with an example of an application
that would tie them together.

<li>Work on the GUI.  You could write a Gtk or Blox back-end for
OmniBrowser, or add the ability to develop in the GUI and sync the files
on the file system.

<li>Develop a system to port changesets
from other Smalltalks.  The idea is to have a merge-like command that
takes two foreign source code files (e.g. from SqueakSource) and merges
the code into a GNU Smalltalk source file.

<li>Or, you could implement a "remote browser", i.e. something that
could browse an already running system.  In other words, the
view/controller and the model would reside on two different instances of
the VM.  This requires implementing or porting some kind of distributed
messaging system.  The same could be done for debugging; you cou
investigate possibly if the protocols that are used by Java debuggers
are suitable to Smalltalk.

<li>Work on command-line tools.  You could port parts of the Refactoring
Browser and make a command-line version of Smalllint for example.

<li>Create a build tool that allows one to coordinate builds with
Smalltalk scripts, like Rake or SCons (see also <a 
href="http://smalltalk.gnu.org/blog/bonzinip/sake-rake-smalltalk";>this</a>
for an example of what I mean).

<li>Build a continuous integration server using Seaside, with code
reports.  This could have many directions: building an interface to
version control systems (svn, CVS, git) that can be used from Smalltalk,
analyze what problems would limit the uptime of a web application
written using GNU Smalltalk and Seaside (memory leaks, etc.),...
</ul>