Log file Viewer

[12:51:53] <aclark> garbas: how'd it go yest?

[12:52:14] <garbas> aclark: just writing a report for you

[12:52:21] <aclark> \o/ thanks

[12:59:43] <aclark> garbas: cool so what's the plan for today?

[13:00:13] <garbas> plan is to finalize this custom select2 widget

[13:00:20] <garbas> i'm almost done

[13:00:43] <aclark> K

[13:00:47] <garbas> then verify that multi vocabulary works with this widget

[13:01:16] <garbas> which kinda completes the task of project_manager and assigned_to widgets

[13:01:31] <aclark> cool

[13:01:59] <garbas> as extra (if time) i'll try to get that permissions/local roles copied over from c.task

[13:02:06] <garbas> and try to make them work

[13:02:38] <garbas> i will anyway have to watch my gf pack for 4h :)

[13:02:47] <garbas> i'm usually done with packing in 10min

[13:02:51] <aclark> hah

[13:05:49] <aclark> garbas: i can definitely handle the permissions/local roles, especially with the c.task example, so I'd suggest focusing all your time on UI

[13:06:25] <aclark> I just wish we could "subclass" (or something) from c.task rather than copy it

[13:06:45] <aclark> BUT I'm not going to worry about that right now

[13:11:59] <garbas> aclark: i would say lets implement it then we can talk with c.task guys if we want to merge projects

[13:12:22] <aclark> garbas: k

[20:40:45] <garbas> aclark: ^ i made project_manager/assigned_to widget to work.

[20:41:08] <garbas> aclark: you have any other UI task you would like me to focus on?

[20:42:01] <garbas> aclark: i can tackle #9 (Fields to share between Task Planner and contained Tasks)

[20:42:14] <garbas> since this is partly also ui "problem"

[21:08:05] <aclark> garbas: sure please do, thanks

[21:10:12] <aclark> garbas: I think you can also make a template to serve as the "Task View" for PMs which will have the exact same UI components that add/edit view has IIUC

[21:10:27] <aclark> supton: please confirm ^

[21:10:44] <aclark> I will then make an "object" action to link to the view

[21:16:52] <supton> aclark: sounds about right, for things that are secondarily tasks, this object action (tab) will be primary view by which folks interact with this stuff...

[21:17:31] <supton> aside from viewlet: https://github.com/upiq/uu.task/issues/13 which will link to the "Task assignment" tab

[21:17:57] <supton> what project managers see on task assignment tab may vary from what assigned parties might see, unless assigned party also has PM role

[21:22:47] <aclark> garbas: ^

[21:22:49] <aclark> supton: thx

[21:46:08] <garbas> aclark: now that i think of due_date, due_date_computed, due_date_computed_relative_to_dow it would make a lot more sense to have it as one field

[21:46:17] <garbas> not three

[21:47:18] <garbas> due = schema.TextLine() ... and then widget would store json accordingly, eg {"type": "date", value: "2015-01-01"}

[21:48:05] <aclark> garbas: k, fine w/me

[21:48:10] <garbas> or {"type": "computed", "value": { field1: "1", field2: .. }

[21:48:35] <garbas> aclark: it would make it a lot easier to implement aquiring values from parent context

[21:50:13] <garbas> ok, i have todo for this evening

[21:50:25] <garbas> 1. all due_date fields should become one

[21:51:46] <garbas> 2. then show value from parent TaskPlanner (if exists)

[21:54:09] <aclark> Cool