From: Tim H. <tho...@te...> - 2013-01-11 11:06:08
|
Am 11.01.2013 08:29, schrieb Denis Bitouzé: > Le jeudi 10/01/13 à 19h50, > Tim Hoffmann <tho...@te...> a écrit : > >>>> Slightly o.t.: Some time ago I already considered the possibility >>>> of subgrouping the settings. (e.g. Editor, Highlighting, >>>> Commands, ...). >>> Do you mean subgrouping in the in the .ini (or txsprofile) file? >>> Could be nice but a UI would be better ;) >> Well, maybe sort of both. I think a UI is necessary if this feature >> should be used by people. One can still decide if we want to make the >> subgrouping explicitly in the ini or only in the program code. >> Reflecting the groups in the ini would be nice. However, this means >> an incompatible change of the format. Then, at least, we'd have to >> recover backward-compatibility by beeing able to convert the old >> format to the new format (additional work). > OK, then maybe not necessary to change the ini structure. Well, still not yet decided. Initially it's less work. But in the long run a more modular ini structure may be easier to maintain. >>>> This would allow the user importing only the editor settings of >>>> someone else without overwriting his build command settings. >>> Overwriting some of them should be allowed if the user prefers so. >> One could organize them in a tree structure so that groups subgroups >> and single items could be selected. >> >> Not sure if users would really use it and if this is worth all the >> effort. - I don't know any other software allowing for this. So it >> seems not to be requested much in general. > I know at least two persons who'd like it: a researcher working in > oriental languages who wants to help colleagues who don't know LaTeX, > providing them an IDE (TXS) with ad hoc configuration, and me who want > to help PhD students to be as efficient as possible with some thesis > class. > > In Emacs sphere for instance, lot of people put their configuration > file on Internet to help others to have a nice customization of their > editor. We can imagine same thing for TXS, maybe with a central place > to store and provide configuration files (and, as I already suggested > it, templates as well that may be easily installed in TXS from TXS). It all takes time. You might have noticed that the template system is on its way :) |