jQuery-File-Upload VS bootstrap-vue

class NehnutelnostUploadImagesView(LoginRequiredMixin, ExclusiveMaklerDetailView, DetailView): template_name = "nehnutelnosti/nehnutelnost\_image\_upload.html" model = Nehnutelnost def post(self, request, *args, **kwargs): self.object = self.get_object() form = ImageUploadForm(self.request.POST, self.request.FILES, nehnutelnost=self.object) if form.is_valid(): nehnutelnost_image = form.save() images_count = self.object.images.count() data = {'is\_valid': True, 'row\_html': image_row_renderer(nehnutelnost_image, self.request), 'name': nehnutelnost_image.image.name, 'url': nehnutelnost_image.image.url,} else: images_count = self.object.images.count() data = {'is\_valid': False, 'errors': form.errors, 'images\_count': images_count} return JsonResponse(data) def get\_context\_data(self, **kwargs): context = super(NehnutelnostUploadImagesView, self).get_context_data(**kwargs) context['images'] = self.object.images.all() context['podorys'] = self.object.podorys return context We use https://github.com/blueimp/jQuery-File-Upload plugin to upload images.

Have been wrecking my nerves trying to use BlueImp JQuery-file-upload plugin. The error messages are cryptic and have been unsuccessful getting any useful help from google.

Here is the setup guide I found but I have no basic knowledge on how to setup this.

I will be using jQuery-File-Upload. maxFileSize might be for that, but it seems only client side, which also means user can bypass the limit and spam big files into my server.

Website/demo: http://blueimp.github.io/jQuery-File-Upload/ The last update: December 2020 Compatibility with Bootstrap versions: Bootstrap v.3 and higher Documentation: yes, how to set up, features description, browser compatibility Developers team support: yes, via GitHub issues page and Stack Overflow page Rating: 31k on GitHub Dependencies: jQuery v1.7+, jQuery UI widget factory v1.9+, jQuery Iframe Transport

And it's a high coincidence that we both released some sort of similar thing at the same time. I love the look of his puppeteer debugger console, his is much more polished that mine :)

Some things I noticed about https://chrome.browserless.io

- after using it for a bit the actual tab in my browser crashed with error "STATUS_BREAKPOINT"

- Does not work on Mobile, it loaded, and ran the script, but I couldn't type into the editor on my Android phone

- I tried to bork it with while(true) page.browser().newPage() it seemed OK

- I tried to bork it with a speedtest, it seemed OK

- No back buttons, so I needed to go to console to history.back()

- No paste into page, no right-click context menu

- Did not raise a pseudo-modal for remote page modal dialogs, I assume it silently closes them. I.e. https://infosimples.github.io/detect-headless/

- Fails (or passes, depending on your perspective) the "Are you Headless?" test at https://arh.antoinevastel.com/bots/areyouheadless

- Did not raise a pseudo-modal for remote page file chooser dialogs, I assume it silently closes them. I.e. https://blueimp.github.io/jQuery-File-Upload/

- Appears to close the browser every time you press the |> play button. I think that makes debugging fluid.

- Does not raise a pseudo-modal for remote page basic auth modal dialogs, it seems to silently close them. I.e https://jigsaw.w3.org/HTTP/Basic/ (at https://jigsaw.w3.org/HTTP/)

All in all I love how the DevTools window is integrated with the page, even tho it does eat up screen real-estate, it's ok. I also love how product-focused Joel is and how the provided scripts are really laser focused on the use cases of his customers. That's what I think is Joel's biggest strength, how much of a good businessman he is, how focussed on his customers he is, and how he delivers that value for them. That's also what I think is my biggest weakness. Compared to how he's building products and features, I'm like wandering around in the dark shining my flashlight on whatever looks interesting to me. I'm not so honed and focused and that's to my detriment, I think. Design is another weakness I have. But we shall see how things go!

Maybe I'll catch up to him. Maybe I'll overtake him! But I'm not sure that side of the business, "puppeteer automation at scale" is necessarily what I want to go into. We'll see what happens tho! :)

4. Bootstrap Vue Bootstrap Vue combines the power of Bootstrap, a popular CSS framework, with Vue.js. It provides a wide range of components and styling options. Check out the Bootstrap Vue website to learn more.

Vue (BootstrapVue)

You say that Afaik is the creator? I didn't see him listed as a major contributor on github: https://github.com/bootstrap-vue/bootstrap-vue/graphs/contributors . Do you happen to have his Github profile link?

For me personally one of the dealbrakers was bootstrap-vue still being stuck with Vue v2 / Bootsrap v4 to this day. react-bootstrap supports Bootstrap v5 since 2021 october.

Bootstrap-Vue: A UI library that provides a range of components based on the popular Bootstrap framework, including forms, buttons, and navbars.

BootstrapVue is the bundle: https://bootstrap-vue.org/

Yes. Please have the courtesy to feedback with a roadmap or prio of the issue. Especially for popular issues.

Asking, politely, for this should not label you as entitled freeloader. It is important input to make an informed decision wether one should just wait for the fix, workaround it, contribute a PR yourself, fork the component or drop it and consider alternatives.

One has to be careful with estimates though so they don’t become false promises. All respect to these maintainers but if I have to give one concrete example, consider following issue in a very popular Vue component, https://github.com/bootstrap-vue/bootstrap-vue/issues/5196 creating a upgrade deadlock for almost the entire Vuejs community. It’s the type of dependency that get so entrenched in everybody’s application that upgrading or moving away from it becomes very expensive and requires long term planning. As such, hundreds of comments there asking for estimates and also dozens of heavy names offering help in forms of PRs, forks or donations, all on a very polite level, but the maintainers kept promising it will be done “very soon” for almost 2 years straight. It appears the last months the war has been adding more obstacles so all respect for that, but even before the roadmap was hopelessly unpredictable.

I get it, as a volunteer other things in life often have higher prio, estimates tend to be optimistic and you might want to work on things in no particular order at all. What’s important is to be transparent, polite and communicate.

What's wrong with Angular? It being largely "batteries included" seemed pretty nice and I really liked the fact that TypeScript was a first class citizen - React and Vue both feel like it's been kind of tacked on, especially when a lot of additional libraries out there don't really have proper bindings.

That said, personally I also think that React kind of went downhill for a bit due to the hooks (after seeing a few projects become really nightmarish to debug due to render loops without clear causes for them, after people sprinkled one too many hooks in there).

Oh, and the Vue 2 to 3 migration is also a bit problematic because still many UI component libraries haven't been migrated over - currently actually using PrimeVue on a project because BootstrapVue still doesn't have proper support https://github.com/bootstrap-vue/bootstrap-vue/issues/5196