Hey people :)
I am finally able to express my opinions on this thread :)

First of all, I'm so sad I couldn't be part of such discussions on the
public chat, unfortunately I will be very busy until half July or some more
:(

Anyway...
Simply put: I'm with Venemo, I'm one of the guys who's been discussing with
him at Devaamo Summit about new homescreen ideas, and I, as him, would love
to move forward.

Let's face it, it's not like we have many people who are attracted by
current Nemo-Harmattan's swipeish interface, so I don't see anything wrong
in changing everything.

I think we can do much better, and I'd love to start the homescreen UI from
scratch (not talking about lipstick middleware of course, just the UI).

I see Nemo as a playfield for us who care about it and care about keeping a
fully open OS (from core to UI) alive, and I think experimenting with new
UXes can only make Nemo better.

I've been trying hard to come up with completely new ideas about a new
homescreen, but as you may imagine, it's no easy task :D

But still, I think we need something completely new, unique, and fresh.

Let's create a new interaction model, we can do this in Nemo! It's not like
we're tied to what we have, in fact there's none even actually using Nemo
daily, as it's not ready for that yet (though it's getting better and
better :) ).

About the graphical design:

I've seen what qwazix was sketching on his laptop at Devaamo Summit:
It's AWESOME stuff guys :D and I hope you'll be able to see it soon :D
I also agree about keeping discussions about the UI/UX in the mailing list,
so that all people who really care about the project can contribute their
ideas/opinions and help shape the future Nemomobile :)

About the components:
We have to keep compatibility with MeeGo components, but hey! Those
components look so old!
So, yeah, on one hand we HAVE TO keep compatibility and maintain them, but
on the other hand, let's start moving to QtQuick Controls as soon as
possible, as that is the future of Qt, in those regards.
New Qt5 mobile applications will use QQControls, so it surely makes sense
to start shaping them for Nemo, as applications will start popping up like
crazy as soon as Qt 5.2 hits iOS and Android with QQControls!





2013/6/24 Filip Kłębczyk <fklebc...@gmail.com>

> W dniu 24.06.2013 13:48, Timur Kristóf pisze:
>
>  Hi guys,
>>
>> Some discussion happened on IRC a few hours ago.
>> We discussed about things and in light of his knowledge and experience,
>> we are suggesting Michael /qwazix/ for the role of leading the creation
>> of the new design. Nobody was against this. I hope everyone agrees.
>>
>
> Yep that is what has happened today in the morning and during intensive
> and fruitful discussion, many  interesting links popped up thanks to Venemo:
> http://www.smashingmagazine.**com/2010/06/29/why-design-by-**
> commitee-should-die/<http://www.smashingmagazine.com/2010/06/29/why-design-by-commitee-should-die/>
> http://en.wikipedia.org/wiki/**Design_by_committee<http://en.wikipedia.org/wiki/Design_by_committee>
> http://www.thousandtyone.com/**blog/**CommitteeDrivenDevelopmentIsNo**
> tJustLameItsDangerous.aspx<http://www.thousandtyone.com/blog/CommitteeDrivenDevelopmentIsNotJustLameItsDangerous.aspx>
> https://mail.gnome.org/**archives/desktop-devel-list/**
> 2006-February/msg00115.html<https://mail.gnome.org/archives/desktop-devel-list/2006-February/msg00115.html>
>
> And cause everyone loves videos here also good one found by Lucien:
> http://www.youtube.com/watch?**v=Wac3aGn5twc<http://www.youtube.com/watch?v=Wac3aGn5twc>
>
> Pasted by Stskeeps:
> http://en.wikipedia.org/wiki/**Participatory_design<http://en.wikipedia.org/wiki/Participatory_design>
>
> So in general idea of choosing a design lead appeared and we got to the
> point that the right man for that task would be qwazix as he probably has
> the biggest experience here when it comes to design.
>
> Regards,
> Filip
>
> PS. Since last Devaamo, Micheal /qwazix/ is also known as Michalis (that
> is how his name sounds nicely in the Greek language).
>
>
>

Reply via email to