From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Jones <bsdmatburt@gmail.com>
Subject: Re: Re: MobileOrg for Android starts to become really usable
Date: Sun, 30 May 2010 19:33:55 -0400
Message-ID: <AANLkTin_U_Ynp7TYdePoP66rPRrgAM5ZCgnovs2oepCS@mail.gmail.com>
References: <87sk5cwg4f.fsf@gmx.ch> <1275071226.14727.8.camel@localhost>
	<loom.20100530T181754-367@post.gmane.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0718534315=="
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=53994 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OIs1K-0007tJ-94
	for emacs-orgmode@gnu.org; Sun, 30 May 2010 19:34:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <bsdmatburt@gmail.com>) id 1OIs1I-0005cx-Fb
	for emacs-orgmode@gnu.org; Sun, 30 May 2010 19:34:18 -0400
Received: from mail-vw0-f41.google.com ([209.85.212.41]:60835)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <bsdmatburt@gmail.com>) id 1OIs1I-0005cm-97
	for emacs-orgmode@gnu.org; Sun, 30 May 2010 19:34:16 -0400
Received: by vws13 with SMTP id 13so4125696vws.0
	for <emacs-orgmode@gnu.org>; Sun, 30 May 2010 16:34:15 -0700 (PDT)
In-Reply-To: <loom.20100530T181754-367@post.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Robert Goldman <rpgoldman@sift.info>
Cc: emacs-orgmode@gnu.org

--===============0718534315==
Content-Type: multipart/alternative; boundary=000feaee5824a196030487d82df0

--000feaee5824a196030487d82df0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

With regard to the note capture display, I'm not sure how I feel about
this... I like having the save button on the page because it reduces the
number of clicks to save the note which can be huge if you are just trying
to quickly jot something down.   I do, however, need to fix it so that the
Save button is always visible.    The thing about this particular Activity
display is that the text box is always fixed to some percentage of the
display... so that the save button would never be off the page but rather
the Text box would scroll if you had too much text in it.   I may consider
adding the save button to a menu once I add more options to the Capture
screen (like adding a TODO flag, or Tags) but I think it's most intuitive i=
f
the save button is on the display.... mainly because you can't miss it, som=
e
things about Android happen in the background so that if you navigate away
from the page it automatically saves the contents... but that's not how thi=
s
capture page works (and I don't know that I would want it to automatically
save if you hit the back button) this allows it to fit into the workflow an=
d
makes it obvious that you have to hit the save button to accomplish the sav=
e
action.     These are just my thoughts.   As I bake out the Capture system =
I
will certainly revisit it if the flow works better to have it under the
'Menu' action.

73,
Matthew W. Jones (KI4ZIB)
http://matburt.net


On Sun, May 30, 2010 at 12:21 PM, Robert Goldman <rpgoldman@sift.info>wrote=
:

> julien cubizolles <j.cubizolles <at> free.fr> writes:
>
> >
> > Le vendredi 28 mai 2010 =E0 11:05 +0200, Sven Bretfeld a =E9crit :
> > > Hi to all, hi Matthew
> > >
> > > I can say that Note capturing works on my HTC
> > > Magic,
> > Working also on my LG GW620, however the SAVE Button gets hidden by the
> on-screen keyboard.
> > I think I've seen other android apps keeping some buttons visible
> > whether the keyboard is or isn't displayed.
>
> If I might comment --- one of the worst things about Android applications=
,
> IMO,
> is the way they are confusing about whether menus should be displayed in
> page,
> or invoked by the menu button.
>
> I'd urge you to avoid the on-page display in favor of the menu button.  I=
f
> you
> stick to that the user never needs to remember to scroll down to find the
> controls and there are just too many ways for the on-page display to be
> rendered
> either hard to reach or completely inaccessible.  This problem is made
> worse
> (especially by contrast with the iPhone) because you don't have full
> knowledge
> of the screen dimensions.
>
> So I'd suggest that if a button is important (save, send, schedule, etc.)
> that
> you make it reachable by the center menu button.
>
> HtH,
> cheers,
> r
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

