Hi there,
reliable sources tell me that it's time for another release. The next holiday is jan 14th, the Orthodox New Year, and I'd like to release 0.9.4 on this day.
"McCLIM 0.9.4 Orthodox New Year"?
This mail marks the start of the freeze period. Please test as aggressively as you can, and keep changes to the core of mcclim to a minimum (of course, documentation improvements are always welcome).
It may be necessary to turn Drei off by default, as there are still some somewhat-serious problems:
* Reader macros are poorly handled by the Lisp syntax, leading to possible Listener breakage. * Delimiter gestures do not work properly for some reason (rtoy has been affected by this). * Sometimes, Lisp syntax is not properly enabled when the input buffer is changed via the presentation history or similar. * Sometimes, Drei will move its output record when stuff is inserted. I *suspect* this is not the same bug as the one triggered by Closure.
Apart from that, great! There's been quite a bunch of changes over the last months, so it's a good time to do a release I think.
Troels Henriksen athas@sigkill.dk writes:
It may be necessary to turn Drei off by default, as there are still some somewhat-serious problems:
- Reader macros are poorly handled by the Lisp syntax, leading to possible
Listener breakage.
- Delimiter gestures do not work properly for some reason (rtoy has been
affected by this).
- Sometimes, Lisp syntax is not properly enabled when the input buffer is
changed via the presentation history or similar.
- Sometimes, Drei will move its output record when stuff is inserted. I
*suspect* this is not the same bug as the one triggered by Closure.
Would it be OK by you to leave *use-goatee* as nil, but mention these problems prominently in the release notes? (The major points of a release, at least from my point of view, are to have a reference point in time, and to have an excuse to make an announcement; if we can get people to run the code, their feedback might help to narrow down the causes of various problems... but they're most likely to start by running the system in its default configuration).
Cheers,
Christophe
Christophe Rhodes wrote:
Troels Henriksen athas@sigkill.dk writes:
It may be necessary to turn Drei off by default, as there are still some somewhat-serious problems:
- Reader macros...
- Delimiter gestures do not work properly ...
- Sometimes, Lisp syntax is not properly enabled ...
- Sometimes, Drei will move its output record when stuff is inserted....
Would it be OK by you to leave *use-goatee* as nil, but mention these problems prominently in the release notes?
FWIW, I agree with Christophe's suggestion. Drei is, in a way, far more McClim-ish than Goatee, and I think enabling it by default is genuine progress (if not on every dimension at once). (All the 'problems' above could be prefaced with 'Sometimes'...)
JQS
John Q Splittist splittist@yahoo.com writes:
FWIW, I agree with Christophe's suggestion.
Okay, then that's how it's going to be. I just dislike the notion of making a release and a few days afterwards tell people to use the CVS version if they want their bug to go away.
-
Christophe Rhodes -
John Q Splittist -
Troels Henriksen