OLD | NEW |
---|---|
(Empty) | |
1 # Introduction | |
Robert Sesek
2015/08/24 18:07:43
Delete?
| |
2 | |
3 This page contains a list of all the design documents that we need to write in o rder to better document how our infrastructure and features are implemented. Fee l free to add something to the list. Doing so does **not** mean that you are sig ning up to write it, we'll find someone! | |
4 | |
5 ## Cross-Platform | |
6 | |
7 * how the password manager works at a high level (when new entries are stored, how scoring works, how imported passwords without stored action URLs are handle d, etc.) (stuartmorgan) (note see https://wiki/Main/ChromePasswordManagerDesignD oc) | |
8 * try servers - how they work, limitations, different supported methods to upl oad patches, etc. | |
9 * how the update mechanism works - how the server communicates with the chrome , how to use Courgette, etc. | |
10 * webintents | |
11 | |
12 ## Mac | |
13 | |
14 * tab dragging in and between windows (pink) | |
15 * tab layout (pink) | |
16 * BWC ownership model, NSViewController/NSWindowController ownership, how to w rite CocoaTests (pink, dmaclach) | |
17 * animations (infobar, download shelf, bookmarkbar) | |
18 * omnibox (class hierarchy, what happens when you type into the omnibox, etc) | |
19 * keypress/keyboard/IME/main menu shortcuts input flow (owner: thakis, work-in -progress at http://sites.google.com/a/chromium.org/dev/developers/os-x-keyboard -handling) | |
20 * how to write l10n-savvy nibs | |
21 * http://dev.chromium.org/developers/design-documents/ui-localization/mac-no tes is decent imho (thakis) | |
22 * however, it has many ???'s for complex examples. it's a great starting poi nt but needs finishing (pinkerton) | |
23 * graphics rendering and event processing for plug-ins, particularly how Mac N PAPI differs from Windows/Linux (awalker) | |
24 * Make sure SpellingPanelPlanningDoc is up to date | |
25 * on-disk app structure and maybe some autoupdate tidbits (mark) | |
26 | |
27 ## Linux | |
28 | |
29 * how zygotes work, why they were chosen (distribution partners), and why it i sn't a recommended approach for others to take (ie, mozilla). Probably should j ust flesh out the LinuxZygote doc | |
OLD | NEW |