From 9d4331bd1c82769679d5bd640599d7afdd9c9734 Mon Sep 17 00:00:00 2001
From: "http://kerravonsen.dreamwidth.org/"
 <http://kerravonsen.dreamwidth.org/@web>
Date: Sun, 3 Apr 2011 22:01:17 -0400
Subject: more flexible, perhaps?

---
 doc/todo/CSS_classes_for_links.mdwn | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

(limited to 'doc/todo')

diff --git a/doc/todo/CSS_classes_for_links.mdwn b/doc/todo/CSS_classes_for_links.mdwn
index 8abe49827..af1093f75 100644
--- a/doc/todo/CSS_classes_for_links.mdwn
+++ b/doc/todo/CSS_classes_for_links.mdwn
@@ -117,3 +117,22 @@ I find CSS3 support still spotty...  Here are some notes on how to do this in Ik
 >>>> applied. One would need to write tests running against the code
 >>>> with all plugins enabled, all templates put to work, in order to
 >>>> ensure consistency is maintained. --[[intrigeri]]
+
+-----
+If you're going to be patching htmmllink anyway, might I suggest something more flexible, like being able to configure the link format?
+(Yes, PmWiki allows this, that's where I got the idea)
+That is, rather than having "<a href=". blah . blah ...
+one could use a sprintf with a default format which could be configured in the setup file.
+
+For example:
+
+    $format = ($config{createlink_format}
+               ? $config{createlink_format}
+               : '<span class=\"createlink\"><a href="%s" rel="nofollow">?</a>%s</span>');
+    return sprintf($format,
+        cgiurl(do => "create", page => lc($link), from => $lpage),
+        $linktext);
+
+I admit, I've been wanting something like this for a long time, because I dislike the existing createlink format...
+
+--[[KathrynAndersen]]
-- 
cgit v1.2.3