[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-active
Subject: Re: [Kde-pim] Kontact Touch GSOC Project
From: Michael Bohlender <michael.bohlender () kdemail ! net>
Date: 2013-04-28 14:36:39
Message-ID: CAOF1ztw1rZEOH2vJcFBcQHCaF-v6zUOOKvcMKSK7VnQxxG_vgA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks for your feedback and your insights.
> One thing that should be added to your proposal is deployment: Thomas wont
> > be able to even have a look at your work if you don't update packages on
> > Mer OBS. That doesn't have to be a lot of work, but should definitely be
> > part of your proposal.
>
> It's briefly mentioned in "set up dev environment (obs)", but I agree that
> it
> makes sense to write somewhere that there will be regular package updates.
> As
> sebas said: I can't compile stuff for the tablet myself, so I need
> packages on
> OBS whenever I'm supposed to try something out (maybe I can swap out QML
> files,
> but everything which is compiled needs to come to me in compiled form).
>
added to Implementation details.
I do like sebas' idea of mixing the two main tasks you outlined instead of
> doing them strictly one after another. in order to make sure that we at
> least
> have _something_ working in the end, come what may.
> Maybe you can chop your work into different UI parts which each get a
> design
> and an implementation cycle, instead of one big design cycle folowed by one
> big implementation cycle.
>
Sounds very reasonable to me.
I divided the work into 5 tasks:
# general layout
# mail list
# display mail
# compose mail
# folder (or whatever way we come up to browse the mail)
We could do 4 of them working 3 weeks on each task with a qml
mockup/prototype followed by the actual implementation.
I can use the idle time (waiting for your feedback) during each mockup
phase to do small tasks like porting a button or things like that.
I am a little worried that the whole project is too much work for me in the
given time. Like stated before "asking for a full rewrite of a mail
application UI within a single GSOC is asking for a bit much". If I don't
progress as expected we could skip one of the above tasks and instead focus
on polishing the remaining three.
Going completely crazy: The whole project looks a lot more achievable if I
pick Tasks or Notes instead of Mail...
But I guess we can't come up with a UX that will work across Kontact Touch
as some problems will only show with complex applications like Mail ?
reworked proposal:
https://docs.google.com/document/d/1qxWHUg-STYimYuqxMyPaD2gHiCDoI_m_YNa5mZkpU1Y/edit?usp=sharing
I think we need to start earlier with the mockups for the general design as
we wont have that much time during the GSoC period as I hoped. I
will try to come up with some Pencil mockups next weeks so that we have a
head start.
cheers
Mike
[Attachment #5 (text/html)]
Thanks for your feedback and your insights. <br><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
class="im"> > One thing that should be added to your proposal is deployment: \
Thomas wont<br> > be able to even have a look at your work if you don't update \
packages on<br> > Mer OBS. That doesn't have to be a lot of work, but should \
definitely be<br> > part of your proposal.<br>
<br>
</div>It's briefly mentioned in "set up dev environment (obs)", but I \
agree that it<br> makes sense to write somewhere that there will be regular package \
updates. As<br> sebas said: I can't compile stuff for the tablet myself, so I \
need packages on<br> OBS whenever I'm supposed to try something out (maybe I can \
swap out QML files,<br> but everything which is compiled needs to come to me in \
compiled form).<br></blockquote><br>added to Implementation details. <br><br><br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I do like sebas' idea of mixing the two main tasks you outlined instead of<br>
doing them strictly one after another. in order to make sure that we at least<br>
have _something_ working in the end, come what may.<br>
Maybe you can chop your work into different UI parts which each get a design<br>
and an implementation cycle, instead of one big design cycle folowed by one<br>
big implementation cycle.<br><div class="im"></div></blockquote><div><br>Sounds very \
reasonable to me. <br>I divided the work into 5 tasks: <br># general layout <br># \
mail list<br># display mail<br># compose mail<br># folder (or whatever way we come up \
to browse the mail)<br> <br>We could do 4 of them working 3 weeks on each task with a \
qml mockup/prototype followed by the actual implementation.<br>I can use the idle \
time (waiting for your feedback) during each mockup phase to do small tasks like \
porting a button or things like that.<br> <br>I
am a little worried that the whole project is too much work for me in
the given time. Like stated before "asking for a full rewrite of a mail \
application UI within a single GSOC is asking for a bit much". If I don't \
progress as expected we could skip one of the above tasks and instead focus on \
polishing the remaining three. <br><br>Going completely crazy: The whole project \
looks a lot more achievable if I pick Tasks or Notes instead of Mail...<br>But I \
guess we can't come up with a UX that will work across Kontact Touch as some \
problems will only show with complex applications like Mail ?<br> <br>reworked \
proposal:<br><a href="https://docs.google.com/document/d/1qxWHUg-STYimYuqxMyPaD2gHiCDo \
I_m_YNa5mZkpU1Y/edit?usp=sharing">https://docs.google.com/document/d/1qxWHUg-STYimYuqxMyPaD2gHiCDoI_m_YNa5mZkpU1Y/edit?usp=sharing</a> \
<br> <br>I think we need to start earlier with the mockups for the general design
as we wont have that much time during the GSoC period as I hoped. I <br>will try to \
come up with some Pencil mockups next weeks so that we have a head start. \
<br><br></div><div><br>cheers<br><br>Mike<br></div><div> <br> <br></div></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