> 3) DIALOGS AND RESOURCES > This is a BIG item for me. > - How are DIALOGS and RCs created? > - Is it WYSIWYG? > - Are there any special tool for this?
The dialog code is mostly contained in classes that end in "View", ie. AboutChromeView (I think it is called that, don't have the code in front of me right now). We use a function called Layout to arrange dialog items onto the page, there are as of yet no special tools or WYSIWYG editors to assist with this. We do have a Layout Manager object in the code, though, that we use for some dialogs. If you are used to Initializing dialogs using InitDialog, the equivalent in Chrome is ViewHierarchyChanged. -F On Mon, Sep 29, 2008 at 07:44, Marc-Antoine Ruel <[EMAIL PROTECTED]>wrote: > > To answer a few quick questions... > > 2008/9/26 HLS <[EMAIL PROTECTED]>: > > 1) Development Machines vs Target Platfiorms > > > > This is critical as many Windows product operations do no like to mix > > compilers, sdks, etc as it may affect other existing building > > operations. This part is covered in other pages, so most of what I > > would like to see follows. But if anything, it can made clear what is > > expected. Does SDK v6.1 work or not? Can you use VCBUILD? What are > > the OS *.DLL dependencies that will define the target platforms? Is a > > Redistribution package possible? etc. > > Platform SDK 6.0, 6.0a and 6.1 are supported. I personally use the 6.1 > but most of the team members use 6.0 by default. > VCBUILD is *not* supported and I personally see no immediate incentive > to change that. devenv.com works fine for our and is completely > command line based. Note that we are slowly moving towards SCons based > build. > > The dll dependencies are pretty straight forward by looking at the > direct dependencies of chrome.dll. We just assume an up-to-date > (security patch wise) Windows system. > > I can't give legal advice, so this is not a legal advice. Look at > http://code.google.com/chromium/terms.html for some license > information. > > > > 2) BASIC TOOLS > > > > - The BASIC tools used, summarizing what is included in the SVN > > downloads what is indepenedent etcs. > > Please visit http://code.google.com/chromium/terms.html > > > - A summary of what the tools do for the solution building. > > I don't have the time right now to write summaries but you can find > out the original authors own summary at their official web sites: (I > agree that this information would be valuable on the dev web site) > > > - What is WEBKIT? > http://www.webkit.org > > > - What is CYGWIN? > http://cygwin.org/ > > > - What is PYTHON? > http://www.python.org/ > > > - What is BASH? > http://www.gnu.org/software/bash/ > > Most of them can be found by a web search and is usually in the top hits. > > > - What can be substituted or minimized, i.e. what tool is a one-time > > processing thing? > > I don't know to what you refer. Incremental builds are supported > (except for some breaking javascript binding changes). If you build > one specific project, all of its dependencies will be built. > > > 3) DIALOGS AND RESOURCES > > > > This is a BIG item for me. > > > > - How are DIALOGS and RCs created? > > Search for .rc files. Most are done through the IDE. > > > - Is it WYSIWYG? > > Some do, some don't. See previous question. > > > - Are there any special tool for this? > > grit is used for localization. Search in the source tree, it's a > python based tool. > > > 4) SUB-SYSTEMS > > > > - What are all the sub-systems of Chome? > > > > http, authentication, cookies, gui, keyboard, download, setup, user > > profiles, hooks, plug-ins, etc. > > Pretty much organized by sub directories. So for instance, there's no > "keyboard" module. This is constantly changing, especially with the > multiplatform effort. > > > - What projects are associated with the sub-systems? > > The mapping is mostly 1-for-1 with their directory. > > > - How/where to report a problem for these sub-systems? > > There is only one bucket: > http://dev.chromium.org/for-testers/bug-reporting-guidelines > > M-A > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
