[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-active
Subject: Re: [Kde-pim] Kontact Touch GSOC Project - mentor needed
From: Michael Bohlender <michael.bohlender () kdemail ! net>
Date: 2013-04-11 11:55:27
Message-ID: CAOF1ztw90_FY-Lnzj8iO9kFXRrwwSDXP--1PuNqg6WNOjgOGdw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> > I finished my GSOC Proposal for a UI/UX rework of Kontact Touch Mail
> today
> > and would like to get a final round of feedback.
> >
> https://docs.google.com/document/d/1Mq7bX6y5VaRO-AcO1Q0fEMUOgswyMUsM0Wl9__x
> > gCgo/edit?usp=sharing
> >
> > For the technical parts: I am sure I mean the right thing but I am not
> sure
> > about the wording. Please correct me if I am wrong.
>
> Looks ok, but I am not sure how useful development against a dummy QML
> model
> would be.
>
Just "ok" is not good enough for me. So lets see what I can improve.
Is the project idea itself not exciting enough for you or is this just
about the technical approach?
> That will most likely only work for rough prototyping, learning to use
> Plasma
> Components and so on,
I did some minor things for PA with PlasmaComponets already and feel
relatively comfortable using it.
The reason I suggested this approach is, that it allows me to got through a
lot of design ideas with my Co Mentor.
Otherwise testing if the UI works on Tablet will be hard and I have no Idea
how to compile stuff for my ARM based Nexus 7.
Waiting for our merproject build servers to compile stuff would also be
quiet time consuming.
I consider the UX design/rework the main part of my project and like to
experiment a lot during the mockup phase.
but I think any real improvement can only be tested and
> validated if it works with the actual data models accessing actual data.
>
+1
an application that just displays dummy data is not of much use.
> E.g. standard Qt Quick (no idea about Plasma Components) is seriously
> limited
> when it comes to usage of Qt item models (no support for table models, yet
> alone tree models), so often extra effort is needed to overcome those.
>
I asked on active@kde.org a while ago and was told that this approach is
used "fairly often" in plasma active.
But maybe I got it wrong or this just does not work well for KDE PIM
related things?
If someone suggests a more sensible approach I have no problem with
adapting it.
Any input from the original Kontact Touch developers?
>
+1
[Attachment #5 (text/html)]
<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div> > I finished my GSOC \
Proposal for a UI/UX rework of Kontact Touch Mail today<br> > and would like to \
get a final round of feedback.<br> > <a \
href="https://docs.google.com/document/d/1Mq7bX6y5VaRO-AcO1Q0fEMUOgswyMUsM0Wl9__x" \
target="_blank">https://docs.google.com/document/d/1Mq7bX6y5VaRO-AcO1Q0fEMUOgswyMUsM0Wl9__x</a><br>
> gCgo/edit?usp=sharing<br>
><br>
> For the technical parts: I am sure I mean the right thing but I am not sure<br>
> about the wording. Please correct me if I am wrong.<br>
<br>
</div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Looks ok, but I am not sure how \
useful development against a dummy QML model<br> would be.<br>
</blockquote><div><br>Just "ok" is not good enough for me. So lets see what \
I can improve.<br>Is the project idea itself not exciting enough for you or is this \
just about the technical approach?<br> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That will most likely only work for rough prototyping, learning to use Plasma<br>
Components and so on, </blockquote><div><br>I did some minor things for PA with \
PlasmaComponets already and feel relatively comfortable using it.<br>The reason I \
suggested this approach is, that it allows me to got through a lot of design ideas \
with my Co Mentor. <br> Otherwise testing if the UI works on Tablet will be hard and \
I have no Idea how to compile stuff for my ARM based Nexus 7.<br>Waiting for our \
merproject build servers to compile stuff would also be quiet time consuming.<br> I \
consider the UX design/rework the main part of my project and like to experiment a \
lot during the mockup phase.<br><br></div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> but I think \
any real improvement can only be tested and<br> validated if it works with the actual \
data models accessing actual data.<br> </blockquote><div><br>+1 <br>an application \
that just displays dummy data is not of much use. <br> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> E.g. standard Qt Quick (no idea about Plasma Components) is \
seriously limited<br> when it comes to usage of Qt item models (no support for table \
models, yet<br> alone tree models), so often extra effort is needed to overcome \
those.<br></blockquote><div><br>I asked on <a \
href="mailto:active@kde.org">active@kde.org</a> a while ago and was told that this \
approach is used "fairly often" in plasma active. <br> But maybe I got it \
wrong or this just does not work well for KDE PIM related things?<br>If someone \
suggests a more sensible approach I have no problem with adapting it. \
<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Any input from the original Kontact Touch \
developers?<br><div><div></div></div></blockquote><div><br>+1<br><br></div><br> \
</div>
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic