Talk:Look & Feel

From Openmoko

Revision as of 16:24, 18 February 2007 by Seba (Talk | contribs)

Jump to: navigation, search

Tony guan 02:36, 6 September 2006 (UTC): Q: If color parameters for the widgets will not be hard coded, there must be somewhere to store and retrieve them. And the method to retrieve it must be identical for any widget. And the method has to be defined before we write the codes. Am I right?

Sean Moss-Pultz A: Most of the color elements will be decided by the actual images used for the theme. There will be a general method to access this information. User:Mickey can you provide more details here?

Michael 'Mickey' Lauer There won't be any need to specify colors "by hand". We will be using a common class for the dialog, i.e. MokoConfirmationDialog, which will handle this automatically according to the selected theme.


Tony guan 02:21, 6 September 2006 (UTC): Q1:Is the Fonts or Theme related to some hardware Buttons?

Sean Moss-Pultz A: Not at this point. Do you think it should?

Michael 'Mickey' Lauer A: IMO we shouldn't try to mimick hardware appearance in the theme.


Tony guan 01:23, 13 September 2006 (UTC):

Q:Is there any place for the logo of the telecom service provider?

(Sean Moss-Pultz) A: I wasn't planning on it. I don't see any reason to clutter up the background. Does anybody really want this?


Q2:Will application be aware of the theme change event?

Sean Moss-Pultz A: Yes. This is a global thing that all affects widgets.


Errors in mock up pictures:

  • 'Alert' example picture 'warring', not warning.
  • Confirmation example - 'sure to delete data' -> 'Are you sure you want to delete deta.'/ 'Delete all data?'

Q: Is this the place to discuss usability and design consistency issues too? Or is it wise to have an independant interface guidelines section? Is it wanted at all? (--Seba 15:24, 18 February 2007 (CET))

Personal tools

Tony guan 02:36, 6 September 2006 (UTC): Q: If color parameters for the widgets will not be hard coded, there must be somewhere to store and retrieve them. And the method to retrieve it must be identical for any widget. And the method has to be defined before we write the codes. Am I right?

Sean Moss-Pultz A: Most of the color elements will be decided by the actual images used for the theme. There will be a general method to access this information. User:Mickey can you provide more details here?

Michael 'Mickey' Lauer There won't be any need to specify colors "by hand". We will be using a common class for the dialog, i.e. MokoConfirmationDialog, which will handle this automatically according to the selected theme.


Tony guan 02:21, 6 September 2006 (UTC): Q1:Is the Fonts or Theme related to some hardware Buttons?

Sean Moss-Pultz A: Not at this point. Do you think it should?

Michael 'Mickey' Lauer A: IMO we shouldn't try to mimick hardware appearance in the theme.


Tony guan 01:23, 13 September 2006 (UTC):

Q:Is there any place for the logo of the telecom service provider?

(Sean Moss-Pultz) A: I wasn't planning on it. I don't see any reason to clutter up the background. Does anybody really want this?


Q2:Will application be aware of the theme change event?

Sean Moss-Pultz A: Yes. This is a global thing that all affects widgets.


Errors in mock up pictures:

  • 'Alert' example picture 'warring', not warning.
  • Confirmation example - 'sure to delete data' -> 'Are you sure you want to delete deta.'/ 'Delete all data?'

Q: Is this the place to discuss usability and design consistency issues too? Or is it wise to have an independant interface guidelines section? Is it wanted at all? (--Seba 15:24, 18 February 2007 (CET))