WYSIWYG editor

hakjoon · 2005-11-08 23:26:58

I’d be willing to try it since I’m going to be working on maybe implementing tinyMCE at work. I haven’t really studied micampe’s code too closely, so no promises but I’ll take a stab at it.

Update

I got tinyMCE 2.0RC4 working last night. So far it seems to be ok. I had to fix some DOM calls to turn textile on and off properly since the interface for that has changed. There is a loading issue with Firefox but it’s a tinyMCE problem (it does it on moxiecode’s site also), It doesn’t seem to keep it from working , and hopefully will be fixed by 2.0.

I have to check on the tabs causing content to be lost, but hopefully I can have a preview release out for early bug hunt this week.

Last edited by hakjoon (2005-11-09 13:44:30)

tinyfly · 2005-11-10 23:18:07

I’ve made my own modifications that seem to work fine for my purposes.

First set “Use Textile” to “Leave text untouched” in the site preferences. (this is important!!)
Then replace the corresponding code in the plugin with the following code

What this does is that:

if you write a new article you get the tinyMCE editor and textile is enabled for the excerpts.
if you edit an existing article that has been created using tinyMCE everything works the same as number 1 above.
if you edit an existing article that has already been created using textile, the tinyMCE editor is disabled and textile works as expected.

Note: I commented out “Toggle Editor” link because I plan on only using tinyMCE to create new articles and have no need to toggle it off.

Last edited by tinyfly (2005-11-10 23:23:08)

tinyfly · 2005-11-17 16:15:32

hakjoon, I am still interested in your update to this plugin. Any more progress on it?

hakjoon · 2005-11-17 16:35:27

Sorry I got caught up with the texbook upgrades and never finished it up.

I originally was thinking of just doing an updated version using tinyMCE 2.0RC4 but I think I’ll hold off until 2.0 is actually out. RC4 has some weird glitches with firefox. Plus integrating iBrowser was going to take a little longer since the syntax has all changed from when micampe did it.

In the meantime I was going to try and integrate the changes I made into micampe’s plugin. This should fix the textile on and off issues that arose with the 4.0.2 update. I need to figure out a way to make the tabs behave but I have an idea. The problem is that the textile setting does not get sent back to the text tab from the other tabs, so the way I modified it the editor gets turned off when you go back which I don’t like.

How much do people actually like the iBrowser image browser? Is it worth trying to update it?

tinyfly · 2005-11-17 16:41:12

I haven’t looked into it that much but if the iBrowser could be made to work with txp’s image upload I would love it. If not though, I don’t really have any use for it.

ramblingwebgirl · 2005-11-19 14:18:23

A few of you mentioned how the image option for this plugin rocks which makes me jealous because I can’t get it to work in v4.0.1 or .2. I’ve tried in both Firefox & IE and I get nothin’ except a blank white screen.

I downloaded this plugin a little while because I know my clients will love it. Everything is working well, except the previous mentioned feature. When I click on the insert/edit image button a pop-window opens and says it’s loading the page, but nothing comes up. :( This app looks very promising so I’m hoping it’s an easy fix that someone can show me how to do (keeping in mind that code isn’t my thing :)

Thanks!

hakjoon · 2005-11-22 14:17:17

I finnally got the image browser working again. I want to try to see if I can get the tabs to stop turning off the editor and then I’ll release an updated version. If I can’t figure it out it’s getting released anyway :) This will update the editor to 2.0RC4 and will work in 4.0.2.

It will not work on 4.0.1 though because the DOM for the write tab just changed too much between the 2 versions. If there is enough interest I could see about making it backwards compatible, although I would really rather work on an FCKeditor version instead and on a more integrated image browser.

tinyfly · 2005-11-22 14:20:42

I don’t really see a need for a backwards compatible version. I would like to see the FCKeditor and integrated image browser option though. What do you see as the advantages of FCKeditor compared to tinyMCE?

hakjoon · 2005-11-22 14:49:17

I more want to do FCKEditor for my own education because we are going to be deciding between the two at work in the future. I like certain things in FCK better and certain things in TinyMCE better so I wanted to go through the montions of integrating them both and see which one gave me more headaches.

One thing I’m curious about is if FCKEditor would allow for <txp: /> tags since it has a much laxer policy on what tags you can insert. I know tinyMCE doesn’t like tags with colons in it.

Plus it has an integrated file/image browser which was looking pretty attractive when I was fighting with ibrowser.

Last edited by hakjoon (2005-11-23 15:50:17)

mrdale · 2005-11-23 04:05:30

Hey Hackjoon,

I’m giddy about your plans to do FCK for txp. Go, Dog, Go!

Gives me a reason to resubscribe to this topic.

Last edited by mrdale (2005-11-23 04:09:56)

hakjoon · 2005-12-01 01:37:48

This took longer then expected but I just released hak_tinymce. I started a new thread so it would a little easier to manage support issues.

Now onto FCKEditor.

Textpattern CMS

Textpattern CMS support forum

#61 2005-11-08 23:26:58

Re: WYSIWYG editor

#62 2005-11-10 23:18:07

Re: WYSIWYG editor

#63 2005-11-17 16:15:32

Re: WYSIWYG editor

#64 2005-11-17 16:35:27

Re: WYSIWYG editor

#65 2005-11-17 16:41:12

Re: WYSIWYG editor

#66 2005-11-19 14:18:23

Re: WYSIWYG editor

#67 2005-11-22 14:17:17

Re: WYSIWYG editor

#68 2005-11-22 14:20:42

Re: WYSIWYG editor

#69 2005-11-22 14:49:17

Re: WYSIWYG editor

#70 2005-11-23 04:05:30

Re: WYSIWYG editor

#71 2005-12-01 01:37:48

Re: WYSIWYG editor

Board footer