Re: PHPDOC changes/modifications browser compatibility

From: Date: Fri, 15 Mar 2002 02:25:05 +0000
Subject: Re: PHPDOC changes/modifications browser compatibility
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-4981@lists.php.net to get a copy of this message
> >Hi Tim, > > > > I think that the changes need some work. Specifically, there are some > >problems with the CSS code. This is a shot of how > >http://www.smur.net/knife/doc/ renders in Konqueror 2.9.9 > >and Mozilla > >0.9.8. > > I have not had the time to test my css in Konqueror... > I'm pretty surprised that it didn't like my div tags though. > > It might be the "em" units I'm using for layout... > Seems like a pretty minor thing to get fixed. I ran your CSS through the w3c validator and fixed a few errors. You can find a slightly revised version here: http://ozma.union.utexas.edu/~busterb/phpdoc.css One of the most surprising issues to me (I hadn't looked at CSS much before) was that CSS does not allow underscores in class names. See here: http://developer.netscape.com/evangelism/docs/technotes/css-underscores/ The class references in the templates will need to be changed to the non-underscored versions, if you want to keep to the spec that is. Also, you were right; every browser seems to have a different notion of what an 'em' is. I set the em units so that they were at least usable on all the browsers I had handy. Check out this screenshot of IE 6, Mozilla and Konqueror, all displaying the same page: http://ozma.union.utexas.edu/~busterb/snapshot2.png > I'm pretty sure that my changes haven't broken the command line version of > phpdoc, but if someone wants to test it and let me know that would be > appreciated. I haven't tested this yet, but hope to soon. > I did notice the command line version of PHPDoc, but I didn't like the > command line version. I like to use a build script to generate all of the documentation for a project, running PHPDoc, jade or whatever else is needed without my intervention. Make is a great tool for generating documentation for large projects, since it can determine if a package needs its documentation regenerated or not. > I never did change index.php for every different project, I wrote the > front-end before I started using it. :) > also, > and this isn't in the file on smur, although I will post a new one right now > http://www.smur.net/code/phpdoc312.zip I'm glad to hear it! I had trouble reviewing the files because they appear to have had all of the linefeed/carriage returns removed. Definitely hard to read ;) I also could not find the HTML templates. Is there a newer version? Thanks, and keep up the good work. - Brent

« previous php.pear.dev (#4981) next »