id	summary	reporter	owner	description	type	status	priority	component	severity	resolution	keywords	cc	release
8586	Keep CKEditor out of egg; suggestion of different approach	Franz	itamarost	The idea of having a full wysiwyg editor was also a must in our company. And furthermore the ability of spell checking, which CKEditor provide, was a must have.\r\n\r\nIn my environment, the plugin didn't work - the CKEditor wasn't shown.\r\n\r\nI had a different approach and wanted to share it with you. Since I haven't committed anything yet to trac or tac-hacks and I am quite new to python, I would like to share it through a Zip-File. In the attached Zip-File I have different small things programmed, but the HtmlContent is kind of a different implementation of the CKEditorPlugin. I would suggest to keep CKEditor itself out of the plugin-egg, since you would like to change the version (because of bugfixes or similiar) or the CKEditor configuration. Therefore a link to the Editor should be parametrizable (as in my attached Component is already).\r\n\r\nThe bad thing of the attached plugin is, that you need to change the file `ticket_box.html` (see documentation inside HtmlContent). I tried to copy it to [trac-environment]/templates, but I couldn't get it to work (see commented code above HtmlContent).\r\n\r\nIf you like, have a look at my code and feel free to make comments.\r\nI would be glad, if you could revise the code or have some ideas to make it smoother.	enhancement	closed	normal	CkEditorPlugin	normal	fixed			0.12