From d2a718c1cbf090ddf1e69ae63b5264d2604bf1cf Mon Sep 17 00:00:00 2001 From: "(no author)" <(no author)@18797224-902f-48f8-a5cc-f745e15eee43> Date: Thu, 11 Jun 1998 20:27:24 +0000 Subject: [PATCH] This commit was manufactured by cvs2svn to create tag 'NORMANDY_BEACH_BASE'. git-svn-id: svn://10.0.0.236/tags/NORMANDY_BEACH_BASE@3667 18797224-902f-48f8-a5cc-f745e15eee43 --- README/mozilla/IDEMenuBar.gif | Bin 0 -> 1575 bytes README/mozilla/IDEPrefs.gif | Bin 0 -> 12532 bytes README/mozilla/macbuild.htm | 916 ++++++++++++++++++++++++++++++++++ README/mozilla/unixbuild.htm | 82 +++ README/mozilla/winbuild.htm | 220 ++++++++ README/mozilla/wininstall.htm | 53 ++ README/nglayout/winbuild.html | 184 +++++++ mozilla/lib/libaddr/MANIFEST | 2 + 8 files changed, 1457 insertions(+) create mode 100644 README/mozilla/IDEMenuBar.gif create mode 100644 README/mozilla/IDEPrefs.gif create mode 100644 README/mozilla/macbuild.htm create mode 100644 README/mozilla/unixbuild.htm create mode 100644 README/mozilla/winbuild.htm create mode 100644 README/mozilla/wininstall.htm create mode 100644 README/nglayout/winbuild.html create mode 100644 mozilla/lib/libaddr/MANIFEST diff --git a/README/mozilla/IDEMenuBar.gif b/README/mozilla/IDEMenuBar.gif new file mode 100644 index 0000000000000000000000000000000000000000..d5444da8c5faa5c3eccea8c1f3ef9b4d6beb32cc GIT binary patch literal 1575 zcmZwGdrZ?u0KoBML1;yUh+%e_SmZG*k5G$UDT)hoJQc#ji4_q16)6OmfI~JAL5L+( zVWVpc@+;a_D99>8MUafmZ91UnPZ357@@P;&h=oNcRbl>y|IzEd`TTR2OD=c03knHj z_$H;8Z3PAZ@c$3Pamdb%dR1`oQhXDjA0L*kJV4BB=sSkev5Z2x|aWy5)+6EBp zC~>_vC4X{lokG#zR_T4-Hd@+PZ>y}Ql59rssQ!W5$9Idq9@p1a-!Jk;RA`8@;bAQ! zXKt)dDUWb4x0#5s(8&j6!F)=*DrV-cJfe2a$7QIYEhCE^GOlWGR<|6)eMw{!FMPCZkJSM(l3ZJgOUc33nil3&QfN;mqn+!d!pJ9riBUeFeYe5`g})ifa0 zRWzAkwMsc~jvm0X7c&~Bg>@;f1w?D2%WnrHM+Ygi_K>GOS+uVUNI46#u6VD_7@wgU z?C`{wiQg~1oR)}M4*172AN=i2Bd0$me`&GB`CTtA)va_U^+dWaUU*QQ{Z=m;?AX7* zK&hYW&@BjCYI0%>e@M6qh34;icI4~#v=gg$WOGSJ__<@>8pL_eyMwfa zGfi?Wm*{VQyzG}lv63Xa`ID@&Qh}ROxm#eYrrddoaH7Jm&@HYcdBdzZ$EqThd}-;9 zhHr1#sJ*t4#c@o?B~dFBg%2l7M8gD9e*68m zTT`#lnJ3cH-h=t$0X-l z>GYb`9#<=hG}vJ^+OJc)JA&czh*p>2(UC6e&(0d1z31D_8{A9jKfkE*HoQ{y`sceS zb9|n$Y2kYpKV5oq@bmGX&@cQv^+Pd7GTNiguoe2@xHCGvI+5$StYM2XmPa^p#qwx+ ohi>`lsh)rL44qbI7{>Ev6o!cc!zP_!vdGfwjkeUr!4~-a2YX!l-v9sr literal 0 HcmV?d00001 diff --git a/README/mozilla/IDEPrefs.gif b/README/mozilla/IDEPrefs.gif new file mode 100644 index 0000000000000000000000000000000000000000..2a0bbb0fd8310d47c6f14603f4556a05104932a9 GIT binary patch literal 12532 zcmc&&^Lt#6(@j5Z+PIAxqp{OuW81cE+qSKZZ9CbZQKOCRrm=18yZ!zX@BB8;%$zyr z%-wzNbHydaI5-Wx{tN!_00RU07n2Z3HUwe}fiOWJFc2^V0tQ3CKnU0j0tP_9Fc2UF z0t7>VKnTzb0t7&SFc32c#0(5E147KqAZ7rF84LsffdIe|01yH&g8%>!01Olf0t1G? z03k4D5EuXi2AV*zq0mq)=rFV!=HH%w0R)51z+eCv4D)X-Gy?*`Kr=8900zSRV*xFi z0l{WwU^4*N4CWsxXfFT=2AF{X05AXs$`LvWh5>?M%)l@JFbs4nlrgGm;qq`Kp3bzs2@<8&}pb0Q2kI6P=!#|P%tQIC`)K7lm~P%6x$LC1fBfn+`lq( z6*K^5W-$MZgzAH?g=PSN82|?AD^xC&1+-`e12BVu`UrIzY5j?RR4vp>s2@<8 z&}pb0P)<<6P=!#|P%tQI=p>XDlm~P%6dMW+^Y29ex}jxg4ho1q0#VNTsqR8VZM^u>n@= zBMn8v@x;PW_>zsqqsdgtl{%x1CFAKojmNSjn@T6LIGm5yN1F}?`~`v$2&9_JXNn|} zX>`Y$E9S}+illO+S}GT+G@7h7##*YD>I~XyH5?s=`1360Ds{(OYu4KECX(pA-KsZ0 z9yiAu<85_Yy#XH)31!;rw+AB7Y4yPE4LidLq|&)E9Ztry0;rj=1|3ZYQ~AQtgtDE@ zM|0)M!M}ad7!EMijK*^b@EF(E+G#5{yV=_=wveu73GId$tS4Lzo3tjoIIEW2K1$}v zb$8yKEH_ziO?HDGF8&NeLx|*ix?DF8FEaI~db(d8E_cTB{Fb6_Uh3jOgw{k{n+NV6 zDE|a}+=HFh5MB|T*M&#HSHt@0HKJ#u^jv5J8^fe9C#5=rmcBSgx|lI1fWyErw1}ldKknav90_~ zRvLRGj+T?t+>8FXNR<+#-leuJUy?j{&D+@h$w&TMh=X(!*XDgEQym-&Ma1&tm^I&nlt{=``s@`#A zd7(~jB~40Ln5BAI{WZj;G|}>!k}NCz7&f5vSn&9y?pJ3zWqH6okS5P4sdKN;ztxH+ zqmVF4y?$QJ`phj!u2ZK(xYKg2_JgIH2|O5s!A_ghZ-au8!{WvA_rQ#5V3=6n0pypvS!4jftkTnR)@c1VL%kFVIg0lAUZw&kS<4%G&!_#hxy4}-WhI#GNe)gQ% z`ig%Q&f;Nly4~|pd0FlAadq4I^NB8ftXqQ5lHJQ$`vIX_RzBi9qgm${#@EY1EP0#@ z=P5huU*harIakx-jJ}p5+MQk5ljabg;T-piw}(IBjPH-T>Ajr6jp2UXF7<5}eu}dz z&+o6dOZJer$F;AzcN;w;d=nf@(ys=|JTSPI0dSw-mmb@g{)^l5C(FvU_z4gI!w?6d zf%8AJKX$y8Ou2V?8xT)k$Nx7N6P#LLKy2eGh|Yi%`ZK2BoUT0os}n`YGO6K*@0UV2 zd}5(=bU(gAQ1=H&aA)jTL=uqw4|-8s9X_xMV5h3MHKN}SMGZ%PH>}UVCPurAR5a22 zy5~B`oXNy1X=3z2Py&RncS)p>QkaHqR?j4a#BzleL-2J+6!AauIQJM-)G3J(p*V_I zB$L(WZ0wYuDC6?HA;sk>qU9#4)SA;{CIpO6l(HmN@c~Dq@PU6N+$Ei&QU{BFsE|->W(?&-PQ5sXHV@mbD zb%@{#O@}(s?Gwwh(U@b7ndp;HG`Ca#*6OEAj}|n8PX)?)6vQOW#+31#+>BYZUS$fu zsx**1K_DE@~qujtx%N33Rk#ovKkR@fGH09GC=}H*%-Nu6p z=S-)B4)|2lY8@Aqw7Puu4dy$9W7(n&`%ZW1DW&EBYAFHM7!j;E@Z#xZs&ZTO|C#olwGw+f0qWjWS zTF6-Qm|PAu4zX1_2U1I&tErAALr0>4=>xA%sV)d_RR&+Am-}%S>j>$rKR!M8eo7)M zb5SnWpp@1mUsPy_8Z1XA;6@wyUR<+ORc%p_sa|50T9JKLEi6DgKGS($Rx&|@K82fD z0Qn{&(Kbdi!sD$y+H>EA9&0OSzNTJ0Z5!J?SJUmm{cZ6Yvwb?X)Zt-O1g-K<=Wuo<>#~Dw~9#Ka1leb4O!X%wBd)3^R ztp{Sx8+-pzkP!liL(LjN$9dsp8+Z8UU;}=G`wt%-co0V$ea~e(jE^Ah+T#fBV8b(u zwgAvoy=&CQF|-e~^`mZaL}JqEHl<62qD+lU#LX_eMP`4^@u^wwomrwkW{(-f32`^4 zurppbMP+m5U~0C(<_5C-rsF)F2sl?Zx{FH4K?6><+{I;F;m^|ED^IPR?qz(GJ%U|D zZ;3dM$Pu>A(3Nx4B}m;#Gm#QaE^MBKi)$(X)Ev=n;V_Zm9r0tajdFG(&3`7Ks#NB+ zm>UBQVm~oR<>POM;cJm*+1ZxKlAna%Yf96DTIgLj7IZ;s3);N*LL=U2c5}#-qiha_ zJa2T8*W{&s6l%4kR%csAcyl;c_aTliD>S_x{aj~`J!dug#7!D&NbnEDU%nh!R;~Sk zwQp^n=&;*azuW#6-#$o>RW`1bHjP+H-x!&*=HvYkM7YI%$cJ*B^sux^4q@*Y<0QH4 z&TgmM`E*byr8^lfwKf%EwXdNu;S96MF4moPR++f5?iAYecxb9)u54JiPncHaY*?#drUt#wN zDOO4r!+se?dpq!-9CrO6;d$BWW9{zod*3rZ{X24oKaCKn3T$9;kb;jGDaEq1_8>6= zTCneqJ9V1QE35;iMIcIq`?b2o$C1FDJ7Xa+H@`Cbzpfz=w_qxEn?rU7HFir%577gP zP`GO>g8iVJ&%sVVg87RB{MBs`+O^KV_;r|DW~3S;wK|4T+LMIq+?oaGWq1a(1&}iZ zyP&whv>thaze_3-Ld^~B>eC^`~uUR ztg*fOzlYl_g<&j*K$a-I+e0IjLY)$+N;1NW+Cxh@qDms7Y91A-grfo;%{9ug(GNYd zGeTNe!)DaOM#_xO+#_u)0{GxuK^8Hm=8@4$KC6^br5xlfaM5MuGIQlp4H?o+8nKBO z(M6@9tr-!78Zi#b(Fxd5*zMjp=Dq?J9zo$cq6cxK9!|DPw)q;a(-P5Z4%m4NcyyrR56nDUq{pjoMcoF8AC{WgiLz!hlA*$FER7O-oJiR zk8{LKMEECKL;xznGcjy+mZSVfm}MhFW5blT9)&0dLN$SMkbV0o?2vuz#3_!%^fVvS zYj0PNc&rQq6{@&Asx;%#;A9SeVNL&Tj-;dX6xOt8nyZKexD?*@xLfn|xbif|Cqo|~ znqNh50B5?8X3Cv;_+^=Yf~TKDM=%XqN|0uH2z8jpQOL;wTC`4CxA3)P~y^UcmK1rVv$wXbVM1u!(?xWxy>Y%VlAdwqmdPO=AC!_4hOTfb(qH3QY z8Z3pK#QGttMN@NHJ^MGcXIuv`6(s*No70(U% z62EyA$z_2=~6h8dZ8{uD=$q5K!eCDNdyy%07cjrXVk znI?dA6-e|5JhV{#cIY(9;o)Om1cP1pR*}th3>244V)U}oln{$c3-X{yUBM;|a)}OX zNM*KU)7KQB>&(A!FT%A*lk6;#&P*q&OpSF+-Ymz~!cA5#Px)9Ou2o)gt5U$cnqwdp zCK{Dxv6ySRn#@C!NDHqN=EaaNCdP~v41iEty3x=dl_srZIMZ-M!+Vw?dPd@DW{A*4 zie+ZKxj(5xhtbw;VKlom^*GD?@0bqDg#T^yggQra3#2fB$ayArmqSj8Xy+Qs-3CvV?wV>Rq;zT@f99}%h~*&gY=F=*Gr9_ z5o$ks)yrd7AdIKbMV7QI*M^VDVMDl`TQjRYcWaSogYm86bEMK<;VUJi3JE9+tjygc zqMd9!3h1RO!;ebEZ;J#%^8^tK{hqDqo^ykS6ZJaXwjyJkEYS98T3GLzOvW4H4jR@q z&2?UK5G9-p@$!wc(iCX3e|EMQYG&KKScGU95019Ib2a-T)Z1CtyLp%99~D%u6~(<&lxR28 zwRKpFf%GdnYu7qEwX3VrTf8Z&2fW&FJ3-ZJZ5C9ZUniM4;~rMhUB{fAC^UtAnO$R5 zRp65@kad?hLczRtcc@$UGGwiDRl0c{WJ|*hYQ;m30*OkZ_Sm!aG-&IHe+WC0F0yUt zK}q`NeB3kjrJLi}6cV7jVye$~Z^Awjt@t@<_6YB>O57>k@8>{ilA+9&3pQtX(D$xN zqfb%>cjh#Q#jpo`-XX4dpL(^bly5}!Kk59!bTg!)ZNy*;`S82Z?)leQb5mhopCYFn zn4*v3u@CiTV9L#IWl)~PbTCd$g5uQ`^2dPo)L5dt@U1nHoMzy^*=9>l7{PIIcS0S6NdVs~_uqB~Df5>(!((?&Qf*l;p#F&4c`pUnzcPes?RR8t-SS zP6W_($!7KnbPi3HQm#YDK*`zXqrJQ~mxdZs!;1I>@55|69sK zCsJOfH*kHpY(3H6rq?ELh^24{FUGonhcU5QmU2Nh!ADMQc_47v!P>^UySm(*2TZlx zSL%|gvO9pwGS+u&g0`Ppe%hi+H=-^x(Eo$uhzkEK#UTpcvc<;k@bhoQBSn!{1;4{_ zh|Bl^9XJa-o>SciGc=NT?1WyXmRFTi@7=#K-m!QR;~`C3=Q9#$GJXtp`1CgVHeU`W z-gh2j{kdBb4hx)#Kh{(&zo15ws52v~;s{16e~BsFI++?koK}MyM-_EO5gjj6i%8LO z#sFlGmdnRPc2)f$vxGpD=6S8#ZhG#{LK=Po6Do5_+gkQfD#ZH%r1@Wx~m zBtM7BBc}_URrI_BV{U)a>R!;PGNT{c@J0x|d^e7K3zsLf$&nbBa99 zJ_&tTg#230>|TjHTaNejPK=#O=Iu_+S+ST{DbHCoJzL3(^(xo^h3WQ`Oe~bzuB0Jj zXyvT5`>ttsuT{RS`An?Vym{2sc>5tZrNl0`>8^EdtaVSUci67YBCpTeF81@TyQ;67 zX)Nt}FO5NT*Cq)z=W^CSXKM?-oBpyRQn4FlWgC4KolP4He~>q}dAAOIw=$5IfA?(; z>Q)vKtZgEr&d9FK$!>kzT;GY^Lh#%8rZnYl%8g>D9}rxbZ}Ty_)T zeY?A6>lKyNie8u;g`E;bm^v2=BQATGc5Mv#FZ1LI(j*=&%C=82JG&k?H=k_K%-{Hz zzaQSe0rYk=b$38BJKjaR{RKPI1G|9)*aEpzz0#;+etS9ef9o5t<_&Sl<%j~d)k0_X zBqy<`QTD3*y?*RF zPGW^a7_h_i_UBaa7!GhEC--di4rfsJE%lBn75@@lA1cKi{6_wh2%2K$JG5aqv`5)r zHa;wqJARpuyd6K;2$fpXH{BlOEpCZ%V8;9Sk1 z=Xfypu(jv7BUdQ4=LqO@pqO>APS7iy+a*!Ee|2*<;dkz<3cKSxv-t)e--|>k~cK8le zh>ldhUJdizQpBGMZ(R)566!FXg`wUUqujsR-8kx9e7L~Ujz7}fx~KJrzEU3<+n;$v z->&o=_zqjgrG9!B8)4ycwJ-qRIO5VQg+T0cMe^`6##o+f6U2c&&cnDFC>);PR zqD9?^JLY9Pfg?KW*MGHVxa@Yi&WAjW)*Tb*zgF>|#W6gme7IoEdrg_TvCccUgy^5% zPQHR~Uct2|vvo&q{9PW5FPE|}Q>SrUPl>wH1@lPgit)G#gwNUX?{jwha(vj2U%%0Q zLLt+b{v#M1_>IA2WEw$;78Q%nhT~g+AT8F{_qq0L`XIE36 zK)Y0dP2fkay-3$rkKB?=f0AlD&}=cR7K_k$E|5aV8m1zpR5zDOpNN8@r9n9}5QdJZ zyMA*yl@~%TAGX3ypS{?HS0T#ia4x>s=FijTr*^5yoN!06clGgyDOqLs1p^_i=l>`OqG`Qx7?^0yAe@h7 zf1%K>>o49NnC3)w9g}Z+!{AZqijZQt62VYbaTNWo?Q$iGZH$ll3){N+N(|pQ#j)=j zvXp%tqJGkJH*z$~wFDA(3Ps+|s0? zp>7b2>84>6&DvV5vZr!Cr&VHot6{;utJ(|DZ@Jg9Y4Vk36G;#KM!}F5 z>$Wa2D$=55JE!Wt;o6b9utqG4uq5qtVr!=bn6XOG^?SL)QgDaAzSaJLQ?jHNQUGXM zGJ&{08b+8Sd1%55y59c@0T9m3^ZCX;8Yc+iDR0*GS3hG?qyLJ&Gu|joUG<$SxQ>CViL4Bq-hSRMAfc52&!E4vaSV9 zVoR6X-dkJMq1$PiHP5NN)MV11tFAX{>Se69oV322+ew#Vnrd&yd9OEJefM!_StGnL zN`*|aI`reYzZwrbiRn0cSltT~i0635Q?anVE{obk%`O%4 z@;t5*>h5oD>s29dW-FEupK~8)EWbw_cOsDcR(wm2$9`7b@Dk3yz+n_Xi(!C4j&3Z=wo6BE+-dlnB}PBT}wNqG3Eb;TEDYH!ZP%}QOX+KBoejEt*tUo$d^{;VZwf%=jZzB%UI5K-^jnh4|Kiko=`LWos6Km%w8m)WFx74+( zYVX~0GN;QKR=r7_ zN56ggOT86u-3KwnU%@F+R(p7wmqJH9M$x%`4{KTzr6P53V)~&=Rm(R@8l7#jKVz|~ zlViQod+)k2qIG4o5h$^L!TB|K1+H)64nVM&xEPj9c1+~a>@Nl-r5b2KnTGdv9KTs} z8{As58PB=GMydQRqnmVg|MTt`v6^(q;-=gB%FQ858nG+0qeje=A|R#59hf0J5$*jmzc#U8l|!?@fK!ZobCd)oGJYYdv8TXNt$$jAx~- zW`rSScweOXK`n=Xi>SG_aMLpP!hDa_(UrDllTumpc}}huam;m-q(;@&I-Q(#0paFO zB+a%`J>I5WxF&`p*0z8~JWI8!)w1cw_35Jph_#{BrlF3&&O}&w<<~u%*e~Ba14KGt ze(6!i7SK+)>7)>M??Gh97VP_={Re{i`d~F8d!f08xB94eKH#u$uAfS?iIGLye^%`f z%7kC`?ZBf7g->yo$Bp7Ur*~tlQ-;3O-XoIdcN?y`5c^cj84bglNOk?g50D zdl^mnZ4KSdZ3v)u{l}4KX@l@-)Vzl^^^4B}Q=R9u_w=PhsMiudk=J~a?XA4{>t64< zsxq!uhNf>}@m!`CtwX^khMy7sF@5wDC5OnPmdV6|l{V4ud-`{0riEop(=%MQMy-5^9Wv%Y@Vw@j#j#apk_Xd$4Wru(JivJ8$gn31_$;JQkndH+Tzv3)E9#?V6ngGhF zz*n8l(rD%fN8aY~h&8x+B@+5S!nAVCMRRBZM_GK)7W}w_slf5NSrAvYH|BpTzs5TR z7p*~`eL4n?1&Ms{iBp(y*ZW9!`MIl*Q39^NSJ_&P+i17RH%oz`g@eGI$4v-g%AO}+s4N|q73=F&okIW5jW-#2* z4&C0cDGc^4;tiqk#D6QoJ5Z*5lBC-@A%*=2)VQS;9H_kAA<~m!?vw0Cbr}-qV%4zu zCU`n@Dj`aD#fyd}Hlq03;8is65XJ^9X1gwCcPeJ9(`VQ`P;=77KqhMCBlhuA3G#o; zvQ~X_Ty?G(WKzP+Iy@!tDfB`sqS)TGWtU?9ui^nn5_apoI3ID0n%RtH5FYVF44vC( z0gbHAOkOf|KLDZ-MD*qdG-jM&@rOnRdPEFg9>zd?$t1eb01@V33~`xPe&^TLa2^1= zFrx%FfR&U5iJO^yKr}n0hs@}=4)?G%i(~=5RN<*uBBzAtZnwG*bND)Q23P_(KN6iS zb-g;8@u@lTv@*x0f#n1gOeIy1B;7D5=C3r$0vA}BbH{wEgEeb93!Qb=!hAw z4UuYX9${0gXgHPb{WNaOEX|QJD5@hRFHQeF=9l=1C`l8`ywkYO?yzq*p9FwE#)TzM z1wHOjdh!%pXoJ-kBQh>MlBGRDt5S{WDAs=?W6x6+WguGw{$30gEaCZWVoV}O*E6Yu zyr2`Y(VPZZu^EzNkrBd|R%eonN1RX~1Fx!#C|S2NzRLI|PNpc!sbLIlH_N(K2^C-f z&%r5w1}FRHCw)MCNzGX|DV!%rLi^c5e|h>7ZL%NfFo;v=R$b(;L*(wbN5R`ug78!K zbi)rw_3OLb0qd0!T3H|8rtVaP((tE~G*kL+#L@c6NMErLFfm{VCQe-@lZ+)ioky{y zMVpdFR)nW(!7|~a3Unfc0&vk|x1#^qh%eSlRT(JuE^`W#)%NX9U)@fh13JP)z^Hpo zTGe@@7{52cX^XeK8W@qy5sDVKG$0XVhps4!mMKo_X`|EWS)a*RM8%eM@gXEJ0dE=1 zK`=xhx_%|8d1Nqc*+uEI6+E-7c$vza*J}~q0E1hxl)KG1W`rz0^bKNJ!Rb@yJHjYJ zl|&~vzcU4V5+rpsF7ZKoR@zdDa)E5KTscEWCCXmc$DX7j15aCi>Q<+z%5dlQ?vkUp=q^{Ppd|v+oeFkw)R+fct3Mk zS#-fRMCdQ^{LD`k29fz@8!4?&8T7reme+X`S;b+M8S4*fPaSaKUNgisG9B;}iRt@S>|z5H@&oV6bqn(M|h&9R!Jxbv;_tHp!z#JXZS z!rib0IlU#FDn@Hmj@q0d+8apg!&mar#Bd;bovv>A5A@n4cYRN{TE9gjhRIje&N}vP zXZBxbzw*k`%E-fZuSW@dA34)0Ym(o7Rh+5OoaJ5lFO{btd&vJuPKHTGU|kzxl8p=x z%X_SozP+(A;=3^|x;jISBPuGmFZD~ChRBj^T047_`i+DJN1FPs&do;9p{ADKc{500 z(w1BAN=EPgr|f=?>WQy}bN8lURBz?-=0VF6&C>+wgw%D#@1OnjudbMz*^BjY>7^kX@HaxW~ysZzxeHJSr{Z;kLJc z3;}$6j=449VvIPT9Mw#ZM~)mTCsQ70Mv!TxrEQ5Q@(ZKu$2Fit2%#5q?1VY>*9RG^ z(2bwbtW5&Ku`LwS$jp{)lRw(Ow^Z^8ycwU!`t%KF+w}gHRjO1SIoD?@S+2@v(aNoN zr&lQ}MHou6Si}@8dOP4pu{dQF=={Fr!Luh>R5QZ2*BSN;an}YS=%*stqKag^IK&Y9 zhs!o4_b}Y8Y&h&}ZPONnLI&J7K(aZ<@;Tp_{MFDSA#Epvb*~modlvp*Z25V`@1CYT z2L63KtJ?Ru51)GP&Nb`I&X0>~C{uqbAfNMoKHH|S8x@Pb(yO@6WlpHYtL;C0dtaX2 zaV=WmLPuFCwbD)O$X`q2MnS9Nw*Id*KqJXftc zSM6R`ohet{Emyq@SFOB0(XVcX!(=s0bOaBsCh~5k`fg_S_bt=6Z1_eqA#PUsM3#_s ztEu~M`c5`WZuUgE*1ePVL=UjLZjO}hF7`PN=2I^A57V0NOQsI)dG3Ci?hFO)K3MqP zb?D39uKr)|bn#qDMjzDQAI#G4A?C z@moftkG^fG(ZkNZ07puuk+>}$dODqCEVeSxgBICS5+z^U)L}~93<7@wqWEL_!9&Ku zX5r=qTDR)qT}%$;*RaFOd537=p2L)fTSU9(CfF0hG`47}GZ*VA4~wM04DT;Usm1O| zN)xUo;JNMROQZR7tHR4f!t;FlKw21U!vl!0+XG_Mm)vq%tEQHso3`Znzn{6uTx zrL6Y+y66<1=NOjVwne}vRN?h^p6`me&#?ImWJKSG-~w&@!S_!dB6#b^M0_(KsE@Gg znR5Jj2D8R@=kU2I4{b6}A0sen-`~(V67u^(KG%GrDZkuCp#6sa z8KJqbP&5V`R;|lorbsM~NR;nX;;Lvgg^IN{J42yxJcHSMw%YQBVltb{{rdFi=3pua z#tO|P;xb<#L_GR?&ggUj*k70w?UTV>O= zw%zcno9bfnDt>`%tJ zxRomfYLy!F7H~5GgX0w-no#TMn&oB7gEUd@mpii+n}xq_M;%Sz?kLeX{J7;ui6p-V zTtcKS=G(*BGUYlH%{%kPuC}84jRXpd$|A|H$WxfFQ599z!zCb3y3@w017=^wR$`rH zbIY~2a~2OnIz^FXr_sRObptRgg@JRA<^ypEsuahz@p8=&p3?0?*tXHTXp5@qZt52j zuVclLtzaszr5s(1&gH++Ok*6Ru_>Ao+xB{a9E6soimHF3Y2=16 za(V8Ah}E_fMUduxE>4!w`av!tWd?!IN!O3!qyVy&QtqS?9(&-%Ydm>unitq|Qs%g> zdQ#?k9(PdY`980hi_-O|P-KMQdQlZ}ao$oE#m?eTd8kA!e~Ub9aG@>*T6I#F<#;_) zmuDg%7#GHdYSL6z5Nauu*K{IS7Tc)72Y41usu9(89Cy;zbw5AT*7qH26&DTRdfPNq z(tu7Y`?+4K6Ko}EjB3DI-t?_2R-m((mexqsmh~uZhK{{VZ#$*ABrJx`v(6WWuB*=# z43?*3-i$p@$Dj-I+aPV~-Vca8Kl}cAaaVQ2(sunEKxX%JNQLL-VH(2J=D``9|IdeM zn85p$N#k9QoN0tS%g3n?r)~wrG)514y#~=Nfk>NK*L(nzoF`p?Dc+Y?z_cJDFUyQ5 zo-fO+Xrzs*M-$f@%e#|`qFWZV~mT&7~qnHf|*cSA5 z-(ILHNxkm6=G#{36wRR^GV=V!{wENTk7GL&&yVA8ByA7JPAvC(`}U8d1HIW)Z9mR^ zpmh)DL5}x3=OKrBr1oJ+mLJz~MO6>iNsV*}u=XOS#pZ9J-oZuS__x}NK + + + MacFE Issues + + + + + + + +

