svijee / taskwarrior-androidapp Goto Github PK

This message arrived through Google Play Developer Console:

Occurs in settings trying out new database selection. The default data loads great, but as soon as I hit 'Database' the app hangs for a second and crashes. I use the same databases and they work fine on my phone (samsung galaxy nexus) with the new feature, but the app crashes on this tablet (samsung note 10.1). Thanks for the app, I wish I could contribute more.

Stacktrace:

java.lang.IllegalStateException: ListPreference requires an entries array and an entryValues array.
at android.preference.ListPreference.onPrepareDialogBuilder(ListPreference.java:232)
at android.preference.DialogPreference.showDialog(DialogPreference.java:296)
at android.preference.DialogPreference.onClick(DialogPreference.java:267)
at android.preference.Preference.performClick(Preference.java:942)
at android.preference.PreferenceScreen.onItemClick(PreferenceScreen.java:222)
at android.widget.AdapterView.performItemClick(AdapterView.java:301)
at android.widget.AbsListView.performItemClick(AbsListView.java:1280)
at android.widget.AbsListView$PerformClick.run(AbsListView.java:3067)
at android.widget.AbsListView$1.run(AbsListView.java:3969)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4921)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1038)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
at dalvik.system.NativeStart.main(Native Method)

I have two tasks adjacent to each other in the "next" list. One has a due date, one does not. When I touch the task with a due date, it expands and shows all the details, including the due date.

I touch again to dismiss the details, and touch the task with no due date. The details show the same due date as before, even though it should show nothing.

hya

ive played around with a open source todo app based on todo.txt
https://play.google.com/store/apps/details?id=nl.mpcjanssen.todotxtholo
while its nice its ofc no where near task warrior, yet one very nice feature it has is the ability to 'push' specific task to the android calander via the android 'share' menu.

so one would pick a task , enter the share menu, choose the andoid calander and then can put time/date/notifications etc for that task that would now be linked to the calander. i found that to be quite neat and would love if it could be integrated into the TW android app

thx

Z

I have 2 tasks: one under the "proj1" project and one without project.

Selecting the "no project" button displays only task 2, but selecting the "proj1" project displays both task 1 and task 2. Expected: only task 1 is displayed.

If you have a big list, the danger is that after filtering, you will miss something important. For that reason, it's essential that the user is always aware of the filters in play. One way of doing that is to display at the top of each list. (see attached image) As a bonus, we can also show the report used and number matching tasks.

This form is designed to closely reproduce the command-line experience, so that the experienced taskwarrior user is right at home, and new users will become familiar with the cli filter syntax.

If the filter-set gets too big for a single line, it should "wrap" forcing as many new lines as needed. In order to help keep it condensed, there could be a user-setting where attribute-names (project: priority: etc) could be displayed using the .rc "minimum limit" (in my case, three characters, pro: pri: etc.)

A notification of the day's tasks would be nice each morning.

Enhancement: swiping a task should mark a task as done instead of making the "Projects" menu slide in.

Sitaktif said:
Swiping a task to the right should probably mark a task as done instead of showing
the left menu (it is the emerging paradigm in android, with emails, notifications
etc.).
Sujeevan > Yes, thats true.

I currently share my task files using owncloud (dropbox before that), and would love to be able to do that on the phone.

I know asking for direct integration would be a right pain, so how about the ability to set the location of the data files?

Thanks!

d

There should be some color for urgency and/or priority to help highlight tasks which should be completed sooner.

When the phone is in the USB mass storage mode I get an error message saying "EACCESS (Permission denied)". A message telling me that the app does not work in the USB mass storage mode would be better.

Some like their lists packed tight, some prefer breathing room, with a setting for padding, users could have it both ways. The default setting is something like 5px (?) and at 0px, tasks should be divided by a thin line, and the dropshadow can be turned off.

Hello. Just wanted to point out that I'm getting 404 for https://play.google.com/apps/testing/org.svij.taskwarriorapp

Is there any reason it is not on Google Play? I would love to try it.

The AutoCompleteTextView doesn't display the text in the dropdown. It's possibly an android bug.

When started, the program displays the displays the message "/mnt/sdcard/pending.data (Permission denied) Unable to read to external storage". I can't add then any tasks.

I'm testing on a Motorola XT860 (Milestone 3) without external SD card.

Edit: just discovered that my phone couldn't access the memory because it was connected to the pc. I would like to be able to access my tasks while I leave my phone connected to charge, but now I'm not sure how would that be possible.

In the edit dialog, the field-headers and the field-contents are the same color and this is makes it less than clear what's what. I'd like to see the field-headers in an inverted scheme (white text on black or dark-gray bg) and the header font could be smaller.

