Revamp Form UI about pods HOT 7 CLOSED

Need to put together the form for use on the frontend (publicForm replacement) and the backend (partially completed).

Should use CSS best-practices, follow what Gravity Forms does if you want inspiration. Current publicForm UI is too basic and plain, should have a bit more style to it like Gravity Forms has. New backend form should take it's cue from the WP UI for the post editor, so as much as it can retain that look the better.

from pods.

I'm working on refactoring the Form class, so each field extends a general field class and has more options to hook into from their own custom field types. UI will also be separated out and pulled from the ui folder, which could be made to be hookable so that they could be overridden.

from pods.

Wasn't able to get it to a working point to commit this weekend. I should really find a workflow that has me working from a new branch, now that 2.0 alpha is live lol.

from pods.

Well looky looky, creating a new branch for my commits to go into was super easy. Not sure how that'll work with committing to existing branches, but I'll be working from 2.0-bleeding now and just do pull requests for each real alpha release.

from pods.

OK so you can see a lot of the form stuff I'm doing here:

0a48014

I still have quite a bit of pulling in of each field's data, and then building out the actual field option loop in the setup_edit_field.php, which handles each individual option, setting the defaults for that option, etc. My idea for the form field classes (in /classes/fields/boolean.php) is to make it the one place to modify each field's settings for input, display, saving, and settings. Boolean and Number have been nearly completed, I've been stripping out the actual HTML into the new pods_view function and pulling from the /ui/fields/ folder now.

I should be done soon!

from pods.

Notes for a later self: Build out options for boolean field, then follow that structure for other fields when building out

from pods.

Need to add dependency handling into field options, and switch 'values' array to 'data', then determine grouping

from pods.