MacFE Issues

+ +

A general document on how to build, what works, what doesn't, and +things to watch out for when working on the Mac client. Please +read the entire document before you start tinkering...heck, you +may just learn something!

+ +

Abbreviations you will probably see in this document:

+ +
    +
  • MacFE - the Macintosh front end, including all the + things you see and some you don't.
    • + +
  • XP - cross platform back end code, mostly written in C. + You will see this used like, "This is an XP problem" which means + it's broken everywhere.
    • + +
  • MW - Metrowerks Corporation. They make our build tools + (CodeWarrior) and PowerPlant
    • + +
  • PP - PowerPlant, the GUI framework on which our app is + built
    • + +
  • CWProX - CodeWarrior Pro version X. You'll probably see + CWPro1, CWPro2, and CWPro3. We may also just refer to this as + CW.
    • + +
  • IDE - Integrated Development Environment. CodeWarrior + is an IDE.
    • + +
  • NC - the working name for our Aurora technology, the + Navigation Center.
    • + +
  • HT - HyperTree, a layer of XP APIs over RDF on which + the NavCenter is built.
    • +
+ +

Building

+ +

New 5.0 Features

+ +

Unfinished Features

+ +

Pitfalls

+ +

History and Future

+ +

Help for parts of this document, especially build instructions, +was received from Dan Kogai.

