Ozgur Ugras BARAN wrote:
> On 9/30/06, Georg Baum
> <[EMAIL PROTECTED]> wrote:
>> This is a specialization, but I think we should keep it generic and
>> simple. InsetCommandParams would just store a number of parameters, and
>> the LaTeX command generated from then would simply be
>> \command{param1}[optparam2][optparam3]{param4} etc.
>>
> Ah.. What I intended to do here is introduce a new base class
> (insetparams maybe..). Then one can extend his/her specific params by
> applying new keys_. Index is just an example here and I really didn't
> think about if this is applicable or not. I just open a door for
> specific implementations. If you find it too fantastic, feel free to
> drop all keys and maps from the code.
> - Show quoted text -
> Actually we don't.. I just prefer listed keys for maintainability.
Me too. The problem is that many LaTeX commands do not get their parameters
via the keyval package, but have a predefined parameter order. But as I
outlined previously, we can use the order for LaTeX and have keys at the
same time for LyX. Then we do not need to deal with the order in insets
anymore (except in the constructor), and can always get and set a parameter
by key. The difference to your current implementation is that we do not
have some parameters with keys and some with order, but all parameters have
an order and a key.
Do you want to create another version that does this? I think I got now a
clear picture how it could work with the help of your discussions, so if
you don't want I can also do it.
>> Then you should get a decent editor that does not fight you in
>> maintaining indentation etc, but helps.
>>
> Kate.. decent enough I guess.
Yes, it is quite nice.
> Well, I know how to use svn, just I was too lazy to track down the
> changes for more than 200 diffs. But I did!!! The error is introduced
> with revision 15068.
I see that you found the bug in the meantime, that is great.
> I really like to correct the bug, but i guess this dispatch issue is a
> bit too complex for a newbie like me. If you have any documentation
> about how this mechanism works (and worked before), then I can give it
> a try..
I do not know too much about it, but I think it is not needed anymore.
Georg
