You can create a working set to build specific things.
Select Project -> Build Working Set -> Select Working Set -> New -> Java ->
Next ->
then select your project from the list pane on the left.
Add - give it a name -> Finish
then make sure you select your new working set item on exit of this process
you can then select project -> build and build working set -> your working
set name
----- Original Message -----
From: "Brian Conrad" <[email protected]>
To: <[email protected]>
Sent: Monday, July 19, 2010 6:22 PM
Subject: Re: [android-discuss] Re: Smartphone Noobs
I was Technical Director for Maxis Software and Publishing Director for
Sims Titles (before they were a part of EA). So much of my design
experience comes from that period and how we tried to keep support costs
down by making the use of the programs as obvious as possible. In a couple
of my programs there is a splash screen with button for the things people
will want to do with the program. I've just added a menu to those that
basically tells the user the settings are on the displays where naturally
those setting will effect the display.
Also like EULAs people don't read Help. So I still over the years get
support questions people haven't even bothered to look at the Help where
it was clearly answered. I also have a real-time online help in my
Android programs where issues can be covered as they come up.
BTW, does anyone know how to keep C projects from running make in Eclipse
as you're building Android ones? I've done some searches but have found
nothing so far. Must be a setting somewhere.
Maps.Huge.Info (Maps API Guru) wrote:
All I can say is it is best to write software with the "lowest common
denominator" approach. The people at the bottom of the technical food
chain are the ones who are going to give you the most trouble, so it's
best to make sure you have them covered in any help text and
documentation. They are also more likely to be a bit more grumpy and
have less patience, so it is worth the extra effort to make sure they
can find the answers to their questions without a lot of anguish.
It's really helpful to have friends and relatives who fit that
category, people you can sit down with the software and have them go
through the operation. Watching them quietly will teach you a lot
about what you didn't cover. If Grandma can run your program without
trouble, then most likely 95% of the likely users are going to as
well. Regardless of what you do, you can't get the last 3% to 5% of
users to behave, but that's the way it is when dealing with the
general public.
My app "Radar Now!" requires location services to run and if they
aren't switched on, a hard to miss message pops up explaining this
issue. If only one of the location services is active, a toast pops up
saying which isn't active. Regardless of this fact, I get e-mails from
people all the time saying my program doesn't work, after some back
and forth with them, it becomes obvious they simply didn't read the
message and instead assumed it didn't work. Usually after I explain
this to them along with the simple steps required to start up location
services, they get it to work.
An old saying comes to mind with these situations:
"You can lead a horse to water but you can't make him drink."
a corollary:
"You can issue messages to a user but you can't make them read."
-John Coryat
-John Coryat
--
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
