On 2/6/2011 2:30 AM, Stephen J. Turnbull wrote:
These are relatively simple in some sense, but I don't know if
they
fit with your skill set.
Summary of skill set:
18 years software development experience (16 years ago)
16 years of system/network/information design including task driven user interfaces.
Familiar with C., C++, make (high-level knowledge faded by time)
reasonably knowledgeable Python, Bash
Limitations: hands, time, work as it presents itself
My first goal is to get some version of xemacs running well enough so that I
can get going with a command macro speech recognition interface. Second goal is
to convince one of youse guys to help me get VR-mode running well enough so I
can start doing real work. Third goal is to make a working development
environment out of ??? so I can produce working versions of xemacs if for no
other reason that the test changes others have done as I learn Lisp etc.
I admit to feeling quite frustrated because I'm having so many problems just
getting started. The problems I've encountered are classic newbie problems but
information is scattered if it's written down and I haven't figured everything
out yet.
A couple of things that I think could just leave some improvement. The user
should never have to do anything to get the package manager working. Even the
process of selecting a repository is really ugly. off the top of my head, I
would change the packet management system to easily answer the questions:
Was the package management system set up correctly?
Where are the packages stored?
Is my repository up-to-date?
What package contains what function?
Is this package loaded?
Is this package up-to-date?
How do I select/unselect/load/unload a package?
I know the existing system has a lot of these questions answered and that's a
good thing but there are some things that are just plain obtuse.
I would highly recommend (and I see you are already thinking that way from your
comments) we never ever leave a user without a fully usable package interface.
In this line of thought, there are several other things we need to create as
well such as .xemacs directory and init.el
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta