evoluteur / evolutility-ui-jquery Goto Github PK

This seems like a great tool for me and I really like to dive into it.
But am currently pretty lost right at the start.

Could you provide a simple step by step setup-instruction?
Currently the demo uses localstorage what do I have to do when I want to use a real database?

Thanks for any help
Stefan

Hi!
I use evolutility-server-node and evolutility-ui-jquery.
The project is set up, but there are problems when filtering is used.
I need to filter the data based on the size of the number, but the browser gets the data in the form of a string, not a number.
I tried to solve it, but failed.

               #  evolutility-server-node/models/organizer/test.js
                {
			"id": "a",
			"type": "decimal",
			"inMany": true,
			"column": "a"
		}
              # evolutility-ui-jquery/models/test.js
               {
                    id: 'a', 
                   attribute: 'a', 
                   type: 'decimal',
                   label:'a', 
                   inMany: true,                 
                }

Any plans to support OData?

This is more of a feature request.

Parse.com has a great backend for storing data that can also be retrieved as Backbone Collections. If there is a simple way to integrate with a Parse backend instead of localStorage, this can become an awesome front end for managing Parse objects.

I am not familiar with Backbone, hence finding it difficult to fork the code.

OK for single select lists but not for multiselect.

Hi,
I am submitting a proposal for an enhancement whereby Evolutility UI is able to add custom HTTP header to the HTTP requests. The header will be used to for Cross-Site Request Forgery prevention.
(more on the topic here: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29_Prevention_Cheat_Sheet).

[ ] The implementation of the enhancement requires a new method in the controller app javascript to set a custom header + value in the HTTP request (processed by XHR/jQuery).

Thanks,
Piotr

The test model has changed in Evolutility-Server-Node but Evolutility-UI-jQuery still use the old one.

bower is complaining constantly about the right versions, since your bower.json is very strict about the versions of its dependncies. I think you could insert ~ in front of most version number.

So instead of

"jquery": "2.1.4"

please use

"jquery": "~2.1.4"

Then it will happily accept jquery v2.2.3 as well.

Hi,
I wish to consume restful web services from evolutility framework. Is it possible?

These feature are not implemented yet? I'm seeing the Wine Cellar demo.

How close are you to a 1.0 release? What features are currently missing?

Go to list, click new, add a record, return to list.

After the last record is deleted the app behavior is buggy.

How exactly do you configure the use of REST? Modifying config.js as follows has no effect for me.

var Evol = Evol || {};

Evol.Config = {

	// --- using localStorage
	localStorage: false,

	// --- using evolutility-server-node
	url: 'http://localhost:3000/api/v1/evolutility/',

	// --- using postgrest
	//url: 'http://localhost:3001/'
};

Toggle on, navigate to record, back to list, must click twice to get filter again.

Hi,

We're trying integrating the jquery-front-end with the server node. We are getting the following error message, we try to force the grunt but the front-end is not working properly.

Really appreciate your help.
Best regards.
Julio.-

The current evolutility version supports SQL Server+.NET. Will the new version support the same?

The evolutility backend offers an LOV endpoint. But in the frontend you use hardcoded lists for LOV fields, like this:

id: 'priority', attribute: 'priority', type: 'lov', label: 'Priority', required: true,
                    width: 100,  inMany: true,
                    list: [
                        {id: 1, text: '1 - ASAP'},
                        {id: 2, text: '2 - Urgent'},
                        {id: 3, text: '3 - Important'},
                        {id: 4, text: '4 - Medium'},
                        {id: 5, text: '5 - Low'}
                    ]

Is there a way to easily fetch the list items from the backend instead?