Integrate with Quicktags / TinyMCE to remove autotrigger on highlighting

Benjamin Melançon - December 4, 2007 - 13:50
Project:Universal Link Filter
Version:5.x-1.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:closed
Description

While many people may prefer the instant access of the pop-up, others (myself included) would prefer the search for content to start only if specifically triggered, as by highlighting and pressing a button.

I think it would make most sense to integrate this with the modules that already add buttons on top of textfields, such as Quicktags and TinyMCE or FCKeditor.

(Aside: I wonder if buttons for textfields ought to be a core API that all such modules can use.)

#1

garthee - December 9, 2007 - 03:19

Yeup I agree with you, there should be a core API to control the buttons on top of textfields. I am not using TinyMCE or FCK.. therefore I don't see any problem in having uLink control bar there. But for other it will be posing some difficulties.

I will look into integrating the UI with Quicktags, if possible

Then about triggering the search, yes, it is already available. There are two searches and a caching method associated with AJAX calls and all three can be individually turned ON / OFF with the control bar available on top of the text field. I initially had iSearch ON by default which will be triggered by highlighting or double clicking a word / phrase and now I made it turned OFF by default, because I see, that user will need it only once he completed the document. Hence no annoyance while he is typing is welcomed.

Thanks for your interest in uLink

Please try with the final version that will be released today

#2

Benjamin Melançon - December 27, 2007 - 11:50

I missed the above response and asked again, but I've moved to a new HTML-helper editor that should be even easier to integrate with, possibly not requiring changes to Ulink, though it would be nice for Ulink to acomodate textfield editors automatically...

I asked...

providing the option to integrate with a project like http://drupal.org/project/bueditor ? To make the search activated by a click, rather than automatically on highlighting?

garthee 10:10
i think i answered that..

11:08
even now user has that option

11:20
he can disable it by ticking off the text box

12:54
adminstrator can totally turn off (ie disable it) or user can optionally disable..

13:46
but by default it is enabled in both situations.. but with the latest update i disabled isearch (ie automatically searching when u highlight the word) in usermode.. so user has to tick the text box to enable it

13:51
and regarding BUEditor.. it is not a standard ne.. so not good to make our application dependent on another module..and forcing users to enable that as well

14:14
so waiting till drupal put a ribbon tool bar on textareas in their API

benjamin melançon 10:14
no, but make it possible for your module to act differently. and BUedditor is awesome. Just switching to it from quicktags, it's very nice

garthee 10:15
yes i checked that module

16:19
few concerns, they allow only buttons (i m not sure . in fact i couldn't ) about adding other types.. like text boxes or select..

benjamin melançon 10:18
as for only allowing buttons, I think Ulink would work more nicely as buttons ("search for highlighted") rather than checkboxes-- that's how I would like to use it, and how most people who have tinymce, fck, bueditor, etc probably expect things to work

garthee 10:19
mm i will check that... but about integrating with BUEditor is a concern.. maybe i have to check with the Author of BUeditor

benjamin melançon 10:21
what makes bueditor neat is that you can easily add new buttons -- %TEXT%

21:36
or: js: eDefPreview();

garthee 10:22
mm but functionality is different ne.. there the buttons insert a tag.. but for me it should let me know whether to run my jQuery or not

benjamin melançon 10:22
so it could be a jQuery, the "js: " prefix seems to allow this magic

#3

garthee - July 10, 2008 - 10:08
Status:active» closed

due to the structural issues, it won't happen

 
 

Drupal is a registered trademark of Dries Buytaert.