<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Camilo Higuita on Medium]]></title>
        <description><![CDATA[Stories by Camilo Higuita on Medium]]></description>
        <link>https://medium.com/@temisclopeolimac?source=rss-15214b503713------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SAaLsvsZc3BAFnEY.</url>
            <title>Stories by Camilo Higuita on Medium</title>
            <link>https://medium.com/@temisclopeolimac?source=rss-15214b503713------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:29:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@temisclopeolimac/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Maui @ KDE]]></title>
            <link>https://medium.com/nitrux/maui-kde-fcdc920138e2?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcdc920138e2</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[mauikit]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 05:39:45 GMT</pubDate>
            <atom:updated>2019-09-11T05:39:45.218Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Maui Project</h3><p>The Maui Project is a group of tools working together to achieve a multi-platform and convergent environment.</p><blockquote>The Maui Project runs on Android, GNU/Linux Desktops, and Plasma Mobile.</blockquote><p>At a high level, there are 4 main components provided. There is a UI/UX framework named MauiKit used to build our set of apps for them to work on different devices, platforms, and screen form factors.</p><p>We also provide a group of libraries used to sync information and data across different devices (libwebdav and libccdav).</p><p>Finally, there is the Maui HIG which informs how the apps should look and behave so our environment can have a cohesive look and feel.</p><p><em>These four components work together to bring the user experience of convergence, not only within a single device but across different platforms, so you can always have a standard set of adaptable apps that carries with it your information.</em></p><p>So far, the suite of Maui Apps is composed of a file manager, music player, image viewer, document viewer, terminal emulator, contacts manager and <em>dialer</em>, simple text editor and a notes and tasks manager.</p><p>All of those apps, tools, and libraries have been incubated into KDE and are now part of the KDE family, for the community to use them, contribute and get involved.</p><p><a href="https://community.kde.org/Incubator/Projects/Maui">Incubator/Projects/Maui - KDE Community Wiki</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1dmbOTNtJ38VKeRUIsYuw.png" /><figcaption>Index — file manager (on GNU/Linux desktop and on Android phone)</figcaption></figure><h3><strong>Incubation process</strong></h3><p><a href="https://community.kde.org/Incubator">Incubator - KDE Community Wiki</a></p><p>Given that the Maui Project has been successfully incubated and now forms part of KDE, you can find all the components (framework, libraries, and apps) at the new KDE Gitlab instance @ <a href="https://invent.kde.org/kde">Invent</a>.</p><p>Later on, find testing builds on the repositories of <a href="https://neon.kde.org/">KDE Neon</a>, so you don’t have to build the project from source yourself.</p><p>What does it mean for the Maui Project to have been incubated and now form part of the KDE community project?</p><p>It means that now all of the Maui Project parts will take advantage of the KDE infrastructure, so you can test and use all of our technologies easily on your devices (Portable, Desktop PC and Phones, be it Android or Plasma Mobile).</p><p>The project will benefit from community support, from translations to promote, and so on, so the project can grow together with the KDE community.</p><p>And finally, it means that the Maui Project follows the <a href="https://manifesto.kde.org/">KDE Manifesto</a>.</p><h3>Maui Parts</h3><p>The following is a comprehensive list of parts that are incubated:</p><h4>libccdav &amp; libwebdav</h4><p>These are libraries to sync information across platforms and devices by making use of cloud solutions.</p><h4><strong>MauiKit</strong></h4><p>MauiKit is the UI/UX framework made to build and prototype applications that support the Maui HIG quickly.</p><p>For this, MauiKit makes use of <a href="https://kde.org/products/kirigami/">Kirigami</a> for convergent applications and adds on top of it some functionality like different components (widgets), views and back-ends, such as a Store view for getting online content, a File Browser, a simple Text Editor and file management tools. Besides, tight integration with the underlying system, be it Android or GNU/Linux.</p><ul><li><a href="https://mauikit.org/">MauiKit - #UIFramework</a></li><li><a href="https://invent.kde.org/kde/mauikit">KDE / MauiKit</a></li></ul><h4><strong>Index</strong></h4><p>Index is a file manager application. You can browse your files and applications and organize your content by using tags and bookmarks, and it also provides a quick overview popup to check out your multimedia files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*in_ttYmNR_lqoJPX-gPa9A.png" /></figure><p><a href="https://invent.kde.org/kde/index-fm">KDE / Index File Manager</a></p><h4><strong>Pix</strong></h4><p>Pix is the image viewer and gallery manager. It allows you to browse, organize, and share your images, photos, and albums. Also to view your images, mark them as *favs*, add them to collections, tag them, and edit them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*Ysfx3gls-Iiuy4SdJZKoHg.png" /></figure><p><a href="https://invent.kde.org/kde/maui-pix">KDE / Maui Pix - Image Gallery</a></p><h4><strong>Vvave</strong></h4><p>Vvave is the music player.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*HJK0S8ws5YlGKGuvoo_0yA.png" /></figure><p><a href="https://invent.kde.org/kde/vvave">KDE / VVave</a></p><h4>&amp; more:</h4><p><strong>Station </strong><em>/ terminal emulator</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*YmJg-5jOX7-8iMdzbnCaIw.png" /></figure><p><a href="https://invent.kde.org/kde/maui-station">KDE / Maui Station - Covergent Terminal Editor</a></p><p><strong>Library </strong><em>/ documents viewer and browser</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*9xS7qsH8ylL6k3YPx-OzkA.png" /></figure><p><a href="https://invent.kde.org/kde/maui-library">KDE / Maui Library - Document and EBook Collection Manager</a></p><p><strong>Buho </strong><em>/ notes and tasks manager</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/1*hWDYPiG_DNPZEGxV0qAPvQ.png" /></figure><p><a href="https://invent.kde.org/kde/buho">KDE / Buho</a></p><p><strong>Nota </strong><em>/ simple text editor</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*FsFy4my1y3Dd_rAZxf78yg.png" /></figure><p><a href="https://invent.kde.org/kde/nota">KDE / Nota</a></p><p><strong>Dialer </strong><em>/ contacts manager</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*opbGe364465RbKy8c8AG6g.png" /></figure><p><a href="https://invent.kde.org/kde/maui-dialer">KDE / Maui Dialer and Contacts Manager</a></p><h3>Discussion and Q&amp;A</h3><p>Here are a few talking points for those interested. There may be questions later and we are happy to discuss them.</p><h4><strong>MauiKit &amp; Kirigami</strong></h4><ul><li>MauiKit is not another Kirigami fork nor does it intent to be a broad propose UI framework for the development of convergent apps. It is a specialization of Kirigami; therefore, it uses Kirigami alongside other tools (in-house made) to follow the Maui HIG.</li><li>MauiKit includes a group of properties design to follow the Maui HIG by default. When one uses the MauiKit to build an app, one could say is building a Maui App.</li></ul><h4>What’s the difference between MauiKit and Maui?</h4><p>MauiKit is the UI/UX framework we use to build applications, while Maui is the project that groups all the parts of the project: apps, frameworks, libraries, services, and tools.</p><h4>Maui HIG &amp; KDE HIG</h4><p><a href="https://hig.kde.org/">KDE Human Interface Guidelines - Human Interface Guidelines documentation</a></p><p>The KDE HIG describes high-level guidelines that have been adapted and applied as new UI Toolkits have appeared (QWidgets, QQC, QQC2…).</p><p>The Maui HIG is then, informed by such high level guidelines and then adapts those fundamental ideas with different design patterns. An example of this is the behavior of Mauikit toolbars. The KDE HIG suggests reach-ability and MauiKit implements it by allowing the toolbars to move depending on the platform and device where the app is used.</p><p>The project can be seen as a playground where new ideas can be tested, nurtured, and then merged on both directions when those are mature and proved. Instead of being perceived as a duplication of work an effort, it shows how dynamic the KDE community is at embracing new ideas and projects, keeping an open mind for newcomers.</p><h3>Current State of the project</h3><p>The project is currently at very active development, and some parts of it are now much more mature than others.</p><p>For a select group of apps, there is already release candidate packages for broader testing, while MauiKit, the core, continues to receive updates, fixes, and improvements along the way.</p><p>The libraries and services continue growing and being curated to work the best way possible on the targeted platforms by staying as close and integrated into the underlying system as possible.</p><h3>Goals, road map and future</h3><p>The Maui Project is going to be shipped by default on <a href="https://nxos.org/">NitruxOS</a>, which is an exciting project working with super new, fresh and inspiring ideas.</p><p>Within a couple of months, there should be a stable release for a selected group of apps and a stable version of MauiKit</p><p>We have some exciting meetings at Akademy 2019, so you can keep an eye on it. If you are around Milan, join us!</p><p><a href="https://akademy.kde.org/2019">Akademy 2019 - Milan, Italy - 7th-13th September | Akademy</a></p><h3>RC Announcement</h3><p>You can test three Maui Apps on your Android device right now. A file manager, an image viewer, and a music player.</p><p>Index, Pix and Vvave APK packages can be downloaded down below. Play and test them. You can report issues and get involved in many ways.</p><p><a href="https://medium.com/@temisclopeolimac/maui-apps-release-candidate-apks-c45589cf00bd">-&gt; https://medium.com/@temisclopeolimac/maui-apps-release-candidate-apks-c45589cf00bd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcdc920138e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/maui-kde-fcdc920138e2">Maui @ KDE</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maui @ Plasma Mobile Sprint 2019]]></title>
            <link>https://medium.com/nitrux/maui-plasma-mobile-sprint-2019-c20031700b3b?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20031700b3b</guid>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[nitrux]]></category>
            <category><![CDATA[plasma-mobile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[kde]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Sun, 14 Apr 2019 03:45:03 GMT</pubDate>
            <atom:updated>2019-04-14T03:45:03.183Z</atom:updated>
            <content:encoded><![CDATA[<p>This year I attended to my first ever KDE Sprint, it was at Berlin and the work was focused on a super special project: Plasma Mobile.</p><p>I have been working on the MauiKit framework and the Maui set of apps for almost a year now, and some of those apps are are going to be shipped with Plasma Mobile by default, so my main work consisted on bringing those apps up to date, work on missing features and fix bugs along the way.</p><p>I also worked a little on getting acquainted with the Plasma Mobile shell, its <em>plasmoids,</em> how they work and how is structured, since I will be eventually hacking on it and start contributing. It is good to get used to it since I’ve been wanting since forever to work on a convergent launcher that can be used on desktop computers and phones, so there might appear a new option eventually.</p><p>So the big overview is that all the apps are now using a better modelling system that allows to have better control over the content, got a cleaner UI interface and gained some features along the way.</p><h4>Index</h4><p>A lot of work went into improving the mobile-ready file manager, Index.</p><p>It now makes use a proper model system and it is powered by a back-end provided by MauiKit FM (file management tools) that now allows to sort the content by title, size, modified date, etc.. it can also group files and folders by categories and sort folders first.</p><p>The UI was cleaned up and now everything is more user friendly.</p><p>You can also make searches, although this feature still needs some work.</p><p>The places sidebar now can show badges counting new files.</p><p>There is still a lot work to be done for Index, and being under active development you should expect more from this app pretty soon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_pV-ikrXAzrnRRU5fY2HgQ.png" /><figcaption>Index with a more cleared UI interface and showing an icon grid view and a list view with some basic information</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jC0NnIjaVupnD9jlPVTvrg.png" /><figcaption>Index search view and sorting options.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6DrffmmT3-T6gm-3OObDpw.png" /><figcaption>Places sidebar badges and new file dialog.</figcaption></figure><h4>Vvave</h4><p>Vvave is the music player, and I managed to completely improved the whole model system, and now it is a lot cleaner, faster and mature.</p><p>Also, thanks to the quick visit from a designer from the Gnome team, Vvave and the other apps got a little of UI clean up.</p><p>So, now Vvave can sort tracks, albums and artists; and the Now playing playlist is smoother and clearer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ta8rx-FApXJlCnleGolMaw.png" /><figcaption>Vvave sorting options thanks to new modeling</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EwNhGwK0aJKDwl86OaMwg.png" /><figcaption>New Vvave Now playing playlist view. Tracks can also be browsed from the toolbar with the current track info by swiping.</figcaption></figure><h4>Buho</h4><p>Buho saw some work on the Editor component which allows to take the notes. And also a complete rework of the modelling, allowing to sort the notes and links saved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TYNt6KTFTmutRWWIMDOxGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_a18L21d4GdV7IIOUGMl-Q.png" /></figure><h4>Pix</h4><p>Although Pix, the image viewer, is not going to be shipped by default, i also worked on it since it should be available for early users to test.</p><p>Now the image viewer can zoom in and out using the pinch gesture, and the UI got cleaned up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDp6mwYdxlphgukIOc-obw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uJHwwXXRlB8ly1SHM6tAFA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20031700b3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/maui-plasma-mobile-sprint-2019-c20031700b3b">Maui @ Plasma Mobile Sprint 2019</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Index — overview]]></title>
            <link>https://medium.com/@temisclopeolimac/index-overview-b2ddcb16534f?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2ddcb16534f</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[kde]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[maui]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Sun, 04 Nov 2018 21:30:43 GMT</pubDate>
            <atom:updated>2018-11-04T21:30:43.408Z</atom:updated>
            <content:encoded><![CDATA[<h3>Index — overview</h3><p>Index is a convergent file manager that works in GNU Linux desktop distributions, Plasma Mobile and Android.</p><p>Testing APK packages, you can find there Index pre-beta release:</p><p><a href="https://github.com/mauikit/APKS">mauikit/APKS</a></p><p>For trying Index on desktop you can grab the next Nitrux ISO build, compile the app yourself or wait for the beta release for DEB packages.</p><p>It is ready for a Beta release, and with this new entry I want to show you how it looks, works, and the future plans.</p><blockquote>Given that Index is a Maui app, and therefore it follows the Maui HIG by making use of the MauiKit, most of the UI/UX should be very familiar when you get to try all the other Maui apps, such as: Pix, VVAVE, Buho, and Nota.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c6-RtDq4-4ycj-xQWE0rMw.png" /></figure><p>Index also runs smoothly on small screen devices thanks to MauiKit and Kirigami. It sports convenient floating and foldable toolbars to release the clutter on such small devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*URpSkD11tBQTHPco2qVFJQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*CjFkEoNjtHcNAcw3yMvnQQ.jpeg" /><figcaption>Foldable toolbar with the quick action buttons. [left: unfolded, right: folded]</figcaption></figure><h3>Features</h3><h4>Selection bar</h4><p>With this selection bar you can select multiple files across different places. It is like collecting the files you need, and then you can perform the action on the group of selected files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uc3kM0BMeT7mkjqKM9yNrg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJU6B0hy94TPREgPTH7-yg.gif" /></figure><h4>View modes</h4><p>You can switch between a grid view and list view, and soon a Miller columns view is coming too. The preferred view mode is remembered by each directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jqHhGKoaWz9-l5GdJvkLA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HopHOkil2J2U2G1tAGSiYw.gif" /></figure><h4>Sorting and grouping</h4><p>You can sort your files by different filters, be it, by the name, size or creation date, last modified, and type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A4Yl2SVl3k1zWKZFcIiOOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xosv1ymgc6XQ2133z3qkiQ.gif" /></figure><h4>Bookmarking, thumbnail preview &amp; hidden files</h4><p>You can easily bookmark your most regular used directories and they will appear on the sidebar.</p><p>Also, you can switch on and off the thumbnail previews for image files, and soon also for videos, PDFs and text files. This preference is also remembered for each individual directory, same as viewing hidden files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*blLfKCJyU2lkYLuuOlkohg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*CstUGrtsmTJKBCcqQye_AA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*pkvcKBhGt6AoaOwbs5fWsQ.jpeg" /></figure><h4>Search</h4><p>Right now the search doesn’t looks into subdirectories, this is something that will be coming soon; for that labour, in GNU Linux Index will be using MauiKit File Management tools that include interfaces to work with KDE frameworks like Baloo and KIO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-dCqy2v0J0JOLsSuCV2AXw.gif" /></figure><h4>Path-bar</h4><p>Index sports a pathbar that shows you the exact place you are at, and also let’s you type custom paths and when needed it turns into a search field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*9aIZjOuUo8qqzyUXZuVDiw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*7ZhBKR3zZ7hDGs56N9b4uQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*MdkEI4uMh9xuRq_6HN4fPQ.jpeg" /></figure><h4>Places count badges</h4><p>The places sidebar watches the directories to detect changes and lets you know of new files with a count badge. This works also for your custom bookmarks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pSFq5YcBlpjZAbuSoHBeSg.gif" /></figure><h4>Previews</h4><p>You can quickly preview different type of files and get also some basic information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3jTl28T0EmWk5zwaOvre3w.gif" /></figure><h4>Embedded terminal</h4><p>In GNU Linux systems you can count with an embeded terminal. The terminal only shows on the directories you have set and this preference is also remembered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OIxHUSDQvTvanmg6TfnIhQ.gif" /></figure><h4>Others</h4><p>There are also some other small features, like zoom in and out, creating folders and files, sharing files, colouring the folders, etc…</p><p>If you get to try Index and like it or encounter some bus let me know and I will fix them asap. Keep in mind also that this is a pre-beta release intended for wider testing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2ddcb16534f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maui’s monthly]]></title>
            <link>https://medium.com/@temisclopeolimac/mauis-monthly-c39bbb2de9d0?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/c39bbb2de9d0</guid>
            <category><![CDATA[convergent]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kde]]></category>
            <category><![CDATA[mauikit]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Wed, 31 Oct 2018 21:27:25 GMT</pubDate>
            <atom:updated>2018-10-31T21:38:30.644Z</atom:updated>
            <content:encoded><![CDATA[<p>This month has seen several changes and new introductions to the Maui project, from new controls and utilities to the MauiKit Framework, to updated and improved Maui apps, and finally two new applications: Station and Nota.</p><blockquote>To test the Maui apps on Android you can download the APK packages from the following repo. Updated packages will be pushed soon.</blockquote><p><a href="https://github.com/mauikit/APKS">mauikit/APKS</a></p><p>For those who are still not familiar with MauiKit:</p><ul><li><a href="https://medium.com/nitrux/mauikit-ui-tweaks-papercuts-more-d6109f6a8c23">MauiKit UI tweaks/papercuts &amp; more</a></li><li><a href="https://medium.com/nitrux/maui-kit-921207e2d1a7">Maui Kit</a></li><li><a href="https://medium.com/nitrux/mauikit-622575c7b45a">MauiKit Controls</a></li><li><a href="https://medium.com/nitrux/the-nomad-project-522b2e8652c">The Maui Project</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yPSh3NHx7Rs_AR8DiCjocA.png" /></figure><h3>MauiKit: Updates &amp; News</h3><p>Here is a quick list of updates and news:</p><ul><li>Now MauiKit uses by default its own “Maui-Style” custom style on Android, before it was using the Material one.</li><li>Now MauiKit uses by default the Luv icon theme. To deploy on Android, devs just need to clone the Luv icon theme under “src/android/icons” and that’s it.</li><li>Some of the Maui apps are now being shipped by default by Plasma Mobile and also PostmarketOS.</li><li>The Maui apps are now available as preview in the new Nitrux OS iso.</li><li>MauiKit keeps on being optimized for small screens:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*K1NMFg6127xrNScF9cTrXg.png" /><figcaption>Index built using MauiKit running on Android in a 4 inches screen.</figcaption></figure><h3>MauiKit File Management tool</h3><p>This month a lot of work has gone into crafting a set of file management tools and controls that work smoothly, both, on Android and GNU Linux.</p><h4>FMList</h4><p>FMList implements a model for browsing the file system, both on Android and GNU Linux.</p><p>Right now FMList can interact with different kind of “paths”, not only regular file system paths, but also custom ones like:</p><h4>“Apps/”, “Apps/Multimedia”…</h4><p>To display the system installed apps and launch them.</p><h4>“Tags/painting”</h4><p>To display tags created using the MauiKit<em> Shared Tagging System</em>.</p><h4>“Search/.doc”</h4><p>To display files that match the search query</p><p>There are also plans to support remote paths and Trash path.</p><blockquote><strong>FM</strong> is the interface providing a lot of basic file management tools for the MauiKit classes, and is the base to built upon, later on, faster, robust and better tools. For example, on GNU Linux systems, FM will start making use of the <strong>KDE</strong> frameworks, such as <em>KIO</em> and <em>Baloo</em>.</blockquote><h4>FileBrowser</h4><p>FileBrowser is a new control introduced to MauiKit that makes use of FMList to provide by default a bunch of functionality related to file browsing and management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*Lt0u3FrsEIlSKEy8hGsHQQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*5GU47TIqYtC4WsDeyPJriA.png" /><figcaption>FileBrowser control. [left: being used on Index on Android]</figcaption></figure><p>The FileBrowser control is based on MauiKit Page control, and it has a top toolbar with quick action buttons, a floating bottom bar with the browsing action buttons; the main content view, which can be set to an icon view or list view, a selection bar that groups all the selected files and also a file previewer popup, that can be invoked on any file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*NiuraLGN2Lglo9mTu7jXcg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H_Dy8W1d_8kMKUVfCGNCXg.png" /><figcaption>FilePreviewer control on Index, both on Android and GNU Linux</figcaption></figure><p>The <strong>FileBrowser</strong> control is a very nice addition to the group of MauiKit controls, and it is being used right now by the default Maui apps, like Index( the file manager), Nota (a simple text editor), and finally, it is now powering the custom MauiKit FileDialog control. This means that all the improvements that go into this new control will be reflected on all the other apps using it.</p><p>You can now start using this control, and reduce a lot of time programming and be sure that it will continue to improve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*Fu20fEj9yIlLKdhmxtNT_A.png" /><figcaption>FileBrowser control</figcaption></figure><p>Some of the features that this control provides by default are:</p><ul><li>Watch changes on current path and refresh accordingly</li><li>Creation of files and folders</li><li>Previews of files such as images, videos, music and text in a convenient popup with basic details of the file.</li><li>Thumbnail previews of images (in the future this will be expanded to thumbnails previews of videos, PDFs and text files, too)</li><li>Two different views: icon views and a list view (a Miller Column view is coming along the way too)</li><li>Permanent storage of the preferences set for each directory, such as icon size, view mode, thumbnail previews, etc.. .</li><li>View hidden files.</li><li>A convenient selection bar to be able to select multiple files across different directories and places.</li><li>Copy, cut, paste, rename, share, remove actions.</li><li>Sorting by file type, modified date, creation date, size, name, etc…</li><li>Grouping files as a list view.</li></ul><h4>FileDialog</h4><p>This new control makes use of two new Mauikit controls: PlacesSidebar and FileBrowser.</p><p>The FileDialog is a popup dialog that allows you to select files or folders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ou0m5P2NmRbgjUJ1OFfnLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*T3rxX2z7Yul3xQNoI7Sw3A.jpeg" /><figcaption>FileDialog control [left: used on VVAVE on GNU Linux, right: used on Nota on Android]</figcaption></figure><p>It has a set of properties to interact with:</p><p><strong>string initPath:</strong></p><p>sets the initial path, for example, for selecting images a good initPath would be the Pictures directory.</p><p><strong>int mode :</strong></p><p>sets the mode for the FileDialog, there are two modes: <em>modes.OPEN </em>and<em> modes.SAVE</em></p><p><strong>var filters: []</strong></p><p>sets a custom list of filters, for example, to only show images: [“.png”, “.jpg”]</p><p><strong>int filterType:</strong></p><p>sets a standard filter, the values can be: FMList.NONE, FMList.IMAGE, FMList.TEXT, FMList.VIDEO.</p><p><strong>bool onlyDirs</strong>:</p><p>if true only directories will be display, by default his property is set to false</p><p><strong>int sortBy:</strong></p><p>values can be: FMList.MODIFIED, FMList.DATE, FMList.SIZE, FMList.LABEL, FMList.MIME</p><h4>PlacesSidebar</h4><p>This new control lists the common places of the file system for easier browsing. Right now, Index, Nota, and the FileDialog make use of this new control.</p><p>It has a <em>groups[] </em>property to set exactly what kind of places to display: FMList.PLACES_PATH, FMList.APPS_PATH, FMList.TAGS_PATH, FMList.DEVICES_PATH, FMList.BOOKMARKS_PATH.</p><p>Also, the control can track changes on different directories and show a badge that indicates the number of new files on such directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*SkUwRPcbaYZvKbFJs_g9Jg.gif" /><figcaption>PlacesSidebar control with count badges on Index</figcaption></figure><h3>Controls: Updates &amp; News</h3><p>This month MauiKit controls have some new members and some old ones have been updated:</p><h4>Editor</h4><p>This new control has the basic functionality needed to edit text.</p><p>It is being used currently on Nota and also on Buho.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*2VoOmMvBWIP7ZeqMMK7W5Q.png" /></figure><h4>Terminal</h4><p>This control is based on QMLTermWidget and currently it only works for GNU Linux. Android support might come later on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*dhY3dhlKtuMhYc6kc2Mxww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*y3zPoaGI6Cci6TrXg5jlcQ.png" /><figcaption>Terminal component on Index and Station</figcaption></figure><h4>Others</h4><p>Now MauiKit also includes this new controls that have been optimized and customized: Menu, MenuItem and TextField.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*M-buZ6wbPhsUXacTuxNf9w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*8BG289MDe9sERdOrGCFetA.jpeg" /></figure><h3>New Apps</h3><h4>Nota</h4><p>Nota is the new simple text editor for the Maui project.</p><p>In GNU Linux it sports an embedded terminal based on the new MauiKit control Terminal and also uses the Editor control.</p><p>The apps is in a very early stage and it is not yet fully functional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*wedCA5M5qZ-jFgjuarEVrw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nSOv2rNnMB6lxBwDaWDzVw.png" /><figcaption>Nota running on Android and GNU Linux</figcaption></figure><h4>Station</h4><p>Station is a simple terminal emulator. It currently only works on Plasma Mobile and GNU Linux distros.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3cuI2UCuaBal5pmXIdB8NQ.gif" /></figure><p>If you reach to this point, please let me know your thoughts, ideas and suggestions. Also, if you have any kind of questions regarding the project let me know in the comments and I will prepare a Q&amp;A post to answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c39bbb2de9d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MauiKit UI tweaks/papercuts & more]]></title>
            <link>https://medium.com/nitrux/mauikit-ui-tweaks-papercuts-more-d6109f6a8c23?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6109f6a8c23</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kde]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Sun, 30 Sep 2018 16:57:09 GMT</pubDate>
            <atom:updated>2018-09-30T17:12:37.571Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>MauiKit is a framework based on QQC2 and Kirigami, that helps to create convergent applications that run on GNU Linux and Android, based on the Maui HIG.</blockquote><p>This posts aims to show the ongoing work on the UI/UX design, this is still a work in progress so things might changed or get discarded.</p><h3>Coloring/Branding</h3><p>You can set custom colours for the main ApplicationWindow HeadBar using the property <strong>headBarBGColor</strong> and MauiKit will automatically detect changes to it and set the colour of the window decoration and status bar, accordingly, under KDE and Android.</p><p>This allows apps to set a distinct colour brand but still keep the Maui HIG in place.</p><p>Also, it let’s apps set different colours depending on the view and its content, for example, on Pix, the image gallery app, the colour shifts from the default one to a dark one when viewing an image, this allows to focus more on the content.</p><p>To allow this, the MauiKit controls now has a nice colorScheme property you can modify to give each widget/control that special colour accent you want.</p><p>For example, to colourize a MauiKit.Button:</p><blockquote>colorScheme.backgroundColor: “#333”</blockquote><blockquote>colorScheme.textColor: “#fff”</blockquote><blockquote>colorScheme.borderColor: “#444”</blockquote><p>this will only affect that single instance of the button while still keeping all the other properties defined by the MauiHIG.</p><p>and you can still modify the global colours properties to change the colour for all the controls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*YDaEXtXFVS7S-VxSHy9hzQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*OpcjCylSLDRfDIcTw4GAsA.gif" /></figure><h3>Flickable ToolBars</h3><p>Maui.ToolBar is divided into three areas: a rightContent, leftContent and middleContent.</p><p>You can add any kind of control to those areas and rest assure that when the screen size gets too small in width all of the content inside the Maui.Toolbar will still be reachable. This is done within the MauiKit control by making use of a <em>flickable</em> toolbar that allows to slide the content to uncover the hidden controls.</p><p>There are two parts for this flickable action, the first one is within the middleContent area. While the leftContent and rightContent area will still be visible if the space is enough to fit them, the middleContent will be flickable if its content is too wide to fit in the middle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*p4dv1t0a7EuW_m4gveOYQg.gif" /></figure><p>This is better explained with an example, all the Maui apps have a HeadBar that contains a menu button, the views icons and finally a search button, the right and left icons will still be visible as long as they fit in the application window width, and the middle content, meaning the different views icons, will be flickable. This is done so to keep the right and left content visible as long as possible.</p><p>The second part of this flickable action is found when the application window width can not longer fit its children content, so the controls will be flickable horizontally.</p><p>There is also some small UI elements to indicate that the content can be uncovered, such as a small line separator for the middleContent and a drop shadow for the left and right side.</p><p>This is true for all the Maui.ToolBars, and allows to place not only actions or button inside the toolbar, but any other kind of control, such as Maui.TextEntry, Maui.PathBar, etc…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*aWfpiGL--CPTD8CjJGkMKg.gif" /></figure><h3>Maui.ToolButtons text</h3><p>As you maybe have already noticed the Maui apps use on their HeadBars different Maui.ToolButtons with an icon with text besides it; this layout now changes to text under the icon, if the width of the application window is not wide enough.</p><p>This, of course, won’t affect the Maui.ToolButton s without a text property set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*HZ3GMCOFbchWQJ7Ah2tLew.gif" /></figure><h3>Maui.Popup and hints</h3><p>Now MauiKit includes a Popup control that adds some new properties to handle its sizing:</p><p>widthHint, heightHint, maxWidth, maxHeight</p><p>with widthHint and heightHint you give a hint about the size of the popup from 0.0 up to 1, relative to the popup parent’s size.</p><p>and with maxWidth and maxHeight you can set a maximum value for popup height and width.</p><p>For example, on Buho, the notes taking app, the notes dialog-popup has a maximum height and width established but its widthHint and heightHint is 0.9 relative to its parent, so it will take up to the 90% of its parent space but not more than the maxHeight and maxWidth set.</p><p>This behaviour is very useful to set a responsive size for popups on small screens like on phones, but still keep its size from turning too huge on bigger screens like on desktop computers screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LCWOgKjPST4uwdSvk6zuhA.gif" /></figure><h3>About Dialog</h3><p>Now all the Maui apps have this nice About dialog by default without the need to set up anything. MauiKit retrieves the necessary information such as application name, version and icon.</p><p>However, more information can be set by making use the property<em> about, such as:</em></p><h4><strong>string about.appDescription:</strong></h4><p>sets a description text for the application. It is placed within a TextBrowser view. By deafult this property is empty</p><h4>string about.appName:</h4><p>sets the name of the application. By default this value is retrieved from the value set on QApplication or QGuiApplication.</p><h4>string about.appVersion:</h4><p>sets the version of the application. By default this value is retrieved from the value set on QApplication or QGuiApplication.</p><h4>string about.appIcon:</h4><p>sets the icon of the application. By default this value is retrieved from the value set on QApplication or QGuiApplication.</p><h4>string about.appLink:</h4><p>sets the link to the website of the application, and can be accessed from the middle icon on the dialog. By default this value links to the official Maui website.</p><h4>string about.appDonation:</h4><p>sets the link to a donation or crowdfunding website, and can be accessed from the right side icon on the dialog. By default this value is empty.</p><h4>string about.organizationName</h4><h4>string about.organizationDomain</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*nHmTq0P9_uLDFNVmGPKx6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*c4nZSxwWHQat9QV4o5r1eA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*irbMyuVFU4CeXE25bDtLJA.png" /></figure><h3>Maui Apps on tiny screens</h3><p>MauiKit is constantly being deployed on different platforms and devices to test the implementation of its controls on different screen/form factors.</p><p>Even on the most tiny smartphone screens running Android.</p><p>Here, all the work put into the convergence flow of the controls can be tested and fine tuned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*yxCaDwckfIsgWS1vAJO62A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*Mv0tiSNvYb1CqU02UoMq6g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*uxh_mIMeQXwNvj6LjMeMyw.jpeg" /></figure><h3>Maui Apps on Remix OS / Chrome OS</h3><p>Same goes for testing MauiKit on even “larger” screens running Android, such as desktop devices. In this case the tests have been done on RemixOS and even on Chrome OS, to test the convergence of the controls under Android.</p><p>It is also the case of testing for GNU Linux distros both on mobile and desktop devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7eXydfJFpwv6IEbrsBCBRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mL1uCGxJj0n_B7yLvimNIw.png" /></figure><h3>Maui.GridView</h3><p>Another control that has been introduced to MauiKit is the GridView.</p><p>This new control allows to display elements on a grid that gets resized automatically to keep an uniform cell size.</p><p>It can also centre the cells.</p><h4>int spacing:</h4><p>sets the spacing between the cells. By default his value is set to the global property <em>space.medium</em></p><h4>int itemSize:</h4><p>sets a hint about the size of the item to be contained inside the grid cell, this allows to resize the grid cells to keep an uniform size based on the value of the item. This could be think of as a minimum size for the cell size, both height and width. By default this property is set to 0.</p><h4>bool centerContent:</h4><p>if set to <strong><em>True </em></strong>the cells will be centred. by default this property is set to <strong><em>False.</em></strong></p><h4>bool adaptContent:</h4><p>if set to <strong><em>True </em></strong>the cells will be resized automatically to fill the GridView width uniformly, the minimum value the cell will take is the value set with the property <em>itemSize</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6c038vOvRm1n4h5uZ443Jg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMLMOt-dgvc8_JrCw97Ihg.gif" /></figure><h3>ColorScheme</h3><p>MauiKit controls now make use of this new Object that allows to colourize each control individually but still falling back by default to the main application colour scheme.</p><p>How does this work?, well, each control now has a new property named <em>colorScheme. </em>With this new property the colours for a control can be changed to better fit the design needs, while still retaining the other aspects of the control.</p><p>For example, to set a custom colour to Maui.Button:</p><p>colorScheme.backgroundColor: “green”</p><p>or more in detail:</p><p>colorScheme.borderColor: “red”</p><p>colorScheme.backgroundColor: “transparent”</p><p>All of the based colour scheme colours defined int he global ApplicationWindow properties can be changed within each control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*W6mZFFoiuN3QVyhMfmQ3Gg.png" /></figure><h3>Maui.PieButton</h3><blockquote>This will probably be renamed to better fit the new design, but while that is done, let me introduce this new control to you.</blockquote><p>The Maui.PieButton is a control based on Maui.ToolButton that launches an horizontal popup with a Maui.ToolBar within. This allows to have an Android like FAB button with contextual actions.</p><p>Given that the popup is based on Maui.ToolBar it will inherited all its properties including the flickable behaviour when its children content can not longer fit its width size.</p><h4>int alignment:</h4><p>set the alignment of the popup relative to the control. Possible values are Qt.AlignLeft or Qt.AlignRight. By default the value is set to Qt.AlignLeft.</p><h4>int barHeight:</h4><p>sets the height for the popup. By default the value is set to 0</p><h4>int maxWidth:</h4><p>sets the maximum width for the popup, affecting the toolbar within.</p><h4>list[Object] content:</h4><p>with this property the popup Maui.ToolBar can be filled with any kind of controls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*1jvdW1XWDg7daLyZqVnZRA.gif" /></figure><h3>Maui.Dialog</h3><p>MauiKit now also has a Dialog control.</p><p>This new control is based on Maui.Popup, so it inherits the new Popup hints properties.</p><p>Maui.Dialog has a basic layout based on Maui.Page, so it has, by default, as <em>footBar.rightContent </em>two Maui.Buttons colourized with the <em>colorScheme</em> property to indicate a “reject” and “accept” response.</p><p>This control has the following properties:</p><h4>string message :</h4><p>sets the message body of the dialog. By default this property is empty.</p><h4>string title:</h4><p>sets the title of the dialog. By default this property is empty.</p><h4>string acceptText:</h4><p>sets the text for the accept button. By default this property is set to “Ok”</p><h4>string rejectText:</h4><p>sets the text for the accept button. By default this property is set to “No”</p><h4>bool defaultButtons:</h4><p>if set to <strong><em>True </em></strong>the dialog will display the accept and reject default buttons. By default this is set to <strong><em>True</em></strong></p><h4>bool entryField:</h4><p>if set to <strong><em>True </em></strong>the dialog will display a Maui.TextEntry above the footBar area. By default this is set to <strong><em>False</em></strong></p><h4>alias textEntry</h4><h4>alias footBar</h4><h4>alias headBar</h4><h4>alias headBarTitle</h4><h4>signal accepted()<br>signal rejected()</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*dyYRgRW7Iguz0io1-9536Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*iucMEJCL6sLF06RA2BJHwQ.png" /></figure><p>There is probably a bunch of things I’ve forgotten to add here, but as my head is all over the place maybe on a latter post I will include them.</p><p>As always, if you like this project and find it interesting and want to contribute with coding, design, distribution, translations, documentation, etc … let me know. I’m always around telegram as @milohr, and on Github, KDE Phabricator, email milo.h@aol.com. or just comment here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6109f6a8c23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/mauikit-ui-tweaks-papercuts-more-d6109f6a8c23">MauiKit UI tweaks/papercuts &amp; more</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maui Apps— APK packages]]></title>
            <link>https://medium.com/nitrux/maui-apps-apk-packages-5c966f185f0c?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c966f185f0c</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kde]]></category>
            <category><![CDATA[kirigami]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Sat, 25 Aug 2018 19:47:27 GMT</pubDate>
            <atom:updated>2018-08-25T19:47:27.932Z</atom:updated>
            <content:encoded><![CDATA[<p>The Maui Project is a set of basic applications that follow a cohesive HIG that aims for convergence, that meaning that the same app can be used on mobile and desktop devices, such as GNU Linux distributions, Plasma Mobile and Android, and eventually even on Mac OS X, IOS and Windows.</p><p>The project is still in a very early stage but can be already tested on Linux distributions and Android, by building it yourself from the sources or using the APK packages provided:</p><p><a href="https://github.com/maui-project/APKS">maui-project/APKS</a></p><p>To allow a wider testing of this applications I have created APK packages that should be updated every week for you all to test the latest changes.</p><p>So if you’re feeling adventurous and want to try something new and give feedback, this post is for you.</p><p>The apps that currently make part of the project and can be tested are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*OaYPOtfYIaD9r9F67Hj-Xg.jpeg" /></figure><h3>Index</h3><p><em>file manager</em></p><p>Index — Maui’s file manager allows to browse your files and folders using an icon and list view with small preview thumbnails that are resize-able. You can also preview your files content like music files, videos, images, etc… on the information sidebar drawer. You can make multiple selections across different places and folders and then copy, cut, remove or share such selection of files or folders. Also, you can browse your content by tags that were used on all the other Maui applications.</p><p>For Linux based distributions you can even browse your installed applications and launch them from Index.</p><h4><a href="https://github.com/maui-project/APKS/blob/master/Index/index-signed.apk">Download APK</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*sLfjL-7aJf8ZSX-l9AUFsA.jpeg" /></figure><h3>Pix</h3><p><em>image viewer</em></p><p>Pix— Maui’s image collection manager allows to browse your images and view them organized by album, folders and tags.</p><p>Pix UI is thought to work nicely both on desktop and touch devices.</p><p>The tags used on Pix can also be visible on all the other Maui apps.</p><h4><a href="https://github.com/maui-project/APKS/blob/master/Pix/pix-signed.apk">Download APK</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*4NOH0X_rwbidNubXvvK9rA.jpeg" /></figure><h3>VVAVE</h3><p><em>music player</em></p><p>VVAVE— Maui’s music player allows to browse your music collection organized by artists, albums, tracks, playlists and tags such as genres, composers, stats, similar artists, etc..</p><p>VVAVE also shows you contextual information about your music collection such as wikis and music lyrics, so you can have all in one application to carry around.</p><p>Also, you can sync playlists, share your collection on local networks and search for YouTube videos on the app itself.</p><h4><a href="https://github.com/maui-project/APKS/blob/master/VVAVE/vvave-signed.apk"><strong>Download APK</strong></a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*x8tzthPDoneqyaXK9PWW9Q.jpeg" /></figure><h3>Buho</h3><p><em>notes taking</em></p><p>Buho— Maui’s notes taking app allows to take quick notes, put together books with chapters and save links.</p><p>You add tags to your notes and with the chrome/firefox extension collect links while you browse the internet.</p><h4><a href="https://github.com/maui-project/APKS/blob/master/VVAVE/vvave-signed.apk">Download APK</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c966f185f0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/maui-apps-apk-packages-5c966f185f0c">Maui Apps— APK packages</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maui RoadMap]]></title>
            <link>https://medium.com/nitrux/maui-roadmap-c303cacf21eb?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/c303cacf21eb</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kde]]></category>
            <category><![CDATA[nitrux]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 13:01:00 GMT</pubDate>
            <atom:updated>2018-08-21T13:01:00.497Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This year KDE’s Akademy event is officially over and there is now a clear road map for the near future of the Maui Project.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*mEjP6v_pmuDGjOgNpMZo3w.png" /></figure><p>At this year’s Akademy event I talked about VVAVE, the music player that forms part of the Maui Project, and also had the chance to have a discussion around the MauiKit and the other Maui apps about design and development with distribution packagers, designers, developers and other supportive people.</p><p>With this post, my idea is to give you all who are interested in the project a quick overview of what happened at the Akademy event and what’s going to happen next in the near weeks and month.</p><p>So let’s start by the most basic issue that was raised: there was not an easy way to test the applications, the only way was to compile everything from source and even then there were submodules not picking up correctly.</p><p>So that’s the first issue to target on the near roadmap, to release testing packages within the KDE infrastructure, which should allow the Maui apps to be available on the unstable or testing repositories of KDE Neon to easily test the project on Plasma Mobile, Plasma Desktop and also get DEB and APK packages to distribute to elsewhere.</p><p>To make that happen in first place the MauiKit project has to become a full framework instead of working just as a simple submodule. A few steps towards this direction has been made by making Mauikit support cmake instead of just qmake, this move has also been made for all the other Maui apps. <br>After this step is done the MauiKit should be distributed and installed system-wide and then used locally by all the other Maui apps instead of statically linking to the kit.<br>Once that work is done and the project is out in the wild the idea is to get as much feedback and bug reports as possible form the community and improve the apps based on the reports.</p><blockquote>So to recap, the near road map plans aim to make releases of the Maui apps under the KDE infrastructure.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Ug5vFfsjetOiAFZef-W9g.png" /></figure><p>Parallel to that endeavor there will be still an ongoing work on improving the current set of applications back-ends and the integration with the supported/targeted system and devices in order to make beta releases before the stable ones, and also work on the front -end to improve on the Maui HIG and its controls on the side of the MauiKit project.</p><p>For example Index, the file manager will start making use of KDE framework APIs, such as Baloo, KIO and others.<br>All the benefits made on the MauKit should be immediately available on all the other applications.</p><p>So far the plans are:</p><ul><li>Make MauiKit a framework</li><li>Move the apps to make use of cmake instead of qmake</li><li>Set up everything to work with the KDE infrastructure</li><li>Work on the Maui apps back-ends and improve the front-end on the MauiKit side</li><li>Release of testing packages</li></ul><p>And finally, there will be a lot of work dedicated to make all the Maui apps to be on sync between devices, versions and distributions.<br>The idea is to sync all the information that makes sense to be synced. The first iterations of such system would be part of the MauiKit project and probably <br>will make use of other open source services such as NextCloud; this idea applies to Index, VVAVE, Buho and even Pix.</p><p>Then once these goals are meet I’ll start working on finishing up the basic set of convergent applications adding a simple text editor, video player, and a launcher.</p><p>There will be still iterations on the design of the MauiKit controls but that is something is I’ll cover on another post, and let you know what happened on the Maui BOF session at this year’s Akademy event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*sLfjL-7aJf8ZSX-l9AUFsA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*OaYPOtfYIaD9r9F67Hj-Xg.jpeg" /><figcaption>Pix &amp; Index</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*x8tzthPDoneqyaXK9PWW9Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*4NOH0X_rwbidNubXvvK9rA.jpeg" /><figcaption>Buho &amp; VVAVE</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c303cacf21eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/maui-roadmap-c303cacf21eb">Maui RoadMap</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proyecto MauiKit]]></title>
            <link>https://medium.com/nitrux/proyecto-mauikit-550549ddb555?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/550549ddb555</guid>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kde]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 11:48:13 GMT</pubDate>
            <atom:updated>2018-08-20T18:10:20.317Z</atom:updated>
            <content:encoded><![CDATA[<p>El proyecto <strong>MauiKit</strong> hace parte del proyecto <strong>Maui</strong> que apunta a completar un <em>shell</em> para una distribución GNU Linux con aplicaciones convergentes y <em>multiplataforma</em> que se adapten a pantallas de computadoras de escritorio, a teléfonos móviles y otro tipo de dispositivos táctiles.</p><p>Para esta tarea se hace necesario establecer un serie de lineamientos para el HIG(<em>human interface guidelines</em>) del proyecto Maui, que sean probados y aplicados en el grupo de aplicaciones básicas que hacen parte del <em>shell</em>.</p><p>Otro lineamiento esencial del proyecto es mantener un HIG cohesivo y estricto entre las aplicaciones que mantenga una estabilidad y coherencia en el diseño UI/UX a traves de dispositivos y sistemas/distribuciones.</p><p>Basado en el <em>framework</em> <strong><em>Kirigami</em></strong>, de la comunidad <strong><em>KDE</em></strong>, se ha trabajado en un grupo de controles modelados siguiendo un HIG descrito para las aplicaciones Maui, el cual esta siendo desarrollado exclusivamente para el proyecto.</p><p>En la siguientes imágenes(<em>mockups</em>) se ilustra algunas de las ideas fundamentales del HIG que se han aplicado a los controles dentro del proyecto <strong>MauiKit</strong>.</p><blockquote><strong><em>MauiKit</em></strong> es un grupo de controles con un diseño pre-modelado que permite un rápido desarrollo del <em>front-end</em> de aplicaciones convergentes, con utilidades incluidas para Android y sistemas GNU Linux.</blockquote><p><a href="https://github.com/maui-project/qqc2-desktop-style-maui/issues/2">https://github.com/maui-project/qqc2-desktop-style-maui/issues/2</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0eHV4OZEDCYYYqNvkGxfNg.png" /><figcaption>Ilustración 1.1</figcaption></figure><p>EL HIG describe principalmente un <em>layout </em>(distribución) horizontal de las vistas de la aplicaciones <strong><em>Maui</em></strong>. Esta distribución horizontal puede ser plegable(<em>PageRow</em>) para adaptarse a diferentes <em>form factors(</em>factores de forma) que se asemeja a un abanico de papel (ver ilustración 1.1–1.2), o utilizar una aproximación mas tradicional haciendo uso de vistas individuales apiladas no plegables(<em>SwipeView o StackView</em>), e incluso una combinación de ambas como se muestra en la ilustración 1.3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gnTve1tlL7ft76heo28u1Q.png" /><figcaption>Ilustración 1.2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8zManWM5PsDDgFmdLKXxmA.png" /><figcaption>Ilustración 1.3</figcaption></figure><h3>Las Aplicaciones Maui —<em> ApplicationWindow</em></h3><p>El contenido por defecto de las aplicaciones Maui contiene dos barras de tareas y un espacio central donde se ubica el contenido principal de la aplicación.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cIG7WQfLsg9-pTYTVjnuZQ.png" /><figcaption>VVAVE Music Player</figcaption></figure><p>Las <em>ToolBars</em>(barras de tareas) se dividen en dos principalmente, una de encabezado llamada <strong><em>HeadBar</em></strong> y una de pie llamada <strong><em>FootBar.</em></strong></p><p>La barra <strong><em>HeadBar</em></strong> contiene los botones que accionan las vistas principales de la aplicación y permiten el transito entre las diferentes vistas, también contiene, por defecto, un icono a la izquierda para el menu que despliega las opciones globales de la aplicación, y un icono para accionar búsquedas en la parte mas derecha, sugerido como un lugar común para realizar búsquedas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9K1chKYMHvbXGpW5OPipg.png" /><figcaption>Barras de tareas — FootBar y FootBar en Buho</figcaption></figure><p>El <strong><em>FootBar</em></strong> contiene iconos que funcionan como atajos rápidos que permiten operar las acciones mas relevantes de la aplicación, como por ejemplo las acciones de reproducción en un reproductor musical. La posición del <strong><em>FootBar</em></strong> en el pie de la aplicación es ideal para diferentes <em>form factors</em> ya que permite un alcance rápido en dispositivos móviles y táctiles. Esta ubicación para las acciones permite establecer un lugar común y habitual para los usuarios.</p><p>La distribución de <strong><em>HeadBar</em></strong> es adaptable para dispositivos móviles, lo cual permite mover la barra de tareas <strong><em>HeadBar</em></strong> al pie de la vista para mejor alcance con una sola mano. Esta opción es ideal para dispositivos móviles, pero puede ser usada en cualquier vista que haga sentido.</p><p>El la imagen 1.4 se muestra el uso del <strong><em>HeadBar</em></strong> y <strong><em>FootBar</em></strong>, ambos en el pie de la vistas, para dispositivos móviles, en este caso funcionando en un Phablet con el sistema Android.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3qa9th8qRxF88iy91SVNSw.png" /><figcaption>Ilustración 1.4</figcaption></figure><p>Las barras de tarea son sensibles al ancho de pantalla del dispositivo, si el contenido hijo no cabe en el espacio disponible las acciones en forma de iconos pueden ser <em>flicked(deslizadas) </em>para descubrir las acciones ocultas, como se muestra en la ilustración 1.5.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*zaqVeYaE0w0IVjKCRGz1_w.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*BJ0l7gpZA_7KEn5oK3P36A.gif" /><figcaption>Ilustración 1.5</figcaption></figure><p>Las propiedades de estos controladores estan descritas en los siguientes artículos:</p><ul><li><a href="https://medium.com/@temisclopeolimac/mauikit-page-and-toolbar-7e7320d5183f">MauiKit — Page and ToolBar</a></li><li><a href="https://medium.com/@temisclopeolimac/mauikit-622575c7b45a">MauiKit Controls</a></li></ul><p>Ya que los controles se encuentran en constante cambio las notas anteriores no suponen una versión definitiva de documentación, si no, un articulo informativo en el avance del proyecto.</p><p>Algunas de las aplicaciones que hacen parte del proyecto que hacen uso activo de los lineamiento HIG son:</p><p><strong><em>Index</em></strong>, gestor de archivos y ficheros.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*Tr7_elMxWIHxTOSflOKgAQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3NQaHfftiMdDVsrTaR7tBA.png" /><figcaption>Index en dispositivo móvil y de escritorio</figcaption></figure><p><strong><em>Buho</em></strong>, gestor de notas y colector de vinculos <em>links.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IY_qzRDlD8j2CzLNAA9Fbw.png" /></figure><p><strong><em>VVAVE</em></strong>, gestor de colección musical.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8_RV_w0JOWBRENoUEtgrg.png" /></figure><p><strong><em>Pix</em></strong>, gestor de imágenes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*z1mfdmvRs1FiqetqNFcuTA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TCChYY9Id54pQqsLE0h4BQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=550549ddb555" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/proyecto-mauikit-550549ddb555">Proyecto MauiKit</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MauiKit — Page and ToolBar]]></title>
            <link>https://medium.com/nitrux/mauikit-page-and-toolbar-7e7320d5183f?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e7320d5183f</guid>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kirigami]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[nitrux]]></category>
            <category><![CDATA[kde]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 17:03:27 GMT</pubDate>
            <atom:updated>2018-08-01T17:13:24.003Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>MauiKit — Page and ToolBar</strong></p><p>To continue the <a href="https://medium.com/@temisclopeolimac/mauikit-622575c7b45a">previous post</a> about how to use the Maui Kit controls, where I first introduced the ApplicationWindow part with its properties and components, on this new post I will write about the current state of the Page and ToolBar controls that make part of the Maui Kit and have been optimized for convergence and are in continue development.</p><h3><strong>Page</strong></h3><p><a href="https://github.com/maui-project/mauikit/blob/master/src/controls/Page.qml"><em>Source code</em></a></p><p>A page is an essential component inside the Maui Kit. A page allows you to layout the content following the Maui HIG and take advantaged of the templated controls inside of it that make it easier to adapt the UI from desktop to mobile devices.</p><p>The Page control contains the same implementation as the ApplicationWindow, since the ApplicationWindow uses the Page control as its base component.</p><p>That means that you have a <strong>HeadBar</strong>, a <strong>Content</strong> area and a <strong>FootBar</strong>, and the toolbars can be moved and tweaked by making use the properties: <em>altToolBars</em>, <em>floatingBar</em>, <em>footBarOverlap</em>, etc…</p><blockquote>import org.kde.maui 1.0 as Maui</blockquote><blockquote>Maui.Page {}</blockquote><p>The following screenshots show Index, a file manager, making use of the Maui.Page control for the browser view with a floating <strong>FootBar</strong> that overlaps the content and when needed moves back to its own reserved space. This can be done by populating the <em>footBar</em> aliases, and setting to <strong>true</strong> the properties: <em>floatingBar</em>, <em>footBarOverlap</em> and <em>allowRiseContent.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i62rvcdNlRbObVxOY_D_5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nTFMr5fiW-DdjbYRI_zSyg.png" /></figure><p>The following screenshots show VVAVE making use of the Maui.Page control on the right and left view of the <strong>Kirigami.PageRow</strong>. The property <em>altToolBars</em> is set to <strong>true</strong> for the right view and a floating <strong>FootBar</strong> is being used on the right playlist with the property <em>footBarOverlap</em> and <em>floatingBar</em> set to <strong>true</strong>.</p><p>Setting the <em>altToolBars</em> property to the <em>isMobile</em> read-only property is useful for reach-ability of the Page actions on mobile devices such as Phones, Phablets and Tablets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jfmx8iRwhZf9id7Z4E96fQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*Ue86dyvhott11FjYx6lvuQ.png" /></figure><h4>Properties:</h4><p><strong>bool</strong> headBarVisible :</p><p>By default the HeadBar is visible and contains an exit button. This can be modified my setting this property to <strong>false</strong> or setting the headBarExit property to <strong>false </strong>and leaving the HeadBar empty.</p><p><strong>bool</strong> footBarVisible :</p><p>By default the FootBar is not visible. This can be modified my setting this property to <strong>true </strong>or adding components to the FootBar</p><p><strong>bool</strong> headBarExit :</p><p>By default the HeadBar contains an exit button on the left side, this can be modified by setting this property to <strong>false</strong> o changing the exit button icon with the property <em>headBarExitIcon</em></p><p><strong>bool</strong> headBarTitleVisible :</p><p>By default the middle content of the HeadBar is set to contain a title, this can be changed by setting this property to <strong>false</strong>.</p><p><strong>string</strong> headBarExitIcon :</p><p>By default the HeadBar exit button has an icon named “dialog-close”, it can be changed to whatever other icon name that makes more sense.</p><p><strong>string</strong> headBarTitle :</p><p>By default the HeadBar contains a title that is placed on the middle, the title can be set with this property.</p><p><strong>int</strong> margins :</p><p>By default the margins for the Page main content are set to :</p><p><em>contentMargins * 1.5</em></p><p>This can be changed to better adjust to your application design.</p><p><strong>int</strong> footBarAligment :</p><p>By default it is set to <strong>Qt.AlignCenter</strong>, but can be set to any other alignment value. Changes will be only visible if the <em>floatingBar</em> property is set to <strong>True</strong>.</p><p><strong>bool</strong> altToolBars :</p><p>If set to <strong>True</strong>, the HeadBar will be moved to the bottom of the application window. By default this property is set to <strong>False</strong></p><p><strong>int</strong> footBarMargins :</p><p>This property adds margins to the FootBar when it is set as a floating bar using the <em>floatinBar</em> property. It is useful when the FootBar needs to stand out.</p><p><strong>bool</strong> floatingBar :</p><p>If set to <strong>True</strong>, the FootBar will act as a floating bar, it will not occupy the full width of the application window, but instead use the minimum width required to place its children content. Also it will be coloured by making use of the global theming property <em>accentColor </em>and cast a shadow<em>.</em></p><p>By default the floating bar does not overlaps the content, to make it overlap the content the <em>footBarOverlap</em> property will have to be set to <strong>True</strong></p><p>By default this property is set to the<em> altToolBars </em>property.</p><p><strong>bool</strong> footBarOverlap :</p><p>If set to <strong>True</strong>, and also only if the <em>floatingBar</em> property is set to <strong>True </strong>too, the FootBar will act as a floating bar overlapping the content of the window.</p><p>When this property is set to <strong>True</strong>, the content will flick when scrolled down to show a reserved space for the FootBar in order to not overlap important content positioned at the bottom.</p><p>By default this property is set to <strong>False</strong></p><p><strong>bool</strong> allowRiseContent :</p><p>If the properties <em>floatingBar</em> and <em>footBarOverlap</em> are set to <strong>True</strong> this property can be modified allowing the content to be elevated when it reaches the bottom or end. This allows to reveal a reserved space for the floating bar so the FootBar don’t cover important content when needed.</p><p>By default this property is set to:<strong> floatingBar &amp;&amp; footBarOverlap</strong></p><p><strong>bool</strong> contentIsRaised :</p><p>Allows to know if the content flickable is raised up or not.</p><h4>Aliases:</h4><p><strong>alias</strong> headBar :</p><p>This alias allows you to modified the HeadBar and add content to it. The HeadBar is based on Maui.ToolBar so it inherits all its properties, such as:</p><p>headBar.leftContent: []</p><p>headBar.middleContent: []</p><p>headBar.rightContent: []</p><p>headBar.background: {}</p><p>and all the others…</p><p><strong>alias</strong> footBar :</p><p>This alias allows you to modified the FootBar and add content to it. The FootBar is based on Maui.ToolBar so it inherits all its properties, such as:</p><p>footBar.leftContent: []</p><p>footBar.middleContent: []</p><p>footBar.rightContent: []</p><p>footBar.background: {}</p><p>and all the others…</p><h4>Signals:</h4><p><strong>signal</strong> exit :</p><p>This signal is emitted when the HeadBar exit button is clicked.</p><h3>ToolBar</h3><p><a href="https://github.com/maui-project/mauikit/blob/master/src/controls/ToolBar.qml"><em>Source code</em></a></p><p>Maui Kit implements the ToolBar as a horizontal layout with three sections: a <strong>leftContent</strong>, <strong>middleContent</strong> and <strong>leftContent </strong>that can be populated with other controls such as buttons, labels and tool buttons.:</p><p>The ToolBar is a flickable, which means that if the size of its children content can not fit in the available width then the content will be flicked horizontally, allowing to discover the remaining actions, buttons, labels, etc… that couldn’t be fitted by scrolling horizontally.</p><p>The following screenshot shows Buho, a notes taking app, making use of the Maui.Page control that uses the Maui.ToolBar. On the HeadBar the three sections are visible:</p><p>leftContent: has a hamburger menu tool button</p><p>middleContent: has a list of tool buttons, fo notes, links, books and tags</p><p>and finally, the rightContent: has a search tool button</p><p>while the FootBar of the Maui.Page only has a middleContent that includes an add tool button, and the ToolBar has been aligned to the right side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwKh124-gzCVZANUdpjeaA.png" /></figure><p>When the content of the ToolBar can not be fitted on its width then the content will be able to be flicked horizontally to revealed the remaining actions.</p><p>The following images demonstrate how this behaviour works when the width of the window is minimal. This is useful when there are several actions inside the tool bar and there’s not much width, like on small phones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*QNevb6jWB1iKYNG6M_ss4A.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*tPs4_YtCkHlp4RbOmaOWUQ.gif" /></figure><h4>Properties:</h4><p><strong>int</strong> margins:</p><p>This property allows to set a margin space, by default it is set to the global property :<em> space.medium</em></p><p><strong>int</strong> count :</p><p>This property indicates the total number of child items inside the ToolBar</p><h4>Aliases:</h4><p><strong>alias</strong> leftContent :</p><p>This alias allows to add content to the left side of the tool bar.</p><blockquote>leftContent: Maui.ToolButton {id: btn1}</blockquote><p>or</p><blockquote>leftContent: [</blockquote><blockquote>Maui.ToolButton {id: btn1},</blockquote><blockquote>Maui.ToolButton {id: btn2},</blockquote><blockquote>Maui.ToolButton {id: btn3}</blockquote><blockquote>]</blockquote><p><strong>alias</strong> middleContent :</p><p>This alias allows to add content to the middle side of the tool bar.</p><p><strong>alias</strong> rightContent :</p><p>This alias allows to add content to the right side of the tool bar.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e7320d5183f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/mauikit-page-and-toolbar-7e7320d5183f">MauiKit — Page and ToolBar</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MauiKit Controls]]></title>
            <link>https://medium.com/nitrux/mauikit-622575c7b45a?source=rss-15214b503713------2</link>
            <guid isPermaLink="false">https://medium.com/p/622575c7b45a</guid>
            <category><![CDATA[plasma]]></category>
            <category><![CDATA[maui]]></category>
            <category><![CDATA[kde]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Camilo Higuita]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 23:11:54 GMT</pubDate>
            <atom:updated>2018-07-27T23:36:57.667Z</atom:updated>
            <content:encoded><![CDATA[<p>In a previous post I introduced the MauiKit project, the idea with this post is to follow up the previous one and demonstrate some of the controls from the MauiKit and show you how to get started.</p><p>Just to recap, the MauiKit project is a helpful set of <em>templated</em> controls and custom widgets based on <strong>QCC2</strong> and <strong>Kirigami</strong> that follows the Maui HIG and makes it easier to create convergent applications that work well on GNU Linux distros, Plasma Mobile and Android.</p><h4>How to use the MauiKit?</h4><p>The MauiKit works as a submodule and it relies on the KDE framework Kirigami.</p><p>It makes use of qmake to be included into your project and then be built.</p><p>But you can also now make use of cmake to add it as a subdirectory and linked as a static library.</p><p>So let’s say your new project name is Nota, a simple and convergent text editor.</p><p>This is how the project folder would look like when we first create the project using Qt Creator:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtov41rFFnie3V2UK0K5Gw.png" /><figcaption>Nota project</figcaption></figure><p>Now, you will include the MauiKit submodule to your project, but first you need to clone the sources.</p><blockquote>git clone <a href="https://github.com/maui-project/mauikit">https://github.com/maui-project/mauikit</a> — recursive</blockquote><p>Don’t forget to add the “ — recursive” parameter when cloning it, because Maui Kit includes another submodule named “tagging” that needs to be present. It is a shared tagging system that allows all the Maui apps to share tags and metadata information between each other, but I will cover that one on another occasion.</p><p>Now your project folder should look more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTLujojcXNWKeHPYQUVb2w.png" /><figcaption>Nota project with MauiKit submodule</figcaption></figure><p>And now it is time to add it to your project sources, so open up your <em>nota.pro </em>file and add the following lines:</p><blockquote>linux:unix:!android {</blockquote><blockquote>message(Building for Linux )</blockquote><blockquote>} else:android {</blockquote><blockquote>message(Building for Android)<br> include($$PWD/3rdparty/kirigami/kirigami.pri)</blockquote><blockquote>} else {<br> message(“Unknown configuration”)<br>}</blockquote><blockquote>include($$PWD/mauikit/mauikit.pri)</blockquote><p>As I mentioned earlier Maui Kit works on top of Kirigami and so it depends on it. If you plan to deploy your app on a device running Android you will also need to add the Kirigami submodule. That’s what is going on in the first previous lines, it is including the Kirigami module and sources if the platform where your project is being deployed is Android.</p><p>And in the final line we’re including the Maui Kit module and sources, feel free to check out its content and see what’s in there.</p><p>Now we need to expose the MauiKit controls to the QML engine.</p><p>Open up your <em>main.cpp</em> file and add the following lines:</p><p>First include the Maui Kit header.</p><blockquote>#include “mauikit.h”</blockquote><p>and then register the MauiKit components.</p><blockquote>MauiKit::getInstance().registerTypes();</blockquote><p>Your project source files would look now a little more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cMG70b4SX0ws0lFtO2nP6g.png" /></figure><p>And now you’re ready to start creating your next convergent application.</p><p>On your QML files you now can import the Maui Kit controls like this:</p><blockquote>import org.kde.maui 1.0 as Maui</blockquote><p>Now, let’s take a first look of the controls included on the Maui Kit.</p><p>The most important control is the <strong>ApplicationWindow</strong>, it is what will make your app a Maui app, so it is the one I will be covering on this post.</p><h3><strong>Components</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmADbX3QUOxNQGsw2TQz4g.png" /></figure><h3>ApplicationWindow</h3><h4>Properties:</h4><p><strong>bool</strong> altToolBars</p><p>If set to <strong>True</strong>, the HeadBar will be moved to the bottom of the application window. By default is set to <em>the isMobile </em>property, so if the target device is a mobile device the HeadBar will move to the bottom.</p><p>If set to <strong>False</strong>, then the HeadBar will stay at the top of the application window even on mobile devices.</p><p><strong>bool</strong> floatingBar</p><p>If set to <strong>True</strong>, the FootBar will act as a floating bar, it will not occupy the full width of the application window, but instead use the minimum width required to place its children content. Also it will be coloured by making use of the theming property <em>accentColor </em>and cast a shadow<em>.</em></p><p>By default the floating bar does not overlaps the content, to make it overlap the content the <em>footBarOverlap</em> property will have to be set to <strong>True</strong></p><p>By default this property is set to the<em> altToolBars </em>property.</p><p><strong>int</strong> footBarAligment</p><p>By default it is set to <strong>Qt.AlignCenter</strong>, but can be set to any other alignment value. Changes will be only visible if the <em>floatingBar</em> property is set to <strong>True</strong>.</p><p><strong>bool</strong> footBarOverlap</p><p>If set to <strong>True</strong>, and also only if the <em>floatingBar</em> property is set to <strong>True </strong>too, the FootBar will act as a floating bar overlapping the content of the window.</p><p>When this property is set to <strong>True</strong>, the content will flick when scrolled down to show a reserved space for the FootBar in order to not overlap important content positioned at the bottom.</p><p>By default this property is set to <strong>False</strong></p><p><strong>int</strong> footBarMargins</p><p>This property adds margins to the FootBar when it is set as a floating bar using the <em>floatinBar</em> property. It is useful when the FootBar needs to stand out.</p><h4>Theming Properties:</h4><p>This properties can be changed to alter the look of the application from the Maui Kit controls and to the application own controls.</p><p>By default the colours are picked up from the system colour palette.</p><p><strong>int</strong> iconSize<br><strong>color</strong> borderColor<br><strong>color</strong> backgroundColor<br><strong>color</strong> textColor<br><strong>color</strong> highlightColor<br><strong>color</strong> highlightedTextColor<br><strong>color</strong> buttonBackgroundColor<br><strong>color</strong> viewBackgroundColor<br><strong>color</strong> altColor<br><strong>color</strong> altColorText<br><strong>color</strong> accentColor <br><strong>color</strong> bgColor</p><h4>Read only properties:</h4><p><strong>bool</strong> isMobile</p><p>Defines if the target device is a mobile device or not. By default it uses the property <em>Kirigami.Settings.isMobile</em></p><p><strong>bool</strong> isAndroid</p><p>Defines if the operating system of the target device is Android or not.</p><p><strong>int</strong> unit</p><p>Defines an unit making use of point size rather than pixel size. It is useful when the target device does not support pixel units right, like Plasma Mobile right now. By default is uses the property Kirigami.Units.devicePixelRatio</p><p><strong>int</strong> rowHeight</p><p>Defines a standardized height for rows, such is in lists and menus. It is used on the templated controls inside the Maui Kit, and it is recommend it to be used in the application.</p><p><strong>int</strong> rowHeightAlt</p><p>Defines a standardized height for alternative rows, such is in sub-items in lists and menus. It is used on the templated controls inside the Maui Kit, and it is recommend it to be used in the application. It has a smaller height size than the <em>rowHeight</em> property</p><p><strong>int</strong> toolBarHeight</p><p>Defines a standardized height for the toolbars. It is used on the templated controls inside the Maui Kit and for the Maui.ToolBar control, and it is recommend it to be used in the application where fitted.</p><p><strong>int</strong> toolBarHeightAlt</p><p>Defines a standardized height for the alternative toolbars. It is used on the templated controls inside the Maui Kit and for toolbars inside the Maui.Page control, and it is recommend it to be used in the application where fitted.</p><p><strong>int</strong> contentMargins</p><p>Defines a standardized size for content margins in places like Page, Panes and other controls.</p><p><strong>var</strong> fontSizes</p><p>Defines a standardized set of sizes to be used to with fonts.</p><p>The possible values are: tiny, small, medium, default, big, large</p><p><strong>var</strong> space</p><p>Defines a standardized set of sizes to be used for spacing items and layouts.</p><p>The possible values are: tiny, small, medium, big, large, huge, enormus</p><p><strong>var</strong> iconSizes</p><p>Defines a standardized set of sizes to be used for icons and buttons.</p><p>The possible values are: tiny, small, medium, big, large, huge, enormus</p><p>The Application window is based off Kirigami.ApplicationWindow.</p><p>The Maui implementation follows the Maui HIG and suggests the use of toolbars. It is layout vertically and contains: a <strong>HeadBar</strong>, the <strong>Content</strong>, a <strong>FootBar </strong>and a <strong>GlobalDrawer</strong>.</p><p>The <strong>HeadBar</strong> and <strong>FootBar</strong>, are both based on another Maui component: Maui.ToolBar, so they inhere its properties.</p><p>The <strong>Content</strong> can be any other QCC2 control, such a a SwipeView, StackView, or Maui.Page, etc…, but for default there is a <a href="https://api.kde.org/frameworks/kirigami/html/classorg_1_1kde_1_1kirigami_1_1PageRow.html">PageRow</a> from Kirigami, given that Maui.ApplicationWindow is based on Kirigami.ApplicationWindow.</p><p>The <strong>Content </strong>area, as mentioned earlier can be any other control, although the Maui HIG suggests the following horizontal layouts, that can be achieve by making use of a SwipeView or Kirigami.PageRow.</p><p>Here’s an example from VVAVE:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M2cHVN-4M824cnwLN_F-3Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5j7oKV4lI9TIGG8vBoDAfg.png" /></figure><p>By default and for reach-ability the <strong>HeadBar</strong> is moved to the bottom when it is being deployed on a mobile device, but this can be changed by setting the <strong><em>altToolBars</em></strong> property.</p><p>Also, the <strong>FootBar</strong> is styled differently on mobile devices, it is drawn as a floating bar that does not occupy the full width of the window and uses a background color set by the property <strong><em>accentColor</em></strong>. It can be set to overlap the content or not with the property <strong><em>footBarOverlap</em></strong> and the floating bar can be set with the property <strong><em>floatingBar</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmKbkF3wJWFnkHxuVA7wJQ.png" /><figcaption>floating FootBar on Android</figcaption></figure><p>Here’s a preview the floating bar overlapping the content:</p><p>The following app sets the properties mentioned above as:</p><blockquote>accentColor: altColor<br> highlightColor: “#8682dd”<br> altColor: “#43455a”<br> altColorText: “#ffffff”<br> altToolBars: false<br> floatingBar: isMobile<br> footBarOverlap: true</blockquote><p>This results in the following UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*BiN9F-pLVxUJn8o50E5FbQ.png" /></figure><p>Here are other Maui Kit controls I will be covering next:</p><p>ToolBar</p><p>ToolButton</p><p>Page</p><p>FileDialog</p><p>ShareDialog</p><p>PieButton</p><p>Holder</p><p>SelectionBar</p><p>GlobalDrawer</p><p>IconDelegate</p><p>Style</p><p>SideBar</p><p>TagsBar</p><p>NewDialog</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=622575c7b45a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nitrux/mauikit-622575c7b45a">MauiKit Controls</a> was originally published in <a href="https://medium.com/nitrux">Nitrux</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>