Newbie 'Must Read' Thread

@twofus - this should get you pointed in the right direction. It's basically taking the 3 column ready styles, adding a couple more and changing the percentage values to allow for 5 columns.

http://pastie.org/pastes/1326908/text

I haven't tested it at all so you may need to tweak it to get your form just so. I'm just giving you something to spin off of.

the 5 class names you'll see in the CSS are

* gf_first_fifth
* gf_second_fifth
* gf_third_fifth
* gf_fourth_fifth
* gf_fifth_fifth

You would implement those like the other ready class helpers as described here

http://www.gravityhelp.com/css-ready-classes-for-gravity-forms/

If you don't need the fields to be spaced out into columns - which still may be too much spacing if you have a large form, you can make the field containers display inline so the flow next to each other. It's the same basic concept as in the demo here.

http://www.rocketgenius.com/gravity-forms-mad-lib-style-form-demo/

if you scroll down a ways on that page, you'll see the basic CSS and explanation

The helper classes included in the 1.5 version are simply pre-built CSS rules to aid in creating advanced layouts. They've been tested thoroughly and there's no new functionality in the plugin needed to support them. The styles should work in any version if the style rules are added and implemented correctly.

This also goes for the inline styles I referenced in the demo, they're simply CSS rules and don't require any specific version of Gravity Forms to work.

The 5 column style rules I proposed above are based on the 3 column "ready class" rules. I threw those out there because @twofus requested some guidance. I did say that those rules HAVE NOT been tested and may require some additional work. I'm doubtful that they're something that will even be added to the core CSS.

I don't see any issues with the advice.. it's not programming, just good ol' CSS formatting.

For the record Gravity Forms uses standard CSS to style forms and has extensive API hooks available to extend it's functionality using PHP. There isn't anything Gravity Forms specific or special as far as customizations typically go, design wise it's standard CSS and code/functionality wise it's PHP and standard WordPress hook/filter conventions.

Floating fields in CSS is just like floating any element in CSS. However you need to inspect the HTML and determine what elements need to be floated and write custom CSS. You can also use the CSS Ready Classes if you are running Gravity Forms v1.5 Beta.

We can provide you with guidance on how to do things, and are always willing to help with code snippets (both PHP and CSS) but we can't write complex customizations for you if you want to do something beyond a simple code snippet.

As far as documentation goes we are getting ready to launch a new documentation area, including an extensive API hook/filter reference guide. However in order to implement hook/filters you will need to have an understanding of how WordPress hook/filters work and how to implement them using PHP. Our documentation will not be a general how to guide for PHP, CSS or WordPress. It's Gravity Forms specific documentation.

For things Gravity Forms does not do out of the box but can do via customizations (which is practically anything if you know PHP/WordPress/CSS) you will have to have a certain level of understanding of PHP and CSS in order to customize the functionality, otherwise you may want to consider hiring a developer to assist you with complex customizations.

@HuntererGatherer New documentation is under development and will launch with the new site and the public release of Gravity Forms v1.5. Although a single document currently isn't the plan, it's online documentation and not a download. We can look at possibly making a PDF available if there is enough demand for it. The new documentation is based on MediaWiki which powers Wikipedia.com.

No, the last part is incorrect. That would mean that the label would have the class of "gfield_label" AND a class named "input_1_54" which is not the case. All you need is to specify your classname and then by inheritance, the label with the class "gfield_label" will inherit the properties specified in the new rule.

Also, trying to add a unique identifier in the rule negates the whole idea of a reusable class. You really don't need it.

Yes, like I said in the original post, you create a class using the example I created. THEN, simply apply that class name to select fields in the admin. You click on the field name in the form builder, click on the advanced tab then add "myclassname" or whatever you call it in the CSS Class Name field. Save the form and you should see the change if you've applied it properly.

Great news. If you want to use the same tooltip we use in the admin, there are a few steps to setting it up and using it on the front end. I detailed how to do this in a post some time back. Here's the link with the how-to.

http://forum.gravityhelp.com/topic/add-help-tips-next-to-a-field#post-7277

@CGRInc - thanks for the feedback. Everybody has their own opinions about what is or is not adequate documentation. Personally, I think the wiki version is very comprehensive and will be more that adequate for most. We are planning to add some video tutorials as we go along to help as well.