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 |
Jump to:
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
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
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...
#3
due to the structural issues, it won't happen