I have a task with a reported urgency of 7.7200003. I would prefer that to be rounded to 1 or 2 decimal places at most.

When "actioning" a task (ie when displaying the actionbar menu of a task), then tapping on another task will switch to "actioning" that new task instead of doing nothing.

A short tap should either edit or open a menu; select mode should be long click. This is how other applications with lists work at least.

The duedates of a unsaved task are lost, after the screen rotates.

At the moment, going "back" (with the global android "back" button) does not go back in a intuitive
way.

After doing some tests (adding/editing/going in projects/etc...), doing "back back back back back" brought me to some various places in the app I've visited before, including some previous task editions that I though were closed.

"back" should always go "one level up". For example, if I'm in project P, and I edit task T, I want that 1/ back->list of tasks from project P, 2/ back-> list of all tasks for all project 3/ back->close app.

The trick is apparently to "finish" the Activity when one stops editing a task.

I have a task with a description, project and one tag. It have an urgency value of 167.0, and I would expect it to be much lower. It is several months old.

It's useful if we could select the media (microSD) and the directory in which we want to save files.

There should at least be notification that there are unsaved changes.

This will obviously have to wait until the app supports more than the basic fields, but this is a suggestion for how the present display could be enhanced with more data, when available :)

The attached mockup shows a truncated description and additional information; tags, task ID, blocked tasks, blocking tasks and number of annotations, and is a discussion-point.

For those of us who have implemented http://taskwarrior.org/projects/taskwarrior/wiki/Faq4

It would be great to be able to use multiple lists in the android app and make them easily switchable, or even merged and filterable.

try this; choose the "task all" report, rotate your phone from landscape to portrait, and the report changes to "task next".

A checkmark makes sense in each context individually, but when they're on the same screen, there isn't much context as to which is which. Maybe add some text to the 'done' button here?

At the moment, tasks marked as done in the db are displayed like the others.

Either display them differently (grey? strikethrough?) or don't put them in the list.

Ideally even give an option to toggle between the two modes.

the NavDrawer needs some improvements, so I made another mockup. This time it's an animated .gif (8 seconds) to show three possible states for the nav..

some notes;
FILTER
the filter can be entered manually in the box at the top, or, as items are selected, the filter-dialog is automatically filled-in. It should be possible to add a filter using the checkbox, and then edit that in the filter box. This can also act as a quick search-bar for "term" in description.
Clicking the category headings should "accordion" the list.
The gray checkmark on the filter-category indicates one-or-more selected from the category.
Clicking the category checkbox cycles through three states; clear category, any-value-of-category, none-in-category (showing clear checkbox, green-checkmark and red-X, respectively)
Clicking on an attribute checkbox toggles inclusion in the filter list.
Clicking on an attribute name should make that a single selection, and go immediately to the active report.
Clicking on "apply" goes immediately to current report.
Missing; date parameters

SORT
Missing; UDAs

REPORT
Some of these will be easier, and some harder, but they are all important.
Missing; agenda, calendar

The font is too big for my taste (it looks like a "font size 16" on my device - Nexus 4).n

We should probably let the user configure the font size.

It leaves the following backtrace:

