Ajax and WYSIWYG editors
Posted by clifton on 19 Jun 2007 in Tasks
On the philosophy website I attempted to add course section description editing to the course section file uploading page. After doing so I noticed that I began losing track of the shared variables within that page so I decided to split the pages in two.
I was able to set up the uploading page fairly easily but I fell into some errors with the description editing when I attempted to add AJAX to that page. I was initially using a WYSIWYG text editor by the name of htmlarea and I discovered that its JavaScript files conflict with the AJAX Prototype.js framework.
I then found another WYSIWYG text editor (by the name of fckeditor) and I was able to implement this editor on the editing page.
What remains for the Philosophy website is add a new emeritus page, add ajax to the section description editing page, adding the text editor and lastly providing user documentation. I plan to continue work on these remaining tasks.
Also there have been some issues with moving agenda over to the lang account from the lang02 account so today I will be taking some time to look at the files in the lang02 account to look for any hardcoded variables that may be causing the issues.
I was able to set up the uploading page fairly easily but I fell into some errors with the description editing when I attempted to add AJAX to that page. I was initially using a WYSIWYG text editor by the name of htmlarea and I discovered that its JavaScript files conflict with the AJAX Prototype.js framework.
I then found another WYSIWYG text editor (by the name of fckeditor) and I was able to implement this editor on the editing page.
What remains for the Philosophy website is add a new emeritus page, add ajax to the section description editing page, adding the text editor and lastly providing user documentation. I plan to continue work on these remaining tasks.
Also there have been some issues with moving agenda over to the lang account from the lang02 account so today I will be taking some time to look at the files in the lang02 account to look for any hardcoded variables that may be causing the issues.
