The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Javascript VBulletin Editor Toolbar Controls Framework
Intro Writting VBulletin addons, especially those, related to BBCodes extending, I always had difficulties with adding BBCode buttons to editor toolbar. Standard way is too limited: you cannot select which editor to add buttons to, you cannot choose to what line to add these buttons, you cannot create a new toolbar for them? Adding buttons to AJAX-produced editor windows causes troubles? You are TOO limited? Thinking about the solution I tried to do that via plugins and didn?t come to any acceptable solution. I always care about my code beauty so I am strongly against modifying VBulletin PHP code (because that makes updating VBulletin complicated for user. Each new update vanishes your code hacks). The solution I suggest is DHTML way. I have written a small frawework to control editor toolbar. Let me first consider it from the surface (developer article will come in the future, but framework's source code is all commented and (I beleive) easily understandable). Offtopic: you know, with all the power jQuery gives to you why to bother modifying your code via template hooks or via actual template modification if you can do that in one line of code with jQuery by DHTML? It's a question... Using EditorToolbarFramework Framework consists of:
Code:
//Injecting scripts $GLOBALS['headinclude'].=' <script src="clientscript/fractalizer/jquery.js"></script> <script src="clientscript/fractalizer/editorbtnframework/core.js"></script> <script src="clientscript/fractalizer/editorbtnframework/core.js"></script> <script src="clientscript/fractalizer/editorbtnframework/button.js"></script> <script src="clientscript/fractalizer/editorbtnframework/separator.js"></script> <script src="clientscript/fractalizer/editorbtnframework/panel.js"></script> <script src="clientscript/fractalizer/test.js"></script> '; Code:
myBtn = new FRVBEditorCommandButton("TestBTN", "FRControlsPanel_0_LeftEdge", "images/editor/attach.gif", function(){alert("TEST!!!")}); myBtn.tooltip = "MyButton!"; mySep = new FRVBEditorSeparator("TestSep", "TestBTN"); myPanel = new FRVBEditorPanel("TestPanel", "FRControlsPanel_0"); FRVBEM.registerControl(myBtn); FRVBEM.registerControl(mySep); FRVBEM.registerControl(myPanel);
At the first line we create FRVBEditorCommandButton object which is just a clickable toolbar button. We call it ?TestBTN?. We set it up to be relative to predefined ?FRControlsPanel_0_LeftEdge? button. This is autocreated hidden button, that is located at the left of the first (0-index) editor panel. Bu default position is set to ?after?, so our button will be located just after this invisible button, e.g. at the left side of the panel. We also provide an image for this button and onclick handler for button, that just shows us a simple message. At the next line we set up button tooltip and left all other things by default. After that we create a separator between buttons. It also has a name and location set. It will be located just after our just created button. With the next line we create a new toolbar panel for buttons. We call it ?TestPanel? and set it up to be located just after the first standard VBulletin toolbar. On single line editors panel will be added, on double-lined will be inserted after the first standard panel. And at last we just register all objects we created in FRVBEM object to be displayed in every editor including AJAX-produced. That?s all. As soon as document DOM will be ready, FractalizeR?s VBulletin Editor Manager will start working for you integrating buttons into all editors in realtime. Some more details? Locations to choose from While we create controls we have to choose their position. We have the following choice:
Please note, that if control we are positioning our one relative to does not exist, our button will not appear and you will have a warning visible in FireBug console. Editor types to locate buttons in Going back to our previous example, we can position our button in:
We can make any combinations of these three. Control orientation We may want to locate our button Code:
myBtn.controlOrientation = FRVBEM.controlOrientations.after - after related control. This is the default orientation button gets after it is created. No need to set it up manually myBtn.controlOrientation = FRVBEM.controlOrientations.before - or before it By default buttons are shown in any script. But, for example, you can restrict them to only certain scripts, so that extended buttons would not appear in blogs or any other add-on. Just set
By default this restriction is - myBtn.byScriptRestriction = []; - turned off. Processing order If we position our new button relative to another button we created, in order to all work correctly, that migt be necessary to setup processing order. The independent button must have lowest processing order possible, the dependent one should get highest. Order values should start from 0. -1 is reserved as a default value for all newly created buttons, -2 for all newly created panels (so that that would be created before all buttons).
CommandButton onClick handler Each command button have it?s associated onClick handler. From this handler you can access methods of vB_Editor object, that will help you manipulate the text in this editor. Code:
myBtn = new FRVBEditorCommandButton("TestBTN", "FRControlsPanel_0_LeftEdge", "images/editor/attach.gif", function() { event.data.editor.write_editor_contents("We replaced that text with this one!", false); }); Let?s look at the most common methods of this object (class?):
VBulletin code, even JS code is pretty straightforward. So, just open vbulletin_textedit.js and find there all you want! That?s all folks! Pretty easy, isn?t it? P.S. I am not sure I will continue to work on this project because of VBulletin 4 release announced with heavily changed API. But I strongly believe this project will be interesting to most of VBulletin developers at least as a compex Javascript programming for VBulletin. You are free to take this and to modify this and redistribute this in any way, but, please make me credited in all derived works and works, that use my library. Thank you. This article is also published at my site here: http://www.fractalizer.ru/frpost_3/v...ols-framework/ In the attachment you will also find sample VBulletin product to create new panels at the editor. Please note, that a panel will not be shown until you add some controls to it (what is actually you need to do manually). |
#2
|
||||
|
||||
This article is probably in a wrong section. It relates to programming, not to general VBUlletin use
|
#3
|
||||
|
||||
Thanks I`ll take a peek at it after class is over.
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|