{"id":3506,"date":"2010-08-12T09:31:04","date_gmt":"2010-08-12T09:31:04","guid":{"rendered":"http:\/\/www.notmart.org\/index.php\/Software\/Plasma:_now_comes_in_tablets"},"modified":"2010-08-12T09:31:04","modified_gmt":"2010-08-12T09:31:04","slug":"plasma_now_comes_in_tablets","status":"publish","type":"post","link":"https:\/\/notmart.org\/blog\/2010\/08\/plasma_now_comes_in_tablets\/","title":{"rendered":"Plasma: now comes in tablets"},"content":{"rendered":"<p>When designing Plasma Mobile, it was immediately clear that wouldn&#8217;t have been possible to do a &#8220;one design fits all&#8221; application: mobile devices vould have come in pretty diffrent forms:<\/p>\n<ul>\n<li>Different resolution<\/li>\n<li>Different phisical size<\/li>\n<li>That implies, different DPI<\/li>\n<li>Different use cases: an internet tablet and a phone put the emphasis on very different <em>primary<\/em> functions<\/li>\n<\/ul>\n<p>What we have seen right now, is the development of completely different code, from the ground up for different platforms.<\/p>\n<p>In Plasma we always tried to avoid this, by having everything as a plugin, so  it will be necessary to replace maybe the shell itself and just the components that really have to be changed.<\/p>\n<p>With Qt 4.7 a new framework ha been introduced: the declarative UI, that permits to do quite fancy stuff in the QML language in a very short time.<\/p>\n<p>So with the development of Plasma mobile we started an experiment, and here it is (usual VESA drivers disclaimer about the speed that applies to all screencasts done on that <em>weird<\/em> tablet):<\/p>\n<p><object width=\"480\" height=\"385\"><embed src=\"http:\/\/www.youtube.com\/v\/9HHak-XN3tc?fs=1&amp;hl=en_US&amp;color1=0x234900&amp;color2=0x4e9e00\" type=\"application\/x-shockwave-flash\" allowscriptaccess=\"always\" allowfullscreen=\"true\" width=\"480\" height=\"385\"><\/embed><\/object><\/p>\n<p><a href=\"http:\/\/blip.tv\/file\/get\/Notmart-KDEPlasmaMobileTabletEdition746.ogg\">OGG version<\/a><\/p>\n<p>Besides bindings to write plasmoids entirely in QML (or using QML bits into C++ plasmoids), the behaviour of the entire shell, how activities appear\/disappear\/are chosen is completely controlled by this language, so in theory should be enough to change the QML files set to achieve a completely different ui and behaviour.<\/p>\n<p>In theory. But it gets interesting when this becomes actually practice: with just some adaptions to the C++ code of the shell to make it more flexible, last days I wrote a different QML set and a different default layout configuration aimed for bigger, but still touchscreen based tablets.<\/p>\n<p>Those kind of devices always were for me one of the main targets of the netbook &#8220;Newspaper&#8221; containment, that&#8217;s why a quite big amount of attention has been put into the behaviour of &#8220;flicking&#8221; arouund things in it.<\/p>\n<p>Here the pages concept is taken to the extreme: you can phisically change pace with a swipe of the finger, dragging the new one into the screen, as you would change real pages \ud83d\ude09<\/p>\n<p>The search and launch interface is dragged in a similar way, but from the bottom, since it should always be quicly available with a single gesture, no matter on what page you are.<\/p>\n<p>This is just a quick proof of concet, but that shows itself very promising for the future.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When designing Plasma Mobile, it was immediately clear that wouldn&#8217;t have been possible to do a &#8220;one design fits all&#8221; application: mobile devices vould have come in pretty diffrent forms: Different resolution Different phisical size That implies, different DPI Different use cases: an internet tablet and a phone put the emphasis on very different primary [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[2,10,11,7,50],"class_list":["post-3506","post","type-post","status-publish","format-standard","hentry","category-software","tag-kde","tag-kde4","tag-mobile","tag-plasma","tag-touch-screen"],"_links":{"self":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts\/3506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/comments?post=3506"}],"version-history":[{"count":0,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/posts\/3506\/revisions"}],"wp:attachment":[{"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/media?parent=3506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/categories?post=3506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/notmart.org\/blog\/wp-json\/wp\/v2\/tags?post=3506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}