<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Mir 1.4.0]]></title><description><![CDATA[<p dir="auto">mir 1.4.0 got announced and they are dropping stuff releated to UBports. But I'm not sure to understand the implication for UT. What does this imply for us? Can we drop deplicated API or we will need to maintaine them?<br />
mir announcment: <a href="https://discourse.ubuntu.com/t/mir-1-4-0-release/12198" target="_blank" rel="noopener noreferrer nofollow ugc">https://discourse.ubuntu.com/t/mir-1-4-0-release/12198</a></p>
]]></description><link>https://forums.ubports.com/topic/3004/mir-1-4-0</link><generator>RSS for Node</generator><lastBuildDate>Sat, 06 Jun 2026 17:23:24 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/3004.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 15 Aug 2019 21:25:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Mir 1.4.0 on Fri, 16 Aug 2019 20:33:03 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/alan_g" aria-label="Profile: alan_g">@<bdi>alan_g</bdi></a> wow super detail answer thanks for the detail and the explaination.</p>
]]></description><link>https://forums.ubports.com/post/21957</link><guid isPermaLink="true">https://forums.ubports.com/post/21957</guid><dc:creator><![CDATA[Aurze]]></dc:creator><pubDate>Fri, 16 Aug 2019 20:33:03 GMT</pubDate></item><item><title><![CDATA[Reply to Mir 1.4.0 on Fri, 16 Aug 2019 13:18:20 GMT]]></title><description><![CDATA[<p dir="auto"><img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /> Thank you, <a class="plugin-mentions-user plugin-mentions-a" href="/user/alan_g" aria-label="Profile: alan_g">@<bdi>alan_g</bdi></a></p>
]]></description><link>https://forums.ubports.com/post/21938</link><guid isPermaLink="true">https://forums.ubports.com/post/21938</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Fri, 16 Aug 2019 13:18:20 GMT</pubDate></item><item><title><![CDATA[Reply to Mir 1.4.0 on Fri, 16 Aug 2019 09:20:57 GMT]]></title><description><![CDATA[<p dir="auto">tl;dr: There's nothing to worry about, this was expected and planned for.</p>
<p dir="auto">The mirclient APIs used in Unity8 and 16.04 based applications <em>is not</em> dropped, and <em>does not</em> require a build-time option to enable it.</p>
<p dir="auto"><strong>It simply needs switching on with a configuration option at runtime</strong>. (There are many ways that can be supplied, for example, adding code to <a href="https://github.com/ubports/qtmir" target="_blank" rel="noopener noreferrer nofollow ugc">QtMir</a> and <a href="https://github.com/ubports/unity-system-compositor" target="_blank" rel="noopener noreferrer nofollow ugc">unity-system-compositor</a> that fakes passing this as a "command-line option" to Mir.)</p>
<p dir="auto">For a bit of perspective, these APIs have been deprecated for two years, and the UBports developers have been aware of that. Similarly, the Mir developers have been aware that they are used by UBports and have continued to build and test them.</p>
<p dir="auto">Everyone working on this software stack has always known that UBports needs to move off these APIs at some point, but that cannot happen until there is a viable alternative. And that requires moving to a more recent version of Mir (at least Mir 1.3 for this <a href="https://ubuntu.com/blog/mir-support-for-wayland" target="_blank" rel="noopener noreferrer nofollow ugc">Mir support for Wayland</a>).</p>
<p dir="auto">The change to "new Mir" is progressing, and is available on the "edge" channel. Delivering that will allow the migration to Wayland to start.</p>
<p dir="auto">There have been discussions (<a href="https://forums.ubports.com/post/16976">here</a> and <a href="https://discourse.ubuntu.com/t/the-way-to-wayland-for-unity8/9581" target="_blank" rel="noopener noreferrer nofollow ugc">here</a>) about this migration and, when the time comes, the Mir team has the expertise, willingness and availability to help UBport move from mirclient APIs to Wayland protocols.</p>
<p dir="auto">There may be a time during this transition where UBports cannot ship with the latest release of Mir, but the way forward is clear and the problems to be addressed are far smaller than ones that have already been overcome.</p>
]]></description><link>https://forums.ubports.com/post/21933</link><guid isPermaLink="true">https://forums.ubports.com/post/21933</guid><dc:creator><![CDATA[alan_g]]></dc:creator><pubDate>Fri, 16 Aug 2019 09:20:57 GMT</pubDate></item><item><title><![CDATA[Reply to Mir 1.4.0 on Thu, 15 Aug 2019 22:13:38 GMT]]></title><description><![CDATA[<p dir="auto">The APIs are deprecated, not removed yet. We will need to build our version of Mir with them still enabled for now.</p>
<p dir="auto">In order to move away from the deprecated mirclient API, we will require implementations of certain protocol features to be done as Wayland protocol extensions (or to be implemented in a method independent of display server). We will also need either Xmir to use Wayland instead of mirclient, or we'll need to get Xwayland working.</p>
<p dir="auto">These are unfortunately very large tasks, so it will be a while. We can also hang back to a version of Mir which still has mirclient, once it gets removed, if it's still necessary. We are not directly bound to the Mir release schedule.</p>
]]></description><link>https://forums.ubports.com/post/21927</link><guid isPermaLink="true">https://forums.ubports.com/post/21927</guid><dc:creator><![CDATA[dobey]]></dc:creator><pubDate>Thu, 15 Aug 2019 22:13:38 GMT</pubDate></item></channel></rss>