On 4/16/07, Davi Leal <address@hidden> wrote: > If nobody send feedback about the new alerts feature, I am going to have
> several days without too much work. >
> I thought if you send to the list more <div>s, as with menu.tpl, etc., I > could add the needed {t} tags, indentation, etc., so you could have all > the table markup removed in your development environment. Therefore, you
> will be able to work on the needed CSS to get the same or better look&feel > that the one currently at production. What do you think?. > > Just a comment about text browsers: > * 'w3m' _is_ able to renders table layouts, but I think not <div>s one.
> * 'lynx' is _not_ even render table layouts. > > I think the <div>s layout is the way to go. I have read the links > you has posted, and <div>s seem to be good too for mobile devices.
Here's a new version of the Hackers` guide. Some notes:
Valid, semantic, (mostly) accessible XHTML 1.1.
Substantially reduced size.
You don't need an <a> element to use anchor links (href="" They also work with element IDs, so you can use just <a href="" and <h3 id="something">.
There was a lot of empty space, but I guess that's in order to have nicer looking code.
Somebody should add @titles where not defined already.
Markup comments which are not for users (such as "XXX Update this image") should probably be code comments or Savannah tasks instead.
Chapter count numbers can be arranged with CSS (Doesn't work in IE, but who's gonna notice that on a developer page?).
Removed "Back to top" links - From what I see around the web, these are not much used. Also makes for less text.
Whitespace in <pre> is significant.
Tried to make some of the text more terse. It should have the same information content, but should be reviewed.
Moved the PostgreSQL configuration section below the general configuration instructions. Maybe all configuration instructions should be in the same section?
Made shorter IDs.
Added <abbr> with no @title for repetitions of already defined abbreviations, like at gnu.org.
It would be great if someone has a better link to a howto for ssh-agent.
Removed the "web site" section, since it only points to the web site.
Removed shell output in favor of just the input from the user. That way, most of the configuration shell instructions can just be copied verbatim and executed.
I took the liberty of removing the source code section
It`s already explained in the introduction.
There`s a warning that the package is probably outdated.
The flags bit should probably be part of the coding standard (if necessary). By the way, are all todo items marked literally "XXX"?
Maybe we should split the page into several? I'd suggest the following structure:
Introduction
Installation and configuration
Help / other
Whaddya think so far?
-- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound
hackers.xhtml