On Wed, 15 Nov 2000, Angus Leeming wrote:
> Allan wrote them because he wanted the feedback for the "idiot user".
Actually I wrote them so the input checking could be complete. You don't
have to be an idiot to misspell a directory name or filename and since the
browse buttons weren't working yo
On Wed, Nov 15, 2000 at 05:39:12PM +0100, Lars Gullik Bjønnes wrote:
>
> > Note also, that a writeable file need not yet exist but the directory
> > should be writeable. Allan wrote them because he wanted the feedback
> > for the "idiot > user". I
>
> We don't have idiot users.
But we may in
Will do.
A
On Friday 17 November 2000 14:21, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Clearly, it would be better to allow the colors to be editted
> Angus> without a buffer present.
>
> This is probably an oversight. You can probably cha
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Clearly, it would be better to allow the colors to be editted
Angus> without a buffer present.
This is probably an oversight. You can probably change in LyXAction.C
{ LFUN_SET_COLOR, "set-color", "", Noop },
to
I've tracked down the reason why I can't use:
string const arg = lcolor.getLyXName(lc) + string(" black");
LyXFunC::Dispatch(LFUN_SET_COLOR, arg);
when I'm editing the colors in FormPreferences and LyX has no document open.
About line 488 of Dispatch, there is the code:
/
Angus Leeming <[EMAIL PROTECTED]> writes:
| if( !ReadWriteInfo::ReadableFile(file) )
| std::cerr << ReadWriteInfo::ErrorMessage() << std::endl;
|
| I'll do this anyway and put it into xform_helpers.[Ch]. If you like it, we
| can always move it into support.
|
| Does this mean that you a
On Wednesday 15 November 2000 16:39, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | Note that the new functions are more sophisticated than the old ones. In
> | particular, they can tell you WHY the dir/file isn't read/writeable.
>
> I feel that this is a bit too much o
Angus Leeming <[EMAIL PROTECTED]> writes:
| Note that the new functions are more sophisticated than the old ones. In
| particular, they can tell you WHY the dir/file isn't read/writeable.
I feel that this is a bit too much of hand holding. And they are not
core support functions... I'd say move
good question!
Note that the new functions are more sophisticated than the old ones. In
particular, they can tell you WHY the dir/file isn't read/writeable.
Note also, that a writeable file need not yet exist but the directory should
be writeable.
Allan wrote them because he wanted the feedba
Angus Leeming <[EMAIL PROTECTED]> writes:
| patch2 continues the FormPreferences clean up, but
Why do we want to have:
int IsDirWriteable (string const & path);
bool IsFileReadable (string const & path);
int IsFileWriteable (string const & path);
_and_
(WriteableDir, ReadableDir, Writeabl
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Why not sort on rgb numbers? and also remove "indian red" if
| Lars> "IndianRed" exists and have the same rgb value.
|
| How do you know which one should be removed?
ptt
On Wed, 15 Nov 2000, Angus Leeming wrote:
> Two patches attached.
>
> patch1 is very small. Just a couple of tiny things.
>
> patch2 continues the FormPreferences clean up, but
> it also allows you to change the LyX LColors.
>
> A couple of bugs remain, but I'd be grateful of some help/adv
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Why not sort on rgb numbers? and also remove "indian red" if
Lars> "IndianRed" exists and have the same rgb value.
How do you know which one should be removed?
JMarc
Angus Leeming <[EMAIL PROTECTED]> writes:
| browser. Not a straight alphabetical sort, but into a "rainbow" sort so that
| all names containing "red" ane grouped together, then those containing
| "orange" etc. What do people think?
Why not sort on rgb numbers? and also remove "indian red" if
"
Two patches attached.
patch1 is very small. Just a couple of tiny things.
patch2 continues the FormPreferences clean up, but
it also allows you to change the LyX LColors.
A couple of bugs remain, but I'd be grateful of some help/advice. See the
ChangeLog entry.
Finally, a useability quest
On Tue, Nov 14, 2000 at 02:29:59PM +, Angus Leeming wrote:
> I think Lars would reply "Nada, nada, nada...", but since I've no idea what
> this means I'll just say, "So sue me"!
In portuguese that means:
* nothing, nothing, nothing
or
* swim, swim, swim
Now you choose. ;-)
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I think Lars would reply "Nada, nada, nada...", but since I've
Angus> no idea what this means I'll just say, "So sue me"!
Well, "xform" is a noce name too actually :)
JMarc
On Tuesday 14 November 2000 13:58, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Attached is a clean-up of FormPreferences. Each tab folder is
> Angus> now encapsulated in its own class.
>
> Angus> The patch also activates the various "Browse"
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached is a clean-up of FormPreferences. Each tab folder is
Angus> now encapsulated in its own class.
Angus> The patch also activates the various "Browse" buttons, although
Angus> LyXFileDlg still needs to be modified to make it
Attached is a clean-up of FormPreferences. Each tab folder is now
encapsulated in its own class.
The patch also activates the various "Browse" buttons, although LyXFileDlg
still needs to be modified to make it straightforward to return a directory
if that is what is desired.
Angus
patch.di
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Here is that patch.
Angus> I've simply commented out FL_LIGHTER_COL1. It's not yet used
Angus> anyway. If you can work out how to highlight the active folder,
Angus> it won't be.
Fine. I applied the patch.
Angus> The patch also
Here is that patch.
I've simply commented out FL_LIGHTER_COL1. It's not yet used anyway. If you
can work out how to highlight the active folder, it won't be.
The patch also adds the ability to write any changes to the xforms GUI to
file and to then read them back in next time. LyXLex is very e
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> The Colors tab is now working and, to show you all the fun you
Angus> can have with it, I've given it the ability to modify the
Angus> colors of the xforms GUI. In fact, this is ALL you can do with
Angus> it at the moment; modifyin
Attached is yet another patch to FormPreferences.
I think you'll like this one...
The Colors tab is now working and, to show you all the fun you can have with
it, I've given it the ability to modify the colors of the xforms GUI. In
fact, this is ALL you can do with it at the moment; modifying
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached is a patch that gets rid of the timer. Feedback now
Angus> uses the Preemptive handler instead. Much simpler. The patch
Angus> also finishes off the Converters and Formats tabs. ALMOST. I
Angus> need a little help to finis
On Wed, Nov 08, 2000 at 06:43:08PM +, Angus Leeming wrote:
> Can't yet Apply the Converters because I didn't have time to make Converter a
> "real" class. Ie, it's still static. Perhaps you'd do this, Dekel, as you
> know the code best. (Everything in FormPreferences should be ready; all yo
On Tue, Nov 07, 2000 at 10:23:47PM +0100, Lars Gullik Bj&resh;nnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> | Use
> | struct compare_formats {
> | bool operator()(Format const & a, Format const & b) {
> | return a.name < b.name;
> | }
> | }
> |
> | and then
> | s
Attached is a patch that gets rid of the timer. Feedback now uses the
Preemptive handler instead. Much simpler. The patch also finishes off the
Converters and Formats tabs. ALMOST. I need a little help to finish off, so...
I haven't made use of a functor; if anyone is desperately worried, then
On 07-Nov-2000 Dekel Tsur wrote:
>
> I guess you only use Latin languages, in which case a single keymap suffices.
> But if you want, for example, Hebrew/Russian/English, then you need 3
> different maps!.
>
Well I understood that you have other keymap problems then me and I want
to resolve th
> bool FormatsCompare( Format const & a, Format const & b )
> {
> return( a.name < b.name );
> }
> and then
> sort( formats_vec.begin(), formats_vec.end(), &FormatsCompare );
>
> And something similar for sorting Commands:
>
> bool CommandCompare( Command const & a, Command const & b
> > On 06-Nov-2000 Dekel Tsur wrote:
> > >
> > > I want to add a keymap entry to the languages file, so that the keymap
> > > can automatically change when the language is changed (esp. useful for
> > > multilingual files).
> >
> > I surely don't want this! I have only one keyboard and I want m
Dekel Tsur <[EMAIL PROTECTED]> writes:
IMHO the default keymap for any given keymap should be the default
keymap for the system, if _nything_ else is wanted it should be
configured and decided by the user. i.e. we should not add a keymap
field to languages.
Lgb
| On Tue, Nov 07, 2000
Dekel Tsur <[EMAIL PROTECTED]> writes:
| Use
| struct compare_formats {
| bool operator()(Format const & a, Format const & b) {
| return a.name < b.name;
| }
| }
|
| and then
| sort(formats_vec.begin(), formats_vec.end(), compare_formats());
|
| PS Is there a template for
On Tue, Nov 07, 2000 at 06:42:27PM +, Angus Leeming wrote:
> Well now. I defined
>
> bool FormatsCompare( Format const & a, Format const & b )
> {
> return( a.name < b.name );
> }
> and then
> sort( formats_vec.begin(), formats_vec.end(), &FormatsCompare );
>
> And something simi
Well now. I defined
bool FormatsCompare( Format const & a, Format const & b )
{
return( a.name < b.name );
}
and then
sort( formats_vec.begin(), formats_vec.end(), &FormatsCompare );
And something similar for sorting Commands:
bool CommandCompare( Command const & a, Command cons
On Tue, Nov 07, 2000 at 10:19:19AM +0100, Juergen Vigna wrote:
>
> On 06-Nov-2000 Dekel Tsur wrote:
> >
> > I want to add a keymap entry to the languages file, so that the keymap
> > can automatically change when the language is changed (esp. useful for
> > multilingual files).
>
> I surely do
On Tue, Nov 07, 2000 at 09:39:22AM +, Angus Leeming wrote:
> > why aren't you doing it the way I originally did ? namely
> >
> > int i = fl_get_browser(formats_->browser_formats);
> > if (i > 0) {
> > Format const & f = formats_vec[i-1];
> > fl_set_input(formats_->input_fo
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> sigh... Jean-Marc, I've worked flat out on this stuff for two
Angus> weeks. If anybody feels the need to clean up the code base,
Angus> then they won't find me stopping them. This isn't meant to be a
Angus> flame, just exhaustion!
On Tue, 07 Nov 2000, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Because I sort the list of names (which I store). If I could
> Angus> sort the list of formats by name, then I'd do that instead.
> Angus> Note that the STL is largely unknown t
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Patch attached. Any answers to the questions below? Angus
BTW, do you still want me to apply the patch (since there has been a
bit of discussion)?
JMarc
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Because I sort the list of names (which I store). If I could
Angus> sort the list of formats by name, then I'd do that instead.
Angus> Note that the STL is largely unknown to me and whilst I do have
Angus> reference literature, I f
On Mon, 06 Nov 2000, Dekel Tsur wrote:
> The items in the combox shouldn't have the full path and the kmap
> extension, namely, it should be
> american-2
> american
> instead of
> .../lyx-devel/lib/kbd/american-2.kmap
> /lyx-devel/lib/kbd/american.kmap
Sure. I just wanted to get something wo
On 06-Nov-2000 Dekel Tsur wrote:
>
> I want to add a keymap entry to the languages file, so that the keymap
> can automatically change when the language is changed (esp. useful for
> multilingual files).
I surely don't want this! I have only one keyboard and I want my
keys as they are. If I li
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> I want to add a keymap entry to the languages file, so that the
Dekel> keymap can automatically change when the language is changed
Dekel> (esp. useful for multilingual files).
Except that french users with a qwerty keyboard (all non
On Mon, Nov 06, 2000 at 11:12:08AM +0100, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> I think that you should list all (and only) .kmap files. (But
> Dekel> you can just replace the keymap comboxes by simple text input
> Dekel> buttons, as I am
> (LanguagesXXX): the kbmap choices now contain the files
> sytem_lyxdir/kbd/*.kmap. I think that these choices should eventually
> be replaced by an input with a file browse button, but since the browse
> buttons don'y yet work, this'll do for the moment.
The items in th
Patch attached.
Any answers to the questions below?
Angus
2000-11-06 Angus Leeming <[EMAIL PROTECTED]>
* src/frontends/xforms/forms/form_preferences.fd: Inactive tab folders
are no longer dark. Haven't yet worked out how to lighten the colour of
the active tabfolder. An
On Mon, 06 Nov 2000, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> I think that you should list all (and only) .kmap files. (But
> Dekel> you can just replace the keymap comboxes by simple text input
> Dekel> buttons, as I am going to remove the
>
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> I think that you should list all (and only) .kmap files. (But
Dekel> you can just replace the keymap comboxes by simple text input
Dekel> buttons, as I am going to remove the
Dekel> kbmap_primary/kbmap_secondary variables from lyxrc.)
> I think that you should list all (and only) .kmap files.
> (But you can just replace the keymap comboxes by simple text input buttons,
> as I am going to remove the kbmap_primary/kbmap_secondary variables from
> lyxrc.)
Ok. We're to leave it up to the user to get things right here?. But why are
On Sat, Nov 04, 2000 at 12:48:29AM +0200, Dekel Tsur wrote:
> Few more remarks:
> The converters tab doesn't have a flags field.
> The formats tab is doesn't have a shortcut field.
One more:
The Add button in converters/formats tabs should be named add/change
I do have a question on the behavior
>
> To do list:
> * Colours, Formats and Cnnverter tabs: make functional.
> * Update LyXRC::getDefinitions(). Boo! Hiss!
> * Language kbmaps. Don't load with "list of languages", load with "list of
> available kbmaps". I'm stuck here because I don't know which of the different
> files in lib/kb
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> You mean the RGB struct? Two points: 1. It's tiny. 2. This is
Angus> definitely evolving code. It may be that it's useful to LColor
Angus> too, in which case fine; we'll put it somewhere global. In the
Angus> meantime, think of it
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Please don't apply my former patch. This one implements a RGB
Angus> struct in FormPreferences. All the rest is identical.
Concerning the tab color scheme, it does not look very good to me
(this dark grey is too eye-catching). I'd
On Fri, 03 Nov 2000, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Please don't apply my former patch. This one implements a RGB
> Angus> struct in FormPreferences. All the rest is identical.
>
> I am not sure that I like having this code in fo
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Please don't apply my former patch. This one implements a RGB
Angus> struct in FormPreferences. All the rest is identical.
I am not sure that I like having this code in formpreference. Does it
mean that other frontends will have t
Please don't apply my former patch. This one implements a RGB struct in
FormPreferences. All the rest is identical.
Lars, I take it that you're happy that I have a go at cleaning up LColor?
Angus
On Fri, 03 Nov 2000, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | I
The attched patch adds a converter tab to FormPreferences. It also addresses
some requests from Dekel and Jean-Marc. See bottom.
To do list:
* Colours, Formats and Cnnverter tabs: make functional.
* Update LyXRC::getDefinitions(). Boo! Hiss!
* Language kbmaps. Don't load with "list of languages"
Angus Leeming <[EMAIL PROTECTED]> writes:
| I don't thing the LColor entries need know about the colour name at all. Why
| not just have LColour::color containing a list of coloured elements
| (background, foreground, latex etc) and change LColour::ColorEntry to
|
| struct ColorEntry {
|
On Thu, Nov 02, 2000 at 10:22:35PM +, Angus Leeming wrote:
> Esp. with the Formats (Outputs->Formats). This is the first point: where
> should it go. Formats are for input AND output. Suggestions for the name of a
> new top level tab?
>
> Second point. I shoved in the "Viewers" field with t
On Fri, 03 Nov 2000, Jean-Marc Lasgouttes wrote:
> Angus, I'll apply your patch. Note however that it contains lines
> like
> if( name == "gray0" ) name = "black"
> if( name == "gray100" ) name = "white"
> which probably do not compile better on your machine than it does on
> mine :
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> The colours tab is a shameless copy of an xforms demo. I've
Angus> tried to write it in C++, but I'm a bit of a novice still. All
Angus> feedback welcome.
A few remarks:
- the field showing the resulting color is not visible enou
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached is a patch implementing Colours and Formats tabs. You
Angus> can't actually DO anything with them yet, but I'd like some
Angus> feedback.
Angus, I'll apply your patch. Note however that it contains lines
like
if(
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> oh yes, and I THINK I've fixed the crash problem when closing
Angus> LyX after opening FormPreferences. Could someone check, as I
Angus> can't reproduce the problem here...
Angus, a question: would it be possible to change the fon
oh yes, and I THINK I've fixed the crash problem when closing LyX after
opening FormPreferences. Could someone check, as I can't reproduce the
problem here...
Angus
On Thu, 02 Nov 2000, Angus Leeming wrote:
> > Attached is a patch implementing Colours and Formats tabs. You can't
> actually
Attached is a patch implementing Colours and Formats tabs. You can't actually
DO anything with them yet, but I'd like some feedback.
Esp. with the Formats (Outputs->Formats). This is the first point: where
should it go. Formats are for input AND output. Suggestions for the name of a
new top le
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Attached is a clean-up patch to FormPreferences and LyXRC.
I'll apply it.
JMarc
Angus Leeming <[EMAIL PROTECTED]> writes:
| > Why? you have access to cvs.lyx.org and should be able to do a cvs
| > add, so that you can get new files into the diff/patch?
|
| I do? No one told me!
Remeber that we set this up before you went on some vacation?
You only need to set your passwor
On Tue, 31 Oct 2000, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | When untarred the attachment will contain:
> |
> | PATCH31Oct2000/src/frontends/xforms/xform_helpers.h
> | PATCH31Oct2000/src/frontends/xforms/xform_helpers.C
>
> Why? you have access to cvs.lyx.org and
Angus Leeming <[EMAIL PROTECTED]> writes:
| When untarred the attachment will contain:
|
| PATCH31Oct2000/src/frontends/xforms/xform_helpers.h
| PATCH31Oct2000/src/frontends/xforms/xform_helpers.C
Why? you have access to cvs.lyx.org and should be able to do a cvs
add, so that you can get new fi
Attached is a clean-up patch to FormPreferences and LyXRC.
>From the ChangeLog:
* src/frontends/xforms/xform_helpers.[Ch]: new files. Repository for
useful xforms helper functions. At present contains only formatted().
Input a string and it returns it with line breaks so tha
Jean-Marc Lasgouttes wrote:
>
> > "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes:
>
> Garst> I would still like to see texmf/tex instead of just tex to
> Garst> isolate the ls-R generated by texhash. I brought it up before
> Garst> and you said not for 1.1.4 :) Garst
>
> Why should it
> "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes:
Garst> I would still like to see texmf/tex instead of just tex to
Garst> isolate the ls-R generated by texhash. I brought it up before
Garst> and you said not for 1.1.4 :) Garst
Why should it be isolated?
JMarc
Jean-Marc Lasgouttes wrote:
>
> > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Lars> besides I don't think we should put too many levels of
> Lars> directories in .lyx but rather keep it as flat as possible.
>
> The idea was that there would be several ui files in ui/. A sc
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> besides I don't think we should put too many levels of
Lars> directories in .lyx but rather keep it as flat as possible.
The idea was that there would be several ui files in ui/. A sciword or
msword ui file come to mind.
JMar
On Mon, 30 Oct 2000, Lars Gullik Bjønnes wrote:
> I think you used the wrong name for getFeedback, imho it should have
> been getDescription.
Changed.
> | * feedback is now output via a timer callback loop that is functionally
> | identical to that in Toolbar_pimpl. No longer any need to change
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | * feedback is now output via a timer callback loop that is
Lars> functionally | identical to that in Toolbar_pimpl. No longer any
Lars> need to change an entry to | get feedback. The only items not
Lars> providing feedback ar
Angus Leeming <[EMAIL PROTECTED]> writes:
| Thanks for the various bits of feedback.
|
| Attached is a patch that adds one or two missing variables to
| FormPreferences.
| It also cleans up the existing code:
| * I've moved the various Feedback messages into LyXRC to avoid
| duplication in
I
Thanks for the various bits of feedback.
Attached is a patch that adds one or two missing variables to FormPreferences.
It also cleans up the existing code:
* I've moved the various Feedback messages into LyXRC to avoid duplication in
the other frontends.
* We select the languages using a Combox
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Imho bindings should go into their own file, why they can very
| Lars> well be edited from preferences.
|
| I'll reiterate the opinion that they should go in ui/. THey ar
Angus Leeming <[EMAIL PROTECTED]> writes:
| H! But I can not use the key shortcut #L to "launch" the combox (try!)
| and then use the arrow keys to scroll through it. I can do this with the
| current set up.
Probably missing from the combox code... patches will be accepted.
| This isn't
On Mon, 30 Oct 2000, Juergen Vigna wrote:
> On 30-Oct-2000 Angus Leeming wrote:
> >> Angus, it would be much better to use a combox for the list of
> >> languages (it is too long here).
> >
> > How would using a combox make it shorter? I'm happy to make it a combox,
> > but this just seems to be s
On 30-Oct-2000 Angus Leeming wrote:
>> Angus, it would be much better to use a combox for the list of
>> languages (it is too long here).
>
> How would using a combox make it shorter? I'm happy to make it a combox, but
> this just seems to be style rather than substance.
>
Well have a look at
On Mon, 30 Oct 2000, Jean-Marc Lasgouttes wrote:
> Angus, it would be much better to use a combox for the list of
> languages (it is too long here). Moreover, the old way of using the
> list of languages for kmaps is plain wrong. You should get (in some
> way) the list of available kmap files (eit
Angus, it would be much better to use a combox for the list of
languages (it is too long here). Moreover, the old way of using the
list of languages for kmaps is plain wrong. You should get (in some
way) the list of available kmap files (either hardcoded or from
a text file).
JMarc
Angus> Attached is a patch adding a Languages tab to FormPreferences.
Angus> (Also one or two miscellaneous bits.)
Applied.
JMarc
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Imho bindings should go into their own file, why they can very
Lars> well be edited from preferences.
I'll reiterate the opinion that they should go in ui/. THey are just
another (non-graphical) way for the user to access lyxf
Angus Leeming <[EMAIL PROTECTED]> writes:
| What to do with individual bind keys?
| Eg \bind "Delete" "delete-backward"
| \bind "F12" "language french"
Imho bindings should go into their own file, why they can very well be
edited from preferences.
In the preferences file we store the "main" bin
On Fri, Oct 27, 2000 at 05:56:48PM +0100, Angus Leeming wrote:
> Outputs->Exporters.
> \converter
>
> Outputs->Viewers
> \viewer
You also need \format
> Inputs->Importers
> \converter
Note that currently there is no difference between converters used for
exporting and conve
Attached is a patch adding a Languages tab to FormPreferences. (Also one or
two miscellaneous bits.)
Below is a list of all the lyxrc variables that are not yet set by
FormPreferences. I've grouped some of them in the tabs that they'll end up
being set in.
Colours Tab
Ability to set
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I haven't found a way of getting a callback when clicking the
Angus> mouse on an input box. Only when altering the contents. This
Angus> isn't ideal, as it means that you get feedback for these inputs
Angus> only by altering the te
On Fri, 27 Oct 2000, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> FormPreferences is now much more user-friendly as it has
> Angus> Feedback and Warning messages. It's also more coder-friendly as
> Angus> it's now modular. Modules are based on
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> FormPreferences is now much more user-friendly as it has
Angus> Feedback and Warning messages. It's also more coder-friendly as
Angus> it's now modular. Modules are based on tabs, so it's easy to
Angus> folllow the flow of the code
My last patch appears to have got lost but no worries. It's superceeded by
this one.
FormPreferences is now much more user-friendly as it has Feedback and Warning
messages. It's also more coder-friendly as it's now modular. Modules are
based on tabs, so it's easy to folllow the flow of the cod
94 matches
Mail list logo
