I never replied to this:
at 04:11 AM 6/28/98 -0700, SL Baur wrote:
XEmacs 21.0 is winding down to a close. The latest scheduled release
date is (7/31). Where do you want to go tomorrow?
Ideally, XEmacs 21.1 is in feature freeze now. There are a ton of
bugs to be fixed. It doesn't necessarily have to be the case, but
it's just my feeling.
I would prefer for feature freeze to be relaxed for features that don't
exist under mswindows but do under X. If the final output of the 21.x
schedule is an mswindows editor that is virtually identical to the X
version I would be happy.
I'm personally very pleased with XEmacs 21.0. It does just about
everything I want it to do, and no more.
It does more than I believed possible back in January ;)
One possible way is to split the development trees such that we have a
rigidly controlled stable branch (21.x) and a no-holds-barred
cvs should make this easy.
The biggest problem for a legacy app like Emacs is maintenance. There
are plenty of areas where XEmacs shows its age. Two of which are in
the character/line oriented (re)display and the non-standard Lisp
extension language engine.
1. I would primarily like to see some *much* flashier graphic support in
XEmacs. The sad fact is that flashness is going to sell it to new users
followed by useability. That's what sets XEmacs apart from FSFmacs IMHO. To
that end here are some random thoughts:
1a) Pixel based tab stops. We have to have these to support proportional
width fonts properly. I petitioned Chuck to do it but I think he got pulled
onto other things before he could look at it.
1b) Columns, or text areas or linked buffers. Basically someway of keeping
text in certain areas of the screen. Even allowing scrollbar linkage of
side-by-side buffers would probably suffice.
1c) General frame-based rather than buffer based graphics display. Maybe
done by overlaying frame graphics over buffer graphics. This would allow us
to add cool stuff to the look and feel of frames and do precise graphics in
a frame (char pos based graphics is a bit hit and miss). Even better if we
had 1b so that we could keep text out of the graphics areas.
1d) Proper sub-window support including widgets in buffers - i.e. so that
you could embed proper toolkit-based scrollbars, buttons, toolbars,
selection boxes etc in a buffer. widget.el is ok but pretty limited.
1e) gif animation.
2) I've mentioned CORBA support ;) It would be nice to browse the name
service, say, with dired. A proper lisp binding would allow cool debugging
of CORBA services.
3) unify url base file finding. So for instance you could type in:
maybe someone has done this already?
That's all! ;)
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp