On Wednesday 10 October 2007 18:24:55 Edwin Leuven wrote:
> that's why we need a proper ui interface to load packages and set their
> options
IMHO that is not lyx job's.
--
José Abílio
Andre Poenitz <[EMAIL PROTECTED]> writes:
> On Wed, Oct 10, 2007 at 12:43:03PM +0200, Jean-Marc Lasgouttes wrote:
>> BTW, when opening the bindongs.lyx file, I get:
>>
>> BufferParams::readToken(): Unknown token: false
>> Object::connect: No such slot
>> lyx::frontend::GuiErrorList::select_adapt
José Matos wrote:
Just because you are a latex expert does not mean that you don't want to
know what are the packages that lyx depends on without looking directly to
the source, or am I missing any detail here? :-)
that's why we need a proper ui interface to load packages and set their
opti
On Wed, Oct 10, 2007 at 12:43:03PM +0200, Jean-Marc Lasgouttes wrote:
> BTW, when opening the bindongs.lyx file, I get:
>
> BufferParams::readToken(): Unknown token: false
> Object::connect: No such slot
> lyx::frontend::GuiErrorList::select_adaptor(QListWidgetItem*)
> Object::connect: (sender n
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> Yes. This was one of the problems I had when thinking about such a
>> feature. This and the underscores like _F_ile are nice things, but the
>> inset cannot give them to us as it is.
>
> What if InsetInfo becomes a non-editable InsetText?
This is something
> Yes. This was one of the problems I had when thinking about such a
> feature. This and the underscores like _F_ile are nice things, but the
> inset cannot give them to us as it is.
What if InsetInfo becomes a non-editable InsetText?
Bo
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> > But translators can not change this inset in LaTeXConfig.lyx...
>>
>> Translator will/can write their own version of LaTeXConfig.lyx if they
>> chose to. In this case, the yes/no shall be translated.
>
> The inset returns translatable _("yes"), and _("no"
> In this case, I think it is not useful. Such a file should explain
> what commands do and how to obtain it. The shortcuts for things like
> Cut are already shown in the menus, after all.
It is something like
http://wiki.lyx.org/uploads/LyX/keyboardShortcuts/bpeng/reference.pdf
Bo
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> 2/ we do not get the nice triangle between levels
>
> I see. That is a special character \lyxarrow (menu separator), that
> can not be displayed in this button, unless we use InsetText, not a
> button.
Yes. This was one of the problems I had when thinking
Bo Peng wrote:
i not upset, and i think that i am the one being rational here
Shortcuts.lyx would be the first, and may be the last lyx document I
would print, and put next to my screen when I use lyx.
I agree that this file have some benefits for someone wanting to learn
by hart the shortcu
On Wednesday 10 October 2007 16:17:50 Abdelrazak Younes wrote:
> I am not everybody but I've never ever had a look at this file. But I am
> not a LateX expert. But, as Edwin asked, if I was a LateX expert would I
> need this file?
Just because you are a latex expert does not mean that you don't
> I am not everybody but I've never ever had a look at this file. But I am
> not a LateX expert. But, as Edwin asked, if I was a LateX expert would I
> need this file?
If we are going to keep this file around, InsetInfo simplies the
handling of it. Right now, latex chktex will generate a sed file
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> i not upset, and i think that i am the one being rational here
>
> Shortcuts.lyx would be the first, and may be the last lyx document I
> would print, and put next to my screen when I use lyx.
In this case, it should be a tightly packed cheat-sheet (is tha
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> Instead of having predetermined categories, the first argument of
>> InsetInfo could be an lfun. Then InsetInfo would just invoke this lfun
>> to get the needed information. This means that the information will
>> also be available for other uses (without a
> > But translators can not change this inset in LaTeXConfig.lyx...
>
> Translator will/can write their own version of LaTeXConfig.lyx if they
> chose to. In this case, the yes/no shall be translated.
The inset returns translatable _("yes"), and _("no"), which can be
translated in the po files.
B
> 2/ we do not get the nice triangle between levels
I see. That is a special character \lyxarrow (menu separator), that
can not be displayed in this button, unless we use InsetText, not a
button.
Bo
"Bo Peng" <[EMAIL PROTECTED]> writes:
> But translators can not change this inset in LaTeXConfig.lyx...
Translator will/can write their own version of LaTeXConfig.lyx if they
chose to. In this case, the yes/no shall be translated.
JMarc
Jean-Marc Lasgouttes wrote:
"Leuven, E." <[EMAIL PROTECTED]> writes:
well what is the point of latexfeatures.lyx? first nobody looks at
this.
If you prove this you might have a point. IF.
I am not everybody but I've never ever had a look at this file. But I am
not a LateX expert. But, as
On Wednesday 10 October 2007 16:04:24 Bo Peng wrote:
> > Hmm, not sure this is _really_ useful.
>
> I am not sure either. I guess Jose can make a decision for us.
Not unless I have to. :-) And IMHO are are not there yet.
You can always shoot to the least common denominator and start building
> 1/ we do not get the underlined shortcuts
That belongs to shortcut:LFUN.
> 2/ we do not get the nice triangle between levels
That will not be configurable, but I can certainly use triangles.
> 3/ there is no line breaking possible of the inset and the result will
>look bad on screen.
Tha
> > 2. handle the availability of package, textclass and font...
> > } else if (type_ == FONT_INFO) {
> > // name_ is the class name
> > info_ = LaTeXFeatures::isAvailable(name_) ? _("yes") :
> > _("no");
> > }
>
> This one looks wrong to me.
You may be rig
> > You mean allowing the insertion of this inset from command buffer?
> > Otherwise, I do not see why this is needed.
>
> Yes, also for the benefit of lyxserver. We should allow arguments to
> lfuns as often as possible.
You are right, but when I type info-insert in command buffer, nothing
happen
> i not upset, and i think that i am the one being rational here
Shortcuts.lyx would be the first, and may be the last lyx document I
would print, and put next to my screen when I use lyx.
Cheers,
Bo
> I am not sure why you feel so upset about this feature.
i not upset, and i think that i am the one being rational here
regards, ed.
PS and no, i won't start signing my mails with "napoleon" ;-)
"Leuven, E." <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> And when the documentation is printed?
>
> no, and so what? as long as we have documented where to find the
> info, and as long as it is easily accessible
I think this discussion is becoming irrational. Instead of answering
Jean-Marc Lasgouttes wrote:
> And when the documentation is printed?
no, and so what? as long as we have documented where to find the info, and as
long as it is easily accessible
>> we can then simply add a shortcut in the help menu that shows this log file
>> in the same way we show the latex l
"Leuven, E." <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> No. Having a documentation that is kept up to date when the lazy
>> developers change something without touching the documentation is
>> good. Note also that people who use mac or emacs bindings will
>> appreciate to see
Jean-Marc Lasgouttes wrote:
> No. Having a documentation that is kept up to date when the lazy
> developers change something without touching the documentation is
> good. Note also that people who use mac or emacs bindings will
> appreciate to see the right bindings. A documentation that only sa
"Leuven, E." <[EMAIL PROTECTED]> writes:
> 1. to document the shortcuts it would be enough to write "see
> Tools->Preferences->Shortcuts". time would be better spend
> implementing this.
No. Having a documentation that is kept up to date when the lazy
developers change something without touching
maybe i am misguided, but i must say that this "feature" smells like bloat to
me.
if i understand i well, it is basically used to have shortcuts in the docs and
more easily generate latexfeatures.lyx
1. to document the shortcuts it would be enough to write "see
Tools->Preferences->Shortcuts".
"Bo Peng" <[EMAIL PROTECTED]> writes:
> I might have gone too far. The attached patch fixes a non-gui bug, and
> adds menu:func. That is to say, "menu:math-limits nolimits" would
> yield Edit -> Math -> Change Limits Type -> Inline. :-)
This feature is useful, but shows the limits of the inset:
1
"Bo Peng" <[EMAIL PROTECTED]> writes:
> 2. handle the availability of package, textclass and font...
> } else if (type_ == FONT_INFO) {
> // name_ is the class name
> info_ = LaTeXFeatures::isAvailable(name_) ? _("yes") : _("no");
> }
This one looks wrong t
"Bo Peng" <[EMAIL PROTECTED]> writes:
>> You should also allow to do "info-inset arg".
>
> You mean allowing the insertion of this inset from command buffer?
> Otherwise, I do not see why this is needed.
Yes, also for the benefit of lyxserver. We should allow arguments to
lfuns as often as possib
> > NO. This provides an inset that reveals system information such as
> > shortcut, package and textclass availability, and rc settings.
>
> why an inset?
Because the same document would display different things depending on
system configuration. We store 'shortcut:font-bold' in this inset, and
i
Bo Peng wrote:
On 10/9/07, Edwin Leuven <[EMAIL PROTECTED]> wrote:
does this add a ui to edit the keybindings?
NO. This provides an inset that reveals system information such as
shortcut, package and textclass availability, and rc settings.
why an inset?
This
inset is used in LaTeXConfig.l
On 10/9/07, Edwin Leuven <[EMAIL PROTECTED]> wrote:
> Bo Peng wrote:
> > Forgot the patch.
>
> i missed what this is doing.
>
> does this add a ui to edit the keybindings?
NO. This provides an inset that reveals system information such as
shortcut, package and textclass availability, and rc setti
Bo Peng wrote:
Forgot the patch.
i missed what this is doing.
does this add a ui to edit the keybindings?
Attached is an updated patch that
1. use enum ...
enum info_type {
UNKNOWN_INFO, // Invalid type
SHORTCUT_INFO, // Keyboard shortcut
LYXRC_INFO, // RC entry
PACKAGE_INFO, // Availability of package
TEX
> I am always a bit slow unfortunately. However, I am very interested by
> your patch and I am glad you finally did that.
This dates back to my 'B-F' conversation thread, in which F could not
find any information about shortcuts.
> You should also allow to do "info-inset arg".
You mean allowing
> So, what is the purpose of this inset? Only to display the shortcut or
> also to modify them?
Only to display them. Although it is *very* tempting, and is not
difficult to do (implementation wise), I do not think it is a good
idea to modify shortcuts etc in these insets. Customization belongs to
"Bo Peng" <[EMAIL PROTECTED]> writes:
> My idea about an information inset does not trigger much discussion.
> The attached is an almost complete patch that adds InsetInfo
I am always a bit slow unfortunately. However, I am very interested by
your patch and I am glad you finally did that.
> This
Bo Peng wrote:
On 10/8/07, Bo Peng <[EMAIL PROTECTED]> wrote:
Attached is a more polished patch,
So, what is the purpose of this inset? Only to display the shortcut or
also to modify them? If advantage of displaying it inside LyX is of be
able to generate the documentation automatically, whi
On 10/8/07, Bo Peng <[EMAIL PROTECTED]> wrote:
> Attached is a more polished patch,
That patch can not be applied after Uwe's commit. Attached is an
updated one, with a lyx2lyx fix.
Bo
Index: development/scons/scons_manifest.py
===
-
Attached is a more polished patch, with the additional ability to
display all rc entries using names such as "lyxrc:bind_file".
This improves the documentation and visibility of lyx shortcuts, which
are, to normal lyx users, more important than the customization of
shortcuts.
Jose?
Bo
Index: deve
44 matches
Mail list logo
