ellykits / neat-form Goto Github PK

Add ability to handle logic by passing condition and specifying actions to be performed when the condition(s) is evaluated successfully.

This is a normal radio group with nested layout

Should allow users to select and view images

The rule engine seems to persist only a single rule even as you move between different forms

Toast notifications allow for passing dynamic text to their title/message. Internally the notifications uses a calculation listener that updates UI wherever the calculation is changed when the rules are fired.

Currently when a calculation field changes for a toast notifications all the calculation listeners are fired when we only need to update the UI for toast notification whose calculation has been update. We need to build a dependency map like we do with other field calculations without having to create a new attribute but maintain the field calculation template.

Will be using GitHub Packages for dependency management.

The documentation here https://github.com/ellykits/neat-form/wiki/5.-Form-Specification describes the rules_file as required but currently works without

This is a handy library which does almost everything I need (basically a form schema is generated server-side, form JSON downloaded and then rendered dynamically).

All the defaults are fine, except for the text color in forms. For some reason in my app when I render it on a white background the date field text is also white and I have no idea how to go about specifying an alternative text color (I've been googling and editing styles.xml for hours now and unable to change anything in the rendered form). I see I can generate a manual layout for the form, but I'd rather no do that as form definitions can change daily, and the default LinearLayout is perfect for my needs.

Any tips on how to change the text color (in particular for the date field) ?

Should have been done by yesterday. New android libraries will only be available on jetpack

This factory should allow selecting multiple options from checkbox like a checked list.

Already submitted an issue here App crash when you click searchable spinner after changing screen orientation

• Add support for Multi language support configuration
• Add support for Multi language support rendering

Currently the views are just created from JSON and embedded to the provided root view normally a view group. having a multi step form will allow embedding views onto a fragment that can be added to any existing activity.

Implement maximum and minimum dates for datepicker dialogue

Some widgets do not contain the meta_data attributes after saving data and retrieving it via the formbuillder.getFormDetails()

You can use the below form to recreate the issue

Implement support for customising neat form library forms with android xml layout .

This is important especially for large screen devices e.g Tablets whereby the default neat library forms would not make the best use of screen estate.

Date picker that follows material design guidelines

Add functionality that allows grouping fields together.

Kotlin Serialization is now 1.0 and production ready. Gonna switch to use it instead of GSON because why not it's Kotlin dependency 😄

Optimize the way views are created

• There is a slight delay currently of about 4 seconds when the view with the JSON form builder is loaded. Work to resolve this by offloading some of the tasks to background thread plus just look into any other issues that can be further optimized to improve the performance of the app in general

Implement passing of custom checkbox attributes via custom xml form layout

Instead handling data saving in the library we left it to the implementers but the library will return as a callback the data from the views which can be access via the FormBuilder

Bug fix for app crushes when the custom xml layout contains views which are not available in json forms

Add an attribute that will be used for applying theme to the widget. The applied theme will be used for every widget of that type.

Add an implementation of validating required form fields while completing the forms

Bump down the minimum sdk version of the library

Allows steps to be hidden base on skip logic defines on other steps fields
Example : if Age is > 5 hide step 2 and 3

This view pops up a dialog where you can select items and it writes them back to the view. More of an expansion panel view

Hello,
I am evaluating solutions for use to fill up forms on android.

My needs are the following,
I need to be able to define the forms on a backend and the app should pull the definition down and display the forms based on that.
I want there to be a way of defining dependencies in fields making up the form. So if there is a condition that field2 should be displayed when field1 is answered as 'Yes' then the UI should parse that and display accordingly.
Some of the form fields also need to be signature captures and file(images) uploads.

Is this use case a good fit for neat-form ?