Why we ever split content from layout? And are those reason still there or have been fully addressed ? What is the disadvantages of your new plan? What WAS the advantage of splitting them several months ago?
Just want to make sure that we won't flip our decision 180 degree every 6 months. Suresh Duddi wrote: > -------- Original Message -------- > Subject: Heads up: Content dll being merged into Layout dll - ETA Oct End > Date: 26 Oct 2001 16:57:28 GMT > From: [EMAIL PROTECTED] (Suresh Duddi) > Organization: Netscape Communications > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Newsgroups: > netscape.public.mozilla.performance,netscape.public.mozilla.layout > > http://bugzilla.mozilla.org/show_bug.cgi?id=106161 > Bug 106161 - merge Content & Layout libraries > > Plan: > > Build content/ as a static dll and layout/ will assimilate it. This is > expected to land mid next week (oct end). > > Why: > > There is a lot of footprint and performance wins that can be got by > merging them. A lot of targetted deXPComification is being planned post > the merge - nsStyleData, nsRuleNode > > How will this affect us: > > Depending on the actual implementation, if you make a change in content/ > you will have to build layout/ too to get the changes reflected into the > layout dll. gkcontent.dll wont exists anymore after this. > > This is planned for 0.9.6. I hope to land this mid next week. I will > give warning prior to landing it. > > dp
