[mcclim-devel] One char patch to presentation-defs

[rpgoldman at real-time.com]

>>>>> "PA" == Paolo Amoroso <amoroso at mclink.it> writes:

    PA> Christophe Rhodes <csr21 at cam.ac.uk> writes:
    >> problems than social ones.  My own feelings on CLiki-as-bugtracker are
    >> known, I think, but Paolo is a perfectly acceptable User Interface
    >> from my point of view, so while he remains willing to serve like that,
    >> it's fine.  What we lack is any kind of automatic regression testing
    >> to give confidence that bugs remain fixed; lacking a wide userbase as

    PA> Yes, I am still willing to maintain the bug list.  Any feedback on
    PA> that page after using it for some time?  Is the page easy to browse?
    PA> Any redundant information?  What about moving the closed bugs section
    PA> to a different page?

Is there some reason to do this instead of a Bugzilla?  Is the latter
just too much of a pain to maintain?

    PA> As for testing, each time I update my working copy of the CVS
    PA> repository, I also rebuild the CLIM Listener and play a bit with it.
    PA> Occasionally, I also do this with the demos.  It's not formal testing,
    PA> but does provide a quick opportunity to see whether anything is
    PA> obviously broken.

Would you consider writing up a McCLIM cliki page describing what you
do when you play with the lisp listener?  This is the only application
beside my own (that I know of) that uses format-graph-from-roots.  I'd
love to have a quick list of things to try before committing a patch.

    >> Secondly, how do we cause the available development resources to grow?
    PA> [...]
    >> anything exciting?  (People here may not know that the closure web
    >> browser is at least partially revived: it is known to run in McCLIM
    >> using the X backend and recent CMUCL or SBCL releases; on the other
    >> hand, there's no way that a web browser is going to be a killer
    >> application in today's world...)

    PA> A web browser application probably not, but a comfortably hackable
    PA> browser may have some appeal.

How about a front-end for some of the MP3 stuff in Practical Common
Lisp?

How about configuration consoles for some of the CL applications out
there.  E.g., I've just discovered that Albert has a ton of
configuration options....

Just a thought....

As an aside, can anyone point me to a sample application that has some
pane devoted to displaying information about the state of the
application (e.g., a filename that is the current document, mode of
interaction, etc.)?  I'm a little hazy on how to manage the use of
labels, etc.

Thanks!

R