soa,
Though I agree with you completely that, whether in nature or fink, one has to learn their own lessons and that no truly worthwhile knowledge comes for free
, I really think many basic concepts of running X on X are far too muddled under unnecessary layers of complexity. NOBODY presents them clearly.
Gee, now that I think of it, the same applies not just to gardening, but to understanding women <pc>or men, depending on your gender/preference</pc>.
Actually, I think I have a better analogy. I just spent a week building a model sailboat with really lousy and confusing instructions. I spent far too much time simply trying to interpret the poorly written instructions than in actually building the boat.
Any way, it is nice to see that someone like you is working on this. As someone who paid his X dues (long time Mac user obsessed with running X on OS X and learning about the whole new world available through our new OS...) here are just a few things I think could be improved for new users, though I am not saying I have the best suggestions on how to do that.
1. Simply explain the difference between binaries and source code - binaries are like buying a bicycle that is all put together while source code requires assembly.
2. Clearly explain Xwindows and window managers without all the client - server terminolgy - at least at first. How about some diagrams? A picture is worth 1000 words (or 10,000 links on sourceforge).
3. Clearly explain all the things needed to run X on OSX and what each one does.
A. Fink to go get and install available software.
B. XDarwin to actually run the installed X environment.
C. Your .cshrc file to tell XDarwin where your Xwindows stuff is.
D. Your .xinitrc file to tell XDarwin what window manager to use.
4. The dselect UI is not good. NOT because it is a terminal app - I don't believe terminal apps are a bad thing at all - I just think it can be very confusing to non *nix users. P.S. I don't think the graphic fink app is much better.
Any way, I just think it is more productive to get people up and running without all the pain and frustration - they can still learn something and the basic concepts involved are really not too complicated. I just don't accept the whole "you have to pay your dues thing" when so much of it is due to plain old confusing language and terminology. So much of getting X to run on a Mac is like asking someone to guess a secret handshake. If people want it to be an elitists club, than we are right on track, but if the idea is to get more users (and thus more apps and support from developers), improvements need to be made. I'm looking forward to your Fink beginners guide.
P.S. I work in usability and a really good test of anything is to run it by at least one new user. May I suggest you do this with your guide and then act on any feedback from these users - what was clear and what was not clear... Thanks!