On Wednesday 16 May 2012, Alex Fiestas wrote: > > > > scalable: mostly referring to the available space so screen size (or just > > containment size, applets in panels vs desktop) > > we started with the formfactor concept and gone forward with the device > > specific qml files for plasmoids (experimental news reader, microblog) > > Thanks for the definitions. > > Both organic and scalable interfaces are means to an end if i understood > them correctly: making interfaces that feel natural. > Maybe we should put that into the vision instead?
yeah, they are two parts of our definition of "feel natural" and maybe there are many other points, maybe some may be wrong, but we have i think to define things in different levels of detail: from a general one (having interfaces that feels natural, probably everybody agrees) to more specific definitions on what this means to us. this becomes a second level of what we want to actually achieve (animated transitions, natural looking surfaces, correct illuminations effects and so on) note that this is still quite generic, only after a while it becomes a third level: using qml or not, this or that component etc. this is is implementation. so: * what is the target ** what is our definition our parts that defines that target *** how we get there, implementation (directly resulting in tasks for people, from writing code to higs) > > http://www.andrewschechterman.com/AndrewSchechterman/Qi_Fa_files/UX%20Gl > > ossa ry.pdf http://cyborganthropology.com/UX_Glossary > > http://blog.usabilla.com/the-usability-abc-part-2/#more-3075 > > http://uxmag.com/ > > If for understanding our vision we have to read all that then it is not a > good vision imho. Maybe I don't understand what a vision should is though > (this is the first time I'm participating in something like this). if we want to start to do ux designers tasks, besides finding real ones that know how to do it, we should start to enter a bit in that mindset too. And is not only designing that particular little piece of app, this is just the last small step of the process, is understanding the system, the problems and what we need as a whole. I'm just a little amateur in that, but I find looking at existing literature of those very same problems can be enlightening, it also helps in putting yourself on others clothes (non programmers, designers, ux people etc). this, besides some years of practiche in zooming the problem solving from that particular piece of code or that particular misaligned pixel to how the ui of the whole shell interacts. try to visualize something that actually graphically zooms like a Marble map from the code that is the atoms of a particular applet/grapihc element to the whole shell and how the informations flows between the parts of this zoomed out mental picture. easy useful little mental exercise ;) > > sadly quite outdated. a thing that would be very good from the sprint by > > the non coders that will participate is to write, write and write about > > those topics ;) > > I hope seba's is updated since he is the only core plasma developer comming > (aham aham u.U). 90% i should be there for some days ;) -- Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
