[texworks] The future of TeXworks + how you can help
esperanto at swing.be
Tue Mar 13 16:14:48 CET 2012
One idea I have for a long time is to have the poossibility
to link keyboard short cuts to each action in TW; but to do
this with an external list of short cuts and function's name.
This would allow the user to define his own short cuts.
Most of the users wouldn't modify the default list, however.
One can already do this, partly, with
actionSide_by_Side = Ctrl+-
But as Lukas Klausner did write, many thanks for this program.
Le 12/03/2012 10:09, Stefan Löffler a écrit :
> Hi all,
> after Paul's recent mails regarding the future (and funding), I thought
> it would be a good idea to make the development process and envisaged
> future for TeXworks more transparent. To that end, I've created a
> roadmap on the wiki (http://code.google.com/p/texworks/wiki/Roadmap)
> that documents the targets plan for the next couple of stable releases.
> It does not give an exhaustive list and is only a tentative one, but it
> should hopefully give an impression what we are planning to do, and when
> you can expect to see it.
> Another point that was raised was the low number of (C++) programmers
> currently involved in the project. Funded or not (this is still
> debated), I think that in order to attract new coders, we should offer
> some well-defined projects so prospective programmers get an idea what
> is in the queue and get some pointers where to start. I've put up such a
> list of ideas on the wiki, too
> (http://code.google.com/p/texworks/wiki/IdeasAndProjects). So if you
> have some knowledge of/experience with C++ and want to get involved (or
> know someone else who might be interested), that is a good place to
> start.  Please spread the word.
>  Another good place is the issue tracker, of course. Since we are in
> the middle of some rather large restructuring of the code base, however,
> working on the projects outlined in the wiki is probably the better
> alternative as they are designed to fit into the restructuring process
> (and will solve many outstanding issues on-the-fly).
More information about the texworks