--000feaee5824a196030487d82df0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8">Wi=
th regard to the note capture display, I&#39;m not sure how I feel about th=
is... I like having the save button on the page because it reduces the numb=
er of clicks to save the note which can be huge if you are just trying to q=
uickly jot something down. =A0 I do, however, need to fix it so that the Sa=
ve button is always visible. =A0 =A0The thing about this particular Activit=
y display is that the text box is always fixed to some percentage of the di=
splay... so that the save button would never be off the page but rather the=
 Text box would scroll if you had too much text in it. =A0 I may consider a=
dding the save button to a menu once I add more options to the Capture scre=
en (like adding a TODO flag, or Tags) but I think it&#39;s most intuitive i=
f the save button is on the display.... mainly because you can&#39;t miss i=
t, some things about Android happen in the background so that if you naviga=
te away from the page it automatically saves the contents... but that&#39;s=
 not how this capture page works (and I don&#39;t know that I would want it=
 to automatically save if you hit the back button) this allows it to fit in=
to the workflow and makes it obvious that you have to hit the save button t=
o accomplish the save action. =A0 =A0 These are just my thoughts. =A0 As I =
bake out the Capture system I will certainly revisit it if the flow works b=
etter to have it under the &#39;Menu&#39; action.<div>

<br clear=3D"all">73,<br>Matthew W. Jones (KI4ZIB)<br><a href=3D"http://mat=
burt.net">http://matburt.net</a><br>
<br><br><div class=3D"gmail_quote">On Sun, May 30, 2010 at 12:21 PM, Robert=
 Goldman <span dir=3D"ltr">&lt;<a href=3D"mailto:rpgoldman@sift.info">rpgol=
dman@sift.info</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">julien cubizolles &lt;j.cubizolles &lt;at&gt; <a href=3D"=
http://free.fr" target=3D"_blank">free.fr</a>&gt; writes:<br>
<br>
&gt;<br>
&gt; Le vendredi 28 mai 2010 =E0 11:05 +0200, Sven Bretfeld a =E9crit :<br>
&gt; &gt; Hi to all, hi Matthew<br>
&gt; &gt;<br>
&gt; &gt; I can say that Note capturing works on my HTC<br>
&gt; &gt; Magic,<br>
&gt; Working also on my LG GW620, however the SAVE Button gets hidden by th=
e<br>
on-screen keyboard.<br>
&gt; I think I&#39;ve seen other android apps keeping some buttons visible<=
br>
&gt; whether the keyboard is or isn&#39;t displayed.<br>
<br>
</div>If I might comment --- one of the worst things about Android applicat=
ions, IMO,<br>
is the way they are confusing about whether menus should be displayed in pa=
ge,<br>
or invoked by the menu button.<br>
<br>
I&#39;d urge you to avoid the on-page display in favor of the menu button. =
=A0If you<br>
stick to that the user never needs to remember to scroll down to find the<b=
r>
controls and there are just too many ways for the on-page display to be ren=
dered<br>
either hard to reach or completely inaccessible. =A0This problem is made wo=
rse<br>
(especially by contrast with the iPhone) because you don&#39;t have full kn=
owledge<br>
of the screen dimensions.<br>
<br>
So I&#39;d suggest that if a button is important (save, send, schedule, etc=
.) that<br>
you make it reachable by the center menu button.<br>
<br>
HtH,<br>
cheers,<br>
<div><div></div><div class=3D"h5">r<br>
<br>
<br>
<br>
_______________________________________________<br>
Emacs-orgmode mailing list<br>
Please use `Reply All&#39; to send replies to the list.<br>
<a href=3D"mailto:Emacs-orgmode@gnu.org">Emacs-orgmode@gnu.org</a><br>
<a href=3D"http://lists.gnu.org/mailman/listinfo/emacs-orgmode" target=3D"_=
blank">http://lists.gnu.org/mailman/listinfo/emacs-orgmode</a><br>
</div></div></blockquote></div><br></div>

--000feaee5824a196030487d82df0--


--===============0718534315==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

--===============0718534315==--