Re: inset questions
On 25-Sep-2000 Marko Vendelin wrote: 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. The problem right now (with using CSM) is that you don't get a MouseRelease Event in the Inset if the mouse is released outside the inset! This has to be fixed before. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ He is no lawyer who cannot take two sides.
Re: inset questions
On 25-Sep-2000 Marko Vendelin wrote: >> >> 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. The problem right now (with using CSM) is that you don't get a MouseRelease Event in the Inset if the mouse is released outside the inset! This has to be fixed before. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ He is no lawyer who cannot take two sides.
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)
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
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
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)
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
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 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. Marko
Re: inset questions
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. Marko
Re: inset questions
On Fri, 22 Sep 2000, Allan Rae wrote:
Info will become a collapsible inset and so it won't be needing a dialog
in future. It should be fairly easy to implement (give it a better name
at the same time like InsetProofread or something since it's meant for
sticking editting notes into and should be possible to block export to
certain formats (eg. ascii text).
Hmmm! I see. So first implementation would be
class InsetNote : public InsetCollapsable {
public:
///
InsetNote(); // pass InsetCollapsable colors of Note perhaps
///
void Write(Buffer const * buf, std::ostream os) const;
///
int Latex(Buffer const *, std::ostream , bool fragile, bool free_spc) const {
return 0; }
///
int Ascii(Buffer const *, std::ostream ) const { return 0; }
///
int Linuxdoc(Buffer const *, std::ostream ) const { return 0; }
///
int DocBook(Buffer const *, std::ostream ) const { return 0; }
}
Then somone (!?!) would show me how to write comments to Latex that could
subsequently be interpretted by reLyX and read back into LyX?
By the way, what's wrong with the name? Your comment that "it's meant for
sticking editting notes into", seems perfectly fitted to "Note". Perhaps
you'd prefer "PostIt", especially since the note box is bright yellow!
Feel free to post comments, notes and ideas all over my fridge, all you out
there with ideas on the Best Way Forward!
Angus
Re: inset questions
"Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Then somone (!?!) would show me how to write comments to Latex Angus that could subsequently be interpretted by reLyX and read back Angus into LyX? Angus By the way, what's wrong with the name? Your comment that "it's Angus meant for sticking editting notes into", seems perfectly fitted Angus to "Note". Perhaps you'd prefer "PostIt", especially since the Angus note box is bright yellow! As I see it, we need 3 related insets: - one which outputs as % latex comments (InsetNote?). This one could be restricted to text only, since we cannot expect reLyX to parse everything after a % as valid latex. - one which outputs as a comment environment (InsetComment?) - one which outputs nothing in LaTeX (InsetHidden?) JMarc
Re: inset questions
On Fri, Sep 22, 2000 at 11:28:35AM +0200, Jean-Marc Lasgouttes wrote: As I see it, we need 3 related insets: - one which outputs as % latex comments (InsetNote?). This one could be restricted to text only, since we cannot expect reLyX to parse everything after a % as valid latex. - one which outputs as a comment environment (InsetComment?) - one which outputs nothing in LaTeX (InsetHidden?) The third could be a special case of the first with a checkbox marked. Is there any comment environment in latex? (the second case). JMarc -- José
Re: inset questions
On 22-Sep-2000 Jean-Marc Lasgouttes wrote: As I see it, we need 3 related insets: - one which outputs as % latex comments (InsetNote?). This one could be restricted to text only, since we cannot expect reLyX to parse everything after a % as valid latex. - one which outputs as a comment environment (InsetComment?) - one which outputs nothing in LaTeX (InsetHidden?) This should be 1 inset with a dialog where you can choose the output format! About the question of the 2 point, Lars said there is something like a comment environment in LaTeX, but he has to explain how it works ;) For now we just need 1 and 3! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Humor in the Court: Q: ...and what did he do then? A: He came home, and next morning he was dead. Q: So when he woke up the next morning he was dead?
Re: inset questions
On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote: On Fri, Sep 22, 2000 at 10:44:34AM +0100, Angus Leeming wrote: On the otherhand, José's suggestion of a checkbox is a cool one. Not that I've any idea of how to implement it! Like the url inset. There you have the option from it to be a htmlurl. It would be much more elegant, IMO, if this too was a collapsable inset. This toggling "url-htmlurl" or "export note-don't export note" would be (also elegantly) handled by Lars' suggestion of a context-sensitive menu activated by the right mouse button. (The menu would have just two items for now.) Until such a context-sensitive menu arrives, perhaps use the right mouse button to toggle between available states. Thoughts? Angus
Re: inset questions
About the question of the 2 point, Lars said there is something like
a comment environment in LaTeX, but he has to explain how it works ;)
If you write
\begin{comment}
some text
\end{comment}
in LaTeX, 'some text' won't be typeset.
Is that what you mean?
Andre'
--
Andre' Poenitz [EMAIL PROTECTED]
Re: inset questions
"Angus" == Angus Leeming [EMAIL PROTECTED] writes: Angus Yes. Could you explain what you mean by the second case, Angus Jean-Marc. I don't really see the difference between cases 1 Angus and 3. Why not output to LaTeX always. It's only a note and Angus will not be present in the final printed output. Why not Angus collapse 1 and 3 to just one? It is for part of a document that are either draft or secret and that you do not want to send as latex/sgml. Another recent proposition was to associate tags to those insets (clientA/clientB or article/chapter_of_a_thesis) and be able to generate a document according to a given tag (so you have several versions of the same document). Angus On the otherhand, José's suggestion of a checkbox is a cool Angus one. Not that I've any idea of how to implement it! In this case, the three versions could be merged into one. JMarc
Re: inset questions
"Juergen" == Juergen Vigna [EMAIL PROTECTED] writes: Juergen About the question of the 2 point, Lars said there is Juergen something like a comment environment in LaTeX, but he has to Juergen explain how it works ;) verbatim.sty provides it. However this is quite a big machniery from a LaTeX point of view IMO. JMarc
Re: inset questions
Thanks for all this input.
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.
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!
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
Re: inset questions
Ok, I've made the basic inset. It's a rather boring grey button with black
text. I'd like to Give it the same bright yellow background that InsetInfo
has now, but at the moment this isn't possible because PainterBase::button()
is hard-coded to draw the button in boring grey!
PainterBase PainterBase::button(int x, int y, int w, int h)
{
fillRectangle(x, y, w, h, LColor::buttonbg);
buttonFrame(x, y, w, h);
return * this;
}
I'd like to modify PainterBase::buttonText() and PainterBase::button() to
take a final argument "LColor::color " that is hard-coded to be
LColor::buttonbg, but can be changed if so desired. This would have the added
benefit of giving the same control over buttonText currently enjoyed with
rectText (same class).
Any objections?
Angus
On Fri, 22 Sep 2000, Angus Leeming wrote:
Thanks for all this input.
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.
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!
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
Re: inset questions
"Angus" == Angus Leeming [EMAIL PROTECTED] writes:
Angus Ok, I've made the basic inset. It's a rather boring grey button
Angus with black text. I'd like to Give it the same bright yellow
Angus background that InsetInfo has now, but at the moment this isn't
Angus possible because PainterBase::button() is hard-coded to draw
Angus the button in boring grey!
Angus PainterBase PainterBase::button(int x, int y, int w, int h) {
Angus fillRectangle(x, y, w, h, LColor::buttonbg); buttonFrame(x, y,
Angus w, h); return * this; }
Angus I'd like to modify PainterBase::buttonText() and
Angus PainterBase::button() to take a final argument "LColor::color "
Angus that is hard-coded to be LColor::buttonbg, but can be changed
Angus if so desired. This would have the added benefit of giving the
Angus same control over buttonText currently enjoyed with rectText
Angus (same class).
It seems to me that you would need to pass several colors, in order to
get the 3d effect.
JMarc
Re: inset questions
It seems to me that you would need to pass several colors, in order to get the 3d effect. Yes. Sod that. Let's have "note" with yellow text on a grey background. It looks kinda cute! InsetNote is now a straight replacement for InsetInfo. Ie, it has no output to LaTeX, but is a collapsable inset. The LyX file is a little modified though. It was: \begin_inset Info This is just a stupid little note \end_inset It is now \begin_inset Info collapsed true \layout Standard is just a stupid little note \end_inset I guess that this means that I have to define a change in the LyX file format? I'll start by giving the inset the name "Note" rather than "Info", but how/where do I explain what to do with "old-style" Infos? All pointers appreciated. Angus
Re: inset questions
I'm answering my own mail here. Sorry! But I'm asking another question.
In Buffer::readInset() am I allowed the following code?
string tmptok = lex.GetString();
...
// The old InsetInfo
} else if (tmptok == "Info") {
Inset * inset = new InsetNote;
// A temporary function, identical to InsetInfo::Read, to be
// removed when LYX_FORMAT has moved on sufficiently.
inset-ReadInfo(this, lex);
par-InsertInset(pos, inset, font);
++pos;
// The new InsetNote
} else if (tmptok == "Note") {
Inset * inset = new InsetNote;
// the conventional Read statement
inset-Read(this, lex);
par-InsertInset(pos, inset, font);
++pos;
} ...
I guess that this means that I have to define a change in the LyX file
format? I'll start by giving the inset the name "Note" rather than "Info",
but how/where do I explain what to do with "old-style" Infos?
Re: inset questions
On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote: \begin_inset Info This is just a stupid little note \end_inset It is now \begin_inset Info collapsed true \layout Standard is just a stupid little note \end_inset Why do you keep a state of the inset? IIRC no other inset has this feature. Angus -- José
Re: inset questions
All collapsible insets output this. Indeed, if it ain't found on input, then an error message is output. A. On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote: On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote: \begin_inset Info This is just a stupid little note \end_inset It is now \begin_inset Info collapsed true \layout Standard is just a stupid little note \end_inset Why do you keep a state of the inset? IIRC no other inset has this feature. Angus
Re: inset questions
On Fri, Sep 22, 2000 at 05:26:54PM +0100, Angus Leeming wrote: All collapsible insets output this. Indeed, if it ain't found on input, then an error message is output. A. My mistake then. That means that I have used that feature... BTW is it possible to have \begin_inset XYZ collapsed false ? Angus -- José
Re: inset questions
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | "Angus" == Angus Leeming [EMAIL PROTECTED] writes: | | Angus Then somone (!?!) would show me how to write comments to Latex | Angus that could subsequently be interpretted by reLyX and read back | Angus into LyX? | | Angus By the way, what's wrong with the name? Your comment that "it's | Angus meant for sticking editting notes into", seems perfectly fitted | Angus to "Note". Perhaps you'd prefer "PostIt", especially since the | Angus note box is bright yellow! | | As I see it, we need 3 related insets: | | - one which outputs as % latex comments (InsetNote?). This one could | be restricted to text only, since we cannot expect reLyX to parse | everything after a % as valid latex. | - one which outputs as a comment environment (InsetComment?) | - one which outputs nothing in LaTeX (InsetHidden?) Please remember that this _is_ 1.2.0 stuff. Do not use too much time on this now. Lgb
Re: inset questions
Juergen Vigna [EMAIL PROTECTED] writes: | About the question of the 2 point, Lars said there is something like | a comment environment in LaTeX, but he has to explain how it works |;) read comment.sty? We have had the comment layout for a _long_ time now. You have obviously not used it. Lgb
Re: inset questions
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | "Juergen" == Juergen Vigna [EMAIL PROTECTED] writes: | | Juergen About the question of the 2 point, Lars said there is | Juergen something like a comment environment in LaTeX, but he has to | Juergen explain how it works ;) | | verbatim.sty provides it. However this is quite a big machniery from a | LaTeX point of view IMO. verbatim.sty it was. I do not tink we should care too much about it beeing a "big machinery[sic]" Lgb
Re: inset questions
On Fri, 22 Sep 2000, Allan Rae wrote:
> Info will become a collapsible inset and so it won't be needing a dialog
> in future. It should be fairly easy to implement (give it a better name
> at the same time like InsetProofread or something since it's meant for
> sticking editting notes into and should be possible to block export to
> certain formats (eg. ascii text).
Hmmm! I see. So first implementation would be
class InsetNote : public InsetCollapsable {
public:
///
InsetNote(); // pass InsetCollapsable colors of Note perhaps
///
void Write(Buffer const * buf, std::ostream & os) const;
///
int Latex(Buffer const *, std::ostream &, bool fragile, bool free_spc) const {
return 0; }
///
int Ascii(Buffer const *, std::ostream &) const { return 0; }
///
int Linuxdoc(Buffer const *, std::ostream &) const { return 0; }
///
int DocBook(Buffer const *, std::ostream &) const { return 0; }
}
Then somone (!?!) would show me how to write comments to Latex that could
subsequently be interpretted by reLyX and read back into LyX?
By the way, what's wrong with the name? Your comment that "it's meant for
sticking editting notes into", seems perfectly fitted to "Note". Perhaps
you'd prefer "PostIt", especially since the note box is bright yellow!
Feel free to post comments, notes and ideas all over my fridge, all you out
there with ideas on the Best Way Forward!
Angus
Re: inset questions
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Then somone (!?!) would show me how to write comments to Latex Angus> that could subsequently be interpretted by reLyX and read back Angus> into LyX? Angus> By the way, what's wrong with the name? Your comment that "it's Angus> meant for sticking editting notes into", seems perfectly fitted Angus> to "Note". Perhaps you'd prefer "PostIt", especially since the Angus> note box is bright yellow! As I see it, we need 3 related insets: - one which outputs as % latex comments (InsetNote?). This one could be restricted to text only, since we cannot expect reLyX to parse everything after a % as valid latex. - one which outputs as a comment environment (InsetComment?) - one which outputs nothing in LaTeX (InsetHidden?) JMarc
Re: inset questions
On Fri, Sep 22, 2000 at 11:28:35AM +0200, Jean-Marc Lasgouttes wrote: > As I see it, we need 3 related insets: > > - one which outputs as % latex comments (InsetNote?). This one could > be restricted to text only, since we cannot expect reLyX to parse > everything after a % as valid latex. > - one which outputs as a comment environment (InsetComment?) > - one which outputs nothing in LaTeX (InsetHidden?) The third could be a special case of the first with a checkbox marked. Is there any comment environment in latex? (the second case). > JMarc -- José
Re: inset questions
On 22-Sep-2000 Jean-Marc Lasgouttes wrote: > As I see it, we need 3 related insets: > > - one which outputs as % latex comments (InsetNote?). This one could > be restricted to text only, since we cannot expect reLyX to parse > everything after a % as valid latex. > - one which outputs as a comment environment (InsetComment?) > - one which outputs nothing in LaTeX (InsetHidden?) This should be 1 inset with a dialog where you can choose the output format! About the question of the 2 point, Lars said there is something like a comment environment in LaTeX, but he has to explain how it works ;) For now we just need 1 and 3! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Humor in the Court: Q: ...and what did he do then? A: He came home, and next morning he was dead. Q: So when he woke up the next morning he was dead?
Re: inset questions
On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote: > On Fri, Sep 22, 2000 at 10:44:34AM +0100, Angus Leeming wrote: > > On the otherhand, José's suggestion of a checkbox is a cool one. Not that > > I've any idea of how to implement it! > > Like the url inset. There you have the option from it to be a htmlurl. It would be much more elegant, IMO, if this too was a collapsable inset. This toggling "url->htmlurl" or "export note->don't export note" would be (also elegantly) handled by Lars' suggestion of a context-sensitive menu activated by the right mouse button. (The menu would have just two items for now.) Until such a context-sensitive menu arrives, perhaps use the right mouse button to toggle between available states. Thoughts? Angus
Re: inset questions
> About the question of the 2 point, Lars said there is something like
> a comment environment in LaTeX, but he has to explain how it works ;)
If you write
\begin{comment}
some text
\end{comment}
in LaTeX, 'some text' won't be typeset.
Is that what you mean?
Andre'
--
Andre' Poenitz [EMAIL PROTECTED]
Re: inset questions
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Yes. Could you explain what you mean by the second case, Angus> Jean-Marc. I don't really see the difference between cases 1 Angus> and 3. Why not output to LaTeX always. It's only a note and Angus> will not be present in the final printed output. Why not Angus> collapse 1 and 3 to just one? It is for part of a document that are either draft or secret and that you do not want to send as latex/sgml. Another recent proposition was to associate tags to those insets (clientA/clientB or article/chapter_of_a_thesis) and be able to generate a document according to a given tag (so you have several versions of the same document). Angus> On the otherhand, José's suggestion of a checkbox is a cool Angus> one. Not that I've any idea of how to implement it! In this case, the three versions could be merged into one. JMarc
Re: inset questions
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: Juergen> About the question of the 2 point, Lars said there is Juergen> something like a comment environment in LaTeX, but he has to Juergen> explain how it works ;) verbatim.sty provides it. However this is quite a big machniery from a LaTeX point of view IMO. JMarc
Re: inset questions
Thanks for all this input.
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.
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!
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
Re: inset questions
Ok, I've made the basic inset. It's a rather boring grey button with black
text. I'd like to Give it the same bright yellow background that InsetInfo
has now, but at the moment this isn't possible because PainterBase::button()
is hard-coded to draw the button in boring grey!
PainterBase & PainterBase::button(int x, int y, int w, int h)
{
fillRectangle(x, y, w, h, LColor::buttonbg);
buttonFrame(x, y, w, h);
return * this;
}
I'd like to modify PainterBase::buttonText() and PainterBase::button() to
take a final argument "LColor::color " that is hard-coded to be
LColor::buttonbg, but can be changed if so desired. This would have the added
benefit of giving the same control over buttonText currently enjoyed with
rectText (same class).
Any objections?
Angus
On Fri, 22 Sep 2000, Angus Leeming wrote:
> Thanks for all this input.
>
> 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.
>
> 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!
>
> 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
Re: inset questions
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Ok, I've made the basic inset. It's a rather boring grey button
Angus> with black text. I'd like to Give it the same bright yellow
Angus> background that InsetInfo has now, but at the moment this isn't
Angus> possible because PainterBase::button() is hard-coded to draw
Angus> the button in boring grey!
Angus> PainterBase & PainterBase::button(int x, int y, int w, int h) {
Angus> fillRectangle(x, y, w, h, LColor::buttonbg); buttonFrame(x, y,
Angus> w, h); return * this; }
Angus> I'd like to modify PainterBase::buttonText() and
Angus> PainterBase::button() to take a final argument "LColor::color "
Angus> that is hard-coded to be LColor::buttonbg, but can be changed
Angus> if so desired. This would have the added benefit of giving the
Angus> same control over buttonText currently enjoyed with rectText
Angus> (same class).
It seems to me that you would need to pass several colors, in order to
get the 3d effect.
JMarc
Re: inset questions
> It seems to me that you would need to pass several colors, in order to > get the 3d effect. Yes. Sod that. Let's have "note" with yellow text on a grey background. It looks kinda cute! InsetNote is now a straight replacement for InsetInfo. Ie, it has no output to LaTeX, but is a collapsable inset. The LyX file is a little modified though. It was: \begin_inset Info This is just a stupid little note \end_inset It is now \begin_inset Info collapsed true \layout Standard is just a stupid little note \end_inset I guess that this means that I have to define a change in the LyX file format? I'll start by giving the inset the name "Note" rather than "Info", but how/where do I explain what to do with "old-style" Infos? All pointers appreciated. Angus
Re: inset questions
I'm answering my own mail here. Sorry! But I'm asking another question.
In Buffer::readInset() am I allowed the following code?
string tmptok = lex.GetString();
...
// The old InsetInfo
} else if (tmptok == "Info") {
Inset * inset = new InsetNote;
// A temporary function, identical to InsetInfo::Read, to be
// removed when LYX_FORMAT has moved on sufficiently.
inset->ReadInfo(this, lex);
par->InsertInset(pos, inset, font);
++pos;
// The new InsetNote
} else if (tmptok == "Note") {
Inset * inset = new InsetNote;
// the conventional Read statement
inset->Read(this, lex);
par->InsertInset(pos, inset, font);
++pos;
} ...
> I guess that this means that I have to define a change in the LyX file
> format? I'll start by giving the inset the name "Note" rather than "Info",
> but how/where do I explain what to do with "old-style" Infos?
Re: inset questions
On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote: > \begin_inset Info > This is just a stupid little note > \end_inset > > It is now > > \begin_inset Info > collapsed true > > \layout Standard > > > is just a stupid little note > \end_inset Why do you keep a state of the inset? IIRC no other inset has this feature. > Angus > -- José
Re: inset questions
All collapsible insets output this. Indeed, if it ain't found on input, then an error message is output. A. On Fri, 22 Sep 2000, Jose Abilio Oliveira Matos wrote: > On Fri, Sep 22, 2000 at 04:31:56PM +0100, Angus Leeming wrote: > > \begin_inset Info > > This is just a stupid little note > > \end_inset > > > > It is now > > > > \begin_inset Info > > collapsed true > > > > \layout Standard > > > > > > is just a stupid little note > > \end_inset > > Why do you keep a state of the inset? > IIRC no other inset has this feature. > > > Angus
Re: inset questions
On Fri, Sep 22, 2000 at 05:26:54PM +0100, Angus Leeming wrote: > All collapsible insets output this. Indeed, if it ain't found on input, then > an error message is output. > A. My mistake then. That means that I have used that feature... BTW is it possible to have \begin_inset XYZ collapsed false ? > > > Angus -- José
Re: inset questions
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: | | Angus> Then somone (!?!) would show me how to write comments to Latex | Angus> that could subsequently be interpretted by reLyX and read back | Angus> into LyX? | | Angus> By the way, what's wrong with the name? Your comment that "it's | Angus> meant for sticking editting notes into", seems perfectly fitted | Angus> to "Note". Perhaps you'd prefer "PostIt", especially since the | Angus> note box is bright yellow! | | As I see it, we need 3 related insets: | | - one which outputs as % latex comments (InsetNote?). This one could | be restricted to text only, since we cannot expect reLyX to parse | everything after a % as valid latex. | - one which outputs as a comment environment (InsetComment?) | - one which outputs nothing in LaTeX (InsetHidden?) Please remember that this _is_ 1.2.0 stuff. Do not use too much time on this now. Lgb
Re: inset questions
Juergen Vigna <[EMAIL PROTECTED]> writes: | About the question of the 2 point, Lars said there is something like | a comment environment in LaTeX, but he has to explain how it works |;) read comment.sty? We have had the comment layout for a _long_ time now. You have obviously not used it. Lgb
Re: inset questions
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | > "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: | | Juergen> About the question of the 2 point, Lars said there is | Juergen> something like a comment environment in LaTeX, but he has to | Juergen> explain how it works ;) | | verbatim.sty provides it. However this is quite a big machniery from a | LaTeX point of view IMO. verbatim.sty it was. I do not tink we should care too much about it beeing a "big machinery[sic]" Lgb
inset questions
I see that the following files in src/insets still #include FORMS_H_LOCATION: figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h, insetexternal.C, insetinclude.C, insetinfo.h Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this direction? What about figinset.[Ch]? This leaves the 5 inset files and associated classes. I was going to have a go at making InsetInfo GUI-independent, but have vague notions that people were suggesting that it too should go? (I haven't been paying much attention of late) Is this so or should I do my worst on it? Angus
Re: inset questions
On Thu, 21 Sep 2000, Angus Leeming wrote: I see that the following files in src/insets still #include FORMS_H_LOCATION: figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h, insetexternal.C, insetinclude.C, insetinfo.h Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this direction? What about figinset.[Ch]? The form_graphics.[Ch] in the insets/ directory are obsoleted together with the figinset.[Ch], however since my FormGraphics is still not up to par with the figinset (no inline viewing) it probably should not be removed for now. I'll be back to my development machine tommorow and will try to finish the parts that still need work. I'll be replacing my devel machine and be back to work on FormGraphics. Baruch
Re: inset questions
On Thu, 21 Sep 2000, Angus Leeming wrote: I see that the following files in src/insets still #include FORMS_H_LOCATION: figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h, insetexternal.C, insetinclude.C, insetinfo.h Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this direction? What about figinset.[Ch]? This leaves the 5 inset files and associated classes. I was going to have a go at making InsetInfo GUI-independent, but have vague notions that people were suggesting that it too should go? (I haven't been paying much attention of late) Is this so or should I do my worst on it? Info will become a collapsible inset and so it won't be needing a dialog in future. It should be fairly easy to implement (give it a better name at the same time like InsetProofread or something since it's meant for sticking editting notes into and should be possible to block export to certain formats (eg. ascii text). You work on one of the others, although InsetExternal and InsetGraphics are likely to be merged at some point (I think you were away for those threads) so you might just skip external for now. There's always fine-tuning to do if you need some work to do ;-) Allan. (ARRae)
inset questions
I see that the following files in src/insets still #include FORMS_H_LOCATION: figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h, insetexternal.C, insetinclude.C, insetinfo.h Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this direction? What about figinset.[Ch]? This leaves the 5 inset files and associated classes. I was going to have a go at making InsetInfo GUI-independent, but have vague notions that people were suggesting that it too should go? (I haven't been paying much attention of late) Is this so or should I do my worst on it? Angus
Re: inset questions
On Thu, 21 Sep 2000, Angus Leeming wrote: > I see that the following files in src/insets still #include FORMS_H_LOCATION: > > figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h, > insetexternal.C, insetinclude.C, insetinfo.h > > Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this > direction? What about figinset.[Ch]? The form_graphics.[Ch] in the insets/ directory are obsoleted together with the figinset.[Ch], however since my FormGraphics is still not up to par with the figinset (no inline viewing) it probably should not be removed for now. I'll be back to my development machine tommorow and will try to finish the parts that still need work. I'll be replacing my devel machine and be back to work on FormGraphics. Baruch
Re: inset questions
On Thu, 21 Sep 2000, Angus Leeming wrote: > I see that the following files in src/insets still #include FORMS_H_LOCATION: > > figinset.C, form_graphics.C, form_graphics.h, insetbib.C, inseterror.h, > insetexternal.C, insetinclude.C, insetinfo.h > > Are form_graphics.[Ch] to be made redundant by Baruch's efforts in this > direction? What about figinset.[Ch]? > > This leaves the 5 inset files and associated classes. I was going to have a > go at making InsetInfo GUI-independent, but have vague notions that people > were suggesting that it too should go? (I haven't been paying much attention > of late) Is this so or should I do my worst on it? Info will become a collapsible inset and so it won't be needing a dialog in future. It should be fairly easy to implement (give it a better name at the same time like InsetProofread or something since it's meant for sticking editting notes into and should be possible to block export to certain formats (eg. ascii text). You work on one of the others, although InsetExternal and InsetGraphics are likely to be merged at some point (I think you were away for those threads) so you might just skip external for now. There's always fine-tuning to do if you need some work to do ;-) Allan. (ARRae)
