>From smustudent1@yahoo.com:
> Agreed. I've run into another Xmaxima problem - I don't know if it
> impacts Linux (for the first time in years I don't have ready access to
> a Linux box - aarrrrgghh) but on Windows if you resize the browser
> window with a plot present in the maxima document, the redrawing
> routines seem to have some problems. I sent an email with a screenshot
> to the list but it doesn't seem to have made it - if other people can
> confirm this we might want to file it as a bug.
Cliff, I backed out a change that appears to have been the cause of
this - let me know if the problem goes away with the
latest CVS.
James, I would really like to see a windows binary with CLISP too, but
CLISP windows releases are real windows not MSYS. The maxima build is
so wedded to GNU configure now; how hare will it be to build the
current maxima without it? CLISP used to ship maxima.mem with it, so
they knew how to build maxima before all of the configure
superstructure was put in place. It might be harder now.
It is important to note that under Windows, gcl is hardwired into
xmaxima right now as a special and only case. Not a problem to add
another special case, but because of configure, and maxima as a shell
script, and run-maxima-lisp as a shell script, you have to duplicate
all of their logic before the current approach to multiple lisps will
run under Windows. Presumably you would do that in Tcl in xmaxima, but
I do not like duplicated logic. If you have to do it in Tcl for
xmaxima, then you might as well bite the bullet and replace the
maxima.sh and run-maxima-lisp.sh shell scripts with Tcl scripts. The
drawbacks of having Tcl scripts are less than the nightmare of
duplicated logic, and most people will have Tcl for xmaxima.
James, in your priorities you posted, I would say that Windows binaries
are essential for a final release. No matter what I may think, what I
see in my software distributions is that Windows is 80% of the downloads.
Mike.