Re: inset questions
On Fri, 22 Sep 2000, Angus Leeming wrote:
> Thanks for all this input.
Here's some from me since I missed most of the discussion.
> I'm going to try and summarise it all and so define what the new InsetNote
> should do.
>
> 1. It should be a collapsable inset.
1a. It should be possible to "Melt" any given comment environment. It
should also be possible to turn a selection into a comment such that the
selection is effectively just cut and pasted for the user into a Comment.
This is so we can comment out a chunk of a document but keep all the
formatting info. "Melt" can be JACO (Just Another CSM Option).
It makes sense to melt a commented out section of a document but doesn't
make sense to melt your proofreading notes. In addition we should be able
to navigate from one Note to the next similar to jumping to the next
ErrorBox. Notes are different to Comments and should remain so IMO.
> 2. It should output nothing to Ascii, Linuxdoc or DocBook. Don't argue here.
> We can always change later!
>
> 3. People have suggested a single inset with three different possible outputs
> to LaTeX
> a. No output
> b. %LyXNote% This is a comment
> c. Use the LaTeX comment environment:
> \usepackage{verbatim.sty}
> \begin{comment}
> This is a comment
> \end{comment}
>
> If appears to me that (b) and (c) are functionally identical. Jean-Marc
> suggests that the LaTeX machinery of (c) is relatively large. I know nothing!
I'm still inclinded to have two separate insets. InsetNote and
InsetComment. Remember that we have a Comment environment already (a very
limited one admittedly) and if you do merge all three behaviours (bad idea
IMO) you will also need to handle old documents with Comments in them.
We should instead translate old Comment environments into an InsetComment.
> 4. Output to LyX
> \begin_inset Note some text
> \end_inset
>
> Presumably this could be almost identical to the current output.
> Something additional about LaTeX output.
>
> 5. We need some method of toggling between the three LaTeX output states. As
> the left mouse button opens the inset, this leaves the right mouse button.
> Jürgen seems very against using this to toggle between states, so RMB will
> launch a (very small) dialog containing only a "choice of output" menu. No
> "Ok" or "Cancel" buttons are needed, I think. (Now I think of it, haven't I
> just defined a context-sensitive menu form?)
>
> Angus
Allan. (ARRae)
Re: inset questions
On Mon, 25 Sep 2000, Allan Rae wrote: > I just jumped from first to last emails in this thread so I may have > missed a little bit ;-) > > On Sat, 23 Sep 2000, Marko Vendelin wrote: > > > On Fri, 22 Sep 2000, Angus Leeming wrote: > > > > > 5. We need some method of toggling between the three LaTeX output states. As > > > the left mouse button opens the inset, this leaves the right mouse button. > > > Jürgen seems very against using this to toggle between states, so RMB will > > > launch a (very small) dialog containing only a "choice of output" menu. No > > > "Ok" or "Cancel" buttons are needed, I think. (Now I think of it, haven't I > > > just defined a context-sensitive menu form?) > > > > It seems to me that "Cancel" is needed always. In this case, it will be > > the same for user as to close context-sensitive menu without selecting > > anything by pressing mouse button outside the menu area. > > A CSM should only be visible while the mouse button is held down. Once > the mouse is released the menu closes. If the mouse was over a menu entry > that menu entry's action takes place. If the mouse cursor was outside the > menu borders nothing happens. You don't need a cancel button and CSM's > shouldn't be opened with one click and operated with another. We don't need "Cancel" in CSM, but we need it if we want to emulate CSM with a dialog. Marko
LyX Development News 13th Sept 2000
A bit late notice, but just in case you hadn't spotted it yet there is a "new" LDN complete with pictures from FILM and few other treats. Allan. (ARRae)
Re: Tasks for 1.1.6!
On 23 Sep 2000, Lars Gullik Bjønnes wrote: > There have been a _lot_ of changes sine 1.1.5, and we should really > begin to think of a new release now. lots and lots of changes. > - Make the Online Preferences work better, we really want to > render lyxrc (in its manually-editi-this form) obsolete. Is there any particular reason LyXRC was made non-copyable? Do you want to use a separate LyXRCParams struct to hold all the lyxrc parameters? I need to be able to keep a copy of the lyxrc parameters from startup (or from the system level before user preferences was read) so I either need LyXRC copyable or a separate LyXRCParams struct. I prefer the struct. I also need to totally redesign the Preferences dialog so we don't need so many tabs. This'll need a switch to a nested tabbed dialog which I am still planning/experimenting. I have a few documents to write so I'll be testing LyX fairly extensively in the next couple of weeks. > 1.1.6 will only have XForms as supported GUI, I know that the gnome > and kde ports are comming along fine, but we need more time to get > the rest of LyX GUII. > I'd appriciate "must-be-done" lists from all developers. There still seem to be a few niggling issues with the File->New code. I haven't tried any of the changes in the last week but haven't seen mantion of anything fixing them. Mostly a matter of prompting for saves etc. LyX-Code environment has changed. Pressing no longer starts a new paragraph in .dvi output although it is displayed onscreen as a new paragraph (or at least as a new line) the output just runs all the lines together. Is this really the way we want this to work? All the legacy documents will need fixing if so. I suspect Dekel's patches to cleanup '\n' may have got one too many. Allan. (ARRae)
Re: LyX: The Typesetter's Wordprocessor
On Fri, 22 Sep 2000, Philip McDunnough wrote: > Hi Allan, > I have used Scientific Workplace over the years (a front-end to > LaTeX) and rather liked it. LyX seems very promising indeed. The > question is whether someone is moving it to the Mac OSX operating > system (which I use)? Any information would be appreciated. You are the third or perhaps fourth person to ask me this. None of the others volunteered to work on the port and none of the developers have Mac's let alone OS/X so unless some kind soul volunteers it won't happen. Don't get me wrong, the LyX developers would like to see LyX ported to OS/X (or any other OS for that matter) however we are only a group of volunteers, we don't get paid and we don't have access to many different machines. So while we are enthusiastic for LyX and have many enthusiastic LyX users we don't have the resources (human, machine or monetary) to port to OS/X at present. There are currently works-in-progress porting to KDE-1.1.2 and GNOME both of which may be ported to OS/X at some stage I suppose. OS/X is based on [Free]BSD and KDE is well supported on FreeBSD so I expect you could get access to LyX on OS/X soon although not necessarily in a native port. Regards, Allan. (ARRae) P.S. If you'd like to make a donation toward the development of LyX please take a look at the LyX home page and you'll see a link to LyX funding and sponsorship page. http://www.lyx.org/
Re: buffer failing
No, it's more broad that that. I can be typing whole words of different characters and just get two or three of them. I've never seen this before in any version of lyx. And I'm a, shall we say, passionate user. On Sat, Sep 23, 2000 at 03:50:59AM +0200, Lars Gullik Bjønnes wrote: > [EMAIL PROTECTED] writes: > > | When my computer is even slightly overtasked, and particularly when > | I'm making changes to the middle of existing lines, LyX seems to > | *lose* any character that the computer is not capable of writing > | immediately after I type it because of system constraints. > > This can be a problem with the "don't output heaps of chars after the > user has released the button" solution. > > But LyX is only running XSync (flushes X event buffers) if it is the > same key that is beeing pressed to fast? > > Lgb
Re: buffer failing
On Fri, Sep 22, 2000 at 11:32:35AM +0200, Jean-Marc Lasgouttes wrote: > You mean 1.1.6cvs, right? Maybe. I've just been running "cvs update" in my 1.1.5cvs directory. larry@second lyx-1_1_5>ls ABOUT-NLS Makefile acconfig.h configure*lyx.1 ANNOUNCE Makefile.am acinclude.m4configure.in lyx.man COPYING Makefile.in aclocal.m4 development/ po/ CVS/ NEWS autogen.sh* forms/src/ ChangeLog OLD-CHANGES config/ images/ INSTALL README config.cacheintl/ INSTALL.OS2 README.OS2 config.log lib/ INSTALL.autoconf UPGRADINGconfig.status* libtool* larry@second lyx-1_1_5>cd CVS larry@second CVS>ls Entries Repository Root Tag larry@second CVS>more Tag Tlyx-1_1_5 larry@second CVS>
Re: inset questions
I just jumped from first to last emails in this thread so I may have missed a little bit ;-) On Sat, 23 Sep 2000, Marko Vendelin wrote: > On Fri, 22 Sep 2000, Angus Leeming wrote: > > > 5. We need some method of toggling between the three LaTeX output states. As > > the left mouse button opens the inset, this leaves the right mouse button. > > Jürgen seems very against using this to toggle between states, so RMB will > > launch a (very small) dialog containing only a "choice of output" menu. No > > "Ok" or "Cancel" buttons are needed, I think. (Now I think of it, haven't I > > just defined a context-sensitive menu form?) > > It seems to me that "Cancel" is needed always. In this case, it will be > the same for user as to close context-sensitive menu without selecting > anything by pressing mouse button outside the menu area. A CSM should only be visible while the mouse button is held down. Once the mouse is released the menu closes. If the mouse was over a menu entry that menu entry's action takes place. If the mouse cursor was outside the menu borders nothing happens. You don't need a cancel button and CSM's shouldn't be opened with one click and operated with another. Allan. (ARRae)
gnome: FormCitation
Hi! this patch completes the rewrite of FormCitation in Gnome frontend to use the action area within the main window. This implementation of the dialog has two main modes. First, it allows to insert a new citation by asking for a keyword (regexp) and showing list of citation matching a filter. Second, it allows to change the order of citations or remove them one-by-one. The mode is selected by user or automatically if now citations were found in the inset. This patch contains a small addition to gnome menu. Now it supports large TOCs. Marko formcitation.gnome.patch.gz formcitation.gnome.newfiles.tar.gz
Re: Lost math bindings
On Sat, 23 Sep 2000, Garst R. Reese wrote: > Did you see my proposal to use M-capital-letters for menu shortcuts, > which would leave M-m available for math key bindings. > Would you find that acceptable? > > Marko observed: > And LyX will be the only program I know to do that :). Actually, I know > a > lot of people who open menu and select menu item by keyboard only using > M-f o, for example. > - > But LyX does not have rulers, tabs, doublespaces after periods either. > And how many other programs have hollywood and broadway :) True. But in all programs with the menus I know (Gnome & KDE ...), user can select the menu by M-. We can just change _Math to M_ath or Mat_h and be consistent with the mentioned GUI. Marko
