This mail is an automated notification from the task tracker
of the project: Savane.
/**************************************************************************/
[task #304] Latest Modifications:
Changes by:
Mathieu Roy <[EMAIL PROTECTED]>
'Date:
sam 26.06.2004 à 13:51 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Done
Status | Open | Closed
/**************************************************************************/
[task #304] Full Item Snapshot:
URL: <http://gna.org/task/?func=detailitem&item_id=304>
Project: Savane
Submitted by: Mathieu Roy
On: ven 26.03.2004 à 19:56
Should Start On: ven 26.03.2004 à 00:00
Should be Finished on: lun 26.07.2004 à 00:00
Category: Web Frontend
Priority: 1 - Later
Resolution: Done
Assigned to: yeupou
Percent Complete: 0%
Status: Closed
Effort: 0.00
Planned Release: 1.0.3 ?
Summary: anchors with h3, h4, h5
Original Submission: I think titles should provide anchors, to give easily
pointer, or just to easily navigates, like at http://gna.org/about
It would be a pain to handle that by hand each time. I think a simple
html_part($level, $title); should do the job, where level is between 1 to 5
(that will be translated in h1, h2... h5) and the title the content (that will
be simplified to be an anchor). To avoid i18n issue, maybe a third argument
should exist.
part Numbering would be great to easy (and trivial to do), but we cannot count
on it for the anchors, since users can have more or less parts depending on
their rights.
Commentaires :
------------------
-------------------------------------------------------
Date: ven 26.03.2004 à 20:16 By: Mathieu Roy <yeupou>
Side effect: when someone fill a dependancy or anything that is a form in two
steps that go back to the same place, the anchor should definitely be used!
For detailed info, follow this link:
<http://gna.org/task/?func=detailitem&item_id=304>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
