Issue 77575 - Aqua native controls
Summary: Aqua native controls
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: porting
Classification: Code
Component: MacOSX (show other issues)
Version: 680m211
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ericb
QA Contact: issues@porting
URL:
Keywords: aqua
Depends on:
Blocks:
 
Reported: 2007-05-19 04:03 UTC by msicotte
Modified: 2007-06-23 13:03 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description msicotte 2007-05-19 04:03:59 UTC
Use Apple Aqua look ( native controls)
Comment 1 msicotte 2007-05-19 04:04:23 UTC
keyword
Comment 2 eric.bachard 2007-05-19 07:55:51 UTC
ericb->msicotte

The summary is IMHO too generic, and I fear too much work is concerned.
Comment 3 msicotte 2007-05-19 15:51:41 UTC
msicotte => ericb

I agree - this is too generic for an issue.  I suggest we use it for a
meta-issue like the "Top Ten" for the biggest part of the GSOC you are
mentoring.  Here is what the WIKI entry for the GSOC says:

MacOSX: Complete User Interface respecting Aqua Human Interface Guidelines
* Tasks: some controls are already implemented, but some are still missing. 

The job consists in write the code and implement:
- tabs (implement and bind the TabitemValue class, using Carbon API)
- spinbuttons (implement and bind SpinbuttonValue class, using Carbon API)
- comboboxes (implement and use HICombobox)
- listboxes (work already started)
- texts in comboboxes / listboxes (better task definition to be completed)
- other types of controls: highlight, respect dimensions/spacing ..etc
(only one line omitted as not relevant) 

IMHO this is almost the same - 

If you do not accept, please close the issue.

Thanks,  Mike
Comment 4 pavel 2007-06-23 13:02:05 UTC
yes, too generic.
Comment 5 pavel 2007-06-23 13:03:47 UTC
Closing.