I've been doing some janitorial work in the browser/ dir today, moving various files into better places, and creating subdirectories for significant chunks of code. Without trying to create a byzantine directory structure, sometimes a layer of hierarchy can make it easier to find where various features are implemented and the files involved. I've done already this for code I know fairly well, but others I wanted to float here to get feedback:
multi-process hosting/rendering stuff (things beginning with render_*) subdir name ideas: browser/multiprocess, browser/multiprocess_hosts, browser/renderer_hosts, etc. plugin stuff (things beginning with plugin_*) - maybe there's some overlap with the renderer hosts though? at least conceptually? subdir name ideas: browser/plugin tab contentses (things subclassing tab_contents) subdir name ideas: browser/tabcontents session and tab restore (stuff beginning with session and potentially containing the word "restore") subdir name ideas: browser/restore, browser/session_restore, etc. ssl stuff (stuff starting with ssl_*) subdir name ideas: browser/ssl template URL stuff: (stuff starting with template_url_*): subdir name ideas: browser/template_url metrics: (stuff starting with metrics_*) subdir name: browser/metrics, browser/user_metrics, etc. These are the low hanging fruit, and the stuff I could easily figure out what they represent. Maybe there are some others too. Let me know what you think. -Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