+ +

+ +
+ +Building

+ +

What are the minimum machine requirements?

+ +

To build Navigator, you need a fast PPC Mac. The faster the +better. You can't build with a 68K machine because we have too many +resources, and the build process will crash when trying to generate +resources out of our cross-platform strings. See the discussion below +for a way around this.

+ +

You will need about 96 MB of physical RAM to "fast link" the app. +You can still fast link if you give your machine 96 MB of virtual +memory, but then the VM hit is large enough to counteract any +improvement. One of our beta testers had a machine with only 64MB of +physical RAM (VM was off) and it ran out of memory trying to link. +Turning VM on got it to link, but build time increased greatly.

+ +

Reports from the net indicate that the optimized version +(MozillaPPC) take much less RAM to build than the 96MB we suggest. If +you are running out of memory, try building that instead of the debug +version (the debug symbols require a lot of RAM come link time).

+ +

The moral of the story: get lots of physical RAM and don't use +VM.

+ +

How big of a partition do I need for the source?

+ +

You should be ok with a 400MB disk partition, even when fully +built. This does not include tools like the IDE, just source.

+ +

On an HFS+ volume, a full build takes about 110MB. HFS+ is good, +but utilities are sparse.

+ +

Why do I need CWPro2 or better?

+ +

We use CodeWarrior as our development environment at Netscape for +the MacFE. All of the projects and tools are geared towards the +CodeWarrior IDE. In addition, we make heavy use of PowerPlant and MSL +which you can only get from Metrowerks.

