New Link Options Ideas
Option |
Values |
Comment |
onMouseOver |
javascript code |
Put javascript actions on events |
onMouseOut |
javascript code |
onClick |
javascript code |
onDoubleClick |
javascript code |
onGetFocus |
javascript code |
onLostFocus |
javascript code |
raw |
on or debug |
put an TWiki url parameter to see the raw mode of a topic (like the skin option) |
param |
extra url parameter list |
put more free parameters on a url link like param:pram1=valA&pram2=valB |
Discussions
Hi! The
LinkOptionsPlugin is now relised.
--
AurelioAHeckert - 29 Mar 2005
That is
NICE!
I've always wanted the ability to the kind of popups we have in the edit mode for the help facilities there, those small windows without menu stuff, but maping that javascript to a general topic was just too much effort.
Thank you so much.
Now to integrate it into the application space....
--
AntonAylward - 30 Mar 2005
Thank you, thank you, thank you!
How about measuring and documenting the
PluginBenchmarks?
--
PeterThoeny - 30 Mar 2005
I change the description to:
* Set SHORTDESCRIPTION = Extended external link syntax ==[<nop>[URL or <nop>TopicName][Link Text][Options]]==
This makes it short and descriptive. You can take that into the next release if you wish.
--
PeterThoeny - 30 Mar 2005
Thank You!
The Benchmark is done!
I Will put more options like
onMouseOver
to javascript lovers like me.
More ideas, put hire:
New Link Options Ideas
--
AurelioAHeckert - 30 Mar 2005
Why wouldn't you call
onDblClick
onDoubleClick? Or you would have to rename onClick to nClck
Seriously, it makes it harder to remember.
--
ArthurClemens - 31 Mar 2005
Was not me...
Ok! You are right. Done.
Put more Ideas! What we need and is hard to do?
--
AurelioAHeckert - 31 Mar 2005
This is a great plug-in, but your use of the pipe symbol in the options syntax (for example: [NewWin:600x400|Skin:plain]) causes a formatting problem with the
EditTablePlugin. If you add a modified link in an edit table cell, the pipe gets treated like a table cell delimiter and the settings that follow the pipe wind up in the adjacent cell.
Would it be possible to change the pipe to a safer character?
Thanks,
--
SteveRosenthal - 21 Jun 2005
Well... Ok.
What is better?
# ! /
I'm thinking in put
/
to be the optional separator.
--
AurelioAHeckert - 23 Jun 2005
What about
;
? This would be much more consistent to CSS notation, wouldn't it? Maybe even the
{}
could be used instead of the additional pair of
[]
. This would conclude to the following notation:
[[URL or (InterWiki:)TopicName][Link Text]]{<Options;>Option}
This would be a sensible enhancement of the existing link mechanism and fully backwards compatible,
--
FranzJosefSilli - 23 Jun 2005
checked
.zip
into
CVS
--
WillNorris - 19 Jul 2005
This plugin didn't work for Twiki 4.01. In
TWiki:Plugins/TWiki I found a migrated version for Dakar Beta 5. Some tests show that it works fine. Is this ok?
--
RudiRose - 13 Mar 2006
Aurelio: Please consider upgrading this Plugin so that it runs on Cairo
and Dakar codebase.
HandlingCairoDakarPluginDifferences has more.
--
PeterThoeny - 13 Mar 2006
It would be good if the 'link options' plugins (
ExternalLinkPlugin,
ExitPlugin and
LinkOptionsPlugin) could be integrated.
--
ArthurClemens - 24 Mar 2006
This is a cool plugin. I just installed in TWiki3 and was wondering if it was TWiki4 complient?
--
EricHanson - 23 Jun 2006
I had to make the following change to the currently available ZIP file to make
LinkOptionsPlugin work on TWiki 4.0.4, without which TWiki crashed when
LinkOptionsPlugin was enabled:
--- LinkOptionsPlugin.pm.orig 2006-07-27 11:34:19.865711611 -0300
+++ LinkOptionsPlugin.pm 2006-07-27 11:33:00.723973495 -0300
@@ -52,7 +52,7 @@
# =========================
use vars qw(
$web $topic $user $installWeb $VERSION $pluginName
- $debug $exampleCfgVar
+ $debug
);
$VERSION = '0.10';
@@ -74,9 +74,6 @@
# Get plugin debug flag
$debug = TWiki::Func::getPreferencesFlag( "\U$pluginName\E_DEBUG" );
- # Get plugin preferences, the variable defined by: * Set EXAMPLE = ...
- $exampleCfgVar = &TWiki::Prefs::getPreferencesValue( "EMPTYPLUGIN_EXAMPLE" ) || "default";
-
# Plugin correctly initialized
TWiki::Func::writeDebug( "- TWiki::Plugins::${pluginName}::initPlugin( $web.$topic ) is OK" ) if $debug;
return 1;
That example code for getting preferences values is sooo old ...
--
AntonioTerceiro - 27 Jul 2006
Synced this plugin from SVN, adding Antonios innocent patch.
Aurelio, the
ModificationPolicy of this plugin is currently set to
ContactAuthorFirst. Do you have a comment on Arthurs suggestion or would you allow the policy to be shifted to
PleaseFeelFreeToModify in the interest of combining the plugins?
--
SteffenPoulsen - 27 Jul 2006
Steffen, I talked to Aurelio personally today and he agreed to shift the modification policy to
PleaseFeelFreeToModify. I edited the plugin topic and changed this myself.
In fact I should release a fixed version myself, but hadn't the time to do this today. Thank you for doing that.
--
AntonioTerceiro - 28 Jul 2006