Loved WYSIWYG BBCode editor

Superscript and subscript now tested OK. Horizontal Rule next. This will be a bit harder.

Well, horizontal rule is now done. It took hours. The problem was that it is an empty tag. My sandbox demo sort of works with the hr tag.

The sandbox has an editor box, and the hr works there OK, and the hidden textarea with BBCode in also gets it when you insert, but I have a textarea you can see the underlying bbcode, and that waits for you to move the cursor before it updates to show the newly inserted hr.

On to the next tag. I think I will do the smilies next.

This is awesome - thank you, VERY much, for your efforts!

Just thought I would update y'all.

The smiley plugin is quite a bit of work. I should have it finished tomorrow, then I will look to integrate the Kunena css files, and then start on another (one of the few left) function. The list to do gets smaller.

Thank you for the effort you are putting into this

Really looking forward to testing it.

The bit I am working on right now is the smilies. Let me explain.

CKEditor comes with a smiley plugin. It uses its own smiley images that are in a sub-folder of the smiley plugin folder. So, first problem is to persuade the plugin to use the smilies in the Kunena media folder. Not so hard.

The plugin assumes bbcode symmetry to an image (only one BBcode tag per image). The problem is that Kunena has multiple BBCodes per smiley. This means re-coding the CKEditor plugin to handle multiple codes per image mapping (each smilie bbcode needs to be put through RegExp to escape code any symbol that is reserved.

Finally, the CKEditor plugin requires the user to edit the javascript if you want to change the default smilies. I need to get the plugin to use the settings set by the admin in the Kunena Icons back end administration page.

I had to stop yesterday as my head was spinning. A good night's sleep and a plan of action laid out in my head. Now I am coding it.

Crikey, this is hard.

Getting the plugin to use the Kunena smilies was simply setting a config path variable in the calling html document.

After many hours (way too many), I have now managed to program asymmetric bbcode to smiley lookup (the 2nd bit on the smiley 'to do' list). The finished version will need to call these lists from the #_kunena_smileys table in the Joomla database, but for now I have hand coded them.

Anyway, as much as I can do has now been done. The final version will need some work in the Kunena back end so that, when the user alters the smiley settings, the Kunena php code re-writes the javascript bbcode and smiley plugins. Shouldn't be hard to write. Later for that. The actual coding of smilies for Kunena is done.

I am going to take a look at incorporating the Kunena css code now.

You're working very hard on this one! Thanks from us all.
Really looking forward to being able to add images easily.

This has been the major issue... from my clients.
Thanks again for all your efforts

Whilst it has indeed been both hard and time consuming, I am over the top and on the way down, as it were.

I am going to try what I have got on my live site tonight and tomorrow. I shan't post it here as yet, as there is much I want to do:

1. Get the css and images file path variables working on a live site.
2. Get the quote, quote with citation, spoiler, hide and confidential tags working (they are pretty much done, but the css needs to be fully functional before I can test for sure).

Then show you the test page for comments.

Then ...

1. Manually install and test it as a joomla plugin and then make an installer for it.
2. Make and manually install a Kunena plugin
3. Then integrate it properly with Kunena (means a few hacks to the Kunena files).

Still a way to go.

OMG the css has been driving me bonkers. So, here I am testing a forum page with the new editor in. I use Firefox Object Inspect and can see that the editable area is indeed an iframe with another page in it. It has the correct css files loading. So, I edit the css and refresh the whole page. No change. I hit Ctrl+F5 to force the cache for the page to purge and re-load the css files from new. No change. Because the css file is in an iframe, the Ctrl+F5 does not purge the cache of the iframe's css files!!

Using the Firefox Web Developer toolbar, I switch off caching. NOW it works. Spent hours on that little beauty. You live and learn.