+ +

While we say you need at least CWPro2, you may be able to get by +with Pro1, but probably not for very long. We haven't tested it, so +we don't recommend it. Get the upgrade. CodeWarrior kicks serious +butt!

+ +

How do I setup my development environment?

+ +

This part is very important--and somewhat difficult (especially +when compared to other platforms). I repeat: Read very carefully! +Once this part is done right, the build process itself should be as +easy as drag and drop.

+ +

Here's a list of 3rd party software that we compile into +the application and where to get it:

+ + + +

Here's a list of other build tools that you need to install +in order to build and where to get them:

+ +
    +
  • MacPerl + 5 MPW Tool
    • + +
  • MacPerl 5 Application
    • +
  • MakeStub - MPW (installed with CodeWarrior Heaven option). If + you choose not to install MPW, it is located on the MacOS Tools CD + in "CW Pro 2 Tools:CodeWarrior MPW:MPW:Tools"
    • + +
  • RunTSScript - in Mozilla source distribution + (mozilla:build:mac:RunTSScript), needs to be installed by hand
    • + +
  • ToolServer + - or in the CW distribution (CW Pro 2 Tools:Apple Development + Tools:ToolServer 3.4.1.sit). We recommend pulling it off the + CD because it comes with configuration files for CodeWarrior + which you would have to create manually were you to pull it off + the net.
    • + +
  • New Alias MPW Tool + An MPW tool that creates Finder aliases for files. +
    • + +
  • StreamEdit MPW Tool - MPW (installed with CodeWarrior Heaven option). If + you choose not to install MPW, it is located on the MacOS Tools CD + in "CW Pro 2 Tools:CodeWarrior MPW:MPW:Tools"
    • + + +
  • ToolFrontEnd
    • + +
  • patch + 2.1
    • +
+ +

Once you have all the pieces, here are the steps required to put +everything together:

