diff options
| -rwxr-xr-x | makecomponenttable.sh | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/makecomponenttable.sh b/makecomponenttable.sh index 1e5d4fe8a..06e907523 100755 --- a/makecomponenttable.sh +++ b/makecomponenttable.sh @@ -155,11 +155,11 @@ insert into components (value, program, initialowner, initialqacontact, descript insert into components (value, program, initialowner, initialqacontact, description) values ("Compositor", "NGLayout", "michaelp@netscape.com", "chrisd@netscape.com", "Compositor (aka rendering) is like layout, a catch-all, but for painting problems. If the object is in the right place, but doesn't paint correctly, it's a rendering bug. If it paints ok, but in the wrong place, it's a layout bug. Rendering is for <i>drawing</i>."); insert into components (value, program, initialowner, initialqacontact, description) values ("Selection and Search", "NGLayout", "mjudge@netscape.com", "claudius@netscape.com", "Selection refers to the user action of selecting all or part of a document and highlighting the selected content. Search refers to finding content within the larger context of a document."); insert into components (value, program, initialowner, initialqacontact, description) values ("Style System", "NGLayout", "peterl@netscape.com", "chrisd@netscape.com", "CSS, XSL - CSS and HTML attribute handling. There's some overlap here with the parser, if you're not sure just guess."); -insert into components (value, program, initialowner, initialqacontact, description) values ("Threading", "NGLayout", "rpotts@netscape.com", "", "Unlikely a tester would be able to tell there was a threading problem specifically. The result of threading problems are generally lock-ups. But unless you have a stack trace that specifically points the finger at threading, you should submit the bug against another component."); -insert into components (value, program, initialowner, initialqacontact, description) values ("Viewer App", "NGLayout", "rickg@netscape.com", "", "This is the viewer test app. Utilized by NG Layout engineers to test the layout engine."); +insert into components (value, program, initialowner, initialqacontact, description) values ("Threading", "NGLayout", "rpotts@netscape.com", "rpotts@netscape.com", "Unlikely a tester would be able to tell there was a threading problem specifically. The result of threading problems are generally lock-ups. But unless you have a stack trace that specifically points the finger at threading, you should submit the bug against another component."); +insert into components (value, program, initialowner, initialqacontact, description) values ("Viewer App", "NGLayout", "rickg@netscape.com", "leger@netscape.com", "This is the viewer test app. Utilized by NG Layout engineers to test the layout engine."); insert into components (value, program, initialowner, initialqacontact, description) values ("Widget Set", "NGLayout", "karnaze@netscape.com", "phillip@netscape.com", "Refers to mozilla/widget, the XP widget library used by the layout engine. Think FORM elements: buttons, edit fields, etc. "); -insert into components (value, program, initialowner, initialqacontact, description) values ("XPCOM", "NGLayout", "scc@netscape.com", "", "This is the basis of our component technology; this covers the mozilla/xpcom source directory and includes the \"repository\". Unlikely a tester would be able to tell there was an XPCOM problem specifically. Unless you have a stack trace that specifically points the finger at threading, you should submit the bug against another component."); -insert into components (value, program, initialowner, initialqacontact, description) values ("xpidl", "NGLayout", "vidur@netscape.com", "", "The tool that translates idl into xpcom header files and java script stubs."); +insert into components (value, program, initialowner, initialqacontact, description) values ("XPCOM", "NGLayout", "scc@netscape.com", "scc@netscape.com", "This is the basis of our component technology; this covers the mozilla/xpcom source directory and includes the \"repository\". Unlikely a tester would be able to tell there was an XPCOM problem specifically. Unless you have a stack trace that specifically points the finger at threading, you should submit the bug against another component."); +insert into components (value, program, initialowner, initialqacontact, description) values ("xpidl", "NGLayout", "vidur@netscape.com", "vidur@netscape.com", "The tool that translates idl into xpcom header files and java script stubs."); insert into components (value, program, initialowner, initialqacontact, description) values ("Internationalization", "NGLayout", "ftang@netscape.com", "teruko@netscape.com", "Internationalization is the process of designing and developing a software product to function in multiple locales. This process involves identifying the locales that must be supported, designing features which support those locales, and writing code that functions equally well in any of the supported locales."); insert into components (value, program, initialowner, initialqacontact, description) values ("Localization", "NGLayout", "rchen@netscape.com", "teruko@netscape.com", "Localization is the process of adapting software for a specific international market; this process includes translating the user interface, resizing dialog boxes, replacing icons and other culturally sensitive graphics (if necessary), customizing features (if necessary), and testing the localized product to ensure that the program still works."); |