I dont think this is true, I mean you comment while you code so other developers know what are you coding about specially on things like CSS where you can't gess where that class or ID is used. So you want to referr which area of the site you are styling about.
Same as the html, specially if it's XHTML and you want to separate content from style. Here is an example of an intent to document the CSS file and result in a huge file which will take hours to document, simply because the source CSS wasn't documented (let alone JSP and JS). Check the document here: http://www.openoffice.org/nonav/issues/showattachment.cgi/23157/OpenOffice_Website.odt On Mon, 07 Mar 2005 20:43:08 +0100, :murb: [maarten brouwers] <[EMAIL PROTECTED]> wrote: > Alexandro Colorado wrote: > >> Whatever you decided what I really wish is that you comment the code, >> whenever >> is the CSS code or the HTML/JS. Is really hard getting to document >> tigris >> because most of the css is code generated so the CSS tree grow >> exponentially. >> > This will probably be documented, I think kay had already made plans for > this ;)? Currently too much is still changing to keep documentation up > to date... when close to final documentating stuff should really > happen... this was one of the reasons it took us at sc40 so long to get > over to actually implementing designs. > > g., > > > Maarten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Alexandro Colorado Coordinador de eXpoLinux http://www.expolinux.org Tel: 993 355 0060 Cel: 993 376 0011 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
