1
\documentclass[a4paper, 12pt]{article}
4
pdfauthor={Antti Kaijanm\"{a}ki},
13
\title{ZinC\\Service Description Language\\---\\Unity Direct Indicators}
15
Antti Kaijanm\"{a}ki\\
16
\texttt{antti.kaijanmaki@canonical.com}
21
\pagenumbering{gobble}
32
\pagenumbering{arabic}
36
\fbox{\includegraphics{images/indicators.png}}
37
\caption{Awesome Image}
38
\label{fig:awesome_image}
42
22:14 <Wellark> and I have not even gotten to the indicator parts yet..
43
22:14 <Wellark> basically it's a separate topic
44
22:14 <Wellark> which relies on this one
45
22:15 <Wellark> no hard dependency, but so much more straight forward
46
23:53 <Wellark> but first I will write down some thoughts I have for the indicators
47
23:54 <Wellark> easily supporting the existing profiles we have + also having an option for the "one indicator to rule them all" which is what design seems to be leaning towards on the RTM+1 on the phone and probably tablet
50
\section{current situation}
51
\subsection{indicator background services}
52
\subsection{unity8 indicator panel}
53
\subsection{GMenuModel}
56
\section{Convergence and Unity7}
58
\subsection{Converged indicators on Unity7}
59
offscreen rendering of qml indicators from unity8
60
placing the indicators to unity7
61
utilizing our powerful theming framework to have a unified look'n'feel
64
designers and engineers should talk before the designer starts to draw stuff.
70
http://muistio.tieke.fi/p/sdgsdhgshsehgse
74
- indicator content area
93
Unity.Indicators.Base.qml:
95
/// set by unity8 after it has loaded the indicator qml file
96
property profile-type profle
97
property indicator-type indicator
99
/// listened by unity8
100
property Item panel-area
101
property Item content-area
106
DateTimeIndicator.qml:
108
import Unity.Indicators as ui
121
00:53 < Wellark> this now actually gave an interesting use case
122
00:53 < charles> get off the computer and onto your wife
123
00:53 < charles> </sexist>
124
00:53 < Wellark> which the new indicator framework could address
125
00:54 < Wellark> single indicator plugin could provide any number of "menus"
126
00:54 < Wellark> on a phone where we have limited vertical space
127
00:54 < Wellark> flightmode, wifi, bluetooth could all have their own view
128
00:55 < Wellark> but on desktop they could all go happily to the same panel
129
00:55 < Wellark> not saying that this is what we should do
130
00:55 < Wellark> but it would still open up interesting possibilities
131
00:56 < Wellark> it would just be QML
132
00:56 < Wellark> and easy to implement