mirror of https://github.com/texmacs/doc.git
Updates
This commit is contained in:
parent
4911039da8
commit
c9aee8ac24
|
@ -1,11 +1,16 @@
|
||||||
<TeXmacs|1.0.7.1>
|
<TeXmacs|1.0.7.12>
|
||||||
|
|
||||||
<style|tmdoc>
|
<style|tmdoc>
|
||||||
|
|
||||||
<\body>
|
<\body>
|
||||||
<tmdoc-title|Plans for the future>
|
<tmdoc-title|Plans for the future>
|
||||||
|
|
||||||
<with|color|red|[Should be completed]>
|
There are many things that we would like to integrate in <TeXmacs>. On
|
||||||
|
<hlink|<name|Savannah>|http://savannah.gnu.org/projects/texmacs/>, we
|
||||||
|
maintain a<nbsp>wish list with <hlink|suggestions|http://www.texmacs.org/tmweb/contact/wishes.en.html>
|
||||||
|
by users and other detailed wanted features. Here follows an incomplete
|
||||||
|
list of more general directions for future development, as on september 2,
|
||||||
|
2011.
|
||||||
|
|
||||||
<section|Typesetting>
|
<section|Typesetting>
|
||||||
|
|
||||||
|
@ -17,8 +22,6 @@
|
||||||
<item>Better support for agglomerated documents (from physically
|
<item>Better support for agglomerated documents (from physically
|
||||||
different documents).
|
different documents).
|
||||||
|
|
||||||
<item>Incorporation of better linking primitives (XLink, Proclus).
|
|
||||||
|
|
||||||
<item>More types of dynamic objects, like animations, help balloons,
|
<item>More types of dynamic objects, like animations, help balloons,
|
||||||
<abbr|etc.>
|
<abbr|etc.>
|
||||||
|
|
||||||
|
@ -32,8 +35,8 @@
|
||||||
mention a few of these:
|
mention a few of these:
|
||||||
|
|
||||||
<\itemize>
|
<\itemize>
|
||||||
<item>Searching/replacing texts, formulas, certain environments etc. and
|
<item>Better search and replace tool for structured texts, formulas,
|
||||||
regular expressions.
|
certain environments etc. and regular expressions.
|
||||||
|
|
||||||
<item>Mathematical facilities: simplification of a selected region,
|
<item>Mathematical facilities: simplification of a selected region,
|
||||||
substitutions of formulas in other formulas, etc.
|
substitutions of formulas in other formulas, etc.
|
||||||
|
@ -45,7 +48,33 @@
|
||||||
<item>Grammar checkers and automatic translation programs. Does someone
|
<item>Grammar checkers and automatic translation programs. Does someone
|
||||||
know where to find detailed free dictionaries and stuff like that?
|
know where to find detailed free dictionaries and stuff like that?
|
||||||
|
|
||||||
<item>Incorporation of free speech recognition program.
|
<item>Incorporation of a free speech recognition program.
|
||||||
|
</itemize>
|
||||||
|
|
||||||
|
<section|Converters to other formats>
|
||||||
|
|
||||||
|
There is a constant need for good converters from and to other data
|
||||||
|
formats:
|
||||||
|
|
||||||
|
<\itemize>
|
||||||
|
<item>Of course, <TeX>/<LaTeX> cannot really be considered as a format
|
||||||
|
(it is really a language with an ill defined grammar). Nevertheless it is
|
||||||
|
important to have good heuristic converters in both directions. We still
|
||||||
|
would appreciate help in this direction, in particular in order to
|
||||||
|
support standard documents styles of various journals.
|
||||||
|
|
||||||
|
<item><TeXmacs> is also compatible with <name|Html>, but some things such
|
||||||
|
as forms have not been implemented yet. The importation of tables could
|
||||||
|
also be further improved and it would be nice if the importer could
|
||||||
|
support cascaded style sheets.
|
||||||
|
|
||||||
|
<item>It would be nice to have converters for the document formats used
|
||||||
|
by <name|Open Office>, <name|Word>, and the internal formats used by
|
||||||
|
important publishers such as <name|Elsevier>.
|
||||||
|
|
||||||
|
<item>We would appreciate help for writing a converter from <TeXmacs> to
|
||||||
|
the <name|Texinfo> format, which is the standard documentation format for
|
||||||
|
the GNU project.
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
||||||
<section|A universal spreadsheet>
|
<section|A universal spreadsheet>
|
||||||
|
@ -60,12 +89,14 @@
|
||||||
|
|
||||||
<section|Technical pictures>
|
<section|Technical pictures>
|
||||||
|
|
||||||
I also would like to include a facility for drawing technical pictures. In
|
We have started to include a facility for drawing technical pictures, but
|
||||||
this implementation you should be able to benefit from the fact that you
|
the responsable developer (Henri <name|Lesourd>) is currently no longer
|
||||||
can define macros for making geometrical constructions. It would for
|
part of the <TeXmacs> team. It would be nice to rewrite parts of the tool
|
||||||
instance be possible to write a style file for drawing electronic circuits
|
and extend it further so as to allow for the definition of graphical
|
||||||
or chemical components with a nice icon bar for selecting circuits or
|
macros. This would allow users to define new geometrical constructions. It
|
||||||
components, just as you select lines and circles in usual pictures.
|
would for instance be possible to write a style file for drawing electronic
|
||||||
|
circuits or chemical components with a nice icon bar for selecting circuits
|
||||||
|
or components, just as you select lines and circles in usual pictures.
|
||||||
|
|
||||||
<section|Tools for usage on the web and in networks>
|
<section|Tools for usage on the web and in networks>
|
||||||
|
|
||||||
|
@ -86,7 +117,7 @@
|
||||||
The following improvements should still be made in order to link <TeXmacs>
|
The following improvements should still be made in order to link <TeXmacs>
|
||||||
to computer algebra systems:
|
to computer algebra systems:
|
||||||
|
|
||||||
<\enumerate>
|
<\itemize>
|
||||||
<item>Improving the layout of computer algebra sessions.
|
<item>Improving the layout of computer algebra sessions.
|
||||||
|
|
||||||
<item>Add extra features to increase the interoperability between
|
<item>Add extra features to increase the interoperability between
|
||||||
|
@ -94,21 +125,15 @@
|
||||||
over the layout of big output.
|
over the layout of big output.
|
||||||
|
|
||||||
<item>More semantics for the objects being communicated. This may either
|
<item>More semantics for the objects being communicated. This may either
|
||||||
be high level information (like Openmath or HTML 4.0 mathematical markup)
|
be high level information (like HTML 4.0 mathematical markup or Openmath)
|
||||||
or low level information (including information about the representation
|
or low level information (including information about the representation
|
||||||
of data), depending on the required speed.
|
of data), depending on the required speed.
|
||||||
|
|
||||||
<item>Further possibilities for evolution concern highlighting, debugging
|
<item>Further possibilities for evolution concern syntax highlighting,
|
||||||
facilities and so on.
|
debugging facilities and so on.
|
||||||
</enumerate>
|
</itemize>
|
||||||
|
|
||||||
<section|Interaction with other GNU projects>
|
<tmdoc-copyright|1998--2011|Joris van der Hoeven>
|
||||||
|
|
||||||
We would appreciate help for writing a converter from <TeXmacs> to the
|
|
||||||
<name|Texinfo> format, which is the standard documentation format for the
|
|
||||||
GNU project.
|
|
||||||
|
|
||||||
<tmdoc-copyright|1998--2002|Joris van der Hoeven>
|
|
||||||
|
|
||||||
<tmdoc-license|Permission is granted to copy, distribute and/or modify this
|
<tmdoc-license|Permission is granted to copy, distribute and/or modify this
|
||||||
document under the terms of the GNU Free Documentation License, Version 1.1
|
document under the terms of the GNU Free Documentation License, Version 1.1
|
||||||
|
|
|
@ -1,4 +1,4 @@
|
||||||
<TeXmacs|1.0.4.1>
|
<TeXmacs|1.0.7.12>
|
||||||
|
|
||||||
<style|tmdoc>
|
<style|tmdoc>
|
||||||
|
|
||||||
|
@ -12,12 +12,6 @@
|
||||||
If I have the courage, I might one day write a garbage collector for
|
If I have the courage, I might one day write a garbage collector for
|
||||||
<TeXmacs>.
|
<TeXmacs>.
|
||||||
|
|
||||||
<section|Graphical interface>
|
|
||||||
|
|
||||||
We wish to move towards <with|font-shape|small-caps|Guile-Gtk> or another
|
|
||||||
portable graphical user interface. Now that we have found someone for
|
|
||||||
making a Windows port, this not an urgent issue anymore though.
|
|
||||||
|
|
||||||
<section|Encodings and fonts>
|
<section|Encodings and fonts>
|
||||||
|
|
||||||
<\itemize>
|
<\itemize>
|
||||||
|
@ -43,9 +37,6 @@
|
||||||
several other main optimizations should still be made:
|
several other main optimizations should still be made:
|
||||||
|
|
||||||
<\itemize>
|
<\itemize>
|
||||||
<item>Indexing file names which are in the distribution. This may
|
|
||||||
accelerate booting the program.
|
|
||||||
|
|
||||||
<item>Encode the system environment variables; this will globally
|
<item>Encode the system environment variables; this will globally
|
||||||
accelerate the program. Also, intermediate data during the typesetting
|
accelerate the program. Also, intermediate data during the typesetting
|
||||||
process might be encoded in a more binary way.
|
process might be encoded in a more binary way.
|
||||||
|
@ -55,8 +46,8 @@
|
||||||
|
|
||||||
<section|Scheme>
|
<section|Scheme>
|
||||||
|
|
||||||
The <name|Guile>/<value|scheme> interface should become more robust and
|
The <name|Guile>/<scheme> interface should become more robust and well
|
||||||
well documented. Several things still need to be done for this:
|
documented. Several things still need to be done for this:
|
||||||
|
|
||||||
<\itemize>
|
<\itemize>
|
||||||
<item>Implement a system for ``contextual overloading''.
|
<item>Implement a system for ``contextual overloading''.
|
||||||
|
@ -66,8 +57,8 @@
|
||||||
<item>Systematic use of closures throughout the code.
|
<item>Systematic use of closures throughout the code.
|
||||||
|
|
||||||
<item>A clean interface for manipulating <TeXmacs> content (a unified
|
<item>A clean interface for manipulating <TeXmacs> content (a unified
|
||||||
interface for both internal <TeXmacs> trees and the associated
|
interface for both internal <TeXmacs> trees and the associated <scheme>
|
||||||
<value|scheme> representation).
|
representation).
|
||||||
|
|
||||||
<item>Documentation.
|
<item>Documentation.
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
|
@ -1,4 +1,4 @@
|
||||||
<TeXmacs|1.0.6.9>
|
<TeXmacs|1.0.7.12>
|
||||||
|
|
||||||
<style|tmdoc>
|
<style|tmdoc>
|
||||||
|
|
||||||
|
@ -28,17 +28,13 @@
|
||||||
using <TeXmacs>. Any people interested in developing addional interactive
|
using <TeXmacs>. Any people interested in developing addional interactive
|
||||||
features inside <TeXmacs> are invited to contact us.
|
features inside <TeXmacs> are invited to contact us.
|
||||||
|
|
||||||
<item><TeXmacs> is used in combination with <name|Maxima> in a
|
|
||||||
high-school education project at the <name|Lycée Villegénis> at
|
|
||||||
<name|Massy Palaiseau> (nearby <name|Paris>). In view of this project, we
|
|
||||||
intend to further simplify the user-interface and to make it easier to
|
|
||||||
install up-to-date <TeXmacs> versions under <name|Windows>.
|
|
||||||
|
|
||||||
<item><hlink|Felix Breuer|http://www.felixbreuer.net/index.html> and
|
<item><hlink|Felix Breuer|http://www.felixbreuer.net/index.html> and
|
||||||
formerly <name|David Mentré> have considered developing a <hlink|literate
|
formerly <name|David Mentré> have considered developing a <hlink|literate
|
||||||
programming plug-in|http://david.mentre.free.fr/serendipity/index.php?/archives/8-Literate-programming-as-source-code-comments.html>
|
programming plug-in|http://david.mentre.free.fr/serendipity/index.php?/archives/8-Literate-programming-as-source-code-comments.html>
|
||||||
for <TeXmacs>. Any concrete implementation of their proposals would
|
for <TeXmacs>. Another such initiative is
|
||||||
happily find its way into the main distribution.
|
<hlink|<name|Fangle>|http://www.nongnu.org/fangle/>, which has recently
|
||||||
|
been started by <name|Sam Liddicott>. Any concrete implementation of
|
||||||
|
their proposals would happily find its way into the main distribution.
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
||||||
If you want to start a project based on <TeXmacs>, then please let us know.
|
If you want to start a project based on <TeXmacs>, then please let us know.
|
||||||
|
|
|
@ -1,19 +1,17 @@
|
||||||
<TeXmacs|1.0.6.9>
|
<TeXmacs|1.0.7.12>
|
||||||
|
|
||||||
<style|tmdoc>
|
<style|tmdoc>
|
||||||
|
|
||||||
<\body>
|
<\body>
|
||||||
<tmdoc-title|Major objectives for the upcoming stable versions>
|
<tmdoc-title|Major objectives for the upcoming stable versions>
|
||||||
|
|
||||||
Our main focus for the next stable version 1.1 (to be released during 2007)
|
Our main focus for the next stable version 1.1 (to be released during 2012)
|
||||||
is on the improvement of the user interface and documentation. This
|
is on the improvement of the user interface and documentation. This
|
||||||
comprises the following developments:
|
comprises the following developments:
|
||||||
|
|
||||||
<\itemize>
|
<\itemize>
|
||||||
<item>Increased standardization of the user interface: use M$-style
|
<item>Completion and stabilization of the <name|Qt> port and the
|
||||||
keyboard shortcuts as the default (and provide <name|Emacs> compatability
|
resulting ports for <name|Windows> and <name|MacOS>.
|
||||||
as an option), further simplification of the menus and increased use of
|
|
||||||
popup windows.
|
|
||||||
|
|
||||||
<item>Development of a markup-based graphical user interface for popup
|
<item>Development of a markup-based graphical user interface for popup
|
||||||
windows. This new interface might only be ready after the next stable
|
windows. This new interface might only be ready after the next stable
|
||||||
|
@ -46,13 +44,6 @@
|
||||||
<item>Improve the quality of the <TeXmacs> makefiles so as to make them
|
<item>Improve the quality of the <TeXmacs> makefiles so as to make them
|
||||||
completely compatible with <verbatim|automake> and <verbatim|autoconf>.
|
completely compatible with <verbatim|automake> and <verbatim|autoconf>.
|
||||||
|
|
||||||
<item>Improve the <name|Cygwin> port and other ports of <TeXmacs> and
|
|
||||||
monitor the availability of <TeXmacs> in major distributions.
|
|
||||||
|
|
||||||
<item>Reshape the low-level window interface so as to make the interface
|
|
||||||
to Xlib easily portable to other systems, such as Gtk, Qt, MacOsX,
|
|
||||||
Windows, etc. Also provide plugins for <name|Cairo>, <name|OpenGL>, etc.
|
|
||||||
|
|
||||||
<item>Replace the current widget system by a markup-based system, with
|
<item>Replace the current widget system by a markup-based system, with
|
||||||
the possibility to use widgets (from Gtk, Qt, Aqua, etc.) from standard
|
the possibility to use widgets (from Gtk, Qt, Aqua, etc.) from standard
|
||||||
GUI's instead of the <TeXmacs>-provided style files.
|
GUI's instead of the <TeXmacs>-provided style files.
|
||||||
|
|
|
@ -1,4 +1,4 @@
|
||||||
<TeXmacs|1.0.6.9>
|
<TeXmacs|1.0.7.12>
|
||||||
|
|
||||||
<style|tmdoc>
|
<style|tmdoc>
|
||||||
|
|
||||||
|
@ -10,24 +10,16 @@
|
||||||
development on new features. A few points currently have our priority:
|
development on new features. A few points currently have our priority:
|
||||||
|
|
||||||
<\itemize>
|
<\itemize>
|
||||||
<item>Further development of the graphical drawing mode. First, the
|
<item>Further development of the graphical drawing mode. Our main next
|
||||||
upcoming support of <hlink|<name|Cairo>|http://cairographics.org/>,
|
goal is to allows users to create new macros, either by explicit
|
||||||
<hlink|<name|OpenGL>|http://en.wikipedia.org/wiki/OpenGL>, <abbr|etc.>
|
constructions or constrained-based constructions. Finally, we would like
|
||||||
should improve the rendering quality. Secondly, we intend to allow the
|
to incorporate several features which are typically found in editors of
|
||||||
user to create new macros, either by explicit constructions or
|
vector graphics, such as <hlink|<name|Inkscape>|http://www.inkscape.org/>.
|
||||||
constrained-based constructions. Finally, we would like to incorporate
|
|
||||||
several features which are typically found in editors of vector graphics,
|
|
||||||
such as <hlink|<name|Inkscape>|http://www.inkscape.org/>.
|
|
||||||
|
|
||||||
<item>Extended features for computer algebra sessions, such as automatic
|
<item>Extended features for computer algebra sessions, such as automatic
|
||||||
folding of large expressions, lazy output (with subexpressions which can
|
folding of large expressions, lazy output (with subexpressions which can
|
||||||
be further evaluated by clicking on them), cas-aided writing, etc.
|
be further evaluated by clicking on them), cas-aided writing, etc.
|
||||||
|
|
||||||
<item>Providing more semantics to mathematical formulas by providing a
|
|
||||||
simple way to construct parsers and pretty printers and to use them for
|
|
||||||
establishing a bijection between presentation and content markup for
|
|
||||||
certain well-defined languages.
|
|
||||||
|
|
||||||
<item>Continue the development of remote <TeXmacs> servers for providing
|
<item>Continue the development of remote <TeXmacs> servers for providing
|
||||||
web-based services in combination with <TeXmacs>. These services comprise
|
web-based services in combination with <TeXmacs>. These services comprise
|
||||||
chatting (with mathematical formulas) and collaborative authoring.
|
chatting (with mathematical formulas) and collaborative authoring.
|
||||||
|
|
|
@ -1,4 +1,4 @@
|
||||||
<TeXmacs|1.0.6.9>
|
<TeXmacs|1.0.7.12>
|
||||||
|
|
||||||
<style|tmdoc>
|
<style|tmdoc>
|
||||||
|
|
||||||
|
@ -7,10 +7,10 @@
|
||||||
|
|
||||||
It is difficult to give a precise roadmap for the <TeXmacs> development,
|
It is difficult to give a precise roadmap for the <TeXmacs> development,
|
||||||
because our plans are permanently adjusted as a function of unexpected
|
because our plans are permanently adjusted as a function of unexpected
|
||||||
needs, help by new contributors and humour. Nevertheless, we tend to spend
|
needs, help by new contributors and personal moods. Nevertheless, we tend
|
||||||
a significant time on a few major objectives, while amusing ourselves with
|
to spend a significant time on a few major objectives, while amusing
|
||||||
the implementation of a few new features. Roughly speaking, our roadmap can
|
ourselves with the implementation of a few new features. Roughly speaking,
|
||||||
therefore be divided into three major parts:
|
our roadmap can therefore be divided into three major parts:
|
||||||
|
|
||||||
<\enumerate>
|
<\enumerate>
|
||||||
<item>A limited number of major objectives for the upcoming stable
|
<item>A limited number of major objectives for the upcoming stable
|
||||||
|
|
Loading…
Reference in New Issue