On this page we will plan future releases and features that will go into this releases.

Current plan is like this (feel free to comment if you want something to be changed or added):

  • Version 1.x
    • 1.0-alpha1
      - core code and database tables stabilization. (DONE)
      - put each form element definition in separate inc file. (DONE)
      - colapse/show all elements commands in form builder. (DONE)
      - qform elements categories like core and advanced - use this for "add new element" select control in form builder. (DONE)
      - qforms_extra date element - add formatting for a date value. (DONE)
    • 1.0-beta1
      - try ti fix node preview bug. (DONE)
      - improve usability for close/open all elements controls. (DONE)
    • 1.0-beta3
      - re-factor plugin system - use object approach. (IN PROGRESS)
      - do upgrade path from prev version.
    • 1.0-beta4
      - experiment with tokens and grouping (for fieldset support) - just to be sure that new object model will support this features in future.
      - add formating support for textarea elements - like core textarea and markup element from qforms_extra.
    • 1.0 stable
      - production ready release.
      - release qforms_extra 1.0 stable release in parallel.
    • 1.x

      - small core improvements in form builder UI: add help system for different form elements with nice popup effect.
      - ability to add start/end date/time for each survey.
      - qforms_extra - new elements: file upload, time, image (ability to add logos to different surveys)
  • Version 2.x
    • Major usability improvements of form builder
      - form previews
      - auto update of preview elements
      - better widget for new element adding (replace select box with something more better).
      - advanced properties section for qform element - like css classes...
    • Better email reporting - tokens support in emails that are send when qform is submitted.
  • Features that are planned in future but we still need to figure in which version to implement them
    • grid element
    • captcha element
    • fieldset element
    • phone element
    • country select box
    • support for fivestar widget and other exotic custom form elements from other contributed modules?
    • form wizards
    • Field-able qforms - add qforms to any Drupal entity (content types, users...).
    • Rules integration
    • Additional module for advanced statistics - qforms_stats
    • Try to expose qforms submission data to the views module
    • New export features
      • Export submitted data to pdf and html or a printer-friendly version
      • Export submitted data from one user to pdf and html or a printer-friendly version
      • Use templates for export

Comments

muitobem’s picture

- Export submitted data to pdf and html or a printer-friendly version
- Export submitted data from one user to pdf and html or a printer-friendly version

pivica’s picture

Yes this are all nice ideas.

I think that template export would be also great - ability to manually define template structure for export.

This would all be very nice features... I will add them to development plan.

mp165’s picture

the module looks great. i think my client will be overwhelmed by webforms, so i'm hoping to set up qforms for them instead. but they want file upload options. anyhow, hope to see it rolled into a release soon :)