WysiWyg Plugin

So I’ve made a first pass at a WYSIWYG plugin using widgEditor. For some reason it doesn’t work on the simple post screen, just the advanced one. It’s in the repository if anyone has any suggestions. Todo: prettier/smaller buttons, strip/add paragraph tags, activate for more than just the main content area.

26 thoughts on “WysiWyg Plugin

  1. I just installed it, and I generally like what I see, but not only does the WYSIWYG not work in the Simple post area (what I use, usually, just because), it removes the existing tag-insertion buttons that were there.

    Deactivated, but not deleted, until there’s a workaround for the Simple post page or there’s a plugin update.

  2. I installed the plugin. When I went back to edit a post I had made with the plugin, it erased whatever content was there when the post loaded into the textarea.

  3. Will, yes the workaround is to switch to the advanced interface as the default.

    Chris, if all the kinks are worked out, possibly.

    Jeremy, that’s pretty scary sounding. Did you “go back” with the back button, or did you edit the post again, was there content on the site?

  4. Testing it out on my testblog and wow is it nice. I think it needs a few more features though but that’s the actual editor. I won’t push this on my real blog yet though.

  5. The only reason I said more features is like the check spelling from Blogger, remove formatting from selection, Blockquote, and aligning. I may be asking for too much but it does remove a lot of quicktags which were useful.

  6. Why not go for the full htmlarea? I installed on my domain and although I never use it, I think it helps people with a Word background. Let’s face it, that’s where most WP users come from…

  7. Matt, you rock. Keep up with the improvements, this looks really promising. Was this in response to any reflections based on Dave Winer’s recent writings?

  8. Matt, as I noted on the wp-hackers list, the lists this script produces aren’t always valid XHTML. Try creating three lines of text. Select them all and click the list button. Then select the middle item and press TAB to put it to the next lower level… then look at the HTML produced. In fact, it seems that every time you go back and change the level of an item, this happens. The only way it doesn’t happen is if you use TAB to indent before you move on to the next item.

  9. Actually on second though the one Toby S showed isn’t bad. It allows for much customization and flexibility. It’s not slow and it has the ability to change to a basic toolbar if the user finds the advanced one confusing. It also has multi-lingual support and even skkins so it can fit the WordPress interface. Maybe you can try it.

  10. Nice. Might be a useful addition to WordPress: Touched that… something to think about for a 1.0 release I guess 🙂

    I’m yet to be won over by these type of tools tho. I think the quick tags work jsut as well – until I can use ctrl+b for bold.. etc then I really don’t see the difference from this and the quicktags – in fact the quick tags are more powerful because I can edit the markup. In this one its removing that option.

  11. matt, a wysiwyg plugin is a good idea. but this one is just as slow, bloated, buggy and crippled as the other ones i tried…

    i wish someone would set up some kind of web-service api to plug Front Page or Dreamweaver into…

    or maybe a XUL interface for wordpress would be appropriate. at least you’d be sure there are no bugs in it — only firefox users could use it.

  12. Well.. that doesn’t mean there’d be no bugs 😉

    Its not perfect, but its better than most of the type.

    I missed the code view option. That raises it up a notch. Its… promising. I’m going to add it to the next (or maybe next but one) release of my plugin.

  13. It’s okay, as such things go, but I would prefer it not become the default post-editor for WordPress. I like to have more control over my code than that.

    Of course, I suppose it could always be made another option: WYSIWYG / Simple / Advanced.

  14. Works great! only one problem… doesn’t seem to work for pages, just for posts. Is there a way to specify that it be used for the input field within the pages editor?

Comments are closed.