[Texmacs-dev] Roadmap towards next stable version [was Re: const refs (yes, again), joint task proposal]

[Joris van der Hoeven]

Hi Miguel,

I would prefer working in a file-based manner, which keeps the diffs
more understandable; David Allouche wanted to do this a long time ago,
starting with the stuff in src/Kernel, and so on.

However, the moment is not exactly well chosen.  My priority is to work
towards the next stable version.  The current roadmap is as follows:

  1) Complete to upgrade the user interface using the new widgets.
     This is almost finished, although several tweaks on the Qt side
     would still improve things.  Optionally, we might want to implement
     Search/Replace in a more modern way, but I might not have time for that.

  2) Francois (and a little bit me) will be robustifying the LaTeX converters.

  3) Reorganizing the menus, I had some further minor ideas about improving
     the editor's interface for certain tags.  I plan to work a week or so on 
that.

  4) I want to add support for exceptions and recover the most harmless ones.
     Also, it would be nice to have a smart console for error messages and 
warnings.
     I definitely want to spent quite some time one this while debugging
     the most important bugs.

  5) Feature freeze, improvement of the documentation, updates of translations.

If you have some time, then it would be nice to robustify the Qt interface.
I will submit a list of remaining issues sometime soon on the bug tracker.
Also, if Max has some time, then I would like to enable the new Pdf renderer.

Best wishes, --Joris


On Sun, Oct 27, 2013 at 07:23:39PM +0100, Miguel de Benito Delgado wrote:
> Hello everybody,
> 
>   we have already discussed several times that a non-negligeable performace
> improvement is to be had by relying less on smart pointers and constref'ing
> arguments everywhere. The task is time consuming and disaster-prone, so I
> propose we join forces. I've set up a task in savannah (
> https://savannah.gnu.org/task/index.php?12916 )  where we may comment on
> the progress and send patches with changes as atomic as possible, i.e. such
> that they may be applied into the trunk after peer-review.
> 
>   See for instance the first attached patch, where I constref'ed a lot of
> usages of string in analyze.?pp, string.?pp and elsewhere.
> 
> Suggestions:
> 
> 1. We work with types, instead of files: first string, then tree, etc.
> 2. We don't leave source files "unfinished", i.e. with some functions
> converted others not. Because we don't want to work on all types at the
> same time, "unfinished" is to be understood wrt. to a given type.
> 3. We don't focus on this task, just maybe complete a few files from time
> to time, and check / update the task in savannah, etc.
> 4. I don't know where changes would have greatest impact on performance,
> but I guess targeting basic data manipulation routines for strings and
> trees (next in the list) makes sense. Any ideas?
> 5. We may start a new branch, but conflict-hell is just around the corner.
> It'd be good to integrate the patches into the trunk once they've been
> checked instead of waiting for the whole task to be finished.
> 
> I know this is not critical stuff, but it's still possible to do some
> progress on it from time to time.
> 
> Best,
> --
> Miguel de  Benito.

> _______________________________________________
> Texmacs-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/texmacs-dev