PWA is not working for me… Everything gets build, but it doesnt work offline, and it has no “add to homescreen” banner as it used to in v 0.17.
What am I missing?
Posts made by luis.gilbert
-
RE: Quasar v1.0-beta.3 released!
-
RE: lookup field (q-select performance tips)
Well, my problem is that I’m using 4 q-select with 800 records each (a chart of account company), so it takes an extra 2 seconds just to render the page in my core i7.
I tried a third component component (v-combobox from vuetify) and it’s a lot faster because (I think) it renders the options list progressively whie you scroll down.Any ideas on how can I “clone” this behaviour?
I prefer not to use vuetify because it needs some CSS customization to work along with Quasar, plus, q-select have better options…
-
RE: QSelect performance with >500 entries
Hi!
I have the same scenario. Did you find a solution to this performance issue?
-
lookup field (q-select performance tips)
Hi,
I am trying to create a basic form in my application.
I need some “lookup” fields such as country, states, etc. Each field might have around 200 records aprox.If I use q-select, it seems to be a performance hit.
So, I would appreciate if someone could point me in the right direction to avoid this problem.I’m thinking I should have smaller lookup’s (like top 10 records in each lookup) and when user input in each field, then execute a search function to return small lookup for specific text… Anyway, I don’t knwo hoe to make it work…
Thanks!
-
RE: [Solved] Datatable search performance
So, based in all your comments, I changed my mind and start using server-side… It looks promising and performance is a lot better (searching and initial render also, because fewer records are sent)…
Now, I need to make some changes to my SQL procedures, but already found a lot of examples out there…Thanks for all your help!
-
RE: [Solved] Datatable search performance
Thanks for your responses. Right now, I don’t have any problems renering the datatable with 23K records, and data I get from server is compressed, so it is pretty fast. Plus, I need this feature for a controlled scenario in my intranet.
So, basically, I am force to find a way to make search faster.As qyloxe correctly assummed , data is in memory, so his suggestion might be a good way to handle search, but I had no luck making it work correctly to search string values in all my columns. I need exactly the same functionality as integrated search… I just need it to be faster… I tried the same amount of records in a third party grid component, and search is a lot faster… I need to find out how their integrated search works, and port it to quasar database search…
This is the structure of a typical array (I want to search a string value in all of my columns, and return result to datatable…
[{“Account_Invoice_ID”:“490248”,“Account_Invoice_Type”:1,“Account_Invoice_Date”:“2018-08-13T00:00:00.000Z”,“Account_Invoice_DueDate”:“2018-08-14T00:00:00.000Z”,“Account_Journal_ID”:3,“Partner_ID”:820,“Partner_RUC”:“1790017478001”,“Partner_Name”:“3M ECUADOR C.A.”,“Partner_Name2”:“3M ECUADOR C.A.”,“Account_Invoice_Status_ID”:3,“Account_Payment_Term_ID”:2,“Account_Invoice_Comments”:“fdgdfgdfgfd fd\nfdg\ndfg\ndf\ngdf\ngdf\ngfdgfdg\ndf\ngfd\ng”,“Creation_User”:“LUIS”,“Creation_Date”:“2018-08-13T13:36:46.883Z”,“Last_User”:“LUIS”,“Last_Date”:“2018-08-13T13:36:46.883Z”,“Company_ID”:1,“SRI_Tipo_Comprobante_ID”:"04 ",“Document_Number”:“304-323-000000066”,“Document_Authorization”:“88888888888888888888”,“Retention_Number”:null,“Retention_Authorization”:“0”,“Retention_Move_ID”:“809151”,“Amount_Untaxed”:5,“Amount_Tax”:0.6,“Amount_Total”:5.6,“Amount_Paid”:0.58,“Amount_Unpaid”:5.02,“Account_Move_ID”:“809150”,“Account_Move_Date”:“2018-08-13T00:00:00.000Z”,“Allow_Edit”:true}] -
[Solved] Datatable search performance
I have a datatable and around 23K rows. Page size is 50, and rendering time good.
My problem: search is very slow (compared to other datatable components from different provider). Is there any way to improve search performance?