diff --git a/about/projects/future.en.tm b/about/projects/future.en.tm index 4bfa00b..256fb7d 100644 --- a/about/projects/future.en.tm +++ b/about/projects/future.en.tm @@ -1,11 +1,16 @@ - + <\body> - + There are many things that we would like to integrate in . On + |http://savannah.gnu.org/projects/texmacs/>, we + maintain awish list with + by users and other detailed wanted features. Here follows an incomplete + list of more general directions for future development, as on september 2, + 2011. @@ -17,8 +22,6 @@ Better support for agglomerated documents (from physically different documents). - Incorporation of better linking primitives (XLink, Proclus). - More types of dynamic objects, like animations, help balloons, @@ -32,8 +35,8 @@ mention a few of these: <\itemize> - Searching/replacing texts, formulas, certain environments etc. and - regular expressions. + Better search and replace tool for structured texts, formulas, + certain environments etc. and regular expressions. Mathematical facilities: simplification of a selected region, substitutions of formulas in other formulas, etc. @@ -45,7 +48,33 @@ Grammar checkers and automatic translation programs. Does someone know where to find detailed free dictionaries and stuff like that? - Incorporation of free speech recognition program. + Incorporation of a free speech recognition program. + + + + + There is a constant need for good converters from and to other data + formats: + + <\itemize> + Of course, / 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. + + is also compatible with , 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. + + It would be nice to have converters for the document formats used + by , , and the internal formats used by + important publishers such as . + + We would appreciate help for writing a converter from to + the format, which is the standard documentation format for + the GNU project. @@ -60,12 +89,14 @@ - I also would like to include a facility for drawing technical pictures. In - this implementation you should be able to benefit from the fact that you - can define macros for making geometrical constructions. It 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. + We have started to include a facility for drawing technical pictures, but + the responsable developer (Henri ) is currently no longer + part of the team. It would be nice to rewrite parts of the tool + and extend it further so as to allow for the definition of graphical + macros. This would allow users to define new geometrical constructions. It + 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. @@ -86,7 +117,7 @@ The following improvements should still be made in order to link to computer algebra systems: - <\enumerate> + <\itemize> Improving the layout of computer algebra sessions. Add extra features to increase the interoperability between @@ -94,21 +125,15 @@ over the layout of big output. 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 of data), depending on the required speed. - Further possibilities for evolution concern highlighting, debugging - facilities and so on. - + Further possibilities for evolution concern syntax highlighting, + debugging facilities and so on. + - - - We would appreciate help for writing a converter from to the - format, which is the standard documentation format for the - GNU project. - - + + @@ -12,12 +12,6 @@ If I have the courage, I might one day write a garbage collector for . - - - We wish to move towards or another - portable graphical user interface. Now that we have found someone for - making a Windows port, this not an urgent issue anymore though. - <\itemize> @@ -43,9 +37,6 @@ several other main optimizations should still be made: <\itemize> - Indexing file names which are in the distribution. This may - accelerate booting the program. - Encode the system environment variables; this will globally accelerate the program. Also, intermediate data during the typesetting process might be encoded in a more binary way. @@ -55,8 +46,8 @@ - The / interface should become more robust and - well documented. Several things still need to be done for this: + The / interface should become more robust and well + documented. Several things still need to be done for this: <\itemize> Implement a system for ``contextual overloading''. @@ -66,8 +57,8 @@ Systematic use of closures throughout the code. A clean interface for manipulating content (a unified - interface for both internal trees and the associated - representation). + interface for both internal trees and the associated + representation). Documentation. diff --git a/about/projects/roadmap-external.en.tm b/about/projects/roadmap-external.en.tm index 20c7bae..1cf3461 100644 --- a/about/projects/roadmap-external.en.tm +++ b/about/projects/roadmap-external.en.tm @@ -1,4 +1,4 @@ - + @@ -28,17 +28,13 @@ using . Any people interested in developing addional interactive features inside are invited to contact us. - is used in combination with in a - high-school education project at the at - (nearby ). In view of this project, we - intend to further simplify the user-interface and to make it easier to - install up-to-date versions under . - and formerly have considered developing a - for . Any concrete implementation of their proposals would - happily find its way into the main distribution. + for . Another such initiative is + |http://www.nongnu.org/fangle/>, which has recently + been started by . Any concrete implementation of + their proposals would happily find its way into the main distribution. If you want to start a project based on , then please let us know. diff --git a/about/projects/roadmap-major.en.tm b/about/projects/roadmap-major.en.tm index 275e1a7..7d4a685 100644 --- a/about/projects/roadmap-major.en.tm +++ b/about/projects/roadmap-major.en.tm @@ -1,19 +1,17 @@ - + <\body> - 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 comprises the following developments: <\itemize> - Increased standardization of the user interface: use M$-style - keyboard shortcuts as the default (and provide compatability - as an option), further simplification of the menus and increased use of - popup windows. + Completion and stabilization of the port and the + resulting ports for and . Development of a markup-based graphical user interface for popup windows. This new interface might only be ready after the next stable @@ -46,13 +44,6 @@ Improve the quality of the makefiles so as to make them completely compatible with and . - Improve the port and other ports of and - monitor the availability of in major distributions. - - 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 , , etc. - Replace the current widget system by a markup-based system, with the possibility to use widgets (from Gtk, Qt, Aqua, etc.) from standard GUI's instead of the -provided style files. diff --git a/about/projects/roadmap-minor.en.tm b/about/projects/roadmap-minor.en.tm index bc201e7..2829e76 100644 --- a/about/projects/roadmap-minor.en.tm +++ b/about/projects/roadmap-minor.en.tm @@ -1,4 +1,4 @@ - + @@ -10,24 +10,16 @@ development on new features. A few points currently have our priority: <\itemize> - Further development of the graphical drawing mode. First, the - upcoming support of |http://cairographics.org/>, - |http://en.wikipedia.org/wiki/OpenGL>, - should improve the rendering quality. Secondly, we intend to allow the - user to create new macros, either by explicit constructions or - constrained-based constructions. Finally, we would like to incorporate - several features which are typically found in editors of vector graphics, - such as |http://www.inkscape.org/>. + Further development of the graphical drawing mode. Our main next + goal is to allows users to create new macros, either by explicit + constructions or constrained-based constructions. Finally, we would like + to incorporate several features which are typically found in editors of + vector graphics, such as |http://www.inkscape.org/>. Extended features for computer algebra sessions, such as automatic folding of large expressions, lazy output (with subexpressions which can be further evaluated by clicking on them), cas-aided writing, etc. - 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. - Continue the development of remote servers for providing web-based services in combination with . These services comprise chatting (with mathematical formulas) and collaborative authoring. diff --git a/about/projects/roadmap.en.tm b/about/projects/roadmap.en.tm index 8ae645c..1ea34ac 100644 --- a/about/projects/roadmap.en.tm +++ b/about/projects/roadmap.en.tm @@ -1,4 +1,4 @@ - + @@ -7,10 +7,10 @@ It is difficult to give a precise roadmap for the development, because our plans are permanently adjusted as a function of unexpected - needs, help by new contributors and humour. Nevertheless, we tend to spend - a significant time on a few major objectives, while amusing ourselves with - the implementation of a few new features. Roughly speaking, our roadmap can - therefore be divided into three major parts: + needs, help by new contributors and personal moods. Nevertheless, we tend + to spend a significant time on a few major objectives, while amusing + ourselves with the implementation of a few new features. Roughly speaking, + our roadmap can therefore be divided into three major parts: <\enumerate> A limited number of major objectives for the upcoming stable