sxemacs-devel
[Top] [All Lists]

Re: Todo List (aka Lets get busy)

From: Sebastian Freundt <hroptatyr@xxxxxxxxxxx>
Subject: Re: Todo List (aka Lets get busy)
Date: Tue, 25 Jan 2005 08:06:15 +0000
User-agent: Gnus/5.110003 (No Gnus v0.3) SXEmacs/22.1.1 (linux)
Steve Youngs <steve@xxxxxxxxxxx> writes:

[snip]
>   o Update the Texinfo docs
>
>     This is a big one, and no doubt quite boring too.  But it has to
>     be done.  SXEmacs manuals _must_ talk about SXEmacs, not XEmacs.
>     A big renaming is needed.  But...
>
>     For you people who are thinking "I'll just write a little Perl
>     script and do a global rename"... _WRONG_.  There are going to be

such a stupid idea, cannot imagine how people come to think perl could be
a solution of something ;P

>     lots of places where renaming "XEmacs" to "SXEmacs" will _not_ be
>     the right thing to do.  A manual renaming is going to be the
>     safest way of doing it.

Nonetheless, I think I could manage to sacrifice some time with it.
Since this is an extra portion of stuff which is not required to build, I
think I'll start another branch for this here locally.

I cannot estimate time yet, since context analyses may vary.

[snip]
>     Be especially careful of URL's and email addresses etc.  (A side
>     note: is `URI' the plural of `URL' or are they completely
>     different things?)

Not completely different, a URI is the Universal Resource Identifier, the
differences are subtle, but most important is that a URI can carry a
portion of the document in its string (the definition says code fragment),
like http://www.some.foo/bar.html#fooagain1 or
scp://me@xxxxxxxx/path/to/bar/foo.c#line1288

In general the URI is more general than the corresponding URL (or even
URN), but that's just a margin note :)


[snip]
>   o Begin windoze code eradication.
>
>     We don't do windoze here, so the windoze code has to go.  This
>     will be a pretty big task, but most of it is #ifdef'd so shouldn't
>     be too bad.
>
>     If this doesn't get finished by release time, that's cool, it can
>     continue into the next release.  Oh, if it _does_ get finished by
>     this release, well that'll be terrific!

Hm, I started to eliminate some occurences of windoze code just when I've
looked through some code for other reasons, so everybody could/should harm
the code by side-effect when viewing the sources.

This isnt really a dedicated search'n'destroy and it doesnt get you fast
to what you're looking for, but that way you can turn a rather boring task
to a minimum of effort.

[snip]
>   o Bignum, bigfloat, ratio
>
>     Jerry James implemented these in XE 21.5 and I know of at least
>     one Berlin-based mathematician that loves them. :-)

Hehe ;P
Yeah along with that, I imagine bringing the whole openssl+gmp into
SXE. Gmp (mpf, mpi and mpq) for calculating with bignums and the hashes
and ciphers of openssl for security applications.


[snip]
>   o Boehm GC (because it is thread-safe, and sexy)

Hm, but why backporting KKCC then?

>   o XFT/UTF stuff
>
>     Much to my dismay, the world seems to be going UTF or bust.  We'll
>     have to as well. :-(  Of course if some miracle happens and the
>     whole world starts speaking nothing but iso-8859-1 we can forget
>     this one. :-)

I'd head the miracle ;)


[snip]
>   o New widget toolkits.
>
>     Should SXEmacs be "skin-able"?

Erm, what's that? We have color-theme.el and we have X resources, so
skinning is just a matter of providing a tarball of someone's dotfiles
along with a suited colour theme and maybe some toolbar-xpms.


[snip]
>   o Display _anything_ in a buffer.
>
>     Including full motion resizable video.

Yay :D

Greets
hroptatyr
Sebastian


<Prev in Thread] Current Thread [Next in Thread>