xfolk-jacobian: Difference between revisions
No edit summary |
m (Reverted edit of Qr8Akx, changed back to last version by Tantek) |
||
(7 intermediate revisions by 5 users not shown) | |||
Line 2: | Line 2: | ||
<p>[http://jacobian.org/recipes/ Jacobian] writes on recipes. These may be cooking recipes, software recipes, recipes for disaster, any kind of recipe. His link blog is sparse appearing to just consist of URLs and titles. However, an investigation of the source reveals that the description of the link is contained in the title attribute of the <a> tag.</p> | <p>[http://jacobian.org/recipes/ Jacobian] writes on recipes. These may be cooking recipes, software recipes, recipes for disaster, any kind of recipe. His link blog is sparse appearing to just consist of URLs and titles. However, an investigation of the source reveals that the description of the link is contained in the title attribute of the <a> tag.</p> | ||
<p>This structure is challenging for xFolk because it uses the title attribute in a completely different way. Consulting recommended and current uses of the title attribute, xFolk's use of the title attribute seems to conform more to the standard approach than Jacobian's. The simple solution is to just switch the title and element values, making the <a> element of both classes taggedlink and description. In this case, the value of the title attribute serves as the link's title and the value of the element serves as the description.</p> | <p>This structure is challenging for xFolk because it uses the title attribute in a completely different way. Consulting recommended and current uses of the title attribute, xFolk's use of the title attribute seems to conform more to the standard approach than Jacobian's. The simple solution is to just switch the title and element values, making the containing <a> element of both classes taggedlink and description. In this case, the value of the <a> element's title attribute serves as the link's title and the value of the <a> element itself serves as the description.</p> | ||
<p>Here is the markup before conversion to xFolk Entry 0.4 with items to be changed bolded.</p> | <p>Here is the markup before conversion to xFolk Entry 0.4 with items to be changed bolded.</p> | ||
Line 8: | Line 8: | ||
<pre><ul id='delicious'> | <pre><ul id='delicious'> | ||
<li> | <li> | ||
<a class= | <a class="delLink" title="Cricket is a | ||
high performance, extremely flexible system for monitoring trends | high performance, extremely flexible system for monitoring trends | ||
in time-series data. Cricket was expressly developed to help | in time-series data. Cricket was expressly developed to help | ||
network managers visualize and understand the traffic on their | network managers visualize and understand the traffic on their | ||
networks, but it can be used all kinds of other | networks, but it can be used all kinds of other job" | ||
href= | href="http://cricket.sourceforge.net/"> | ||
<strong>Cricket</strong> | <strong>Cricket</strong> | ||
</a> | </a> | ||
Line 22: | Line 22: | ||
<pre><ul id='delicious'> | <pre><ul id='delicious'> | ||
<li class= | <li class="xfolkentry"> <!-- changed --> | ||
<a class= | <a class="taggedlink description" title="Cricket" | ||
href= | href="http://cricket.sourceforge.net/"> <!-- changed --> | ||
Cricket is a high performance, extremely flexible system for | Cricket is a high performance, extremely flexible system for | ||
monitoring trends in time-series data. Cricket was expressly | monitoring trends in time-series data. Cricket was expressly |
Latest revision as of 20:58, 19 June 2007
Jacobian
Jacobian writes on recipes. These may be cooking recipes, software recipes, recipes for disaster, any kind of recipe. His link blog is sparse appearing to just consist of URLs and titles. However, an investigation of the source reveals that the description of the link is contained in the title attribute of the <a> tag.
This structure is challenging for xFolk because it uses the title attribute in a completely different way. Consulting recommended and current uses of the title attribute, xFolk's use of the title attribute seems to conform more to the standard approach than Jacobian's. The simple solution is to just switch the title and element values, making the containing <a> element of both classes taggedlink and description. In this case, the value of the <a> element's title attribute serves as the link's title and the value of the <a> element itself serves as the description.
Here is the markup before conversion to xFolk Entry 0.4 with items to be changed bolded.
<ul id='delicious'> <li> <a class="delLink" title="Cricket is a high performance, extremely flexible system for monitoring trends in time-series data. Cricket was expressly developed to help network managers visualize and understand the traffic on their networks, but it can be used all kinds of other job" href="http://cricket.sourceforge.net/"> <strong>Cricket</strong> </a> </li> </ul>
Here is the xFolk conformant version with the element and title attribute values switched.
<ul id='delicious'> <li class="xfolkentry"> <!-- changed --> <a class="taggedlink description" title="Cricket" href="http://cricket.sourceforge.net/"> <!-- changed --> Cricket is a high performance, extremely flexible system for monitoring trends in time-series data. Cricket was expressly developed to help network managers visualize and understand the traffic on their networks, but it can be used all kinds of other jobs. </a> </li> </ul>