The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

Completing the CLIM Specification

• We need a much better representation for trees of output records. Currently they are completely unsorted, so point containment and overlapping region tests can potentially be very slow. R-trees look promising.
• bboard-pane - the layout composite pane that allows arbitrary placement of its children
• Extensions to Goatee, such as Macros (you want it to be an emacs clone? You've got the "e", but the "macs" is still missing!)
• drag and drop - both the "drag" (moving output records) and the "drop" (presentation drag-and-drop translators)
• with-accept-help

Extensions

• A multi-window top level frame. Franz calls this an "activity frame."
• We should have a way of using Cut & Paste in the X backend.
• A composite pane that allows the user to adjust the size of the child panes. What's this called?
• GTK gadgets
• New backends. A Cocoa backend is very high on our hit list (Why not a GNUStep backend? This would also run pseudo-natively on Cocoa, as well as on many other platforms, with a cool Look & Feel -- Andreas Fuchs?) (I see a Cocoa backend filling a real need on Mac OS X; GnuStep doesn't seem as compelling to me. However, the more backends the merrier :) -- Tim Moore?)
• Pie menus, both in general and for the presentation menu.
• Accessibility features, such as a ascii-only backend and speech synthesizer backends for blind/disabled people.
• Convenience stuff. I would like McCLIM? to be usable even with no mouse installed (a feat that not even gnome2 has managed yet).
• pointer documentation in a detached "wholine" window
• pointer documentation as tooltips
• a coherent protocol for multiple applications working together. Multiple applications should "just work" now, but we'd like presentations to be acceptable across applications. How would this interact with window focus, the concept of a key window, etc.? What command loop has control?
• customization. A .mcclimrc file? Well defined variables? A GUI for setting them?
• interaction with the native clipboard-selection-whatever.

Applications

• Lisp listener. Input and output would be accepted and presented, of course. [done]
• inspector
• class browser [Gilbert Baumann has some code (screen shot)]
• presentation inspector
• editor based on Goatee.

Already Done

Completing to the CLIM Specification

• Killing/Yanking + kill rings (these were done by Andreas Fuchs? on 2002-12-15 (for Goatee at least)
• Incremental redisplay and dialog facilities. Incremental redisplay is checked in, still needs some work to conform to the spec. Work on dialog facilities (accepting-values) is underway. [an initial implementation of accepting-values is available]
• An accept presentation method for the form presentation type. A simple version would just use READ. A full-featured version will override the implementation's read and some other stuff (READ-DELIMITED-LIST, read macros) so that accept is called to read the subforms of a form. [This is completely done for OpenMCL. The implementation-specific code for reading subforms still remains to be done for other implementations]
• Presentation histories are implemented.
• with-output-as-gadget - gadgets (native or otherwise) in CLIM stream panes [done by hefner]

This page is linked from: index  

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively