[Message resent with corrected headers]
Bob Weiner <weiner(a)beopen.com> writes:
> P.S. If you want me to respond to something, mail me directly as I rarely get
> the luxury to read these lists. If you have other *very specific* project
> ideas surrounding XEmacs or InfoDock, tell us about them, including
> development timeframes so we can consider sponsoring them.
Here is some very specific areas that XEmacs could do with
improvements, including some that can be done by people with
non-programming skills. Most of these are smaller projects than adding
a whole new Widget set. The times are guesstimates.
- Update the New User manual to reflect version 21, including major
usability improvements for Newbies such as customize. [2 weeks]
- Write a graphical version of the tutorial. This is much more doable
with the new widgets. [1.5 weeks]
- Paint an Open Source set of high-color icons for XEmacs (including
Gnus, VM, W3 and TeX-toolbar). [<1 week for a skilled artist]
- Interface XEmacs with a fast C/C++ parser (gcc with precompiled
headers?) to provide the equivalent of the Intellisense features
contained in Visual Studio. (c.f. Eric Ludlam's work, eldoc, ilisp
JDK and your own oobrowser). [1 month]
Alternatively find out whether XEmacs-NT can call on Visual Studio
to provide the needed information and if so, implement it. [1 week]
- Provide true unicode support for XEmacs (I believe this one might be
already taken).
These are all projects that directly improve the (apparent) usability
of XEmacs to various groups of new and older users. Apart from the
last one I feel they can performed by one committed person in isolation
and then be integrated.
Jan
P.S. To close of with a really hard problem (that to me seems
inappropriate for SourceXchange) that is becoming more and more
relevant.
- Design and implement a clean way of allowing "multiple major modes"
as embedded scripts, ditto HTML, and ditto documentation is becoming
more and more popular. AFAIK there currently isn't an editor that
does this really well.