jackburton | # 41 | 2012-10-07, 16:22 | Report

Okay, nevermind what I posted before. I got the buttonbox to do what I want using size policy properties. I'll use the standard buttons and it should look native and should work in portrait mode.


qt-dialog-portrait-test by brander snaxe, on Flickr

ovekaaven | # 42 | 2012-10-08, 14:59 | Report

getDefaultCalendar ordinarily actually gives you the "Private" calendar, which that user seems to have deleted.

You could consider using getSynchronizedCalendar instead of getDefaultCalendar, since getSynchronizedCalendar gives you the main calendar. It's what I used in syncevolution.

jackburton | # 43 | 2012-10-08, 15:13 | Report

Thanks! Makes sense. I personally prefer my default tasks going to the Private, but your point is valid. I will likely make the synchronized calendar the default and then fall back to default, and then fall back to the first calendar. But now it makes me think I should add a preference for the user to decide default calendar. I could even extend the preference to be per folder.

vi_ | # 44 | 2012-10-26, 11:47 | Report

c'mon jack, don't quit on me now!

Also, what about blocking tasks?

i.e. project requires tasks A, B and C be completed.
Task B REQUIRES task A to be completed before task B can be started.
Task C can be completed at any time.

Thus, Task B is 'hidden' from current tasks till A is completed.

So, the current task list might look like 'A and C' to be completed (because B is hidden till A is done). What do you think?

jackburton | # 45 | 2012-10-26, 12:15 | Report

I am definitely not quitting. Fremantle is my platform of choice until something comes along that can match what it does for me.

Work has been killing me lately. That's all.

I have made progress based on my last roadmap update. Rotation is almost done. Alarms will be there, too. I'm adding some other small enhancements that I need for myself (hehe I'm selfish at times). I've also been spending some random time toying with the notion of doing a full calendar replacement, but that just isn't going to happen before maecaltasks gets further along.

Now, onto your idea. What's funny is that I woke up in the middle of last night and actually thought that I needed to add something as you suggest. Basically a dependency field. I thought up two views for this:

• The NEXT list -> for a given folder, show what's next do to. This can be by date, priority, dependency
• Gantt View -> same as NEXT list, but in a graphical report

Now, I'm also thinking that for a given folder, it would be nice to "flatten" the folders below. This would allow one to see "all undone tasks" in the parent for example in one list. I know this is one that I would use. My example use case is a shopping list. I regularly go to Target or Costco for certain items. And I also have routine items I pick up and also "one off" items I need on my next and only visit. In the current version I would structure it like this:


Shopping List

Target

Next Visit

One off item

Routine

Routine item 1

Routine item 2

Now, my idea is to add a "flat" view for the folder. This is basically select * from children order by whatever, etc. The result would look like this:

Shopping List

Target

One off item

Routine item 1

Routine item 2

In this way you can have structured shopping lists, but when it comes time to shop, there is one easy view to shop with. This same "flatten" concept could be used to take a hierarchical project plan and display all the "next" items regardless of the child folder.

I have lots of ideas on my internal roadmap. I'm not sure which ones the community would want first. For example, I have an idea on how to add recurring tasks in a way that may actually sync when using syncml (by creating instances of new tasks). Or linking a task to a calendar event if you want to timebox an activity in your plan.

These are all doable. It's a matter of timing and priority.

I can start to formalize my internal list and ask for feedback on what to include in next versions. I also welcome your new ideas. Meantime, I need to wrap up the .1 items with rotation and alarms out to the users.

vi_ | # 46 | 2012-10-26, 12:34 | Report

I keenly await the addition of a donate button so that I may supply you with some beer tokens.

vi_ | # 47 | 2012-10-26, 12:39 | Report

Have a play with this. This is the absolute best task list thing I know off:

http://mgsd.tiddlyspot.com/demo3.html

Unfortunately it is completely self contained and doesn't integrate with anything.

jackburton | # 48 | 2012-10-26, 12:48 | Report

Looks like it is GTD, right? Contexts are in my road map for sure.

I'm have also designed a "view" engine where somebody can write their own SQL filter (or get help from me/community on syntax) to create their own views. I believe the combination of "flat" lists with "views" should allow enough flexibility to create good workflows.

For example, I want to write my own view that says "show me all the tasks I have that are due this weekend, but only this weekend." I would name this view "This weekend" and I can always see what's on my plate in my next free time window.

artpra | # 49 | 2012-10-26, 13:12 | Report

MEGAFCUKINGTON!!!!111one!!1one

Please take this advice: don`t forget to organize some donation form when You start that.

jackburton | # 50 | 2012-10-28, 13:15 | Report

Dialogs will look like this in portrait. I found a way to use the native dialog action buttons. In landscape, the buttons appear on the right as they do now.


Fremantle qt dialog portrait by brander snaxe, on Flickr


Fremantle qt portrait dialog by brander snaxe, on Flickr