Delete confirmation, new options and style updates #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated
reduced save and preview debounce timeout
added stopIndex to help with field drops
showWarning
becomesfieldRemoveWarn
Added
events.js, file to register events.
field removal confirmation - configurable with
fieldRemoveWarn
optionsclose edit button at bottom of all field types
clear all button
append
andprepend
options. This lets you append or prepend html to the beginning or end of your form to give user's an idea of what the completed form will look like even for fields they cannot edit. ExampleRemoved
"Form Elements" header of control buttons.
Style updates
field actions moved to top right, delete button style updated. Hover a delete action will turn background of field pink
sortable options restyled
Responsive field attributes
Performance improvements:
update the preview for only the field that was updated.
Notes
instant updates, preview updated faster and save happens whenever a change is made
convert static strings to use _helpers.markup. Currently just flattens out with outerHTML but eventually all for formBuilder elements will have full prototype inheritance.
Numerous improvements were made in this release but more focus in needed on performance in the next couple weeks. Example: when one field is changed, the save cycle runs on the entire set of fields. We should be able to update a single field and have only that fields data node.
@todo: field layout features making use of bootstrap 3 columns