It would really cool if Gravity Forms was laid out on a baseline grid that was configurable. So, as a designer, I could specify that I want my form to line up on a 18px grid, a 20px grid, or a 24px grid, etc. Same with typography: I could specify a label font size of 13px or 16px, and all typography would adjust proportionally.
PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.
Configurable CSS Baseline Grid
-
Yep, that would be cool. Thanks for the suggestion. We'll keep it in mind.
Posted 13 years ago on Friday November 26, 2010 | Permalink -
Cool concept...but a lot to ask IMO.
Basically the issue I immediately see is the overhead of scripting that kind of functionality. Remember it's a plug-in and your users get bored quickly. The longer it takes to load something the less happy your clients will be.
True, the form could be laid out on a canvas where the form field positions are based on X and Y (remember old school graphing math here) but also keep in mind that a form with 50 input fields will have at least 100 extra bits of data to store and retrieve (the form has to remember the positions somehow!). Additionally, the initial development would be on a per pixal bases which means lining up forms, for your end-user, would be a pain and prone to error.
The currently investigated method of adding columnar grid has far less overhead, and would only require calling a small amount of data to determine how many columns are required for the layout.
In the meantime - CSS is your friend. You can style the width of your input fields to your hearts content there.
Posted 13 years ago on Friday November 26, 2010 | Permalink -
@urmedia makes a good point or two here. The main concerns we have are keeping the user interface as performant and intuitive as possible. Yes, there are other form plugins that throw in the kitchen sink, but the downside is that they are slow and difficult to learn.
We evaluate all the feature requests and if they are appropriate to the largest portion of our user base and still keep the UI uncluttered and easy to use, then those features usually get added. That said, other features that may be useful, but appeal to a more niche set of users, may be added as a separate add-on.
When it comes to layout, It's difficult to bulletproof any one method because of all of the variances in theme construction and styling. We can aim for the middle ground, but I agree that some good ol' CSS work is probably the best option for customizations.
Posted 13 years ago on Friday November 26, 2010 | Permalink
This topic has been resolved and has been closed to new replies.