Hello,
For the past three months we have made considerable progress on
implementing Free CLIM. While much code remains to be written, a
substantial fraction has been completed.
We now have code for regions, transformations, sheets and their
protocols, ports, grafts, mediums, graphics operations, output
recording, stream panes, layout panes, application frames, and some
gadgets. We still haven't worked on presentation types, menus,
graphs, incremental redisplay, and much more.
Most of the latest additions work with CMU CL, for which we have
written installation instructions. A small test program shows how to
use layout panes and stream panes and some other elements.
Implementing Free CLIM is a large task, and we could use some help.
Naturally, if you are interested in contributing code, that is a good
thing, but even if you feel that you do not have the time to
contribute any considerable chunk of code, there are smaller, but
equally important, tasks that you could help us with. Here is a
partial list of such tasks:
While we have tested the code sufficiently well to run the test
case, we do not claim that all code has been thoroughly tested. You
can help us by exercising the code, reporting problems and perhaps
even fixing minor bugs.
You can help us by porting the code to other platforms such as MCL,
LispWorks, CLISP and others and by writing installation instructions
for these platforms.
Someone with extensive knowledge about the differences between
different versions of defsystem could help us make the system easy
to compile and load on a variety of systems.
Code reviews. You can take a chapter of the specification and
verify that the code we have written appears to correspond to the
specification.
Take care of compiler warnings. There are currently quite a few
warnings from the compiler (at least from Python). You could help
us find the reasons for the warnings and fix the code.
Uniformization of the code. Several people have worked on the code
and it shows. It would be useful if someone would make sure that
the code corresponds to some widely accepted standard, in particular
with respect to comments and header information for classes and
functions, declarations of generic functions and protocols, etc.
Comments and :documentation. We have added very little comments in
the code, since most is clear from the specification. Some cases,
however, could use additional comments, and many code elements could
use on-line :documentation (which would sometimes just be a compy of
the passage in the specification).
Type declarations. We have not been systematic about type
declarations of slots, function arguments, etc. It would be nice to
have more such type declarations to allow the compiler to detect
more potential problems (and also to have the additional compiler
warnings taken care of).
--
Robert Strandh
---------------------------------------------------------------------
Greenspun's Tenth Rule of Programming: any sufficiently complicated C
or Fortran program contains an ad hoc informally-specified bug-ridden
slow implementation of half of Common Lisp.
---------------------------------------------------------------------
In article <··············@napperon.labri.u-bordeaux.fr>,
Robert STRANDH <·······@labri.u-bordeaux.fr> writes:
> Hello,
>
> For the past three months we have made considerable progress on
> implementing Free CLIM. While much code remains to be written, a
> substantial fraction has been completed.
The sources can be found here:
http://www.mikemac.com/mikemac/McCLIM/index.html
Mike McDonald
·······@mikemac.com
On Tue, 22 Aug 2000 15:41:11 GMT, ·······@mikemac.com (Mike McDonald)
wrote:
> The sources can be found here:
>
> http://www.mikemac.com/mikemac/McCLIM/index.html
Is there a publicly accessible CVS repository?
Paolo
--
EncyCMUCLopedia * Extensive collection of CMU Common Lisp documentation
http://cvs2.cons.org:8000/cmucl/doc/EncyCMUCLopedia/
Paolo Amoroso <·······@mclink.it> writes:
> On Tue, 22 Aug 2000 15:41:11 GMT, ·······@mikemac.com (Mike McDonald)
> wrote:
>
> > The sources can be found here:
> >
> > http://www.mikemac.com/mikemac/McCLIM/index.html
>
> Is there a publicly accessible CVS repository?
Mike McDonald is managing the CVS repository, so he gets to decide the
policy for access to it. I am sure that if you think you are likely
to make some contribution, then Mike would give you access. If you
are only planning to check out the code, the daily snap shot should
work.
--
Robert Strandh
---------------------------------------------------------------------
Greenspun's Tenth Rule of Programming: any sufficiently complicated C
or Fortran program contains an ad hoc informally-specified bug-ridden
slow implementation of half of Common Lisp.
---------------------------------------------------------------------
On 24 Aug 2000 11:57:03 +0200, Robert STRANDH <·······@labri.u-bordeaux.fr>
wrote:
> policy for access to it. I am sure that if you think you are likely
> to make some contribution, then Mike would give you access. If you
> are only planning to check out the code, the daily snap shot should
> work.
I meant anonymous access because I am only planning to keep up to date with
the code. So daily snapshots are an adequate solution for the time being.
Paolo
--
EncyCMUCLopedia * Extensive collection of CMU Common Lisp documentation
http://cvs2.cons.org:8000/cmucl/doc/EncyCMUCLopedia/
For those who aren't familiar with the Free CLIM project, a page about
Free CLIM can be found at
http://www2.cons.org/free-clim/
That page also has a pointer to the CLIM spec.
--
T. Kurt Bond, ···@tkb.mpl.com