Support for FormBuilder or Webform Alternate UI

Neither form_builder or webform_alt_ui are currently supported by this module. I have been kind of waiting for those projects to stabilize and gain some adoption before going forward with integration. It would be nice if the alt_ui would just be integrated into webform core and form_builder be made a dependency so that I don't have to attempt to support 3 different UI variants. I assume that is what will happen with webform v4, but I haven't heard any projections about when it might be released. With the release of webform.com, that possibility seems more real.

Update: I've added a patch for compatibility with the options_element module, and listed the other two (webform_alt_ui and form_builder_webform) as incompatible on this module's front page.
Actually integrating with them still seems a way's off - neither supports all of webform's features yet.

fyi - been several more commits to form builder since this request. may be worth a quick look as drag/dtop UI is well suited for civicrm community.... cross post: #1984768: Consider supporting Webform CiviCRM

Webform Alternate UI appears to be abandoned, so that's one less thing to worry about. Integration efforts can focus solely on form_builder.

What will happen if I disable the "Form builder Webform UI" ... as suggested below??
What happens if I don't disable the module??

The module Form builder Webform UI is not compatible with Webform CiviCRM Integration. Please disable it before continuing.

If you disable "Form builder Webform UI" then the back-end webform tab will look different (you'll see the older-style list of elements rather than the drag-and-drop interface). But nothing else will change in terms of the finished product (the front end webform will be exactly the same).
If you don't disable it and have webform_civicrm enabled, then the drag-and-drop interface will not work correctly and you won't be able to edit the form.

This issue was filed against a branch (7.x-2.x) that is no longer supported. We're sorry we did not get to work through it, but once you upgrade to 7.x-5.x and if the issue persists, please feel free to re-open.