[Record Set #1] Description = -=[DOM Tooltips]=- + By default adds tooltips to anchor and acronym tags that have the title attribute set. Can be told to scan for other elements with title attribute set. + + -=[Explanation]=- + "Head" will be added to all pages, since no criteria has been set. + + -=[Usage]=- + To have DOM-Tooltips re-scan for title attributes of certain elements, call it with: + + tooltip.init(new Array('element 1', 'element 2', ...)); + + ...like so: + + tooltip.init(new Array('blockquote', 'span', 'input', 'img')); + + To change tooltip appearance, edit the dom-tooltips.css file. + + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = Userlevel = Active = true Content = Reference = Location = Head = + Foot = [Record Set #2] Description = -=[Textarea Resizer]=- + Incorporates a handle at the base of every textarea. By clicking and dragging the handle, the textarea can be resized vertically. Control buttons are also added to the top right corner of every textarea. This allows easier access to minimise, restore, best-fit, maximise functions. + + -=[Explanation]=- + This addon is added by just including the code in the "Head" section. "Head" will be added to every page, since no criteria is set. + + -=[Usage]=- + This addon makes use of an embedded funtion to retrieve the blog URL. By enclosing bloginfo('url') with %%, you are able to call bloginfo('url') via KCA. In this case bloginfo('url') will supply the blog url part of the path to the addon files. + + Since tinyMCE uses "true" in the title attribute to identify it's textareas, I also adopted this for Textarea Resizer (In effect this will ignore tinyMCE's textarea - tinyMCE hides it and uses a div for it's operations anyway). So, as a caveat, if you want Textarea Resizer to ignore any textarea, put "true" in the title attribute. + + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = Userlevel = Active = true Content = Reference = Location = Head = + Foot = [Record Set #3] Description = -=[Quicktag Button (Method 1)]=- + Demo showing how to add button to Quicktag panel. + + -=[Explanation]=- + "Content" will only be added when the URL contains "post.php", or "page-new.php" and an element with id="ed_toolbar" is found. + + Whatever is in "Content" will be added at "Reference". "Location" specifies where in relation to "Reference" the "Content" is added. In this case "Content" will be added just "beforeEnd" of "ed_toolbar" element, Ie. "method 1" button is added to the "ed_toolbar" list after all other items. + + -=[Usage]=- + This demo makes use of embedded php functions. In this example, the date() function is called to retrieve the date (inside %% %% tags), then printed by kca (with = prefixing the function name). + + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = post.php, page-new.php Userlevel = Active = true Content = Reference = ed_toolbar Location = beforeEnd Head = Foot = [Record Set #4] Description = -=[Quicktag Button (Method 2)]=- + Demo showing how to add button to Quicktag panel. + + -=[Explanation]=- + "Head" will only be added when the URL contains "post.php" or "page-new.php". + + "Head" contains CSS and Javascript for the "method 2" button. The code is initiated with "schedule" (an enhanced onload function). + + -=[Usage]=- + Makes use of embedded php functions. In this example, the date() function is called to retrieve the date (inside %% %% tags), then printed by kca (with = prefixing the function name). + + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = post.php, page-new.php Userlevel = Active = true Content = Reference = Location = Head = Foot = [Record Set #5] Description = -=["source" button in Quicktags panel]=- + Adds an article "source" button to the Quicktags bar. + + -=[Explanation]=- + "Head" will only be added when the URL contains "post.php" or "page-new.php". + + "Head" contains CSS and Javascript for the "source" button. The code is initiated with "schedule" (an enhanced onload function). + + -=[Usage]=- + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = post.php, page-new.php Userlevel = Active = true Content = Reference = Location = Head = Foot = [Record Set #6] Description = -=[tinyMCE Buttons]=- + Demo showing how to add some buttons to the tinyMCE editor panel (for WP 2.0). Not the prettiest method - but it works. + + -=[Explanation]=- + This addon is just a demo, showing what can be done. There are easier ways to do this I'm sure. + + "Head" will only be added when the URL contains "post.php" or "page-new.php". + + "Head" contains CSS and Javascript for the tinyMCE buttons. The code is initiated with "schedule" (an enhanced onload function). + + -=[Usage]=- + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = post.php, page-new.php Userlevel = Active = true Content = Reference = Location = Head = Foot = [Record Set #7] Description = -=[Admin Panel Clock]=- + Displays a live clock on the admin main menu. + + -=[Explanation]=- + "Content" and "Head" will only be added when the URL contains "wp-admin" and an element with id="adminmenu" is found. + + Whatever is in "Content" will be added at "Reference". "Location" specifies where in relation to "Reference" the "Content" is added. In this case "Content" will be added just "afterBegin" of "adminmenu" element, Ie. the list item is added to the "adminmenu" list before all other menu items. The reason it is on the right hand side of the menu is because it is floated right. + + "Head" contains CSS and Javascript for the clock. The code is initiated with "schedule" (an enhanced onload function). + + -=[Usage]=- + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = wp-admin Userlevel = Active = true Content =
  • %%=date('H:i:s')%%
  • Reference = adminmenu Location = afterBegin Head = + + Foot = [Record Set #8] Description = -=[Clock1]=- + Cut and pasted from bodytag.org with some minor mods. This addon will show a unique digital clock on the front page. + + -=[Explanation]=- + "Head" and "Foot" will only be added when "is_home()" evaluates to "true". + + "Head" contains CSS and Javascript for "clock1". The code is initiated with "schedule" (an enhanced onload function). + + "Foot" contains content that is added to the footer. + + -=[Usage]=- + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = is_home() Needle = Userlevel = Active = false Content = Reference = Location = Head = + Foot =
    +
    +
    +
    +
    +
    +
    +
    +
    +
    +
    [Record Set #9] Description = -=[Nav-Bar Clock]=- + Displays a live clock on the nav-bar. + + -=[Explanation]=- + "Content" and "Head" will only be added when the URL contains "page=kca.php" and an element with id="kca-nav" is found. + + Whatever is in "Content" will be added at "Reference". "Location" specifies where in relation to "Reference" the "Content" is added. In this case "Content" will be added just "afterBegin" of "kca-nav" element, Ie. the clock is added to the "kca-nav" bar before all other items. The reason it is on the right hand side of the menu is because it is floated right. + + "Head" contains CSS and Javascript for the clock. The code is initiated with "schedule" (an enhanced onload function). + + -=[Usage]=- + (De)Activate by (un)ticking "Active" tickbox, followed by "Update". Eval = Needle = page=kca.php Userlevel = Active = false Content =
  • [%%=date('H:i:s')%%]
  • Reference = kca-nav Location = afterBegin Head = + + Foot =