[Kde-pim] Kontact Touch GSOC Project - mentor needed

[Kevin Krammer]

On Thursday, 2013-04-11, Michael Bohlender wrote:

> 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?

It is a bit thin on scope and implementation details.
E.g. does this include folder specific settings UI, composer, attachment 
handling, address book integration/recipient editor, filter/search UI, etc.

Maybe list a couple of example workflows that should be possible with the 
improved UI.

> > 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.

Right, I agree with that.

> 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 would expect that Plasma UI does also work on the desktop or inside a viewer 
application. AFAIK it is possible to build and run Kontact touch like its 
normal version, just using QtQuick as the UI layer.

> I consider the UX design/rework the main part of my project and like to
> experiment a lot during the mockup phase.

Would it then not be better to have someone from PA be the primary mentor for 
this?

> > 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 at 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.

I am just worried that we will end up with lots of QML files that work really 
well on demo data but do not fit onto the actual data objects, etc.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20130411/b2ff32a2/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/