Page MenuHomePhorge
Create Task
Maniphest T1227

Port overlay windows to Kirigami Sheet
Closed, ResolvedPublic1 Story Points
Actions

Details

Ticket Type
Task

Event Timeline

bohlender created this task.Apr 27 2016, 12:31 PM
bohlender moved this task from Backlog to Doing on the Sprint 201617 board.
bohlender added a comment.Apr 27 2016, 1:11 PM

Looks like Kirigami.Sheet expects to be a child of Kirigami.Page. Thats not what we want.
I will have to talk to the Kirigami devs about that.

bohlender moved this task from Doing to Backlog on the Sprint 201617 board.Apr 27 2016, 1:11 PM
bohlender added a comment.Apr 27 2016, 2:07 PM

I talked to Marco. We will get a version that does not require a Kirigami.Page parent within a week or so.

petersen added a project: Sprint 201618.May 2 2016, 6:56 AM
bohlender added a comment.May 7 2016, 11:05 AM

Kirigami.OverlaySheets does not depend on Kirigami.Page anymore but still on Kirigami.ApplicaitonWindow which we don't use...
I will bring it up at the next Kirigami.Meeting

petersen added a project: Sprint 201619.May 9 2016, 7:17 AM
petersen added a project: Sprint 201620.May 16 2016, 6:51 AM
petersen added a project: Sprint 201621.May 23 2016, 7:05 AM
petersen added a project: Sprint 201622.May 30 2016, 8:33 AM
petersen added a project: Sprint 201623.Jun 6 2016, 7:57 AM
petersen added a project: Sprint 201624.Jun 13 2016, 7:53 AM
petersen added a project: Sprint 201625.Jun 20 2016, 8:34 AM
petersen added a project: Sprint 201626.Jun 27 2016, 8:41 AM
petersen added a project: Sprint 201627.Jul 4 2016, 5:12 AM
petersen added a project: Sprint 201628.Jul 11 2016, 7:08 AM
petersen added a project: Sprint 201630.Jul 25 2016, 7:06 AM
petersen added a project: Sprint 201632.Aug 8 2016, 6:02 AM
bohlender moved this task from Backlog to Done on the Sprint 201632 board.Aug 10 2016, 8:04 AM
bohlender closed this task as Resolved.Aug 13 2016, 11:31 AM

After discussion with the Kirigami people we decided that Kirigami.Overlaysheets is not the right fit for our specific usecase. We will stay with our (now reworkded) custom solution.