> -----Original Message----- > From: Markus Karg [mailto:k...@quipsy.de] > Actually the problem is that it is impossible to learn from the WiX > documentation / MSI documentation that what we actually want is just > impossible, due to two facts:
I wouldn't say it is impossible. Many, many people before you learned from the WiX and MSI documentation because they had to. I might say that it is difficult. I still can't grok the MSI documentation. The WiX documentation is very incomplete in certain areas but I'm not a technical writer so I very little to offer to improve that aspect of the project. The community provided tutorials have helped me as much as they've helped others. I have a different learning style. These are all my experiences and apply to me alone. I cannot make any objective and absolute conclusions that would apply to the rest of the community. > (a) Both documentations are in part wrong and incomplete which we > already discussed several months ago in different threads (please don't > discuss this again -- it *is* true as some of our older complains ended > up in improvements and additions of the docs already, which proofs my > thesis). So sometimes one just has to ask, even when you have read and > understood what the docs say. Again, difficult is different from impossible. Your use of the word impossible before makes it very difficult for me to actually listen to you. > (b) In the past 25+ years of coding (yes, I'm one of that old guys with > long beards) I often stumbled about the fact that things *are* possible > even if the docs do not tell. You won't learn about that until you ask > (it might be random that it works on your machine when just trying > out). Ask the community for confirmation that what you found is possible and/or supported. Perhaps what you found _is_ a bug. But wait, you didn't find an undocumented feature, you demanded a solution from the community because you didn't want to implement it yourself from scratch. > Also, not all companies can afford people to invest weeks to find out > things others already discovered as being impossible. It is of no > additional value. Maybe someone else knows for sure that it is > impossible, so you spare lots of time and money when just asking. > > See, not everybody is asking because he's dumb, lazy, or both. > Sometimes asking is the better approach to RTFM (especially if you > already HAVE RTFM multiple times, invested lots of time, and still did > not find the answers). You _did_ find the answer and we confirmed what you found. Instead of asking for confirmation you asked for a handout. > I understand all what you say, but see, in other forums (and I am > writing *and answering* in lots of them, especially in the Java field) > it is *not* wanted that people post lots of source code and lenghty > explanations what already tried out. So we abstained from doing here. > You're right, it would be clearer what we liked to know. So next time I > will post the complete story so that nobody of you might think that we > are dumb or lazy and we can prevent senseless discussions about forum > ethics like this one. > > BTW, it is not very nice to write "start to think" when just *assuming* > a dumb or lazy guy. I would always prefer not to assume dumbness or > lazyness, since it leads to flame wars in the end. I can't judge you on what you do or do not do on other forums as I'm not a part of them. I can only judge you based on how you behave in this forum. Two people in this community lost their patience because of the way you asked for help. This problem is not unique to you. Too many people do not do their homework before posting on the mailing list and when they do post they do not word their questions with enough information to provide context and validate that the pre-requisite homework has been done. It was unfortunate that you got singled out in this particular instance but this entire thread should be reminder to everyone that (myself included) that we need to be smart about how we ask _and_ answer questions. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
