Quick Reply BBCode Buttons (UBBC)

[JJ]

I just use the 'vanilla' version, Chris, and I am very happy to have it. Thanks.

[aRMY83]

I must say Chris that since it's creation and a few bug fixes, I have had nothing but success with this plugin.

[Baller95]

Thanks for the amazing plugin Chris!

[Chris]

Unless I am misunderstanding what you're asking then that question would best be posed in the personal smileys thread jrryan. If you want a plugin to act differently then that plugin must first want to change.

"Change", the Buddha said, "must come from within."

[Todge]

Eton's plugin could indeed add a button (I think), but it wouldn't function. That would need to be done via the Personal Smileys plugin. One plugin cannot control another unless they are specifically written to do so.

[Former Member]

It seems when I use control freak the Quick Reply BBCode Buttons plug in no longer works. Am i doing something wrong?

Thanks!

[Chris]

Dec 15, 2013 9:26:02 GMT -8 @greedsins said:

It seems when I use control freak the Quick Reply BBCode Buttons plug in no longer works. Am i doing something wrong?

Thanks!

ControlFreak is a more advanced version of the quick reply plugin that can also target other areas (not just quick reply). If you're using ControlFreak then you wouldn't need the quick reply plugin since you can add buttons to quick reply using ControlFreak.
By default ControlFreak comes with a premade group on the GROUP CONTROLS tab in order to provide an example of how to create your own control group so the simplest way to add quick reply buttons is to delete that example group then you'll be able to use the QUICK CONTROLS tab which has almost the same interface from the quick reply bbcode plugin (check/uncheck buttons).

If feeling adventurous, you could instead create a group on the GROUP CONTROLS tab and add the buttons you want there then apply it to quick reply by check-marking that option in the target field of th created group. This gives greater over the button sequence as well as the ability to have buttons appear only when in certain specified boards or only if the user belongs to a certain group. If it helps think of it this way, you can see the admin menu when logged in as staff on your forum but someone logged in as a regular member would not see it, same concept here, you have greater control over where, when, how and to whom buttons appear.

[Former Member]

Chris, if I wanted to add two buttons that involved other plugins, would they not work? I was going to add a basic skeleton code/post for @tbserialkiller's Presto and Tabbed Sections in Posts plugin

[Chris]

Dec 18, 2013 17:37:27 GMT -8 ₪» ⅀ ƪ Ƒ «₪ said:

Chris, if I wanted to add two buttons that involved other plugins, would they not work? I was going to add a basic skeleton code/post for @tbserialkiller's Presto and Tabbed Sections in Posts plugin

One Plugin to rule them all, One Plugin to find them,
One Plugin to button them all and in the veefive bind them

Unfortunately the above in not true, plugins possess free will and cannot be easily coerced into actions they were not designed to perform without some powerful voodoo magic. This plugin can indeed create buttons but cannot then force another plugin to do its bidding, change needs to come from within...

I'm familiar only in passing with both the Wormopolis plugins you mention and have absolutely no idea whether they create some sort of custom BBCode which can then be processed at display time. If they do then the next hurdle is do these BCCodes use the traditional tag with space separated attributes/value pairs (e.g. [img src="/pong.png" alt="pong" ])/ I know that in the past colon delimited attributes have been the hallmark of Wormopolis' BBCode representations which would not be compatible with the HTML-like structure V5 and its WYSIWYG subsystem now employs for its BBCodes. That would also mean this plugin which employs that same subsystem would also be incompatible.

If my guess is incorrect and the BBCode is indeed conventional then you definitely can create a button that generates the desired BBCode and optionally prompt for (or  silently adds) any desired attribute/value pairs.

[Wormopolis]

I just dont know how I could even make a working tabbed table function in the visual editor. considering it uses runtime event binding.

presto uses jquery for binding, so MAYBE it would work.. but from what I gather the entire cell gets its HTML rewritten with every keystroke.. so any binding not forced into the tag itself on write would get stripped...

[Chris]

Not on each keystroke but each time there is a need to convert from HTML to BBCode or vice versa. If you examine the source of the word count plugin you'll see that it intercepts the conversion process and pre-converts legacy atrb tags depending on which direction we're going. Just think of it as a page change after each tab switch/conversion and don't worry about your bindings, each switch is an opportunity to rebuild from scratch.

I could try to distill it down to some commented code snippets on my next day off (that plugin is long overdue for an update anyway) if it would help.

[Wormopolis]

how does it close the regular html tags in the visual editor though if its not doing it on keystroke?

[Chris]

Dec 18, 2013 21:05:31 GMT -8 Wormopolis said:

how does it close the regular html tags in the visual editor though if its not doing it on keystroke?

I'm not quite sure what you're referring to but I would suppose same principle as when you insert malformed innerHTML into an element, the browser parses it and performs markup corrections to try and make it correctly formed HTML (although not necessarily to the author's intent).
An AJAX request is only sent to Proboards on tab switches if the tab content is new and no previously cached response for that content already exists, the conversion is then done on the server and sent back.

[Former Member]

You guys are like two aliens speaking utter gibberish so I'm afraid I really can't relate to what's going on and offer any advice. x.x' If it helps at all, the buttons need only work in the BBCode side, I have no problem if they don't work in Preview. If that is of no help, then ignore me, I shall sit in the corner and listen to alien garble. =)

[Chris]

Wormopolis here's the snippet I promised

/* Hook into WYSIWYG tab switches in order to prep/convert custom bbcodes */

var oldSetContent, oldGetContent;
...

if(!oldSetContent){ //if we haven't saved reference to original then hook does not exist yet
	oldSetContent = editor.setContent; //save original setContent
	editor.setContent = function(){
		//call original setContent then do what we need
		//(could also do what we need before the call, all depends on what you need to do)
		oldSetContent.apply(this,arguments); 
		parseEnhancedTags(editor.bindable, logger.parse);
		$(editor.bindable).trigger('keyup.wordcount');
		
	}
}

I'm pretty sure you know how to obtain access to the [WYSIWYG Object] since I've seen you use it before to utilize those same setContent and getContent methods. The editor variable is a reference to a specific editor in the [WYSIWYG Object].editors (currently bbcode and visual) and I use a jQuery $.each loop to cycle through each (variable set on each iteration) since any plugin could theoretically add their own custom editor in there or maybe even Proboards in the future.
I also do a similar hook on the getContent method but just for the visual editor in order to convert any markup on the preview tab that was added by me back into their BBCode equivalent

I should also note that it would be prudent to use try/catch when hooking these critical Proboards methods since an unintended error in your code could mean the user is unable to use the editors. In the example I use try/catch in the parseEnhancedTags function which is why it is not seen in the snippet