+ +
    +
  1. Install CodeWarrior from the CD. While it is large, installing + the "CodeWarrior Heaven" option will guarantee that you have + everything you need. This will give you PowerPlant, MSL, and MPW. + If you choose to install less, proceed at your own risk.
    2. + +
  2. In the Finder, increase the memory partition of the IDE to + 15MB (you can get by with 12, if need be).
    3. + +
  3. Download ToolFrontEnd. After expanding it, in "ToolFrontEnd + Folder:Drop-Ins" there are three items: + +
      +
    • #include
      • + +
    • ToolFrontEnd
      • + +
    • ToolFrontEnd Panel
      • +
    + +

    Create a folder named "Include Scanners". Place the file + "#include" into the Include Scanners folder. Move the Include + Scanners folder to the CodeWarrior Plugins folder. Create a folder + named "ToolFrontEnd". Place the files "ToolFrontEnd" and + "ToolFrontEnd Panel" into the ToolFrontEnd folder. Place this + folder in the CodeWarrior Plugins folder.

    4. + +
  4. Open "ToolFrontEnd Panel" with ResEdit. Change the file type + from 'Panl' to 'PanL'. Save.
    5. + +
  5. Uncompress the StuffIt Archive for ToolServer. The goal is to + let ToolServer and MPW share the same Tools directory so you don't + need to have multiple versions of tools. Do the following: + +
      +
    1. Open ToolServer's Tools folder. There is one file called + "RMetrowerks".
      2. + +
    2. Move RMetrowerks to Tools folder of MPW. MPW folder must be + at "Metrowerks:Codewarrior MPW:MPW" if you installed + Codewarrior Heaven.
      3. + +
    3. Remove ToolServer's Tools folder.
      4. + +
    4. Now create an alias of Tools folder in "CodeWarrior MPW" + and move it to your ToolServer folder. Rename the alias + (probably called "Tools alias") to "Tools"
      5. + +
    5. IMPORTANT: Make sure + you only have one instance of ToolServer on your machine. If + the build script finds the wrong one, the correct tools will + not be found and strange things will happen.
      6. +
    +
    6. + +
  6. After installing the MacPerl MPW Tool distribution (run the + InstallerVISE application), in the "MacPerl ƒ" folder, there + will be an MPW tool named "perl". Install this in MPW's tools + folder.
    7. + +
  7. Install the MacPerl Application (run the + InstallerVISE application). You can install this anywhere, but it is + recommended that you install it inside of your CodeWarrior folder for + easy reference. After installation, you will need to set a preference + to enable double-click launch of the perl scripts. This preference is set + by going under the Edit Menu to Preferences. Click on the "Script" button + and hit the radio button "Run Scripts opened from Finder"
    8. + +
  8. Install the "patch", "MakeStub", "NewAlias" and "StreamEdit" Tools in the tools + folder. Note that "MakeStub" and "StreamEdit" are automatically installed by the + "CodeWarrior Heaven" install option.
    9. + +
  9. Install RunTSScript (found in the Mozilla source distribution) + in the compilers folder in your build environment + ("Metrowerks:Metrowerks Codewarrior:Codewarrior + Plugins:Compilers")
    10. + +
  10. Next, after downloading all the 3rd party software components, + drag WASTE, CWASTE, Menu Sharing, Mercutio, Internet Config, and + the AEGizmo folders (just as they are) into the "MacOS Support" + folder in your build environment.
    11. + +
  11. Start ToolServer from within CodeWarrior (or use MPW if you + are brave enough). We're about to patch some files. Make sure the + ToolServer menu is in the CodeWarrior menu bar by turning on the + preference under the "Extras" panel in + the IDE Preferences (not the project preferences!). The menu bar + should look like this: + +

    + +

    Choose "Start ToolServer" from the ToolServer menu (this is the + icon menu between "Window" and "Help" in the menubar above). You + will now see a window with no close box. This is your ToolServer + Worksheet where you will type (or cut & paste) the commands + for the following steps.

    + +

    In case you have never used MPW/ToolServer before, the + following is very important. Pressing "return" does not + execute commands like you might think. It just inserts a newline + into the worksheet like a normal text editor. To actually get + ToolServer to execute the command, you must press "Enter" (lower + right of numeric keypad). This executes the line that the + cursor is on, and only that line. If you want to execute multiple + lines at once, select them all and hit Enter.

    12. + +
  12. Set the shell variables {IDE} and {Source} to the correct + paths for your build environment. {IDE} is where your CodeWarrior + IDE is located. {Source} is the folder containing the toplevel + "ns" folder of the Mozilla source. Mine look like this (don't + forget to keep the quotes if your path includes spaces), yours + will almost certainly be different (to + punctuate this, the things you need to change are in red). + + 
    Set IDE "Develop:Source331 Build Environment:CW Pro 2:Metrowerks CodeWarrior:"
+Set Source "Source:FreeSource:"
    13. + +
  13. If you are using CWPro2, execute the following lines to patch + LDropFlag to draw correcly over non-white backgrounds. You do + not have to do this if you are using Pro3 because it has been + fixed. + + 
    directory "{IDE}MacOS Support:PowerPlant:_In Progress:_Table Classes:"
+patch LDropFlag.cp "{Source}mozilla:lib:mac:patches:LDropFlag.patch"
+duplicate -y "{Source}mozilla:lib:mac:patches:DropFlag Icons.rsrc" "{IDE}MacOS Support:PowerPlant:PowerPlant Resources:"
    14. + +
  14. Execute the following lines to patch menusharing.c to allow it + to compile with the new Universal Headers. It references an + obsolete header file (GestaltEqu.h). + + 
    directory "{IDE}MacOS Support:Menu Sharing Toolkit 4.1:"
+patch menusharing.c "{Source}mozilla:lib:mac:patches:menusharing.patch"
    15. + +
  15. If you are using CWPro2 straight off the CD, you need to patch + AppleEvents.r to fix a problem with the Universal Headers (the + definition of the 'aedt' resource was omitted). You do not have + to do this if you have applied the netborne patch to Pro2 or are + using Pro3 because it has been fixed. + + 
    directory "{IDE}MacOS Support:Headers:Rez Headers:"
+patch AppleEvents.r "{Source}mozilla:lib:mac:patches:AppleEvents.r.patch"
    16. + +
  16. You need to patch stat.mac.h to fix a problem in MSL where + lines were omitted (both CWPro2 and Pro3 share this problem) + + 
    directory "{IDE}Metrowerks Standard Library:MSL C:MSL Mac:Public Includes"
+patch stat.mac.h "{Source}mozilla:lib:mac:patches:stat.mac.h.patch"
    17. + +
  17. If you are using CWPro3, you have to unstuff and copy the old + Grayscale Appearance classes into the PowerPlant hierarchy. As of + Pro3, they are now obsolete and are located with the rest of the + obsolete PowerPlant files. We'll fix this shortly.
    18. + +
  18. Congratulations! Now you are ready to build. Once these steps + are done, you don't have to repeat these setups the next + time!
    19. +
+ +

Ok, so how do I build?

+

In the folder mozilla:build:mac:, there are several Perl scripts with +names of the form BuildMozillaXXX.pl, where XXX is "Optimized", +"Debug", "Tinderbox", et al. Each script builds the corresponding +version of Mozilla. If you configured the MacPerl application to +execute scripts that are opened from the finder, all you have to do is +double click on the appropriate one; otherwise, launch MacPerl, and +run the appropriate script from the "Run Script..." menu item.

+ +

These `configured build' scripts are simple, and you might want to +make your own to force your build to StopForErrors(), or alternatively +DontStopForErrors(), et al. You can set up certain build-script +variables and (soon) compile-time flags. Compare the supplied scripts +to figure out what you might want. Note that CodeWarriorLib, Moz.pm, +and BuildList.pm, are AppleScript libraries and Perl modules meant to +be used by a `configured build'. Use your favorite POD viewer (Shuck +comes with MacPerl) to view the documentation in the Perl scripts.

+ +

If there were any errors in any of the projects along the way, the +script will stop at that point and the IDE will tell you the errors. +You can fix them and make sure they current project builds, but to +continue the automation, you have to start from the beginning by +double-clicking the script again. This isn't quite as bad as it +sounds because the previous projects are already built (unless you +changed some major header file). Please note that stopping the script +once it has started is difficult. We are working to address +this issue.

+ +

After the build is complete, you can find aliases to the built libraries +and the final Mozilla application. Debug builds are built to +Mozilla:dist:client_debug, while optimized builds are built to Mozilla:dist:client. +

+ +

Don't worry too much about the numerous warnings generated during +the build. We try our best to get the XP teams to use real compilers, +but alas, they continue to write warning-laden code. There is also +some generated code (Java is one example) that has a lot of warnings +that we can't help either. If you write any new code, please help us +in our quest to get zero warnings.

+ +

How long does it take to build?

+ +

On a G3 with the source and IDE on a RAM disk, it takes about 25 +minutes. On a PowerTowerPro 225 and everything on the hard drive, it +takes about 45mins to an hour. On a 9500/132 it takes over 2 1/2 +hours.

+ +

The moral of the story: Don't try this on your 6100/66.

+ +

From Dan Kogai:

+ +
It took me 70 minutes to build Mozilla Debug with + configurations below; + +

PowerMac 7600/120
+ 192MB RAM (No VM)
+ 1 + 4 GB HD (No RAM Disk)
+ MacOS 8.1
+ CWPro2
+ HFS+

+ +

What's special about running the debug build?

+ +

Running the optimized (non-debug) version is easy, just +double-click it and it will work. This is because all the shared +libraries are compiled directly into the application. We don't do +this with the debug version to facilitate changing bits in projects +other than the main one. This way, you don't have to relink the +entire app (which can take a while) to see the changes, just the +project that was modified.

+ +

As a result, you have to find a way to get all the shared +libraries from where they are built (scattered throughout the tree) +into the same folder as the app so CFM can find them. Luckily, the +BuildList script will create all these aliases for you and put them +in the right places!

+ +

Another nicety about the debug build is that there is a special +"trace" function which can be used to display messages about the +state of the application as it runs through certain blocks of code. +To see these messages (since the Mac doesn't have stdout or stderr) +you need to run an application called TraceMonitor. TraceMonitor is +available through Apple Computer with the ASLM package. +

+ +

How do I build a 68K version?

+ +

For now, you can't. The projects have not been kept up to date and +aren't even in the tree anymore. If you would like to create them and +get all the exports right with CFM-68K, go right ahead. We will be so +happy!

+ +

Why use IDE_Options.h when all that is in the project file?

+ +

It was originally intended to make sure that all 300 of us at +Netscape are using the same environment and compilation flags. If +something gets turned on/off by accident in the project prefs, it can +introduce a subtle bug that can take days to track down for naught. +Having a file that specifies exactly what flags should be used +guarantees that this can't happen.

+ +

Now that we move to net development, I'm sure you will agree that +this is even more important.

+ +

+ +
+ +New 5.0 Features

+ +

Navigator Center (Aurora)

+ +

The Navigation Center (referred to as "Aurora" in press releases) +is an attempt to make it easier to access and organize information on +the web. The NC unifies Bookmarks, History, Search, and local files +into a sequence of workspaces which are accessible from a single +location in the browser window. One of the ways the NavCenter +diverges from a similar concept seen from our competition is the +ability for users to create their own workspaces to organize and +store information from both the web and their desktop.

+ +
    +
  • Main access point is a bar along the left side of the + browser.
    • + +
  • Each icon represents a workspace. Click any workspace icon + once to slide out a hierarchical tree (like the list view in + the Finder) that displays the information appropriate to that + workspace. You can manipulate the URLs and folders in the tree + while you are surfing the web in the adjacent pane.
    • + +
  • Clicking on another workspace while the shelf is open switches + to showing the contents of that workspace.
    • + +
  • To hide the shelf, click the close box above the column + headers
    • + +
  • To create new bookmarks, drag bookmarks from the location + bar of the browser into the NC and file them where you want. + Of course, the old methods still work. + +
      +
    • If the NC shelf is not open, drag to the workspace where + you want to file the bookmark and after a small delay, the + shelf will spring open. You can now drop your new + bookmark exactly where you want.
      • + +
    • If the workspace you want is not displayed, drag over that + workspace and after a small delay, the contents of that + workspace will become visible.
      • +
    +
    • + +
  • You can also open a stand-alone NC window from the + Communicator menu. The standard "cmd-b" and "cmd-h" for bookmarks + and history are wired to open a new NC window with the appropriate + workspace visible.
    • + +
  • You can hide the list of workspaces at the left of the + browser window by choosing "View:Hide NavCenter Selector". You can + show it again by doing the same thing. Even when hidden in the + browser, the stand-alone versions are always available.
    • + +
  • Drag bookmarks to the trash to delete them. You can also hit + the "delete" key (backspace) to remove bookmarks.
    • + +
  • The NavCenter is fully context-menu savvy. There are + many commands that are in context menus that are not in the main + menubar (right now).
    • + +
  • ToolTip savvy. Both the title and URL can be seen in + their entirety by hovering over the appropriate column.
    • + +
  • 3-state sorting: alphabetical, reverse-alphabetical, + none. Like in the Finder, setting a sort does not change the + hierarchy or make any permanent modifications to your + organizational structure.
    • +
+ +

Personal Toolbar

+ +
    +
  • A toolbar to store bookmarks, first seen on Win/UNIX in 4.0. + Single click to load URL in current browser window
    • + +
  • Drag and drop bookmarks to the toolbar to add them. + Drag existing bookmarks on the toolbar to rearrange the order. + Drag bookmarks to the trash can to remove them from the + toolbar.
    • + +
  • Dynamically allocates horizontal space to buttons on + toolbar. Adding new buttons shrinks existing ones, removing + buttons distributes the vacated space to existing buttons. + Changing the window width reallocates space accordingly.
    • + +
  • You can further manipulate, rename, rearrange, add to and + remove the URLs in the folder that represents the personal toolbar + in the Navigation Center.
    • + +
  • ToolTips show the full title.
    • +
+ +

Navigator

+ +
    +
  • new "Mariner" technology makes table layout much faster and + does not reload the page when the window is resized.
    • + +
  • buttons/popup menus in the chrome now look more like MacOS + controls.
    • +
+ +

Composer Features

+ +
    +
  • Drag and Drop
    • + +
  • Direct manipulation editing of tables
    • +
+ +

+ +
+ +Unfinished "Features"

+ +

This source release is not of beta quality, hence it will have +lots of bugs that a normal beta (or even an alpha) would not have. +There are many features which we are not even close to being finished +with, let alone knowing what the final UI will be. Here are some +things that we know about but didn't have time to get to before the +code left the building. Feel inclined to help us out? +Grrrrrrreat!

+ +

Aurora

+ +

Aurora is definitely a work in progress. Here are the bugs that we +just don't have time to fix

+ +
    +
  • Real icons for files on disk
    • + +
  • changing view from XP code (e.g., JavaScript) has not been + tested, but should work
    • + +
  • move vs. copy notification (cursor doesn't change, etc. No XP + support for this yet)
    • + +
  • double-click on the text of an item should launch the url, not + trigger an in-place edit
    • + +
  • separator needs UI consensus and its own icon
    • + +
  • drag & drop + +
      +
    • can't disallow drags to trash when pane is read only. Trash + will still highlight even though nothing will happen.
      • + +
    • occasional -49 error when dragging repeatedly to browser + window. I think the DragManager is corrupt because -49 is not a + drag manager error and d&d doesn't work anywhere else after + that.
      • + +
    • drag feedback doesn't work correctly when view is sorted or + when some items are local vs. remote.
      • + +
    • Composer needs to correctly handle HT_Node flavor
      • + +
    • Sometimes things will move, other times they will copy. Its + an XP thing.
      • +
    +
    • + +
  • Chrome properties not correctly respected (relies on personal + toolbar being hidden to hide NavCenter)
    • + +
  • sort state of columns not saved (nor is anything else with + columns)
    • + +
  • we shouldn't be using HT_SetNodeName(). Use HT_SetNodeData() + instead
    • + +
  • Open/Close context menu does not redraw disclosure triangle + after executing
    • + +
  • There are currently no user configurable prefs for Aurora. + This will change.
    • + +
  • You can't edit the URL field because RDF uses this as the key + in its database. As a result, having two bookmarks in the same + workspace can lead to odd behavior
    • + +
  • Undo/redo does not work yet (XP problem)
    • + +
  • Cut deletes nodes, it does not put them on a clipboard. + Copy/paste do nothing. This is an XP problem.
    • +
+ +

Still major work to do:

+ +
    +
  • create new workspaces with d&d
    • + +
  • rollover feedback on selector
    • + +
  • sitemap notification
    • + +
  • scroll selector bar
    • + +
  • HTML pane/search pane
    • + +
  • spring-loaded folders on d&d
    • +
+ +

General FE Problems

+ +
    +
  • DNS lookups may hang up the machine for up to a minute. + Don't worry, your mac did not freeze!
    • + +
  • FTP doesn't work quite right. URLs typed into the location bar + will not load and the MIME mappings (save to disk, etc) are broken + so everything is loaded into the browser window instead of saving + to disk.
    • + +
  • frame around current tab group broken
    • + +
  • tabbing around to text entry areas and back to the Location + field is broken
    • + +
  • can't drag from Navigator when app is in background
    • + +
  • Folders on personal toolbar. Sigh, unless we can rewrite the + bookmarks menu code, we just don't have enough hierarchical menu + id's to put menus on personal toolbar folders. They still act as + drop sites, so you can drop urls into them but clicking on them + will just beep.
    • + +
  • Printing is....sub-optimal.
    • + +
  • "Mariner" layout improvements are nice, but on very + complicated pages the machine will hang for a few seconds while it + is relaying out the page. This can last 4-6 seconds sometimes. + This really looks bad when the NavCenter shelf is sliding out + during a drag and drop. If you are patient enough, you will be + rewarded, but it is slow.
    • +
+ +

+ +
+ +Pitfalls

+ +

There are a couple of pitfalls that we have to keep straight when +it comes to editing resources.

+ +

Why do I keep getting messages about unknown custom types in +Constructor?

+ +

For starters, make sure you have an alias to the following two +files in your Constructor folder:

+ +
    +
  • mozilla:cmd:macfe:rsrc:CrossProduct:Mozilla_Custom_CPPbs
    • + +
  • mozilla:cmd:macfe:rsrc:Communicator:MailNewsCppbs.cnst
    • +
+ +

You may have to explicitly open these files up while running +Constructor to be able to see the new types, especially for the ones +in MailNewsCppbs.cnst. Not sure why yet.

+ +

For editing other kinds of resources, we have a TMPL file for +ResEdit/Resourcerer. Place these in the appropriate location for your +resource editor

+ +
    +
  • mozilla:cmd:macfe:rsrc:CrossProduct:Mozilla_Custom_TMPLs
    • + +
  • mozilla:cmd:macfe:rsrc:CrossProduct:Other_Comm_TMPLS.rsrc
    • +
+ +

Why don't my toolbar buttons work anymore in the browser +window?

+ +

Because of the way we have the toolbars as CIncludeViews (which +work in a similar way to #include in C/C++), the RidL will be messed +up if you edit the main browser window PPob. Constructor regenerates +this list based on all the controls that are in the view when you +save, but because we use CIncludeView, the toolbar buttons aren't +actually in the view so the RidL is empty. They will still show up +when you build, but they won't do anything because they are not +registered with the browser window. Until we fix this, just use +Resourcer to replace the incorrectly generated one with an old +version. The old version is about 58 bytes long and the new one is +about 10 so you should be able to easily tell which is which.

+ +

Why are there so many damn resources?

+ +

As you may have noticed, we've got too many damn resources. Most +of them are 'STR ' resources which are generated at build time and +contain all of our cross-platfrom strings. We would like to generate +these resources more intelligently (into 1/10 the number of 'STR#' +resources maybe) but ran out of time before the source had to go out. +Before you rush out and change it for us, stop! There are some +constraints on the final solution, mostly to do with i18n and l10n +being able to leverage existing work on older product to do new +products. If you want to help us out with this, please send us some +email and we can have out i18n team talk with you to make sure it +gets done correctly!

+ +

Why doesn't it work better with Internet Config?

+ +

For starters, the main reason why we never drank the IC kool-aid +was that there was no support for multiple profiles. Being one of the +main features which our competition did not have, we thought this was +pretty important. There are rumblings in the IC world that IC 2.0 +will support multiple profiles. Great! That still leaves us with the +second reason: there are many, many, many preferences that we use +that are not reflected in IC. As a result, we already have to +maintain prefs for those that are not covered by IC so we can't be +totally IC dependent.

+ +

Of course, now that the source is free, maybe we can drive the +direction of IC to include all of our wacky networking prefs.

+ +

Where are all my old 4.0X bookmarks and prefs?

+ +

In the process of getting the source ready for distribution, we +removed all mentions of "Netscape" from the product. As you may know, +the 4.0X preferences are stored in a folder called "Netscape Users." +Well, that folder is now called "Navigator Users" and the preference +file is now called "Navigator Preferences" instead of "Netscape +Preferences."

+ +

It's probably best not to use any of your old prefs at this point +since some of them rely on security calls that are no longer in the +free source product. After you create a new profile (and you will +have to when you start the free source), copy your bookmarks.html +file from your old profile into the new user profile folder and +replace the empty one that's already there (if there is one).

+ +

For your old bookmarks to be seen, you must throw away the +"NavCntr" folder created in your new profile folder. After you do +that bookmarks will be imported into Aurora automagically. Note that +changes that you make to your bookmarks in 5.0 will not (as of today) +be written back to the Bookmarks.html file, but instead are stored in +a database within the "NavCntr" folder. If anything gets corrupted in +the NavCenter, you can always throw this folder into the trash and +your original bookmarks will be reimported.

+ +

Also note that these new bookmarks and preferences are totally +separate from your 4.0X prefs.

+ +

+ +
+ +History and Future

+ +

History

+ +

Excuse me while I ramble...

+ +
    +
  • Built using Metrowerks PowerPlant, the client has been PPC + native from day one. 68K support was dropped in 5.0 due to the + high cost of maintenance. Any takers?
    • + +
  • Mail/News was added in 2.0 and Composer was added in 3.0 + (called Navigator Gold). Both were dramatically improved with + 4.0.
    • + +
  • Java came to the Mac in 3.0, even though Windoze and unix had + it in 2.0.
    • + +
  • Multi-byte language support for inline edit fields added in + 4.0
    • + +
  • The preferences used to be STR# resources. Now they are done + in javascript.
    • + +
  • Because of the sheer number of resources (and the "theoretical + limit" on the number of resources in a file imposed by the + Resource manager -- which we still exceed on a daily basis), a + number of strings and icons were moved out of the main application + and into a file called "Netscape Resources" in 4.0
    • + +
  • For plain-text email/form composition, we used VText up + through 4.0. For 5.0, we switched to WASTE because of its minimal + impact on the PowerPlant hierarchy. VText caused us fits every + time we wanted to upgrade to a newer version of PowerPlant because + it wrapped its tentacles around every limb of PowerPlant.
    • + +
  • 4.0 included a new memory management scheme which drastically + reduced the amount of memory used by the client. This is why the + memory partition of 4.0 is about half of 3.0.
    • + +
  • A version of Navigator sans Mail/News/Composer debuted with + 4.03, and again two days later with 4.03.1.
    • +
+ +

Future

+ +

There is certainly a lot to do. In order to not duplicate too much +work (since we are still working on this full time here at Netscape), +I've put together a list of what we plan on doing and what we want to +do but probably won't get around to because of time constraints.

+ +

Things that we are going to focus on:

+ +
    +
  • More NavCenter work
    • + +
  • Solve the issues with too many 'STR ' resources (see note on + issues page)
    • + +
  • Modularization (HTML display isolated from networking, + etc)
    • + +
  • use new Appearance Manager classes in PowerPlant
    • + +
  • Navigation Services (new open/save dialogs in Allegro) + support. We have an ancient SDK and have integrated it in a few + places, but the current implemenation that we have doesn't work + very well. It's cool, though.
    • + +
  • More drag and drop in composer.
    • + +
  • More support for Internet Config (see note on issues + page).
    • + +
  • external Java VM support (MRJ, etc)
    • +
+ +

Things we would like some help on:

+ +
    +
  • printing support
    • + +
  • 68K version
    • + +
  • Context Menu Manager support
    • + +
  • bug fixes of any kind
    • + +
  • performance tuning of any kind
    • + +
  • getting around the limitation of 255 hierarchical menus + imposed by the OS. This would let us do a "real" personal toolbar + with folders that have popup menus.
    • + +
  • Fixing the build system so it uses makefiles without having to + give up the CW IDE for source browsing/editing.
    • + +
  • better publishing in Composer
    • + +
  • add NavCenter to Composer window
    • + +
  • better table editing in Composer
    • +
+ +
+ +
+ +Mike Pinkerton (pinkerton@netscape.com)
+ + + diff --git a/README/mozilla/unixbuild.htm b/README/mozilla/unixbuild.htm new file mode 100644 index 00000000000..6bd661ba9cd --- /dev/null +++ b/README/mozilla/unixbuild.htm @@ -0,0 +1,82 @@ + + +Unix Build Instructions + + + +

+Unix Build Instructions

+This document explains how to build Mozilla for Unix. +
+
+
Requirements:
+
+  Memory:
+    32MB of RAM, 128MB of swap, recommended 64MB of RAM.
+
+  Tools:
+    GNU C/C++ compiler 2.7.2 or better
+    GNU make 3.74 or better
+    Motif 1.2 (Lesstif has been used with limited success)
+
+  Tools that will be helpful later:
+    Perl 5.0
+    CVS 1.8.1
+    RCS
+    gdb 4.16
+
+  NOTE:
+    * gcc version 2.8 has been used successfully.
+      Your mileage may vary.
+
+Build:
+
+  Untar the tar.gz file with the following (or your favorite variant thereof):
+
+    gzip -dc tarball.tar.gz | tar -xvf -
+
+  Set the following environment variables:
+    csh/tcsh: 
+      setenv NO_SECURITY 1
+      setenv MOZ_MEDIUM 1
+      setenv MOZILLA_CLIENT 1
+      setenv NO_MDUPDATE 1
+
+    sh/bash/ksh:
+      NO_SECURITY=1
+      MOZ_MEDIUM=1
+      MOZILLA_CLIENT=1
+      NO_MDUPDATE=1
+      export NO_SECURITY MOZ_MEDIUM MOZILLA_CLIENT NO_MDUPDATE
+
+  Debug build is default; optimized build:
+      setenv BUILD_OPT 1
+      (BUILD_OPT=1; export BUILD_OPT)
+
+  On AIX, append /usr/lpp/xlC/bin to your PATH.
+  On Solaris, SINIX, and UnixWare, prepend /usr/ccs/bin to your PATH.
+
+  Build it.  Default target is "export libs install":
+    cd mozilla
+    gmake
+
+NOTE:
+
+If you haven't got perl:
+
+setenv PERL /bin/echo
+
+gmake -e
+
+Run the app:
+  Executable lives in mozilla/cmd/xfe/{ARCHITECTURE}.{DBG|OPT}.OBJ
+    (e.g. mozilla/cmd/xfe/Linux2.0.31_x86_DBG.OBJ/mozilla-export)
+  Statically-linked app is "mozilla-export"
+  dynamically-linked app is "moz-export"
+ +
+
Copyright © 1998 Netscape +Communications Corporation
+ + + diff --git a/README/mozilla/winbuild.htm b/README/mozilla/winbuild.htm new file mode 100644 index 00000000000..6ec6b7f85f1 --- /dev/null +++ b/README/mozilla/winbuild.htm @@ -0,0 +1,220 @@ + + + + + + + WinFE Build Instructions + + + +

+WinFE Build Instructions

+This document explains how to build Mozilla for the Windows platform. WinFE +is the Windows front end module.  +
Required Tools: +
    +
  • +Microsoft Visual C++ version 4.2 or later
    • + +
  • +GNU Tools for Windows:You can find these all over the web. Specifically, +you'll need:
    • + +
                    cp.exe
+
+                rm.exe
    + + +Netscape has internally modified version of gmake, shmsdos and win32gnu +that we use to get around some problems we were having keeping in sync +with the Unix version of gmake. This version of gmake and it's source is +included in the Mozilla source distribution. The specific files pertaining +to this are: +
                    gmake.exe
+
+                shmsdos.exe
+
+                uname.exe
    +These are located in the \tools\bin directory of the source package. All +of these tools need to be put in your path. +
  • +Additionally, there are Netscape-developed tools that need to be built +prior to your first compile. These are covered in the build section.
    • +
+Setting up: +
    +
  • +You need a Pentium with at least a 133 MHz processor and at least 250 megs +(NTFS partition) or 500 megs (FAT partition) of hard drive space. You need +to have a minimum of 64 megs of memory in order to build this tree. Having +at least 128 megs of memory will make your debugging experience noticeably +less agonizing
    • + +
  • +The preferred platform is NT 4.0. NT 3.51 will also work, and Win95 might +work if you're lucky. Maybe.
    • + +
  • +Install MSVC. If you don't choose to have the MSVC install modify your +environment variables for PATH, INCLUDE, and LIB information, be sure to +run VCVARS32.BAT out of the MSVC bin directory prior to attempting to build.
    • + +
  • +Download and install GNU tools. Put them in your path.
    • + +
  • +Install Mozilla source.
    • + +
  • +There are several environment variables you will need to set, either manually +or via a script within a command session, or by setting them in your system +environment located through the Control Panel | System icon. Those variables +are:
    • + +
      +
    • +set MOZ_BITS=32
      • + +
    • +set MOZ_DEBUG=1 (don't set this if you want to build an optimized release +build)
      • + +
    • +set MOZ_GOLD=1
      • + +
    • +set MOZ_MEDIUM=1
      • + +
    • +set MOZ_NT=351 (if running NT 3.51, don't set otherwise)
      • + +
    • +set MOZ_OUT=(location of resulting executable and totally optional, see +Notes for more details)
      • + +
    • +set MOZ_SRC=(top of your tree, drive letter and path, i.e. set MOZ_SRC=d:\mozilla_src. +The topmost directory under this should be mozilla)
      • + +
    • +set MOZ_TOOLS=(location of the bin directory containing your GNU tools. +The build looks for MOZ_TOOLS\bin\gmake.exe, so make sure your MOZ_TOOLS +is figured appropriately)
      • + +
    • +set NO_SECURITY=1
      • + +
    • +set NSPR20=1
      • + +
    • +if you are running VC++ 5.0 or higher: set _MSC_VER=1100
      • +
    +
+Building: +
    +
  • +You need to be running a vanilla command prompt. Other shells may work, +but you might have to tweak makefiles.
    • + +
  • +Build the tools: This generates several tools that handle things +like dependency generation
    • + +
      +
    • +cd mozilla\config
      • + +
    • +nmake /f makefile.win
      • +
    + +
  • +Build the whole lizard: This will do a complete build of the source +tree. You will end up with a mozilla.exe at the end.
    • + +
      +
    • +cd mozilla
      • + +
    • +nmake /f client.mak
      • +
    +
+  +
    +
  • +If you want to build communicator a piece at a time, these are the steps +that client.mak steps through. If you successfully ran the client.mak step +above, you don't need to do this.
    • + +
  • +Build the back end: This builds cross platform components like NSPR +and the shared library modules. All of the interesting output from this +part of the build will end up in mozilla\dist, under public\ if it's a library +header, and under WIN32_D.OBJ\ (or WIN32_O.OBJ\ for an optimized build) +if it's a dynamic or static library. The exception is the NSPR public headers, +which live in WIN32_D.OBJ\include.
    • + +
      +
    • +cd mozilla
      • + +
    • +nmake /f makefile.win
      • +
    + +
  • +Build the front end: This builds and links into the final executable, +mozilla.exe.
    • + +
      +
    • +cd mozilla\cmd\winfe\mkfiles32
      • + +
    • +nmake /f mozilla.mak DEPEND=1
      • + +
    • +nmake /f mozilla.mak
      • +
    +
+Notes: +
    +
  • +MOZ_OUT: If you don't set this, mozilla.exe will be generated into mozilla\cmd\winfe\mkfiles32\x86dbg +(or x86rel for optimized builds)
    • + +
  • +This build process does not use Visual C++ generated project files for +several reasons having to do with (among other things) size, maintainability, +and the long term desire to start using more of tools like gmake, or plug +and play developer tools. This does not preclude you from using the Visual +C++ IDE, or it's debugger (somebody fill this out with more detail).
    • + +
  • +All of the DLLs that you need to run mozilla.exe get copied automagically +into your output directory as the last part of build, so all you need to +do is cd into x86dbg and run mozilla.exe to get a runnable browser.
    • + +
  • +On a Pentium II 266 MHz machine with 128 megs of memory, it takes approximately +30 minutes to build. Your mileage may vary.
    • +
+ +
+
Copyright © 1998 Netscape +Communications Corporation
+  + + diff --git a/README/mozilla/wininstall.htm b/README/mozilla/wininstall.htm new file mode 100644 index 00000000000..ad0da276972 --- /dev/null +++ b/README/mozilla/wininstall.htm @@ -0,0 +1,53 @@ + + + + + + Running Mozilla... + + + +

+Running Mozilla Without Trashing Netscape +Installation

+This document explains how to run mozilla.exe separately from +netscape.exe without trashing your regular installation of Netscape +Communicator. This is necessary if, for example, you want to use Communicator's +mail client while you work on Mozilla development. +
+
+
    +
  1. +Before running mozilla.exe, create a new user profile either from +a Netscape 4.0x installation using the "User Profile Manager" shortcut +in the Utilities folder (on Windows) or by using  the -new_account +option on the command line of either netscape.exe or mozilla.exe.  +We suggest calling the profile "mozilla."
    2. + +
  2. +Always use that new account when running mozilla.exe, and never +run netscape.exe using that same account profile.
    3. +
+To make things easier, you can start the application with the user account +on the command line, for example: +
    mozilla.exe -P"mozilla"
+This assures that prefs and the cache will not interfere between the two +versions. This will be especially +
important as new prefs are added to the Mozilla product. Note that +you must use quotes around the name and there can be no space between the +"P" and the profile name. Otherwise, the application won't catch the profile +switch, and it will try to load the profile name as the initial URL. + +

+

+
You can copy your bookmark.htm file from an existing profile +to your new profile directory if you want to share bookmarks. + +

After the initial 3/31 release, we will add some code to Mozilla to +prevent running with a profile that is already being used by netscape.exe. +
  +

+
Copyright © 1998 Netscape +Communications Corporation + + diff --git a/README/nglayout/winbuild.html b/README/nglayout/winbuild.html new file mode 100644 index 00000000000..254d085ea21 --- /dev/null +++ b/README/nglayout/winbuild.html @@ -0,0 +1,184 @@ + + + + + + + NGLayout Windows Build Instructions + + + +

+NGLayout Windows Build Instructions

+This document explains how to build NGLayout for the Windows platform.  +
Required Tools: +
    +
  • +Microsoft Visual C++ version 4.2 or later
    • + +
  • +The same set of tools for building Mozilla
    • +
+Setting up: +
    +
  • +You need a Pentium with at least a 133 MHz processor and at least 250 megs +(NTFS partition) or 500 megs (FAT partition) of hard drive space. You need +to have a minimum of 64 megs of memory in order to build this tree. These +numbers are approximations.
    • + +
  • +The preferred platform is NT 4.0. NT 3.51 will also work, and Win95 might +work if you're lucky. Maybe.
    • + +
  • +Install MSVC. If you don't choose to have the MSVC install modify your +environment variables for PATH, INCLUDE, and LIB information, be sure to +run VCVARS32.BAT out of the MSVC bin directory prior to attempting to build.
    • + +
  • +Download and install GNU tools. Put them in your path.
    • + +
  • +Install NGLayout source.
    • + +
      +
    • +cd <your-source-area>
      • + +
    • +unzip -o -q win-19980415.zip
      • +
    + +
  • +There are several environment variables you will need to set, either manually +or via a script within a command session, or by setting them in your system +environment located through the Control Panel | System icon.
    • + + +

     Note: There is an additional variable for building NGLayout! +Use this list carefully! + +

     The variables are: +

      +
    • +set MOZ_BITS=32
      • + +
    • +set MOZ_DEBUG=1 (don't set this if you want to build an optimized release +build)
      • + +
    • +set MOZ_GOLD=1
      • + +
    • +set MOZ_MEDIUM=1
      • + +
    • +set MOZ_NT=351 (if running NT 3.51, don't set otherwise)
      • + +
    • +set MOZ_OUT=(location of resulting executable and totally optional, see +Notes for more details)
      • + +
    • +set MOZ_SRC=(top of your tree, drive letter and path, i.e. set MOZ_SRC=d:\mozilla_src. +The topmost directory under this should be mozilla)
      • + +
    • +set MOZ_TOOLS=(location of the bin directory containing your GNU tools. +The build looks for MOZ_TOOLS\bin\gmake.exe, so make sure your MOZ_TOOLS +is figured appropriately)
      • + +
    • +set NO_SECURITY=1
      • + +
    • +set NSPR20=1
      • + +
    • +if you are running VC++ 5.0 or higher: set _MSC_VER=1100; if you are running +VC++ 4.2 then set MOZ_VCVER=42
      • + +
    • +set STANDALONE_IMAGE_LIB=1
      • + +
    • +set MODULAR_NETLIB=1
      • +
    +
+Building: +
    +
  • +You need to be running a vanilla command prompt. Other shells may work, +but you might have to tweak makefiles.
    • + +
  • +Build the tools: This generates several tools that handle things +like dependency generation
    • + +
      +
    • +cd mozilla\config
      • + +
    • +nmake /f makefile.win
      • +
    + +
  • +Build the NGLayout: This will do a complete build of the source +tree. You will end up with a viewer.exe at the end. The viewer.exe will +be in your dist\win32_[OD].obj\bin directory (O will be used when you don't +set MOZ_DEBUG; D will be used when you set MOZ_DEBUG).
    • + +
      +
    • +cd mozilla
      • + +
    • +nmake /f nglayout.mak
      • +
    +
+Running: +
    +
  • +Once you have built the system, do this to run the viewer program (the +viewer program is a simple test program that uses the nsIWebWidget API +to embed a web widget object). The viewer program has a few basic menu +items, include "Samples" which load sample tests.
    • + +
      +
    • +cd mozilla\dist\win32_[OD].obj\bin
      • + +
    • +.\viewer.exe
      • +
    +
+Notes: +
    +
  • +This build process does not use Visual C++ generated project files for +several reasons having to do with (among other things) size, maintainability, +and the long term desire to start using more of tools like gmake, or plug +and play developer tools. This does not preclude you from using the Visual +C++ IDE, or it's debugger. Once you have built a viewer.exe do this to +run it under the debugger:
    • +
+ +
    +
      +
    • +cd mozilla\dist\win32_[OD].obj\bin
      • + +
    • +msdev viewer.exe
      • +
    +
+ +
+
Copyright © 1998 Netscape +Communications Corporation
+  + + diff --git a/mozilla/lib/libaddr/MANIFEST b/mozilla/lib/libaddr/MANIFEST new file mode 100644 index 00000000000..29033347d69 --- /dev/null +++ b/mozilla/lib/libaddr/MANIFEST @@ -0,0 +1,2 @@ + +# empty