Lars Gullik Bjønnes wrote:
But we should require more of the people that actually want this to do the work.
I did write that batch-file. The total work to do a shell-script from scratch would be more work than using the batch-file that was there.
You are right that I do not send polished patches that are ready to apply. I do not have the time to do that, but I do play ball. From time to time, I kick a ball towards where I'd like LyX to move, and luckily there are friendly players that sometimes take the ball and score.
Most of the time, we are playing towards the exact same goal: The windows work also benefits Unix LyX. The spaces-in-filenames issue is also a Unix issue, and similar with other improvements that originate from the Windows work.
Yes, sometimes there is extra work done on the Windows side which does not directly benefit Unix LyX. But indirectly, I maintain that even those things help Unix LyX. The goal is just bigger now, so it is easier to score.
A winning team attracts more talent. The better Windows LyX is, the more potential for talented contributors. Look at the traffic now on this list. I believe half of it is Windows related.
The main barrier right now for C++ contributions from the Windows crow is the ridiculous compile times for 1.3.x on Windows. This problem disappears with 1.4.x LyX, since that compiles with MSVC, which is faster than Unix gcc. (Maybe Rob could try to get 1.3.x to compile with MSVC?)
I find it absurd that we should start obstructing things for ourselves by demanding that contributors are only allowed to go for themselves and score all on their own. It is so much more fun to play on a team.
Regards, Asger
