I agree with you Philip! I have been wanting to write a similar email for a
while. I would love to help develop LyX. In fact, I learned C++ with that
being my primary purpose. But I am still lost when trying to navigate the
code.
I would love for some of the experienced developers to maybe document all
of the steps in particular bug fixes... For example,
1. I knew I had to look in xxx.cpp because... (e.g. I did a grep using the
phrase "yyy")
2. Then I went to the line containing the word xxx
3. Because xxx is of class yyy, I went to yyy.h
4. etc.
Even though every bug is so special, I think that we could learn a lot by
following such documentation.
Thank you!
Xu
2011/10/29 PhilipPirrip <p...@net.hr>
> Hi Vincent. Thanks for the reply. One day I hope there would emerge a sort
> of an overview of the whole code, to help the new beginners.
> I'm sure that making inset by coping some other shouldn't be that hard.
> But then it comes to all sorts of things that are interconnected
> (translations, input encodings, spell-checking), and it gets harder to
> understand them all. For example, what would need to be changed if I just
> introduce \begin{otherlanguage}{xyz} \end{otherlanguage} as the environment
> of the inset? This pair is not present now in LyX (but there's a similar
> polyglossia pair, yes). What if I want to disable foreign language
> underlining for that inset? How to tell the spell checker that the inset is
> using some other language?
> ...
>
>
>
> First of all, be sure that people think that a "foreign language inset"
>> is useful. Otherwise, it might be a waste of your time implementing
>> something that may not be used.
>>
>
> I've just tried to convince Richard on that, please take a look at
> http://www.lyx.org/trac/**ticket/7848<http://www.lyx.org/trac/ticket/7848>
> .
>
>
>
>
