I agree with some of your comments, especially doing research first, but still think it was pretty harsh - especially since he was indeed asking for best practices, not just "how do I print?". And only typing, "RTFM: Print Job", unless used in a humorous way, is pretty mean no matter how you like to spin it and think its not. I think you could have instead replied with something like, "In the help files, just look up: 'Print Job'' or 'search on Google for Flash and Print" would have made your point pretty clearly to him that he could do some more research and find his answer instead.
Anyway, I don't want to clog up the list anymore with banter, but I will say, that MIT teddy bear is a great idea. I sometimes realize the answer to my question as I take a break away from my desk or write the question out in an e-mail to Flashcoders, and end up not posting it. Jason Merrill >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] Behalf Of Steven >>Sacks >>Sent: Tuesday, February 21, 2006 9:48 PM >>To: 'Flashcoders mailing list' >>Subject: RE: [Flashcoders] HOW TO: Print a MC - first try. >> >> >>> Steve, I hope you take this in the tone it was intended >> >>Well, I felt his first question was worded in a way that made >>it seem that >>he didn't know about PrintJob. A quick look in the help >>panel or google >>would have helped him on his way. >> >>This is true for any issue people are having. There is built-in >>documentation (which can be lacking, I know), there is >>google, and there are >>the flashcoders archives. All of these resources are >>available for people >>before they ask simple questions on basic actionscript ("How >>do I duplicate >>a movieclip?" would be another RTFM question). >> >>RTFM is not necessarily said with malice or ego. Regardless >>of the presence >>of the F, it's just the accepted acronym as I'm not sure I've >>ever seen RTM. >>I wasn't being malicious in my curt reply. I passed on the >>important piece >>of information (PrintJob) that was needed to focus his >>search. If I just >>said RTFM and that's it, then yeah, I'm a dick. But, I >>pointed out what the >>term he needed to look up was, and that it was in the >>(freakin) manual. >> >>> Maybe he never realized PrintJob was in the manual >> >>Not directed at Corban specifically here, but that's no >>excuse for anyone. >>Flash comes with searchable documentation. Open the help >>panel, click on >>the search icon, type in "print" and it is easily found. >>Open google and >>search for "printing in flash" and the second result returns >>a tutorial and >>more detailed information. It takes little effort to do some legwork >>yourself first. If you come up with zilch after that and you're still >>having an issue with your code, post it up to Flashcoders. >> >>In the end, Corban was having a specific issue and when he >>posted it, I was >>able to help him, and happily so. Funnily enough, one of the >>answers to his >>questions (the size issue and the way flash draws pixels) was >>something I >>read on the second link on Google when I did that very search >>as an example >>for him that there was information out there on printing in >>Flash. And this >>is my point. If you take the time to do a little research >>yourself, you >>will learn something a lot faster than if you ask the list >>and wait for a >>response. Again, this is not specific to Corban. >> >>When I wanted to print landscape in portrait using PrintJob, >>I searched the >>Flashcoders archives first and found nothing. Then, I >>searched the web and >>found a solution. Ended up it was extremely wrong and it >>took me awhile to >>figure out why. Now, I understand PrintJob a lot more than I used to >>because I was forced to play around with it (and I found out >>that the class >>has some undocumented bugs with printing scaled/rotated clips >>that require >>workarounds). When I figured it all out, I posted my results >>to Flashcoders >>for the specific purpose of having something on the subject >>in the archives >>for those who follow behind me, including linking to what >>google returned >>and why it was wrong, just in case somebody searched for the >>solution like I >>did. >> >>If your intent is to not scare off new coders from asking >>questions here, >>that's fine and good but new coders should also learn how to >>do their own >>research first. It will only benefit them to learn how to be more >>resourceful. Have you heard the fable about the computer lab >>at MIT? It's >>been said they have a teddy bear there that you must explain >>your problem to >>in full before you ask the staff member in the lab. The >>lesson is that >>often you will solve your own problem by talking it out >>first. Google can >>be your teddy bear, too. >> >>_______________________________________________ >>[email protected] >>To change your subscription options or search the archive: >>http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >> >>Brought to you by Fig Leaf Software >>Premier Authorized Adobe Consulting and Training >>http://www.figleaf.com >>http://training.figleaf.com >> NOTICE: This message is for the designated recipient only and may contain privileged or confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this e-mail by you is prohibited. _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
