Re: question 4 of x - help to update the docs for 1.6.0
On 24/09/2008 00:25, Uwe Stöhr wrote: In the preferences there is under Look Feel the option Open documents in tabs. But when I uncheck it and restart LyX, the docs are still opened in tabs. What is this option supposed to be? The option doesn't work at restart. Otherwise, it works: it 'Opens documents in tab' if checked and in new window if not. Abdel.
Re: current session handling can break LyX completely
On 24/09/2008 01:44, Uwe Stöhr wrote: Our session handling is incorrect and can break LyX completely: http://bugzilla.lyx.org/show_bug.cgi?id=5274 (It took me a lot of time to find a workaround to get LyX usable again, so I think this should be fixed before rc3 is released.) Are you aware that LyX is perfectly usable without the menubar and the toolbar? That you can launch any dialog thanks to the mini buffer? I tell you that so that you don't waste so much time next time you are stuck. Abdel.
Re: question 1 of x - help to update the docs for 1.6.0
On 24/09/2008 14:42, Jean-Marc Lasgouttes wrote: Uwe Stöhr[EMAIL PROTECTED] writes: Jean-Marc Lasgouttes schrieb: I have a question of my own too: do you have plans to use InsetInfo in the docs? How can I insert an InsetInfo, there is no menu entry for this? Where should I use it? Everything is explained in src/insets/InsetInfo.h, and it ends with: There is currently no GUI, no menu entry for this inset. There is no menu entry but there is a minimal GUI for the advanced user, accessible from the context menu when right-clicking on an info inset. Abdel.
Re: about character styles
On 24/09/2008 20:08, Uwe Stöhr wrote: rgheck schrieb: Well, if you're going to leave InsetInfo until after 1.6, we can do this together. You can tell me what character styles you want, and I'll produce definitions of them that you can use. This wouldn't help. What we need is a way to define your own character styles. That means that the users can define its own character styles and change their definitions via a dialog (similar to branches). Currently the user has to fiddle around with a text editor and the layout files. He furthermore has to read the Customization manual carefully to understand how the layout files are modified. This is not user friendly and error prone, so I doubt that users will use character styles. There is a difference between _using_ character styles and _creating_ character style. Using already defined character style (ex: urls) is already possible and easy. Abdel.
Re: lyx and collaborative editing.
On 24/09/2008 01:39, Christian Ridderström wrote: On Tue, 23 Sep 2008, Andre Poenitz wrote: If LyX has support for the VCS tool that you use, these actions (checkout, commit, update) can all be done from within LyX. Isn't the problem _merging_ of changes, or, equivalently, resolving of conflicts? Indeed, but as I understood Uwe's simplest use case, only one person would actively be editing the document. In this case merging isn't necessary. I could have misunderstood him of course, and I also think that with five authors, you really do want to be able to do merging. However, if they work on different chapters, maybe the automatic merging will be good enough? Maybe yes. But you'll need a method to 'lock' paragraphs. As a side note, I was in the open source manifestation yesterday in Paris. This is a very corporate event, everybody there talks about their new colloborative methods based on some wysiwyg wiki engine. So yes, collaborative editing is the new religion in the corporate world :-) Abdel.
Re: changeset 26514
On 24/09/2008 20:53, Richard Heck wrote: Uwe Stöhr wrote: Maybe we should adopt a new rule: Any changes made to the docs by anyone but you (or your designated appointee) should be done with change tracking enabled. Then you can check them out and accept or reject the changes, and then check the clean version back in. This would indeed be very helpful. Let us propagate the rule then! That's a good idea. Abdel.
Re: [patch] Tabbing in listings
On 25/09/2008 00:53, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
-
-
+ { LFUN_LISTINGS_TAB_INSERT, listings-tab-insert,
SingleParUpdate, Edit },
maybe we can use LFUN_TAB_INSERT, so we can re-use it somewhere else when
needed?
What about LFUN_UNICODE_INSERT? (unicode-insert put here the symbol for
tab).
Abdel.
Re: Display of index in the Outline window--sorted alphabetically
On 24/09/2008 17:55, Uwe Stöhr wrote: Can you please make it possible to sort the index entries in Document Outline alphabetically? It would make all the difference in the world to a serious indexer. I fully agree with you. Without a sorting for index entries, labels, etc., the outliner is quite useless for larger documents. Sad to know that the feature is useless. I'll remove it... Abdel.
Re: Display of index in the Outline window--sorted alphabetically
On 25/09/2008 02:47, Uwe Stöhr wrote: this patch will sort anything in outliner automatically. sort won't be correct for nonascii characters. This is what I meant, please apply. Not as is of course. This needs to be optional, enabled via a new button or by clicking in the title bar of the outliner. Abdel.
Re: LyX layout editor - specification
rgheck wrote: I think a lot of our users just find layout creation and editing to be a black art. Which is likely due to lack of documentation... /Konrad
Re: LyX is Nominated for the Lutèce d'Or 2008
On 18/09/2008 21:34, Abdelrazak Younes wrote: Dear all, LyX enthusiasts, users and developers, I have the pleasure to announce you all that LyX is Nominated for the Lutèce d'Or 2008! I am going to the next OpenSource manifestation in Paris (details below). As they asked for candidature for innovative projects I had the idea to inscribe LyX and we are nominated :-) So, LyX was nominated in 'The best foreign project in Open Source Software carried out' category, together with OpenOffice and OpenSuze. OpenOffice won of course. But it is already very good that we were nominated in this very corporate and commercial events. Abdel.
Re: LyX is Nominated for the Lutèce d'Or 2008
On 19/09/2008 19:45, Andre Poenitz wrote: On Fri, Sep 19, 2008 at 12:46:57PM +0200, [EMAIL PROTECTED] wrote: Abdelrazak Younes[EMAIL PROTECTED] writes: I just got the answer: Only one, unfortunately! I'll drink a glass of wine for each of you... Red wine for me please. I guess you can put some beer into wine glasses, too Nope, only wine in there. Just for you I drank some wine with bubbles as a replacement. Abdel.
Re: question 1 of x - help to update the docs for 1.6.0 - forgot this
Uwe Stöhr [EMAIL PROTECTED] writes: Why is there no GUI? Because it is more intended for documenters than plain users. And because it was thought that the current choice is as fast as what a gui would give (unless maybe if we have a function browser). I mean the users will see this inset in the documentation files and ask how to use it and what it is for. So InstInfo should at least be described in the Extended or Customization manual. Could you do this please? I am a bit busy now, and actually I do not know more that what is explained in InsetInfo.h. Bo is the guy who knows the details. JMarc
Re: LyX layout editor - specification
Konrad Hofbauer wrote: rgheck wrote: I think a lot of our users just find layout creation and editing to be a black art. Which is likely due to lack of documentation... Revert. Customization manual! Sorry for the noise. /Konrad
Re: LyX is Nominated for the Lutèce d'Or 2008
On 19/09/2008 12:37, Jürgen Spitzmüller wrote: Abdelrazak Younes wrote: I just got the answer: Only one, unfortunately! I'll drink a glass of wine for each of you... Yes. (That'll make quite some glasses, though, so watch out for the buses afterwards). I made my duty nevertheless and drank as many glasses as required... Santé! pretty hard this morning... Abdel.
Re: question 1 of x - help to update the docs for 1.6.0 - forgot this
On 25/09/2008 09:39, Jean-Marc Lasgouttes wrote: Uwe Stöhr[EMAIL PROTECTED] writes: Why is there no GUI? Because it is more intended for documenters than plain users. And because it was thought that the current choice is as fast as what a gui would give (unless maybe if we have a function browser). As I said, there is a GUI and it is pretty useful... Abdel.
Re: [Cvslog] r26527 - in /lyx-devel/trunk/src: BufferView.cpp Cursor.c...
[EMAIL PROTECTED] writes: Author: poenitz Date: Wed Sep 24 23:27:41 2008 New Revision: 26527 URL: http://www.lyx.org/trac/changeset/26527 Log: streamlining setter syntax. using mutable references seems a bit outlandish compared to the rest of LyX - d-cursor_.selection() = false; + d-cursor_.setSelection(false); Are you aware that setSelection does more than setting directly selection()? In particular, it refuses to set the selection when the cursor and the anchor are at the same place. This is a situation that happens in some places, and there is a risk of breaking selection. JMarc
Re: Display of index in the Outline window--sorted alphabetically
Pavel Sanda [EMAIL PROTECTED] writes: Can you please make it possible to sort the index entries in Document Outline alphabetically? It would make all the difference in the world to a serious indexer. if you are able to compile lyx yourself this patch will sort anything in outliner automatically. sort won't be correct for nonascii characters. You mean that it sorts also the Table of contents? Gasp. JMarc
Re: changeset 26514
Abdelrazak Younes [EMAIL PROTECTED] writes: Let us propagate the rule then! That's a good idea. ... if we do not forget to cleanup afterwards. JMarc
Re: question 1 of x - help to update the docs for 1.6.0
rgheck [EMAIL PROTECTED] writes: Can't you put an InsetInfo into a character style of the appropriate type? We can do better: specify an InsetLayout for these things. Of course, life would be easier if InsetLayout was at InsetText level... JMarc
Re: Cursor::anchor()
Vincent van Ravesteijn - TNW [EMAIL PROTECTED] writes: How can I modify the anchor position of a selection ? Why do you need to do that, actually? JMarc
Re: LyX layout editor - specification
Pavel Sanda [EMAIL PROTECTED] schrieb: Richard Heck wrote: G Milde wrote: On the other side would be a wizard like layout-creator with drop-down and selection lists (like the citation insert dialogue) for GUI creation of layouts without exposure to the syntax. A wizard is pretty much what people have been wanting can you enumerate for what particular things you would use wizard? 1. Creation of a new *.layout, [optionally also *.inc, or *.module] file typically based on an existing one. 2. [optionally] Editing an existing *.layout, *.inc, or *.module file In both cases, the resulting file should be saved in LyXHome/layouts. Draft - (using the DocumentsSettings dialogue in LyX 1.6 as example): * Edit Layout window styled after Document Class tab: + First line: instead of a Document class, you choose a base layout (*.layout) or New from a drop down list. + Second line: choose matching latex class from a drop-down list. + (Options and preamble) + instead of the Modules selection widget, there are two: - *.inc files (what GUI name should these get?) · with *.inc files included in the base layout pre-selected · with tool-tips ([docstring], list of provided Styles) - Styles (with all styles in the layout file and the included files pre-selected). Additional buttons allow editing of Styles (opening a Style Edit window: [Edit] edit the selected style and store changes in the layout file under the same name. [New] ask for a new name [Copy] like new, but pre-select the selected style as base-style in the Style Edit window (see below). Style Edit window + First line: base style - drop down list of available styles. - default Standard, - other Styles map to a CopyStyle key in the written file. + List of keys and values, - pre-set values updated according to the chosen base style, - depending on the permitted values with either drop-down list, number-selector, or free-form text entry. Günter
Re: LyX is Nominated for the Lutèce d'Or 2008
Abdelrazak Younes [EMAIL PROTECTED] writes: I made my duty nevertheless and drank as many glasses as required... OK, but what about a price instead? JMarc
Re: LyX is Nominated for the Lutèce d'Or 2008
Abdelrazak Younes [EMAIL PROTECTED] writes: So, LyX was nominated in 'The best foreign project in Open Source Software carried out' category, together with OpenOffice and OpenSuze. OpenOffice won of course. But it is already very good that we were nominated in this very corporate and commercial events. I wonder how many other projects like ours filled out the forms. And did you get to drink a glass of OpenSuze? ;) JMarc
Re: LyX is Nominated for the Lutèce d'Or 2008
On 25/09/2008 10:19, Jean-Marc Lasgouttes wrote: Abdelrazak Younes[EMAIL PROTECTED] writes: So, LyX was nominated in 'The best foreign project in Open Source Software carried out' category, together with OpenOffice and OpenSuze. OpenOffice won of course. But it is already very good that we were nominated in this very corporate and commercial events. I wonder how many other projects like ours filled out the forms. I don't have the number but quite a few apparently. That's what the guy at my table told me. He is a journalist at 01-informatique and was a member of the jury. He told me he voted for us but we didn't really have a chance against OpenOffice. And did you get to drink a glass of OpenSuze? ;) Lapsus révélateur :-) Is it open suse? Abdel.
Re: LyX is Nominated for the Lutèce d'Or 2008
Abdelrazak Younes [EMAIL PROTECTED] writes: Is it open suse? Yes. Or rather openSUSE. But some times ago, the proper capitalization was something like SuSE... JMarc
Re: Multi-LFUN Binding
rgheck [EMAIL PROTECTED] schrieb:
This has now been committed.
Just a name change proposal: command-alternatives - command-try
Next issue is the bindings. There ought to
be other places we can use this, too, no?
1. a find-next binding that recalls the last search from the find dialogue
without re-openign it -- falling back to dialog-show findreplace.
2. I would like some alternative binding for mathed:
* all of \ { [ ] } ~ are hard-to-get (with AltGr+something) on my German
keyboard.
* OTOH, the ä, ö, ü, and ß keys are rarely (or not at all) used in math.
However, these keys self-insert, so they do not fail and the current
alternatives version does not work in this case :-(
Therefore, IMO there is also need for some context-specific bind syntax,
e.g. one of
* \bind key command-math mathfun; fun
* \bind key fun
\bind-math key mathfun
* \bind key fun
\bind key mathfun math
Re: menu structure
Konrad Hofbauer wrote: Edwin (and others), great thanks for starting to work on this! I have a number of suggestions for changes, strictly based on the HIG [1] (except those sentences starting with IMO). If something is left open by the HIG, I refer to what I assume are applications that well consider the HIG, namely Safari and OmniGroup software (=OG). Unfortunately the HIG do not cover tabbed applications, so I take Safari 3 and Firefox 3 as reference here. Instead of having different ui/inc-files circulating around, I think it makes more sense if you maintain the master version and include from my suggestion what you deem appropriate. OK ??? I go menu-by-menu (in random order), and only talk about the suggested changes (everything else OK). I say in advance that IMO the Document-Menu should disappear. File *** The HIG says (also related to an older discussion): Close should close the active tab (or window if it is the last tab). Add a Close File to close the active file (in all views/windows). [2] And combining this with what Safari (and Firefox) do with regards to tabs, I propose: New Window New Tab New File New From Template ... Open ... Open Recent --- Close Window Close Tab Close File Save Save As ... Save All Revert to Saved --- Import ... (more to this later) Export As ... (more to this later) [3] --- Version Control Compress File (but IMO this should really be IN the document settings) Statistics ... (this is like Properties, or Get Info) --- Print ... Document Settings ... [4] Concerning Import/Export: According to HIG this should rather be a normal Save As / Open-dialogue, with a drop-down-list to select the format to export/import. This is not just a menu change, but would allow the IMO nice feature of being able to specify a file-name / location for exports (see this as wish-list entry). Having something like Export As, where the filename can be specified would be nice, sure. However, export using the same base filename as the LyX file is a very common case, so that ought to be possible still, and with no more keypresses or waiting than today. Bringing up a save dialog with a default filename filled in probably achieves this, but be careful. Dialogs that populate themselves with a list of existing files tends to be rather slow to open when there are lots of files, or when the folder is on some other server. Now, that is necessary when opening, but definitely not when saving/exporting. (Also, many such dialogs are very slow because they use one call to the filesystem and one call to the window system per file existing in the folder. That approach is wrong because it is too slow. Read the entire file list first, which should be no slower than an ls command. Then fill the display quickly, perhaps it can be done with one operation now that everything is in memory. Save as from firefox is totally rotten for example, when there are 20 000 files already. And I don't need to see them at all, just SAVE THIS.) Something to think about if this change is implemented. Helge Hafting
Re: menu structure
Konrad Hofbauer wrote: Jean-Marc Lasgouttes wrote: Can you point to a program where _all_ document-level settings are in File menu? We shall not over-interpret the HIG. I do not have much to compare to by hand, only OO 2.3 and Word 2003. Word 2003 has the Page Setup in File, OO has Properties in File. Both of them don't have a Document menu. Both have (a Windows-HIG) Tools menu. What is the difference between file and document in the first place ??? A document may consist of several files. For example, the book where each chapter is a file of its own. Document settings matter only for the master document file, when you print/export the book. The chapter files may have their own settings, but they are used only if you print chapter files separately. Also, don't forget the users who have had LyX as their main word processor for a long time. It is the previous version of LyX that matters for us. Not what word does, because we don't use or have word. There are clearly many more word users in the world, but most of them are not going to switch even if the menus match as closely as possible. I am used to LyX, and for me, the File menu is where I find file-related stuff common to all apps. I.e. save/open/new/print/export/import. That's the place where I have to deal with folders and disks. The Document menu is much more application specific. Not all file-oriented apps deal with documents at all. Many do, but in very different ways. This is where I go for layout options like margins, page size and document-wide font setup. This is is where I go for other document-related stuff, like change tracking. Still - some change is ok with me, if it improves LyX. But not just change for change's sake, or in order to follow some principle to the letter. When following a rule strictly make things worse, it just means the rule have (unstated or undiscovered) exceptions. Maybe the outline toggle fits better on the view menu? Its use is very much like the toolbar toggles. Helge Hafting
Re: about character styles
Hi Uwe, Richard, Abdel, as a user (with some latex background and several years as grateful LyX user) I would like to contribute my 2cents. For me it would be a helpful start to find in the documentation a short explanation of the existing character styles. That certainly would help to construct new ones (using vim to edit a layout file ;-) Thanks for all your engagement Hellmut Uwe Stöhr schrieb: rgheck schrieb: Well, if you're going to leave InsetInfo until after 1.6, we can do this together. You can tell me what character styles you want, and I'll produce definitions of them that you can use. This wouldn't help. What we need is a way to define your own character styles. That means that the users can define its own character styles and change their definitions via a dialog (similar to branches). Currently the user has to fiddle around with a text editor and the layout files. He furthermore has to read the Customization manual carefully to understand how the layout files are modified. This is not user friendly and error prone, so I doubt that users will use character styles. Concerning the docs, when I use character styles, I have to describe how they can be created and edited, but then the character styles need an UI as we currently discuss in the layout editor thread. So I'll have to postpone this to LyX 1.7. regards Uwe -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: LyX layout editor - specification
Richard Heck wrote: Pavel Sanda wrote: Richard Heck wrote: G Milde wrote: On the other side would be a wizard like layout-creator with drop-down and selection lists (like the citation insert dialogue) for GUI creation of layouts without exposure to the syntax. (However, I would not call this an editor -- hence my alternative suggestion.) A wizard is pretty much what people have been wanting, and is really what Pavel was asking about. But layout syntax highlighting and the like would also be welcome. can you enumerate for what particular things you would use wizard? black art. That's certainly the sense you get on the user list. So I think some kind of simple wizard---that is, more or less what you're calling a database sheet, if I understand you correctly---would already go a long way towards helping people create simple layouts. no my question was different. i hoped fort list of templates for: - character style - ... just trying to collect as many ideas as possible. pavel
Re: lyx and collaborative editing.
Uwe Brauer wrote: Christian Ridderström wrote: On Mon, 22 Sep 2008, Uwe Brauer wrote: This solution exists. See here for instance http://www.pmwiki.org/wiki/Cookbook/PublishPDF Having read this again, it seems to be that you cannot directly write Latex or Lyx input into the wiki which is then converted. You have to start with some wiki dialect, is this correct? Correct. It converts wiki (via XML, then LaTeX) to PDF. Please note that allowing plain, arbitrary LaTeX to be parsed on an open wiki is a security risk. why is this so, what a pity that would be ideal for collaboration. Because running latex on unrestricted input in practice lets you do anything you can do with a program. Want to plant a virus program? Embed the virus in latex code as a string of bytes, then add some trivial latex code to (1) write the virus to a disk file, and (2) execute that file somehow. Or maybe executing it isn't even necessary if it gets published on the wiki where unsuspecting people will stumble across it. There are ways around this, such as: * Verify the latex code, but that is almost impossible to do. * Use a password protected system where only trusted users have access. They will not abuse latex per definition - they are trusted. Fine for collaboration within an organisation, not so fine for something as open as a public wiki. * Set up the latex parsing very carefully, perhaps using a chroot where only the necessary latex files are available, and all read-only. Run it under a special userID that isn't used for anything else. Take care to set up quotas and ulimit. Set up a timer that kill the latex run if it takes too long. The setup is now safe - even the most diabloical programmer cannot abuse latex worse than wasting some disk space and cpu time within the set limits. And the disk space is supposedly freed up when latex is finished. Well, they can still cause network traffic, such as running DOS/cracking attacks against other hosts within the time limit. Maybe there is a way of removing network access too. :-/ Helge Hafting
Re: Display of index in the Outline window--sorted alphabetically
Uwe Stöhr wrote: this patch will sort anything in outliner automatically. sort won't be correct for nonascii characters. This is what I meant, please apply. this patch was never meant to be applied to trunk, just a help for the ones really starving for it ;) to be enough for my taste it would need: - proper locale support. i don't know any one-liner which could be done. QStandardItemModel knows nothing about it; QSortFilterProxyModel would be needed and i don't (want;) understand the logic of all the TocModel* classes. unless Abdel has some idea how this could be solved without to much rework i'm not going to touch this more. - there is no ui for sorting (check box either in preferences or in the pane) - it is not context sensitive, it will sort any kind of list, while only for some of them is it useful (or am i wrong here?) That it doesn't sort non-ASCII characters in the right order is no problem as you are only one or two entries away in the worst case you don't know how my language looks like :) pavel
Re: Display of index in the Outline window--sorted alphabetically
Jean-Marc Lasgouttes wrote: Pavel Sanda [EMAIL PROTECTED] writes: Can you please make it possible to sort the index entries in Document Outline alphabetically? It would make all the difference in the world to a serious indexer. if you are able to compile lyx yourself this patch will sort anything in outliner automatically. sort won't be correct for nonascii characters. You mean that it sorts also the Table of contents? Gasp. i thought the same but its not so big problem - it doesnt change the structure and we put the numbers before items. anyway i didn't mean this patch to be solution. pavel
Re: LyX layout editor - specification
Pavel Sanda wrote: call for help, it would be possible for me to lead lyx layout editor as a small school project provided that it is work complicated enough. If the end goal is a working, complete and useful layout editor then I can't see how that wouldn't be complicated enough? i know there are people mastering layouts better than me, so it would help if you can help to write down some specification of features it should have. by 'complicated enough' i mean it should know more than just provide database sheet for the attributes described in our customization manual, since that is trivial to write and won't need more people/months to code... so its a question whether we can produce such a feature-list :) Not just a database sheet - a working C++ app that can read all of the existing layout files that comes with LyX, and allow any kind of supported modification that we today do with text editors. Helge, iirc you have advertised small java beast some time ago - do you have some specification? i'm also CC-ing Guenter and Steve as our layout power users from the second maillist. The spec was small - basically to be able to open a layout file in a GUI, and modify it and save it. It should support the stuff found in existing layout files at the time. Due to limited time, my students didn't have to implement _everything_. And they used java, so nobody picked it up later. The program they made could open and modify layout files, but not those that comes with LyX. First - it doesn't support every construct. Secondly, it is not robust at all, so an extra blank line and so on will trip it up and crash. So, for a more serious spec: * support all layout files in todays LyX and earlier. Because users already have homegrown .layouts for earlier versions of LyX. * The user should be able to: - create complete new document classes - make and maintain layout modules - modify existing classes and make changes like a new paragraph type or charstyle * The user should not need to know about the .layout file format at all. All the options for how LyX displays a paragraph type should be contained in the GUI. * The user may need to know latex in order to tell this layout editor what should happen when this new kind of paragraph is used. Still, it'd be nice if this app knows quite a few of the easier tricks in latex, such as colors, font sizes and font attributes. * Write the thing in C++, so that it can be integrated in LyX later. * Extending this thing should be easy, for surely the next version of LyX will have more layout options. Design with this in mind. * The workflow should encourage smart usage, not stupid. Example: I need a charstyle with green text for marking stuff in my next online book. The smart approach is a layout module implementing this. The ecessively stupid way is to copy the entire book.layout and add this functionality to the otherwise identical copy. But sometimes, a new class is in place because many changes is needed compared to existing document classes. It is still smart to use copystyle to refer to existing unchanged constructs, instead of copying everything and then modifying some items. * Be robust. - The program should not get in trouble if the file has some errors because the user messed it up with a text editor. - Skipping over some errors (but logging them) is nice. - Missing end_something can be added when something new unexpectedly begins. - Crashing should not happen, and a file should be really bad to get rejected as apparently not a .layout file at all. * If it isn't too complex already - document the software well too. :-) Helge Hafting
Re: [patch] Tabbing in listings
Vincent van Ravesteijn - TNW wrote: Shift-Tab aka. BackTab; it should be used in a Listing inset, when the cursor is right after a space or Tab or when there is a selection. so the only difference to the current backspace is that it also knows to eat 4 spaces in one step, right? i'm not sure this is not overdesigned, just to synchronize shift+tab key press maybe the same as 4x backspace. pavel
Re: [patch] Tabbing in listings
Abdelrazak Younes wrote:
+ { LFUN_LISTINGS_TAB_INSERT, listings-tab-insert,
SingleParUpdate,
Edit },
maybe we can use LFUN_TAB_INSERT, so we can re-use it somewhere else when
needed?
What about LFUN_UNICODE_INSERT? (unicode-insert put here the symbol for
tab).
we need this lfun to be disabled in normal paragraphs, so we can bind it to tab.
pavel
Re: Display of index in the Outline window--sorted alphabetically
Pavel Sanda [EMAIL PROTECTED] writes: i thought the same but its not so big problem - it doesnt change the structure and we put the numbers before items. anyway i didn't mean this patch to be solution. And unnumbered sections? JMarc
Re: LyX layout editor - specification
Helge Hafting wrote: So, for a more serious spec: thanks, i was waiting for such kind of mail ;) * If it isn't too complex already - document the software well too. :-) this is mandatory anyway. pavel
Re: Display of index in the Outline window--sorted alphabetically
Jean-Marc Lasgouttes wrote: Pavel Sanda [EMAIL PROTECTED] writes: i thought the same but its not so big problem - it doesnt change the structure and we put the numbers before items. anyway i didn't mean this patch to be solution. And unnumbered sections? i expected this needle :) thats why i wrote the last sentence. pavel
RE: [patch] Tabbing in listings
Shift-Tab aka. BackTab; it should be used in a Listing inset, when the cursor is right after a space or Tab or when there is a selection. so the only difference to the current backspace is that it also knows to eat 4 spaces in one step, right? i'm not sure this is not overdesigned, just to synchronize shift+tab key press maybe the same as 4x backspace. pavel No, it also works on a selection, then it eats a tab or spaces from the beginning of each line spanned by the selection. This is extremely useful if you want to indent/unindent multiple lines in one action. Otherwise you'd have to do backspace, arrow-down, backspace, arrow-down etc. Vincent
RE: Cursor::anchor()
How can I modify the anchor position of a selection ? Why do you need to do that, actually? Jmarc Well, if you select multiple lines and you hit tab then a tab will be inserted at the beginning of each line. As a consequence, the selection needs to be updated to shift one pos to the right.. Vincent
Re: Multi-LFUN Binding
G Milde wrote:
Next issue is the bindings. There ought to
be other places we can use this, too, no?
1. a find-next binding that recalls the last search from the find dialogue
without re-openign it -- falling back to dialog-show findreplace.
2. I would like some alternative binding for mathed:
* all of \ { [ ] } ~ are hard-to-get (with AltGr+something) on my German
keyboard.
* OTOH, the ä, ö, ü, and ß keys are rarely (or not at all) used in math.
However, these keys self-insert, so they do not fail and the current
alternatives version does not work in this case :-(
the same holds for 1. case. but we may put this fallback directly to code.
Therefore, IMO there is also need for some context-specific bind syntax,
e.g. one of
not for 1.6 though.
pavel
Re: [patch] Tabbing in listings
Vincent van Ravesteijn - TNW wrote: No, it also works on a selection, then it eats a tab or spaces from the beginning of each line spanned by the selection. This is extremely useful if you want to indent/unindent multiple lines in one action. doxy, doxy, doxy ! :) pavel
Re: [patch] Tabbing in listings
Vincent van Ravesteijn wrote: Et voila, .. (oh no, no more french on the list...) i just tried this patch and seems to work correctly. if there are no other comments, i'll put it in. lfuns will be sorted later. pavel
Re: [patch] Tabbing in listings
Vincent van Ravesteijn wrote: + LASSERT(pit paragraphs().size(), /**/); + LASSERT( pit paragraphs().size(), /**/ ); + LASSERT(cur.pit() = 0 cur.pit() paragraphs().size(), /**/); btw gcc gives warnings about those lines (comparison between signed and unsigned integer expressions). pavel
Re: Display of index in the Outline window--sorted alphabetically
On 25/09/2008 12:05, Pavel Sanda wrote: Uwe Stöhr wrote: this patch will sort anything in outliner automatically. sort won't be correct for nonascii characters. This is what I meant, please apply. this patch was never meant to be applied to trunk, just a help for the ones really starving for it ;) to be enough for my taste it would need: - proper locale support. i don't know any one-liner which could be done. QStandardItemModel knows nothing about it; QSortFilterProxyModel would be needed and i don't (want;) understand the logic of all the TocModel* classes. unless Abdel has some idea how this could be solved without to much rework i'm not going to touch this more. I more or less know how to do this but there's other more urgent thing to do. The locale aware technique is used in a number of items already (languages, layouts) so one just have to do the same. - there is no ui for sorting (check box either in preferences or in the pane) I'd say a toggle button directly in the pane. - it is not context sensitive, it will sort any kind of list, while only for some of them is it useful (or am i wrong here?) Right, toc sorting is not very useful... Abdel.
Re: [patch] Tabbing in listings
On 25/09/2008 13:37, Pavel Sanda wrote: Vincent van Ravesteijn wrote: + LASSERT(pit paragraphs().size(), /**/); + LASSERT( pit paragraphs().size(), /**/ ); + LASSERT(cur.pit()= 0 cur.pit() paragraphs().size(), /**/); btw gcc gives warnings about those lines (comparison between signed and unsigned integer expressions). Make that a pit int(paragraphs().size()). But this kind of assertion is not needed, this is already detected in debug mode by the stl. Abdel.
Re: Multi-LFUN Binding
Pavel Sanda wrote:
G Milde wrote:
Next issue is the bindings. There ought to
be other places we can use this, too, no?
1. a find-next binding that recalls the last search from the find dialogue
without re-openign it -- falling back to dialog-show findreplace.
if you mean a fallback to search dialog when no string was entered before
i can put it in.
pavel
diff --git a/src/BufferView.cpp b/src/BufferView.cpp
index 9daa2aa..1be8369 100644
--- a/src/BufferView.cpp
+++ b/src/BufferView.cpp
@@ -1189,6 +1189,10 @@ bool BufferView::dispatch(FuncRequest const cmd)
FuncRequest req = cmd;
if (cmd.argument().empty()
!d-search_request_cache_.argument().empty())
req = d-search_request_cache_;
+ if (req.argument().empty()) {
+ theLyXFunc().dispatch(FuncRequest(LFUN_DIALOG_SHOW,
findreplace));
+ break;
+ }
if (find(this, req))
showCursor();
else
Re: [patch] Tabbing in listings
Abdelrazak Younes [EMAIL PROTECTED] writes: Make that a pit int(paragraphs().size()). But this kind of assertion is not needed, this is already detected in debug mode by the stl. But why is pit an int? JMarc
Re: Display of index in the Outline window--sorted alphabetically
Abdelrazak Younes schrieb: I fully agree with you. Without a sorting for index entries, labels, etc., the outliner is quite useless for larger documents. Sad to know that the feature is useless. I'll remove it... I like the new outliner handling very much! It boosts the work speed a lot. But the label listing in outliner is kind of unuseful when you cannot sort them, you will see what I mean hen you use it e.g. for the UserGuide. regards Uwe
Re: Cursor::anchor()
Vincent van Ravesteijn - TNW [EMAIL PROTECTED] writes: Well, if you select multiple lines and you hit tab then a tab will be inserted at the beginning of each line. As a consequence, the selection needs to be updated to shift one pos to the right.. Just redo the selection with the right values... JMarc
Re: Display of index in the Outline window--sorted alphabetically
Abdelrazak Younes schrieb: This is what I meant, please apply. Not as is of course. This needs to be optional, enabled via a new button or by clicking in the title bar of the outliner. OK. Nevertheless I used the sorting extensively last night to rework the documentation files. It is a big improvement, sorting and of course the possibility to look whether a label is referenced or not. So thanks to all who contributed to this feature. regards Uwe
Re: [patch] Tabbing in listings
On 25/09/2008 14:32, Jean-Marc Lasgouttes wrote: Abdelrazak Younes[EMAIL PROTECTED] writes: Make that a pit int(paragraphs().size()). But this kind of assertion is not needed, this is already detected in debug mode by the stl. But why is pit an int? That's historical: pit_type == pos_type == int Abdel.
Re: Display of index in the Outline window--sorted alphabetically
On 25/09/2008 14:32, Uwe Stöhr wrote: Abdelrazak Younes schrieb: I fully agree with you. Without a sorting for index entries, labels, etc., the outliner is quite useless for larger documents. Sad to know that the feature is useless. I'll remove it... I like the new outliner handling very much! It boosts the work speed a lot. But the label listing in outliner is kind of unuseful when you cannot sort them, you will see what I mean hen you use it e.g. for the UserGuide. I know, that was a joke, I am not going to kill my baby :-) Abdel.
Re: Display of index in the Outline window--sorted alphabetically
On 25/09/2008 14:32, Uwe Stöhr wrote: Abdelrazak Younes schrieb: I fully agree with you. Without a sorting for index entries, labels, etc., the outliner is quite useless for larger documents. Sad to know that the feature is useless. I'll remove it... I like the new outliner handling very much! It boosts the work speed a lot. But the label listing in outliner is kind of unuseful when you cannot sort them, you will see what I mean hen you use it e.g. for the UserGuide. I'll add a button for that. Abdel.
Re: [patch] Tabbing in listings
Abdelrazak Younes [EMAIL PROTECTED] writes: That's historical: pit_type == pos_type == int From what I remember, there was a reason for pos (we use -1 to get labelfont, or something), but not for pit, is it? JMarc
Re: [patch] Tabbing in listings
On 25/09/2008 15:04, Jean-Marc Lasgouttes wrote: Abdelrazak Younes[EMAIL PROTECTED] writes: That's historical: pit_type == pos_type == int From what I remember, there was a reason for pos (we use -1 to get labelfont, or something), but not for pit, is it? AFAIR, the only reason that was given to me when I wanted to change pit_type to size_t is that we are not sure of out of bound issues that may appear in loops. I am quite confident nowadays that there will be no such issue. So fine with me if you want to change it. Abdel.
[PATCH] Re: question 1 of x - help to update the docs for 1.6.0
rgheck [EMAIL PROTECTED] writes:
Well, if you're going to leave InsetInfo until after 1.6, we can do
this together. You can tell me what character styles you want, and
I'll produce definitions of them that you can use. I've already done
this for Customization, as you'll see if you look under EditText
Styles.
What about the following instead:
1/ make InsetInfo depend on InsetCollapsable (this is only because I
need this to have an insetlayout, in principle InsetText is OK).
2/ provide styles for the different types of insetinfo
3/ waste a lot of time finding all the small ingredients that makes it
work :)
I think this works well enough to go in trunk.
JMarc
svndiff src/insets/InsetInfo.cpp src/insets/InsetInfo.h lib/layouts/stdinsets.inc
Index: src/insets/InsetInfo.cpp
===
--- src/insets/InsetInfo.cpp (revision 26538)
+++ src/insets/InsetInfo.cpp (working copy)
@@ -47,11 +47,10 @@ namespace lyx {
InsetInfo::InsetInfo(Buffer const buf, string const name)
- : InsetText(buf), type_(UNKNOWN_INFO), name_(),
+ : InsetCollapsable(buf, Collapsed), type_(UNKNOWN_INFO), name_(),
mouse_hover_(false)
{
setAutoBreakRows(true);
- setDrawFrame(true);
setInfo(name);
}
@@ -63,15 +62,15 @@ Inset * InsetInfo::editXY(Cursor cur,
}
-void InsetInfo::draw(PainterInfo pi, int x, int y) const
+string InsetInfo::infoType() const
{
- InsetText::draw(pi, x, y);
+ return nameTranslator().find(type_);
}
-string InsetInfo::infoType() const
+docstring InsetInfo::name() const
{
- return nameTranslator().find(type_);
+ return from_ascii(Info: + infoType());
}
@@ -136,6 +135,7 @@ void InsetInfo::read(Lexer lex)
_(Missing \\end_inset at this point.),
from_utf8(token));
}
+ setLayout(buffer().params());
updateInfo();
}
@@ -240,20 +240,21 @@ void InsetInfo::setInfo(string const n
string type;
name_ = trim(split(name, type, ' '));
type_ = nameTranslator().find(type);
+ setLayout(buffer().params());
updateInfo();
}
void InsetInfo::error(string const err)
{
- InsetText::setText(bformat(_(err), from_utf8(name_)), buffer().params().getFont(),
- false);
+ InsetText::setText(bformat(_(err), from_utf8(name_)),
+ Font(inherit_font), false);
}
void InsetInfo::setText(docstring const str)
{
- InsetText::setText(str, buffer().params().getFont(), false);
+ InsetText::setText(str, Font(inherit_font), false);
}
@@ -281,9 +282,11 @@ void InsetInfo::updateInfo()
break;
}
if (type_ == SHORTCUT_INFO)
- setText(bindings.rbegin()-print(KeySequence::Portable));
+ InsetText::setText(bindings.rbegin()-print(KeySequence::Portable),
+Font(getLayout().font()), false);
else
- setText(theTopLevelKeymap().printBindings(func));
+ InsetText::setText(theTopLevelKeymap().printBindings(func),
+Font(getLayout().font()), false);
break;
}
case LYXRC_INFO: {
@@ -329,7 +332,7 @@ void InsetInfo::updateInfo()
info.insertInset(0, new InsetSpecialChar(InsetSpecialChar::MENU_SEPARATOR),
Change(Change::UNCHANGED));
for (i = 0; i != names.back().length(); ++i)
-info.insertChar(i, names.back()[i], bp.getFont(), false);
+info.insertChar(i, names.back()[i], Font(getLayout().font()), false);
names.pop_back();
}
break;
@@ -379,4 +382,5 @@ docstring InsetInfo::contextMenu(BufferV
return from_ascii(context-info);
}
+
} // namespace lyx
Index: src/insets/InsetInfo.h
===
--- src/insets/InsetInfo.h (revision 26538)
+++ src/insets/InsetInfo.h (working copy)
@@ -12,8 +12,7 @@
#ifndef INSET_INFO_H
#define INSET_INFO_H
-#include InsetText.h
-#include RenderButton.h
+#include InsetCollapsable.h
#include Cursor.h
#include support/gettext.h
@@ -78,7 +77,7 @@ namespace lyx {
/** Used to insert index labels
*/
-class InsetInfo : public InsetText {
+class InsetInfo : public InsetCollapsable {
public:
enum info_type {
UNKNOWN_INFO, // Invalid type
@@ -95,12 +94,14 @@ public:
///
InsetInfo(Buffer const buf, std::string const info = std::string());
///
+ InsetCode lyxCode() const { return INFO_CODE; }
+ ///
+ docstring name() const;
+ ///
Inset * editXY(Cursor cur, int x, int y);
///
EDITABLE editable() const { return NOT_EDITABLE; }
///
- void draw(PainterInfo pi, int x, int y) const;
- ///
void read(Lexer lex);
///
void write(std::ostream os) const;
@@ -117,8 +118,6 @@ public:
///
void doDispatch(Cursor cur, FuncRequest cmd);
///
- InsetCode lyxCode() const { return INFO_CODE; }
- ///
void setInfo(std::string const info);
/// update info_ and text
void updateInfo();
@@ -128,6 +127,8 @@ public:
docstring toolTip(BufferView const bv, int x, int y) const;
///
docstring contextMenu(BufferView const , int, int) const;
+ /// should paragraph indendation be ommitted in any case?
+ bool neverIndent() const { return true; }
private:
///
Re: [patch] Tabbing in listings
Abdelrazak Younes [EMAIL PROTECTED] writes:
AFAIR, the only reason that was given to me when I wanted to change
pit_type to size_t is that we are not sure of out of bound issues that
may appear in loops. I am quite confident nowadays that there will be
no such issue. So fine with me if you want to change it.
Ahh, yes, it was about loops like
while(pit 0) { ... ; --pit)
that could just wrap around at 0, right?
JMarc
Re: [PATCH][RFC] selection of items in ErrorList
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: After looking at what the converter selection code in prefs does, I came up with the following simple patch, which hooks on the currentRowChanged signal instead of itemSelectionChanged. It works perfectly for me (qt 4.2.3). However, before committing, I'd like to know: what is the difference between these two signals? There are other places relying on itemSelectionChanged, shall I fix them? Ping! JMarc
Re: unicode in math
On Wed, 24 Sep 2008 09:43:34 + (UTC) G Milde [EMAIL PROTECTED] wrote: Enrico Forestieri [EMAIL PROTECTED] schrieb: Please test. Unfortunately, I did not have the time to compile a patched LyX. But maybe, the attached test file can be some help? Thanks Günter latin-1-supplement.lyx Description: application/lyx
Re: [patch] Tabbing in listings
On 25/09/2008 15:16, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes[EMAIL PROTECTED] writes:
AFAIR, the only reason that was given to me when I wanted to change
pit_type to size_t is that we are not sure of out of bound issues that
may appear in loops. I am quite confident nowadays that there will be
no such issue. So fine with me if you want to change it.
Ahh, yes, it was about loops like
while(pit0) { ... ; --pit)
that could just wrap around at 0, right?
Right.
Abdel.
Re: [PATCH] Re: question 1 of x - help to update the docs for 1.6.0
On 25/09/2008 15:14, Jean-Marc Lasgouttes wrote: rgheck[EMAIL PROTECTED] writes: Well, if you're going to leave InsetInfo until after 1.6, we can do this together. You can tell me what character styles you want, and I'll produce definitions of them that you can use. I've already done this for Customization, as you'll see if you look under EditText Styles. What about the following instead: 1/ make InsetInfo depend on InsetCollapsable (this is only because I need this to have an insetlayout, in principle InsetText is OK). Why not transferring InsetLayout to InsetText as you initially suggested? Abdel. 2/ provide styles for the different types of insetinfo 3/ waste a lot of time finding all the small ingredients that makes it work :) I think this works well enough to go in trunk.
Re: Undo problems
Pavel Sanda [EMAIL PROTECTED] writes: don't remember. i guess i just mimic the preexistant code - there was dispatch(FuncRequest(getLfun(), lfun)); already called and i only added dispatch(FuncRequest(LFUN_GRAPHICS_GROUPS_UNIFY...) after it. I moved the code around, and it does not use LFUN_GRAPHICS_GROUPS_UNIFY anymore. Shall I remove the lfun? JMarc
RE: Display of index in the Outline window--sorted alphabetically
also: could you reverse the sort order in the combobox in the toc panel? the toc is used most often so it would be nice to have it on top...
Re: [Cvslog] r26539 - /lyx-devel/trunk/src/frontends/qt4/GuiView.cpp
Pavel Sanda [EMAIL PROTECTED] writes:
btw what happen if nesting of undo group is not correct,
like eg {{} and somebody calls undo.
I tried hard to enforce it, but it is indeed a bug that might happen,
and I cannot really fight against it (for example early returns without
closing the group).
also i wondered when the groups are nested
in eg { {} {} } the next undo will undo the whole thing?
Yes. This means you can add a group whenever you are not sure. Extra
groups do not cost anything.
JMarc
Re: [PATCH] Re: question 1 of x - help to update the docs for 1.6.0
Abdelrazak Younes [EMAIL PROTECTED] writes: 1/ make InsetInfo depend on InsetCollapsable (this is only because I need this to have an insetlayout, in principle InsetText is OK). Why not transferring InsetLayout to InsetText as you initially suggested? Because it requires a bit more work, which is not really for 1.6. Moreover, I use the 'corners' type of decoration, which is only implemented by InsetCollapsable. JMarc
Re: [patch] Solving selection painting bugs
Vincent van Ravesteijn - TNW [EMAIL PROTECTED] writes: Thus, if the selection is outside the current Inset, we don't touch pi_.selected_. OK. JMarc
Re: lyx and collaborative editing.
Uwe Brauer a écrit : Christian Ridderström wrote: On Mon, 22 Sep 2008, Uwe Brauer wrote: This solution exists. See here for instance http://www.pmwiki.org/wiki/Cookbook/PublishPDF Having read this again, it seems to be that you cannot directly write Latex or Lyx input into the wiki which is then converted. You have to start with some wiki dialect, is this correct? Correct. It converts wiki (via XML, then LaTeX) to PDF. Please note that allowing plain, arbitrary LaTeX to be parsed on an open wiki is a security risk. why is this so, what a pity that would be ideal for collaboration. Uwe Planet Math (http://planetmath.org/) is a collaborative encyclopedia based on LaTeX, with some restrictions to maintain a coherent look and feel (like the style of a scientific journal). The server part can be installed on any machine, the software required is downloadable from their web site. Maybe this could help solving the problem ? Best wishes
Re: [patch] Tabbing in listings
Pavel Sanda wrote: Et voila, .. (oh no, no more french on the list...) i just tried this patch and seems to work correctly. if there are no other comments, i'll put it in. lfuns will be sorted later. I wonder if something needs to be done on reversion to 1.5.x. IOW, is this a file format change? Jürgen
Re: Display of index in the Outline window--sorted alphabetically
On 25/09/2008 15:34, leuven edwin wrote: also: could you reverse the sort order in the combobox in the toc panel? the toc is used most often so it would be nice to have it on top... Why not simply rename that to Document Structure? Or maybe just Sections? Abdel.
Re: lyx and collaborative editing.
Michel Lavaud wrote: Uwe Brauer a écrit : Christian Ridderström wrote: On Mon, 22 Sep 2008, Uwe Brauer wrote: This solution exists. See here for instance http://www.pmwiki.org/wiki/Cookbook/PublishPDF Having read this again, it seems to be that you cannot directly write Latex or Lyx input into the wiki which is then converted. You have to start with some wiki dialect, is this correct? Correct. It converts wiki (via XML, then LaTeX) to PDF. Please note that allowing plain, arbitrary LaTeX to be parsed on an open wiki is a security risk. why is this so, what a pity that would be ideal for collaboration. Uwe Planet Math (http://planetmath.org/) is a collaborative encyclopedia based on LaTeX, with some restrictions to maintain a coherent look and feel (like the style of a scientific journal). The server part can be installed on any machine, the software required is downloadable from their web site. Maybe this could help solving the problem ? Best wishes Hello This looks extremely interesting. I will try that out. Thanks very much for this pointer (I tried so many google searches, this did not show up) regards Uwe Brauer
Re: about character styles
Abdelrazak Younes schrieb: There is a difference between _using_ character styles and _creating_ character style. Using already defined character style (ex: urls) is already possible and easy. I'm aware of that, but using character styles without being able to define, and more important, to change them, is no improvement. What is the advantage of character styles? That you have a customized defined style for certain document parts that you can change easily. So for \url, \footnote, \noun, \emph, etc. I can already do this by inserting a preamble or ERT command, but for character styles defined in a layout file, I can't do this easily, I have to learn the layout file syntax, use a text editor, and restart LyX after a change. So I fear that users won't use character styles when they are not able to modify and define them easily. Btw. the Customization manual uses existing character styles, but the black corners around a character style inset makes the document hardly readable within LyX. Perhaps gray or a decent color instead of black makes it better.
Re: Undo problems
Jean-Marc Lasgouttes wrote: Pavel Sanda [EMAIL PROTECTED] writes: don't remember. i guess i just mimic the preexistant code - there was dispatch(FuncRequest(getLfun(), lfun)); already called and i only added dispatch(FuncRequest(LFUN_GRAPHICS_GROUPS_UNIFY...) after it. I moved the code around, and it does not use LFUN_GRAPHICS_GROUPS_UNIFY anymore. Shall I remove the lfun? sure pavel
Re: current session handling can break LyX completely
Abdelrazak Younes schrieb: Are you aware that LyX is perfectly usable without the menubar and the toolbar? That you can launch any dialog thanks to the mini buffer? Indeed, you are so right! So let's remove them then. I mean they only block space that can be used better for the main window. I'm wondering why other programs still use menu and toolbars - poor retards. regards Uwe
Re: current session handling can break LyX completely
Uwe Stöhr wrote: Abdelrazak Younes schrieb: Are you aware that LyX is perfectly usable without the menubar and the toolbar? That you can launch any dialog thanks to the mini buffer? Indeed, you are so right! So let's remove them then. I mean they only block space that can be used better for the main window. I'm wondering why other programs still use menu and toolbars - poor retards. i agree, the fullscreen is enough. should i prepare the patch? pavel
RE: Display of index in the Outline window--sorted alphabetically
Why not simply rename that to Document Structure? that works in english, but not necessarily in all languages... ? edwin
Re: about character styles
Uwe Stöhr wrote: Abdelrazak Younes schrieb: There is a difference between _using_ character styles and _creating_ character style. Using already defined character style (ex: urls) is already possible and easy. I'm aware of that, but using character styles without being able to define, and more important, to change them, is no improvement. What is the advantage of character styles? That you have a customized defined style for certain document parts that you can change easily. So for \url, \footnote, \noun, \emph, etc. I can already do this by inserting a preamble or ERT command, but for character styles defined in a layout file, I can't do this easily, I have to learn the layout file syntax, use a text editor, and restart LyX after a change. Actually, no, you don't have to restart LyX---changes to modules are seen whenever the modules are reloaded---though it is recommended that you not make a bunch of changes while you're actually editing a file. Safety first. So I fear that users won't use character styles when they are not able to modify and define them easily. But honestly, it isn't that difficult! I would have thought you could look at the logicalmkup module and figure out pretty quickly how to do a new one. Yes, you might need to look at the documentation to figure out exactly what your font options are, but we have some very good people who work on that. ;-) And yes, you have to know the equivalent LaTeX. But it'll be a very long time before we can avoid that. Richard Btw. the Customization manual uses existing character styles, but the black corners around a character style inset makes the document hardly readable within LyX. Perhaps gray or a decent color instead of black makes it better.
Re: changeset 26514
Jean-Marc Lasgouttes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: Let us propagate the rule then! That's a good idea. ... if we do not forget to cleanup afterwards. I think the plan was that Uwe would basically be in charge of cleanup. And maybe he wouldn't feel the rule was always needed, but only when heavy translation work was ongoing. But that's his call. rh
Re: [PATCH][RFC] selection of items in ErrorList
Jean-Marc Lasgouttes wrote: Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: After looking at what the converter selection code in prefs does, I came up with the following simple patch, which hooks on the currentRowChanged signal instead of itemSelectionChanged. It works perfectly for me (qt 4.2.3). However, before committing, I'd like to know: what is the difference between these two signals? There are other places relying on itemSelectionChanged, shall I fix them? Ping! I looked into this a bit, but came up with no answers. But here's a guess. Maybe it's like a key-press vs key-release thing, and itemSelectionChanged is being fired before the new row has actually been set (ie, when the old item is deselected), whereas currentRowChanged is fired only when the new row has been set? I guess the answer is in the Qt sourcecode, but I've been there before and have no desire to go back ;-) rh
Re: Multi-LFUN Binding
G Milde wrote:
rgheck [EMAIL PROTECTED] schrieb:
This has now been committed.
Just a name change proposal: command-alternatives - command-try
I know that one is long, but it's a bit more explicit.
Next issue is the bindings. There ought to
be other places we can use this, too, no?
1. a find-next binding that recalls the last search from the find dialogue
without re-openign it -- falling back to dialog-show findreplace.
Pavel's in-code solution seems better.
2. I would like some alternative binding for mathed:
* all of \ { [ ] } ~ are hard-to-get (with AltGr+something) on my German
keyboard.
* OTOH, the ä, ö, ü, and ß keys are rarely (or not at all) used in math.
However, these keys self-insert, so they do not fail and the current
alternatives version does not work in this case :-(
Therefore, IMO there is also need for some context-specific bind syntax,
e.g. one of
* \bind key command-math mathfun; fun
* \bind key fun
\bind-math key mathfun
* \bind key fun
\bind key mathfun math
As Pavel said, this would be excellent, but isn't for 1.6.
rh
Re: [PATCH] Re: question 1 of x - help to update the docs for 1.6.0
Jean-Marc Lasgouttes wrote: rgheck [EMAIL PROTECTED] writes: Well, if you're going to leave InsetInfo until after 1.6, we can do this together. You can tell me what character styles you want, and I'll produce definitions of them that you can use. I've already done this for Customization, as you'll see if you look under EditText Styles. What about the following instead: 1/ make InsetInfo depend on InsetCollapsable (this is only because I need this to have an insetlayout, in principle InsetText is OK). 2/ provide styles for the different types of insetinfo 3/ waste a lot of time finding all the small ingredients that makes it work :) I think this works well enough to go in trunk. This looks good to me. It's really a great illustration of why InsetLayout was such a great idea. Yours, if I recall rh
Re: [PATCH] Re: question 1 of x - help to update the docs for 1.6.0
rgheck [EMAIL PROTECTED] writes: This looks good to me. It's really a great illustration of why InsetLayout was such a great idea. Yours, if I recall Maybe, but Martin did all the hard work. JMarc
Completion Bindings
OK, the new binding for completion-accept is in trunk. We could really use one for complete, as well. I was thinking, as I think Stefan also suggested, some spacebar-related binding. But most of these are taken (of course). Any ideas? Alt-Shift-Space seems to be available in cua.bind, but that is taken on Mac and may not work on Windows? rh
Re: [PATCH][RFC] selection of items in ErrorList
rgheck [EMAIL PROTECTED] writes: I looked into this a bit, but came up with no answers. But here's a guess. Maybe it's like a key-press vs key-release thing, and itemSelectionChanged is being fired before the new row has actually been set (ie, when the old item is deselected), whereas currentRowChanged is fired only when the new row has been set? I guess the answer is in the Qt sourcecode, but I've been there before and have no desire to go back ;-) OK, I'll just put it in. JMarc
Re: [Cvslog] r26544 - /lyx-devel/trunk/lib/bind/site.bind
On Thursday 25 September 2008 16:31:42 [EMAIL PROTECTED] wrote: Author: rgheck Date: Thu Sep 25 17:31:41 2008 New Revision: 26544 URL: http://www.lyx.org/trac/changeset/26544 Log: Well, we've agreed on this binding. We could still use one for complete, but, Jose, this is enough for rc3. Now that this patch is in what is missing? I am asking this because if there is not any urgent patch needing to go in I will release tomorrow a tentative candidate to rc3. In between I advise caution to commits, please. :-) Documentation and translations updates are OK. -- José Abílio
Re: [Cvslog] r26544 - /lyx-devel/trunk/lib/bind/site.bind
José Matos wrote: On Thursday 25 September 2008 16:31:42 [EMAIL PROTECTED] wrote: Author: rgheck Date: Thu Sep 25 17:31:41 2008 New Revision: 26544 URL: http://www.lyx.org/trac/changeset/26544 Log: Well, we've agreed on this binding. We could still use one for complete, but, Jose, this is enough for rc3. Now that this patch is in what is missing? Well, it would be nice to have a binding for LFUN_COMPLETION_COMPLETE, but we still have the usual problem: Too many LFUNs, not enough keys. But there is no urgent need, it seems to me: Having this binding makes completion pretty usable, and rc3 can go as far as I'm concerned. I think I also speak for Pavel here, but he should speak up if he doesn't agree. Richard
Re: [Cvslog] r26527 - in /lyx-devel/trunk/src: BufferView.cpp Cursor.c...
On Thu, Sep 25, 2008 at 09:44:10AM +0200, Jean-Marc Lasgouttes wrote: [EMAIL PROTECTED] writes: Author: poenitz Date: Wed Sep 24 23:27:41 2008 New Revision: 26527 URL: http://www.lyx.org/trac/changeset/26527 Log: streamlining setter syntax. using mutable references seems a bit outlandish compared to the rest of LyX - d-cursor_.selection() = false; + d-cursor_.setSelection(false); Are you aware that setSelection does more than setting directly selection()? In particular, it refuses to set the selection when the cursor and the anchor are at the same place. This is a situation that happens in some places, and there is a risk of breaking selection. That would be the setSelection() overload without arguments, no? I noticed that unlucky setupo... Andre'
Re: An idea about the appearance of key-bindings in the statusbar
On Thu, 25 Sep 2008, Nikos Alexandris wrote: What about improving the appearance of key-bindings in the statusbar? Increase space between key-bindings and interchange the background colour for each key-binding (light background - darker background - light background - darker background - ... ). I retouched a screenshot of the current appearance (attached pictures from the original the retouched version). Its not my best photo-editing attempt (there is also a huge empty space in the retouched picture -- couldn't invest more time on it) but I think it's clear enough of what I am thinking. Hopefully you like it and it's easy to implement. Hi Nikos, I think you have good ideas, and developers seem to notice them, but even so I'm forwarding it to the developers' list. (lyx-devel AT lists.lyx.org ) regards, Christian PS. Maybe the ability to see a log/history of the most recent commands could be useful. Do we have that possibility? -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
Re: LyX is Nominated for the Lutèce d'Or 2008
On Thu, 25 Sep 2008, Abdelrazak Younes wrote: I don't have the number but quite a few apparently. That's what the guy at my table told me. He is a journalist at 01-informatique and was a member of the jury. He told me he voted for us but we didn't really have a chance against OpenOffice. This is cool, thanks for telling us about it! /Christian -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
Re: menu structure
On Thu, 25 Sep 2008, Helge Hafting wrote: Konrad Hofbauer wrote: Jean-Marc Lasgouttes wrote: Can you point to a program where _all_ document-level settings are in File menu? We shall not over-interpret the HIG. I do not have much to compare to by hand, only OO 2.3 and Word 2003. Word 2003 has the Page Setup in File, OO has Properties in File. Both of them don't have a Document menu. Both have (a Windows-HIG) Tools menu. FWIW, I like having a separate menu for 'document' related issues. I used LyX again quite recently after not having used it for a _long_ time, so long that I'd had time to forget there was a document menu. (Back when I was a regular user, it was so long ago that document settings were somewhere else). However, even me not really being used to the location of the document settings, I found it quickly and it soon felt right. What is the difference between file and document in the first place ??? A document may consist of several files. For example, the book where each chapter is a file of its own. Document settings matter only for the master document file, when you print/export the book. The chapter files may have their own settings, but they are used only if you print chapter files separately. I think Helge makes a very good point here. A file and a document aren't necessarily the same. (FWIW, I did my thesis as a multi-part document as he describes it so the use case isn't that uncommon.) Having said the above and sounding negative, I think it's great that you are looking at menu structure in a structured way! /Christian -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
Re: lyx and collaborative editing.
On Thu, 25 Sep 2008, Helge Hafting wrote: why is this so, what a pity that would be ideal for collaboration. Because running latex on unrestricted input in practice lets you do anything you can do with a program. Want to plant a virus program? Embed the virus in latex code as a string of bytes, then add some trivial latex code to (1) write the virus to a disk file, and (2) execute that file somehow. Or maybe executing it isn't even necessary if it gets published on the wiki where unsuspecting people will stumble across it. There are ways around this, such as: * Set up the latex parsing very carefully, perhaps using a chroot where only the necessary latex files are available, and all read-only. snip Even with such a setup, or running the entire conversion in a separate virtual machine that's reset each time, there would still be a risk involved in letting _arbitrary_ users execute _arbitrary_ LaTeX software on it. How do you know they aren't skilled enough to write a program that escalates their privilegdes, and finally manages to break out of the VM. Well, they can still cause network traffic, such as running DOS/cracking attacks against other hosts within the time limit. Maybe there is a way of removing network access too. :-/ That should at least be doable using a VM. There's no reason it must have external network access. /Christian -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
Re: Cursor::anchor()
On Thu, Sep 25, 2008 at 01:20:39PM +0200, Vincent van Ravesteijn - TNW wrote: How can I modify the anchor position of a selection ? Why do you need to do that, actually? Jmarc Well, if you select multiple lines and you hit tab then a tab will be inserted at the beginning of each line. As a consequence, the selection needs to be updated to shift one pos to the right.. Vincent Are you sure? Doesn't sound right if you're also indenting the line the anchor is on... the insert location is outside the selection. - Martin
Re: lyx and collaborative editing.
On Thu, 25 Sep 2008, Uwe Brauer wrote: Planet Math (http://planetmath.org/) is a collaborative encyclopedia based on LaTeX, with some restrictions to maintain a coherent look and feel (like the style of a scientific journal). The server part can be installed on any machine, the software required is downloadable from their web site. Maybe this could help solving the problem ? This looks extremely interesting. I will try that out. Thanks very much for this pointer (I tried so many google searches, this did not show up) In case you don't need a lot of math (which I doubt), the MimeTeX plugin can be used: http://www.pmwiki.org/wiki/Cookbook/MimeTeX It was installed at wiki.lyx.org, and it works by taking a piece of LaTeX equation, convert it to an image and embedding that image. However, I think I removed it because it also allowed you to generate an image that contained /etc/passwd ... /Christian PS. If you trust your users, and use e.g. a VCS to send files to a central repository, you could set up the system so that when the files are sent to the central repository, the server automatically runs LaTeX on the files. This could of course also be done with .lyx-files. (Which reminds me that we should perhaps do this for the LyX documentation? Or at least script it, so that we can generate it on the server.) -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
Re: Display of index in the Outline window--sorted alphabetically
On Thu, Sep 25, 2008 at 03:50:02PM +0200, Abdelrazak Younes wrote: On 25/09/2008 15:34, leuven edwin wrote: also: could you reverse the sort order in the combobox in the toc panel? the toc is used most often so it would be nice to have it on top... Why not simply rename that to Document Structure? Or maybe just Sections? Abdel. Outline? - Martin
Re: An idea about the appearance of key-bindings in the statusbar
Christian Ridderström wrote: PS. Maybe the ability to see a log/history of the most recent commands could be useful. Do we have that possibility? you mean lyx -dbg action ? pavel
Re: [Cvslog] r26544 - /lyx-devel/trunk/lib/bind/site.bind
Richard Heck wrote: Now that this patch is in what is missing? Well, it would be nice to have a binding for LFUN_COMPLETION_COMPLETE, but we still have the usual problem: Too many LFUNs, not enough keys. But there is no urgent need, it seems to me: Having this binding makes completion pretty usable, and rc3 can go as far as I'm concerned. I think I also speak for Pavel here, but he should speak up if he doesn't agree. yes, the urgent part is in. pavel
Re: [Cvslog] r26544 - /lyx-devel/trunk/lib/bind/site.bind
On Thu, Sep 25, 2008 at 06:22:06PM +0100, José Matos wrote: Now that this patch is in what is missing? What about the patch for accented unicode characters in math? -- Enrico
Re: Undo problems
Pavel Sanda wrote: Jean-Marc Lasgouttes wrote: Pavel Sanda [EMAIL PROTECTED] writes: don't remember. i guess i just mimic the preexistant code - there was dispatch(FuncRequest(getLfun(), lfun)); already called and i only added dispatch(FuncRequest(LFUN_GRAPHICS_GROUPS_UNIFY...) after it. I moved the code around, and it does not use LFUN_GRAPHICS_GROUPS_UNIFY anymore. Shall I remove the lfun? sure i did it finally. pavel
