As promised, here is my wishlist for mobile:
* I want to be able to mark as complete todos from the home page.
o My first attempt was to put a very short form on the mobile
home page that marks a todo complete with one click. I
experimented with this a bit, but haven't been able to make
it work. It is a little over my head and I anyone has
suggestions on how to do it, I would love a pointer or two.
My attempt was to:
+ drop a form_tag into line 2 of _mobile_todo.rhtml that
copied from the form_tag in show.m.erb
+ add a hidden input of "done" modeled after the
check_box_tag in _edit_mobile
+ and last a image_submit_tag to use a clickable image
to submit the form instead of a button
o but, so far, it hasn't worked. I was getting errors like:
"ActionView::TemplateError (undefined method
`stringify_keys' for false:FalseClass) on line #3 of
app/views/todos/_mobile_todo.rhtml:" My form was not
passing the right stuff into the controller I suppose.
* I want to be able to click on the Done? checkbox on the edit form
and have it just submit the form from there. if it is done, get
it out of here. I actually had it working for a while when I
broke it and I am not sure why. I added an "onclick="(if
done.checked) done.form.submit()"" to the new mobile.js. I think
I need to know the name of the form, but it seems to be not set or
is a string based on the id of the individual todo. I tried
making functions and calling them, embedding them in the checkbox
html, but I am not sure why if I had it working that I can't get
it back. If I could get idea above to work, this would not be as
important, but still might be useful from time to time.
* Last, I would like to be able to quickly set due dates / show from
dates for todos. As it is, it is way to many clicks. I typically
leave it blank and go back later (or not) and set it on a full
browser. click, scroll, click for the day; click scroll click for
the month; and click scroll click for the year. Way too much
clicking. six clicks and three scrolls. My thought is to create
some buttons, similar to the choices on the full interface. One
to set the date select to today, one for tomorrow and one for a
week. I would do this for both date fields. The select date drop
downs would still be there...
* Finally, drop a second submit button at the bottom of the form too
so you don't have to scroll to back to the top if you had gone
down to set a date... I had two at one point, but suspected it
was the reason I had broken my checkbox submit js...
These are my ideas. I would welcome yours as well. If you have
suggestions, I am all ears!
- Tim
On Sat, Mar 20, 2010 at 9:58 PM, Tim Madden <[email protected]
<mailto:[email protected]>> wrote:
I wanted to start a discussion about the future of our mobile
interface with the group and solicit some feedback.
First, the mobile version is a great asset to have. The interface
is super lightweight, clean and works universally (more or less).
However, the mobiles that are in the pockets of many tracks users
today, likely most, have browsers capable of much more. Every
"smartphone" and many non-"smartphones" support some level of
javascript. However, if you visit the mainline tracks interface
on your smartphone, the experience is comprised. I happen to use
a blackberry (and we used to have an ipod touch, but the kids
fried it) and it works but much of the javascript goodies are lost
and this actually limits the interface's usefulness. For example,
autocomplete and javascript powered drop down menus among others
(at least on my blackberry) do not work.
So my thought is we need some happy medium between the two.
Something with some basic javascript for things like ticking off
completed actions while respecting the expected screen resolution
of ~320px wide. It should avoid drop down menus and the add and
edit form probably need to be left to a separate page instead of
region of the page or an overlay on the existing page.
The question I have is what path offers the least resistance to
achieve this goal? (We must be realistic. This is an open source
project after all. We may have big dreams, but we also have small
time budgets to contribute!) One path would be to take the
existing mobile interface and layer in some of the important
javascript goodness we want... Alternatively, we could clone the
rich interface and dumb down the javascript to the essentials and
slim the width of the interface to an arbitrary goal ( say 320px)?
Maybe there are tools to use I am unaware of??
Let me know if you have input on the idea. I am willing to take a
run at a development branch, but wanted to gather some opinion first,
Thanks, Tim
_______________________________________________
Tracks-discuss mailing list
[email protected]
<mailto:[email protected]>
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
