ckeditor package in bitweaver

A bitweaver package is built around a fairly simple framework which allows new ones to be added quite easily. The file 'bit_setup_inc.php' identifies the package to the handler and includes any setup bits for using it. In the case of ckeditor, this is where the ckeditor.js is added to those that will be loaded as part of a page. This has been modified to prevent it being loaded until a user log's in, but still needs a little work to only load it on pages that actually need it. Another area that needs tidying to modernise things is to move loading these files until after the content, but a few bits of javacode are used in building the content so this can be fun.

On pages that use ckeditor the loader also needs to be triggered, and bitweaver has a second file that allows material to be added to the end of the generated page via the via the footer_inc.tpl file, which is a smarty template that can be tailored as required. As with the setup file, this should only be outputing the required code on a page that actually needs this and that is a work ing progress. I know we had a flag for it, but I';ve not found it yet.

On the current setup, the ckeditor config.js file controls additional configuration changes, but my own build is a self contained package so this is blank. This is an area I need to play with further, and I think I'm slowly working out how to play with this. At some point it should be possible to make changes to the ckeditor configuration via the bitweaver admin console. That can currently select between 4 tool bar layouts which are configured in the footer_inc.tpl file but adding extra options should be possible going forward.

Using CK5 is on hold at the moment until I can work out how to configure the inline build to include the 'source' button without having to pay for the premium licence.