Support guidelines are already available. They're not that hard to find on our
Web pages. Developers starting at:
<http://www.palmos.com/>
can click on the "Developers" button to get to:
<http://www.palmos.com/dev/>
This page includes a "New Developers:Getting Started" link, which takes you to:
<http://www.palmos.com/dev/started/>
There's a lot of good starting points there. Developers can also click on the
"Support" item in the Quick Index, taking them to:
<http://www.palmos.com/dev/tech/support/>
That page gives many, many support options. The last link on the page --
"Technical question checklist" -- takes you to this page:
<http://www.palmos.com/dev/tech/support/questions.html>
This page attempts to make sure that you've covered all the self-help options
before submitting a question to an actual human being or, failing that, a
Development Support engineer.
However, I will grant that Brian's suggested list includes some items not found
on any of those Web pages. Perhaps his ideas can be incorporated into those
pages.
-- Keith Rollin
-- Palm OS Emulator engineer
"Richard Hartman" <[EMAIL PROTECTED]> on 08/03/2000 10:05:06 AM
Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent by: "Richard Hartman" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
cc: (Keith Rollin/US/PALM)
Subject: Re: To beginner programmers (was Re: This is not fair)
Something like this -- newsgroup guidelines --
should be posted by the list manager on a regular
basis ... bi-weekly?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Brian Mathis wrote in message <19774@palm-dev-forum>...
>
>Maybe it's time for a repost of this:
>---------------
>
>I hope I can offer some advice. Some of these may be obvious, I'm not
>trying to be insulting, but I run into this type of stuff all the time
>when helping with Perl problems.
>
>
>1. Read the messages here, all of them. Some things may not make sense
>at first, but the more you pay attention, the more things fall into
>place. You may be working on something 3 months down the road, and
>you'll remember "I've seen this somewhere before". Then you can search
>the archives for the answer. This brings me to #2.
>
>2. Use the archives. There are 2 web searchable archives of this list.
> http://www.escribe.com/findgroup.html?query=palm
> http://www.egroups.com/list/palm-dev-forum/info.html
>
>3. Put forth a serious effort to solve something first. Don't run to
>the mailing list every time you have a problem. Figuring it out by
>yourself will teach you much more than just the one thing you're
>searching for.
>
>4. If you have a doubt about if something will work or not, write a
>small test app and try it out. If you're using POSE, you really can't
>hurt anything (of course, you're using POSE to develop already, right?
>:) Don't be afraid to experiment.
>
>5. When the time comes to ask a question, try to be as informative as
>possible about the situation. "It doesn't work" doesn't help us or you
>at all. Something along the lines of, "I am trying to accomplish <this
>task>. I think the best way to do it is <this way>. Here's the code
>I'm using to do it. I'm expecting it to do <this>, but it seems to be
>doing <that> instead. I'm using [code warrior | gcc] on [windows | mac
>| unix] and targetting for PalmOS version ## using SDK version ##."
>
>6. If you get stuck on something, take a look at the source code for the
>built in apps that's included with the SDK. It helps a lot. There are
>also other various source examples around.
>
>
>Well, there's a laundry list for you. :) I hope that helps, and have
>fun getting into it.
>
>
>--
>Brian Mathis
>Direct Edge
>http://www.directedge.com
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
