Quantcast
Channel: ActiveTopics
Viewing all articles
Browse latest Browse all 72689

Features I'd Like to See Added to Contour

$
0
0

I've been working quite a bit with Contour the past few months and while I find it a great product, I can't help feeling that it is lacking some very specific features. I've compiled a list and was wondering what the community thought, and also if HQ had any kind of roadmap on when the next version of Contour will come out and what will be available in that release. Feel free to add more features that I've missed.

My list is sorted by priority by what I feel is important:

  • Ability to set the aliases for the fields.
    Fields with the same caption will be fixed by this.
    Field types need uniquely identifiable class names or ids for frontend javascript/css.

  • UI for form entries needs love:
    Fields in entries section should be sorted in the order that they exist on the form, NOT alphabetically.
    Select all, select none, forms that have more than... 5 entries? run off the page... Not very friendly for clients to manage their data.

  • Ability to sort form steps.
    Ability to move fields or fieldsets to different steps.
    (This can be accomplished by altering the database, yes, but it would be best for end users if this functionality was integrated into the UI.)

  • Conditional showing/hiding/skipping of fields/steps based on the value of another field. (Workflow/Javacript) -- Not much can really be done for this one I guess, but it would be nice to keep this in mind and find a better way to approach it.

  • Default settings for all forms. Would be nice to set it once and have all forms take the default.

  • More control, overall, of the markup would be nice, that way errors, captions, tooltips, etc, can be better targeted with javascript and CSS.

I know you've got to make money somehow, HQ, but it would sure be nice if this project was a bit more open so we could do more to contribute to it. Rewriting all the fieldtypes isn't practical and doesn't remove the old ones. Perhaps one approach could be that the core of Contour could be commercially licensed, where as the Providers could take a more open source approach. Then there wouldn't be a need for something like the Contour Contrib project.

Anyhow, there's my thoughts. I hope we can get some disussion started here.


Viewing all articles
Browse latest Browse all 72689

Trending Articles