<?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[Scopes current and future]]></title><description><![CDATA[<p dir="auto">I was thinking on scopes and want to open a discussion about the current state of them and possibility for future.<br />
I was thinking that the scopes could be QML applications simply loaded inside an Qt/QML application.<br />
This could bring a lot of scopes opportunities:</p>
<ul>
<li>any QML app can be set as scope and be at the user's fingertips</li>
<li>a lot of UI customisation possibilities</li>
<li>webapps can be loaded as scopes through WebView / WebEngine to support HTML / Javascript scopes</li>
<li>they can interract with the OS instead of just providing static content</li>
<li>support is provided through Qt updates</li>
</ul>
<p dir="auto">Downside:</p>
<ul>
<li>no support for Golang</li>
</ul>
<p dir="auto">How scopes are built now lack a lot, you have little customisation and little freedom for them and they can't do anything but show some information.<br />
They could be given the option to be started / closed when they get focused / hidden through QML Loader to reduce memory footprint or kept always on, in case someone wants to leave it running(a music player scope can be given as example).</p>
<p dir="auto">I wasn't sure where this could be discussed, so since this comes into user experience(more or less) I thought here it's the best place to do it.<br />
What do you think?</p>
]]></description><link>https://forums.ubports.com/topic/903/scopes-current-and-future</link><generator>RSS for Node</generator><lastBuildDate>Wed, 11 Mar 2026 09:31:54 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/903.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 19 Jan 2018 17:47:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Scopes current and future on Sun, 21 Jan 2018 13:15:40 GMT]]></title><description><![CDATA[<p dir="auto">It still won't solve the navigation pattern conflitcts though. I still think that even pure QML apps as scopes are an overkill for both performance and UX reasons.</p>
<p dir="auto">The current concept of what scopes are is not bad - they just need to be faster, more flexible and dynamic.</p>
]]></description><link>https://forums.ubports.com/post/6765</link><guid isPermaLink="true">https://forums.ubports.com/post/6765</guid><dc:creator><![CDATA[Mitu]]></dc:creator><pubDate>Sun, 21 Jan 2018 13:15:40 GMT</pubDate></item><item><title><![CDATA[Reply to Scopes current and future on Sat, 20 Jan 2018 08:11:39 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mitu" aria-label="Profile: mitu">@<bdi>mitu</bdi></a> said in <a href="/post/6743">Scopes current and future</a>:</p>
<blockquote>
<p dir="auto">This is definitely not a good idea in my opinion. Apps' navigation patterns would interfere with desktop navigation, what would mean that having set unav as a scope you would not be able to swipe between desktops.</p>
</blockquote>
<p dir="auto">I am not talking about the possibility of allowing every application to run as scopes.<br />
There can and should be standards to allow this feature, for example:</p>
<ol>
<li>an application should be a pure QML application which doesn't start from an executable file, but from a QML file(where the main view of the application is loaded through Loader to MainView and not declared as a child of it to decouple from it)</li>
<li>there should be a standard to communicate to the system that it can be loaded as a scope, and which QML file should be the main view of the scope.</li>
</ol>
<p dir="auto">If I will have the time I will try to make a desktop prototype for testing to show what I am talking about.</p>
]]></description><link>https://forums.ubports.com/post/6746</link><guid isPermaLink="true">https://forums.ubports.com/post/6746</guid><dc:creator><![CDATA[vadrian89]]></dc:creator><pubDate>Sat, 20 Jan 2018 08:11:39 GMT</pubDate></item><item><title><![CDATA[Reply to Scopes current and future on Fri, 19 Jan 2018 22:09:12 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/vadrian89" aria-label="Profile: vadrian89">@<bdi>vadrian89</bdi></a> said in <a href="/post/6736">Scopes current and future</a>:</p>
<blockquote>
<p dir="auto">any QML app can be set as scope and be at the user's fingertips<br />
webapps can be loaded as scopes through WebView / WebEngine to support HTML / Javascript scopes</p>
</blockquote>
<p dir="auto">This is definitely not a good idea in my opinion. Apps' navigation patterns would interfere with desktop navigation, what would mean that having set unav as a scope you would not be able to swipe between desktops.</p>
<p dir="auto">Scopes definitely need their API standards, and some limits in the functionality, so that they could be fast, safe and not breaking the Ubuntu's UX.</p>
<p dir="auto">Of course what scopes are and how they work is definitely what shoud be rethought and redone, but still "whatever" is not the right answer.</p>
]]></description><link>https://forums.ubports.com/post/6743</link><guid isPermaLink="true">https://forums.ubports.com/post/6743</guid><dc:creator><![CDATA[Mitu]]></dc:creator><pubDate>Fri, 19 Jan 2018 22:09:12 GMT</pubDate></item><item><title><![CDATA[Reply to Scopes current and future on Fri, 19 Jan 2018 18:56:47 GMT]]></title><description><![CDATA[<p dir="auto">I'm a fan of scopes and if your proposal is to give them new life, well be my guest. Unfortunately, I cannot dig more into your thoughts since I'm not a developer, but it sounds good to me and I definitely support your idea!</p>
]]></description><link>https://forums.ubports.com/post/6738</link><guid isPermaLink="true">https://forums.ubports.com/post/6738</guid><dc:creator><![CDATA[matteo]]></dc:creator><pubDate>Fri, 19 Jan 2018 18:56:47 GMT</pubDate></item></channel></rss>