E/SQLiteDatabase(816): close() was never explicitly called on database '/data/data/org.svij.taskwarriorapp/databases/tasks.db' 
E/SQLiteDatabase(816): android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here
E/SQLiteDatabase(816):  at android.database.sqlite.SQLiteDatabase.(SQLiteDatabase.java:1943)
E/SQLiteDatabase(816):  at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:1007)
E/SQLiteDatabase(816):  at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:986)
E/SQLiteDatabase(816):  at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:1051)
E/SQLiteDatabase(816):  at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:770)
E/SQLiteDatabase(816):  at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:221)
E/SQLiteDatabase(816):  at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:157)
E/SQLiteDatabase(816):  at org.svij.taskwarriorapp.db.TaskDataSource.open(TaskDataSource.java:30)
E/SQLiteDatabase(816):  at org.svij.taskwarriorapp.MenuListFragment.setTaskList(MenuListFragment.java:104)
E/SQLiteDatabase(816):  at org.svij.taskwarriorapp.ArrayListFragment.onActivityCreated(ArrayListFragment.java:140)
E/SQLiteDatabase(816):  at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:892)
E/SQLiteDatabase(816):  at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1083)
E/SQLiteDatabase(816):  at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:635)
E/SQLiteDatabase(816):  at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1431)
E/SQLiteDatabase(816):  at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:523)
E/SQLiteDatabase(816):  at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1133)
E/SQLiteDatabase(816):  at android.app.Activity.performStart(Activity.java:4475)
E/SQLiteDatabase(816):  at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1928)
E/SQLiteDatabase(816):  at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1980)
E/SQLiteDatabase(816):  at android.app.ActivityThread.access$600(ActivityThread.java:122)
E/SQLiteDatabase(816):  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1146)
E/SQLiteDatabase(816):  at android.os.Handler.dispatchMessage(Handler.java:99)
E/SQLiteDatabase(816):  at android.os.Looper.loop(Looper.java:137)
E/SQLiteDatabase(816):  at android.app.ActivityThread.main(ActivityThread.java:4340)
E/SQLiteDatabase(816):  at java.lang.reflect.Method.invokeNative(Native Method)
E/SQLiteDatabase(816):  at java.lang.reflect.Method.invoke(Method.java:511)
E/SQLiteDatabase(816):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/SQLiteDatabase(816):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/SQLiteDatabase(816):  at dalvik.system.NativeStart.main(Native Method)
E/System(816): Uncaught exception thrown by finalizer
E/System(816): java.lang.IllegalStateException: Don't have database lock!
E/System(816):  at android.database.sqlite.SQLiteDatabase.verifyLockOwner(SQLiteDatabase.java:2090)
E/System(816):  at android.database.sqlite.SQLiteDatabase$1.entryRemoved(SQLiteDatabase.java:2182)
E/System(816):  at android.database.sqlite.SQLiteDatabase$1.entryRemoved(SQLiteDatabase.java:2178)
E/System(816):  at android.util.LruCache.trimToSize(LruCache.java:197)
E/System(816):  at android.util.LruCache.evictAll(LruCache.java:285)
E/System(816):  at android.database.sqlite.SQLiteDatabase.deallocCachedSqlStatements(SQLiteDatabase.java:2143)
E/System(816):  at android.database.sqlite.SQLiteDatabase.closeClosable(SQLiteDatabase.java:1126)
E/System(816):  at android.database.sqlite.SQLiteDatabase.finalize(SQLiteDatabase.java:1914)
E/System(816):  at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:182)
E/System(816):  at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:168)
E/System(816):  at java.lang.Thread.run(Thread.java:856)

"Urgency" should be implemented exactly like in the original taskwarrior client.

Of all the taskwarrior reports that might be translated to the android app, there are 3 that I might consider to be both "reports" and "report-styles"; list, long and minimal. ("ls" could be in there, or not) which could be thought of as report styles maximal, normal and minimal, which could (and should) be applicable to other reports.

Several of the reports are not typical lists, like calendar, count, history and stats. Another group of reports will generate a sub-set, (or super-set) like active, all, blocking, overdue, recurring and waiting. Newest & oldest are primarily sort-directives, and projects and tags are sort of hybrids; a list with some summary.

That means that any one of the three styles could be used in listing active, all, blocking, overdue, projects, tags, recurring and waiting, and this feature-request if for a user-setting that will allow the user to indicate which of the three will be used by default. This way, any of these reports could be invoked with a single keystroke, and will display in the users preferred style.
(of course, I'm getting ahead of myself, and no "styles" exist yet, so I'm just playing "what if")

Soon people will start forking like crazy when the taskd server is out of alpha. So we need some test suites for automatic regression testing so things that are broken can be detected as soon as it happens.

What I did:

• Added a task with today as due date
• Closed the app
• Starteded the app and when I get the due notification the app crashes (But not always, I do not get the notification then everything works fine (besides I get not notified about task I have to do today).

At the moment, one cannot scroll when editing a task in landscape mode.

It is a problem since all the elements don't fit the screen.

Task are deleted immediately. To be asked, if the task should really be deleted would be nice.

We could display more tasks on screen if the space between each task was smaller.

The current time is used instead.

When adding tag(s) to a task, they are not saved.

Version 0.12

Batch task management would be nice.

The upper-left button to make the left menu slide in is not active when launching the app.

After swiping to the right (menu slides in) and to the left (menu slides out), the "<" character appears next to the taskwarrior icon on the top left corner and one can then click on it.

Button should be clickable from the beginning.

When adding a task, there should be a dropdown of existing projects.

Does this app support task annotations yet?

It's currently not possible to delete a due date, if one of the date/time pickers are setted.

Maybe it would be a solution to add a delete-dialog on a long click on the TextViews.

After changing the orientation in the "add Task" activity the date and time are always set, even they weren't before. if no date was set, the date is automatically set to 01.01.70 (Unix Starttime) and Time is set to 00:00 or 01:00

The tasks should be more compact (I can only see four 2-line tasks on my nexus 4,
which has a hell of a big screen). This is [partly] due to:

• keeping space empty below the tasks's titles (for priority etc.). This space should
  be dynamic I think.

In other words, there should not be any blank lines when displaying tasks.

The daily notification is currently broken. It does not correctly handling the time to notifiy the user.