Wordpress WYSIWYG editor

It is on our development roadmap and we will be adding it to fields where it makes sense later this year.

We had held off on adding it in the past due to the fact we wanted to leverage core functionality and TinyMCE functionality in WordPress prior to v3.3 made it difficult to do. WordPress v3.3 introduced the editor API which makes it easier to use.

We have actually already begun implementing editor API functionality within Gravity Forms. We just haven't added it to the fields for front end use just yet.

We implemented the editor API on the Notification admin so that it can be used when creating your email notifications. This was a first step towards broader use of the editor API within Gravity Forms.

We didn't rush to implement using the editor API all over Gravity Forms as soon as WordPress v3.3 was introduced because it's a brand new WordPress API and we have to be very careful with introducing new features in Gravity Forms because of how large our user base is. If the editor API turned out to have issues, then that would negatively impact our users.

We have to be very careful with how we introduce features in Gravity Forms. We no longer have the luxury of being able to quickly drop in new features at a moments notice because of the large number of users that now rely on Gravity Forms. We have to be more deliberate with how we introduce new functionality so that it doesn't introduce major issues for our user base.

It's different when developing a free application where ultimately users aren't paying anything so you can rush to introduce features and functionality and if it blows up... oh well, just rinse and repeat. Gravity Forms is a commercial product and that development methodology, while fun and fast paced, wouldn't be acceptable to users who are paying for our product.

This is why we have held off rolling out the feature more broadly. The Notifications were the first step, seeing if there were any issues in the editor API within WordPress itself after WordPress v3.3 had been on the market for sometime was the second step and the next step is going to be implementing the editor API as an option in fields where it would be useful.

So we will be adding it as an option on the Post Body field in a release later this year.

As for farming it out to a developer to develop as an Add-On? There is nothing stopping any developer from doing so. If someone wants to create a 3rd party add-on for Gravity Forms... they can do so. The hooks and filters are there to do so and developers are more than welcome to develop Gravity Forms Add-Ons. There are plenty of 3rd party add-ons for Gravity Forms on wordpress.org already.