On 01/09/2012 04:29 PM, Benjamin Otte wrote:
Hey,
Here's another discussion point I want people to think about before
the hackfest. This time it's not so much about API in a direct way but
more about a guiding principles for the kinds of APIs we want to
provide. The short question is this:
On Tue, Jan 10, 2012 at 08:16:53PM +0100, Stefan Sauer wrote:
On 01/09/2012 04:29 PM, Benjamin Otte wrote:
Who gets to decide how an application looks?
This question is aimed at theming and the question of graphic
design[1] and not at intersection design[2]. The way I see it, there
is
On Tue, Jan 10, 2012 at 2:25 AM, Benjamin Otte o...@gnome.org wrote:
On Mon, Jan 9, 2012 at 5:40 PM, Tristan Van Berkom t...@gnome.org wrote:
I think the first thing we have to keep in mind is that while well-known
use cases of GTK+ are in the domain of desktop applications there
is a great
Hey,
Here's another discussion point I want people to think about before
the hackfest. This time it's not so much about API in a direct way but
more about a guiding principles for the kinds of APIs we want to
provide. The short question is this:
Who gets to decide how an application looks?
Very interesting topic, I'm going to throw some responses out there
without thinking too hard, if the thread gets very interesting we can
build from there ;-)
I think the first thing we have to keep in mind is that while well-known
use cases of GTK+ are in the domain of desktop applications there
Hej, great read!
Regarding your point on Application design theming for different form
factors, I think there isn't any logic in even attempting the same user
interface design (not talking about theming here) for lets say, desktops
and tablets. And on the topic of mobile devices, the user
On Mon, Jan 9, 2012 at 5:40 PM, Tristan Van Berkom t...@gnome.org wrote:
I think the first thing we have to keep in mind is that while well-known
use cases of GTK+ are in the domain of desktop applications there
is a great deal of use cases that are not tied in to desktop environments
(be
On Mon, Jan 9, 2012 at 5:59 PM, Jan Jokela janjok...@gmail.com wrote:
Hej, great read!
Regarding your point on Application design theming for different form
factors, I think there isn't any logic in even attempting the same user
interface design (not talking about theming here) for lets say,
On Mon, Jan 9, 2012 at 5:36 PM, Benjamin Otte o...@gnome.org wrote:
On Mon, Jan 9, 2012 at 5:59 PM, Jan Jokela janjok...@gmail.com wrote:
Hej, great read!
Regarding your point on Application design theming for different form
factors, I think there isn't any logic in even attempting the
On Mon, Jan 9, 2012 at 1:44 PM, Jan Jokela janjok...@gmail.com wrote:
. But for the App to
be cohesive with the platform, the theme (the design and usability features
of widgets) must remain identical.
this notion of cohesiveness with the platform doesn't seem to bother
the developers of most
On Mon, Jan 9, 2012 at 6:49 PM, Paul Davis p...@linuxaudiosystems.comwrote:
On Mon, Jan 9, 2012 at 1:44 PM, Jan Jokela janjok...@gmail.com wrote:
. But for the App to
be cohesive with the platform, the theme (the design and usability
features
of widgets) must remain identical.
this
On Mon, Jan 9, 2012 at 2:05 PM, Jan Jokela janjok...@gmail.com wrote:
Take iPhoto, Calendar and similar apps, even the ones not developed by
Apple.
Many of them style widgets to a certain look and feel and most have a bunch
of custom widgets. And I see this as essential for making great
On 01/09/2012 06:25 PM, Benjamin Otte wrote:
Keep in mind that those kiosk or other embedded applications
themselves are the platform though. So for those cases, the
distinction does not matter. It doesn't even matter if you have
multiple applications if you still control the design of all of
13 matches
Mail list logo
