<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 21, 2017, at 2:25 PM, Robert Helling <<a href="mailto:helling@atdotde.de" class="">helling@atdotde.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dirk,<div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 21 Jan 2017, at 23:21, Dirk Hohndel <<a href="mailto:dirk@hohndel.org" class="">dirk@hohndel.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Here's my plan for right now. Fix things so we go back to Kirigami 1.</span></div></blockquote></div><br class=""></div><div class="">remind me: Didn’t we run into some problems („bugs“) in Kirigami for which by sticking with an old version we give up any hope of them ever being fixed? Not that I tried too hard myself (and having no idea what the differences between 1 and 2 are besides the numbers).</div></div></div></blockquote><br class=""></div><div>There are tons of bugs in Kirigami. As in TONS. That said, who believes that any of them will get fixed in Kirigami 2? I see no indication of that.</div><div><br class=""></div><div>In the meantime, to explain the difference... it's a little more than just the version number. Kirigami 2 is based on Components.2 instead of Components. Which means that pretty much every single class that we have used, every graphical element has changed. It's a complete API break. And the documentation of what needs to get done to port things is "it's not hard to port". Seriously.</div><div>I have yet to find anything that gives you even the faintest instructions.</div><div class=""><br class=""></div>What I have figured out so far by looking at the crash logs is this:<div class="">- no more styles</div><div class="">- no more control object for buttons</div><div class="">- no more ScrollView</div><div class="">- opened turns into sheetOpen</div><div class="">- no more Action</div><div class="">- ComboBox is completely changed</div><div class="">- TableView appears gone</div><div class="">I spent about 15 hours on that and the result is an app that doesn't work. It doesn't open the keyboard when you tap on an input field. None of the ComboBoxes work. All of our model handling code is broken. It makes me want to cry if I think how much time I have spent on this.</div><div class=""><br class=""></div><div class="">To call this a complete disaster would be way too kind to the Kirigami developers. I know that Marco and Sebastian used to be on this mailing list (I doubt they still are, haven't heard from them in months), but given that we were their poster child first application I feel completely abandoned and kicked to the floor.</div><div class=""><br class=""></div><div class="">/D </div></body></html>