Re: whats next

Okay here is what's needed: ----- HEAD ------- o Link to the skin .js file o Link to the skin .css file (these two with defaults to plain.js and plain.css) ----- BODY -------- o BODY event onload="skin()" o All further content of the BODY within a <DIV id="pageContent" style="display:none;"> You can just put in here all the HTML for the the pages which don't have constant subsections (non function reference pages). We will have to handle using only css here. o <DIV id="pageTitle"> containing the title string for the page o <DIV id="userNotes"> containing each individual user note inside its own <DIV> (without ID). If possible, with each note element (contributor, date, email, text) grouped with SPANs (ie. <SPAN>contributor</SPAN> &lt;<SPAN>email@blah.com</SPAN>&gt; <BR><SPAN>note text blah blah</SPAN>) Note that Im trying to leave out as many HTML code as possible o <DIV id="navigation"> all the navigation HTML code. If possible just point out the individual elements like location, next and previous, this page online with their corresponding links code. (ie. <SPAN id="navNext"><A href="tonextpage.html">next page</A></SPAN>) Function reference pages: o <DIV id="headers"> enclosing all of the following: - purpose - availability - usage * If possible enclosing each separate item in a <SPAN> tag with the same id (ie. <SPAN id="purpose">purpose text </SPAN>) o <DIV id="summary"> grouping the summary HTML o <DIV id="description"> grouping the description HTML o <DIV id="examples"> grouping each individual example in its own <DIV> (without IDs) if possible, if not then all the HTML code for examples in here. If it's not possible to group examples separately then merge the code with description above ? o <DIV id="seeAlso"> see also HTML code here. If not possible to separate then merge again with description. * Notes: Just see it as if you were assigning php variables with each <DIV id="..."> or <SPAN id="..."> As the data is more separated from the HTML code, the skin designers will have more elements to play with. Maybe we could develop an XML system in the future, to completely separate the data from the HTML, don't you think ? Okay I hope this all makes sense -- Gnz ----- Original Message ----- From: "Gabor Hojtsy" <goba@php.net> To: "Gonzalo De la Peña Andreu" <gnz@corelian.com> Cc: "PHP chm list" <php-doc-chm@lists.php.net> Sent: Saturday, 02 March 2002 09:12 Subject: Re: whats next > > Yea I had previously dlded and tested the files. > > > > To be honest I don't think I need to make any speed measurement script or > > something, to me all files open pretty fast. I don't think I would be > > annoyed at all consulting the chm file. I think I wouldnt even notice > > there's been DHTML activity to draw the page. That's only my oppinion. > > > > Maybe there could be a difference on a really low end machine (ie. > Explorer > > 4 on a 100 mhz pentium or something like that), but then I don't think > that > > kind of users would be interested in using a fancy skin. > > > > I say we chose the skining method that we feel is less complicated and > will > > contribute make the chm smaller. What do you think ? > > OK, so let's implement the innerHTML methods, as noone replyed > to our conversation. We will define the standards :) > > Can you please send a list in reply to this mail with the > tags I need to add IDs (and what IDs), and other needed > modifications to make the pages capable of this design > method. > > Please also consider the grouping problems I expressed > before... This may mean a different id structure for > examples, or I don't know exactly what... > > Goba > > >