Mockups implemented:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 30 2016
May 23 2016
May 17 2016
May 16 2016
May 13 2016
May 11 2016
May 10 2016
The only thing missing is saving of loaded drafts, for which we have to remember the entity id.
May 9 2016
Another alternative would be
That ends up being more verbose (without additional macro magic), but the property definitions can be reused in other places, such as the property mapping.
Alternatively we could define properties with classes and use template wrappers like this:
pull request at https://github.com/cmollekopf/docker/pull/19
May 7 2016
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
May 3 2016
May 2 2016
Apr 27 2016
I talked to Marco. We will get a version that does not require a Kirigami.Page parent within a week or so.
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.