hi luke your videos help me understand quasar and vue very well. i have question on Quploader computedProps how to use them? please if possible let me know. once again thanks for uploading.
You're most welcome! Take a look at "Vue Template Refs". It's confusing, because even though they're called "template refs", they're different to the "ref" we know of from the composition API. Basically, we create a ref for the uploader: "", and now when we do this: "const uploaderComponent = ref()", Vue automatically attaches uploaderComponent to that ref. Now we can access it's computed properties via "uploaderComponent.someComputedProperty.value"
Honestly these days... I ask chat GPT to help with questions like this 😁 You would have to use some native JavaScript APIs that I never have from memory!
Do you have an idea how to persist the Q-Uploader file queue when routing away from and back to the page harboring the Uploader? Im trying for an hour or two and I am about to give up.. local storage does not seem to be an option. Thanks for your good content!
@@skycastlechronicles not sure I fully understand, but it sounds like you have a list of files, the user goes to a different page, the user goes back to the page with q-uploader, and you want it to still show the files that were there originally? If that's the case, the only way you'll achieve this is with indexeddb!
@@LukeDiebold Thx, Ill look into that! Yeah, I got a Q-Uploader component with files queued for upload. then I route away and back and want the queue to be reinstated (cuz its empty when I return), ChatGPT told me I could create a blob for the files or sth, I already tried to deserialize the Files, save them to and reconstruct from local storage but I didnt manage to get the optical confirmation of the Upload in the Browser, nor the exact save files in the model.files prop :D I might just not do it, its such a minor improvement to the UX..
@@skycastlechronicles hmm, now that I think about it this might be possible. You'd just need to make sure your uploader component is outside the page so it isn't affected by a change of route (ie in the layout, provided that the pages the user navigates to are within that same layout.)
@@LukeDiebold yes it did! there where some things I didn't know and are not in the docs! great job doing these! is there a way to add those things in the docs? I would like to add it
hi luke your videos help me understand quasar and vue very well. i have question on Quploader computedProps how to use them? please if possible let me know. once again thanks for uploading.
You're most welcome!
Take a look at "Vue Template Refs".
It's confusing, because even though they're called "template refs", they're different to the "ref" we know of from the composition API.
Basically, we create a ref for the uploader: "", and now when we do this: "const uploaderComponent = ref()", Vue automatically attaches uploaderComponent to that ref. Now we can access it's computed properties via "uploaderComponent.someComputedProperty.value"
Hi! if i want to upload my images as a blob, how can I do it?
Honestly these days... I ask chat GPT to help with questions like this 😁
You would have to use some native JavaScript APIs that I never have from memory!
how to stop form submission if user did not upload files?
Do you have an idea how to persist the Q-Uploader file queue when routing away from and back to the page harboring the Uploader? Im trying for an hour or two and I am about to give up.. local storage does not seem to be an option.
Thanks for your good content!
@@skycastlechronicles not sure I fully understand, but it sounds like you have a list of files, the user goes to a different page, the user goes back to the page with q-uploader, and you want it to still show the files that were there originally?
If that's the case, the only way you'll achieve this is with indexeddb!
@@LukeDiebold Thx, Ill look into that! Yeah, I got a Q-Uploader component with files queued for upload. then I route away and back and want the queue to be reinstated (cuz its empty when I return), ChatGPT told me I could create a blob for the files or sth, I already tried to deserialize the Files, save them to and reconstruct from local storage but I didnt manage to get the optical confirmation of the Upload in the Browser, nor the exact save files in the model.files prop :D I might just not do it, its such a minor improvement to the UX..
@@skycastlechronicles hmm, now that I think about it this might be possible.
You'd just need to make sure your uploader component is outside the page so it isn't affected by a change of route (ie in the layout, provided that the pages the user navigates to are within that same layout.)
@@LukeDiebold Intriguing idea! That would circumvent the whol issue! I have to look into Layouts some more! 😬🫣🤩
And to think that 30 mins ago I came to this channel looking specifically for this video, XD
Hahaha, amazing timing.
I hope it helped!
@@LukeDiebold yes it did! there where some things I didn't know and are not in the docs! great job doing these!
is there a way to add those things in the docs? I would like to add it
@@gazorbpazorbian yea sure ☺️
There should be an edit button at the top of the QUploader page ☺️
Thanks for the video, but how we can create a fully customized file uploader in the Quasar? or not use q-uploader
Oh, I thought I mentioned this at the end.
Checkout this part of the docs:
quasar.dev/vue-components/uploader#supporting-other-services
For not using QUploader, you could just use plain javascript!
Also take a look at QFile in case that's what you need :)
wonder if there's a way to remove the list scroll, just have the files and q-uploader adjust its size (height) accordingly
hello bro did it work with you the q-uploader, somehow mine is not working, i just don't know why
thanks
hello is q-uploader still working today,? mine is not working. please help
.
and when i add :8080 in localhost its uploading 99.99% but not 100% so still not uploaded