update docs for v0.4.0

[icebob]

• vue-multiselect field remove scoped styles #20
• fieldSubmit Submit button field #26
• customizable styles Extract styles #29
• fieldCleave Add independent vanilla field components #31
• fieldPikaday Add independent vanilla field components #31
• fieldNoUiSlider Add independent vanilla field components #31
• fieldGoogleAddress new field: google address autocomplete #33
• visible & disabled, values schema functions description
• ES5 examples (change visible(model) {...} to visible: function(model) {...} )

[lionel-bijaoui]

Need help with the doc ?

[icebob]

Maybe 😃

[lionel-bijaoui]

Go on, tell me: how can I help?

[icebob]

The docs on gitbook.com. I don't know it enough good, I don't know the contribution is available.

https://www.gitbook.com/book/icebob/vueformgenerator/details

[lionel-bijaoui]

I just created an account on gitbook, please authorize me so I can try.

[icebob]

OK, I added.

[icebob]

Please check, can you modify the docs?

[lionel-bijaoui]

YES ! 🎉

[icebob]

Great!

[lionel-bijaoui]

Maybe we should specify "vanilla vs jQuery" in the installation.md? I fear the dependency list could be misunderstood and seem daunting. Maybe dependency should be specified only for each field ?

[icebob]

Yes we need specify dependencies for every each field

[lionel-bijaoui]

I'm going to create a branch on gitbook for the v0.4.0 and start modifying the doc

[icebob]

Great! Thanks!

[lionel-bijaoui]

I don't understand what multiple do, can you explain please ?
It is listed in component.md and fields/field_properties.md, is it two different options, or a mistake ?

[icebob]

You can test in in dev mode. Use CTRL key and select multiple rows in table. In this case you can edit fields for multiple models. And component shows fields where multi: true.

But currently it is not complete, because validator can't handle it correctly yet.

[lionel-bijaoui]

So the main multi activate the option, and field level multi activate each field to be part of it ?

[icebob]

Has multi and multiple. Both exists.
Field has property multi.
Component has multiple˛which activate this "multi mode".
See in dev example:

vue-form-generator(:schema='schema', :model='model', :multiple="selected.length > 1")

So if we select 2 or more rows we set multiple to true

[lionel-bijaoui]

Ok I get it 🆒

[lionel-bijaoui]

@icebob I just finished vueMultiselect documentation (on branch v0.4.0), I need your feedback.

[icebob]

Great!

I checked it.

• did you tried the usage examples? Because I think it is not working properly:

  values: [
    {
      "name": "Vue.js",
      "language": "JavaScript"
    },

VueFormGenerator is only handle {id: 1, name: ''} objects as item of values.
Because when you select the item, the component write the value of id field only to the model property.

• There is no link to the page. Missing from Fields page: https://www.gitbook.com/book/icebob/vueformgenerator/edit#/edit/v0.4.0/fields/README.md

Otherwise, good job! Thank you 👍

[lionel-bijaoui]

• I haven't tested it, but with key and label allow for a total control on your object.
• Yes, I still have work to do. Have you checked this page ?

[lionel-bijaoui]

@icebob noUiSlider is almost done (need more examples)
I have checked and tested all examples for vueMultiselect and noUiSlider and fixed a few things.

[icebob]

Great!

[lionel-bijaoui]

@icebob noUiSlider and cleave are finished. Example tested and everything 🎉

[icebob]

For #40 (comment) :

fieldSubmit: only a simple input type=submit. There is a validateBeforeSubmit property in schema. If it is true, running validation after button click. If validation success, call the onSubmit callback from the schema

[icebob]

customizable styles: we can show with example that user can use custom styles for this component. You created a jsfiddle with a new style. You can link it to docs as an example.

[icebob]

visible & disabled, values schema functions description:

visible and disabled property in the schema can be a function too. Example
The function got the model as parameter.

values property in select* fields can be a function. In this case you can generate dynamically the items. Example. This function gets the model and schema as parameters.
You can use this example in docs too.

{
    type: "select",
    label: "Item",
    model: "item",
    values: function(model, schema) {
        switch(model.category) {
            case "Fruit": return ["Apple", "Peach", "Orange"];
            case "Vehicle": return ["Car", "Bicycle", "Ship"];
            case "Animals": return ["Lion", "Dog", "Cat"];
        }

        return [];
    }
}

[lionel-bijaoui]

@icebob pikaday field done !

[icebob]

1 observation: spectrum is a jQuery based field. Currently it is under "vanilla"

[icebob]

I added onPlaceChanged to googleAddress field.

[lionel-bijaoui]

Why not call it text then ? Or textButton ?

[icebob]

text is too common. But change to buttonText

[lionel-bijaoui]

I have reorganize the build-in field alphabetically

[icebob]

Please do it on optional fields too.

[lionel-bijaoui]

Ok

EDIT: Done

[lionel-bijaoui]

@icebob I think I'm done. Sorry for the delay, I was very busy at work yesterday.

[lionel-bijaoui]

The schema on this page is {...}. Should we not write what the schemalook like in details ?

[icebob]

Ok, do it

[lionel-bijaoui]

@icebob I have made some reorganization to the structure and properties here

[icebob]

I moved your screenshot to the assets, ok?
https://www.gitbook.com/book/icebob/vueformgenerator/edit#/edit/v0.4.0/assets/Capture%20d%E2%80%99%C3%A9cran%202016-08-29%20%C3%A0%2017.39.15.png

[lionel-bijaoui]

Oh sorry about that crappy screenshot (badly cropped), I was just a test to see if I could upload a photo to gitbook. You can delete it :)

[icebob]

Ok :)

[icebob]

I add a new tasks to this issue, but I'm doing. Done

[lionel-bijaoui]

Ok i'm done with schema example

[icebob]

Great! Thanks

[icebob]

So all tasks done?

[lionel-bijaoui]

I guess so, I looking at the documentation, trying to find problems

[icebob]

OK

[lionel-bijaoui]

Maybe there a thing, but it is more an improvement than a real problem.

For field like pikaday or noUiSlider, I have added default values. Most fields don't have that information.
I guess it can be improved later and is non blocking for the merge.

What do you think ?

[icebob]

Yes, it is a good idea. But for this open a new issue and we do it later.

[lionel-bijaoui]

Roger that!
I think we are go :)

[icebob]

Thank you for your contribution!

[lionel-bijaoui]

You are welcome, thank you for your work on the plugin 👍

[icebob]

I'm making the new release. Could you merge the docs v0.4.0 branch to the master?

[lionel-bijaoui]

Done

[icebob]

New version released: https://github.com/icebob/vue-form-generator/releases/tag/v0.4.0

[lionel-bijaoui]

That crazy list of changes :D