> If you are proposing a totally different approach, you need to show
> that why your approach is better than mine, and convince others to
> stop my attemp in the next few days, with maybe a plan to implement
> yours by yourself.
No, no, that's not how is goes! Your embeddeding code has been removed after a long discussion and
it took some time to fully polish it out. It turned out that the embedding issue is critical and
needs a lot of testing. According to our release plan we are short before the first beta and there
are so many other things to do to finish LyX 1.6.0.
So when you want to work on the embedding stuff, please do it in a separate branch that can be
merged with trunk after LyX 1.6.0 is out.
We have to stop implementing new features now! There is live after LyX 1.6.
Besides this, your approach is very rude: Say something against me or I'll shove it in. Why do
others need to be conviced that you stop actions? Setting others under pressure is not acceptable.
The embedding issue is without a doubt critical, so the wise decision is to be careful with it and
take some time discuss things.
Uwe
p.s. While I thinking about the last development cycle, listings comes into my mind. This feature
was an example what happens when a feature is put in late and without good enough testing. What I
still miss is that one can insert/enter tabulators to listings fields. I have spoken to some
informatics guys recently who told me that the current listings implementation is not very useful as
many programming languages use tabs, but LyX don't support them.
