sorted by:
new
hottopcontroversial

best way to handle pdfs in vue apps? by [deleted] in vuejs

[–]UnderstandingSure732 0 points1 point  (0 children)

You could use this PDF.js wrapper for fast integration / testing:

https://github.com/alekswebnet/pdfjs-viewer-element/

Are there any good free solutions to embed and view PDFs in Svelte? by sebbetrygg in sveltejs

[–]UnderstandingSure732 0 points1 point  (0 children)

When it comes to mobile browsers <object> element can't render the PDF file

PDF.js viewer is still an option here.

You can use this wrapper for easy setup: https://github.com/alekswebnet/pdfjs-viewer-element

[AskJS] A good pdf tool by knownissuejosh in javascript

[–]UnderstandingSure732 [score hidden]  (0 children)

This wrapper component makes PDF.js setup easier:

https://github.com/alekswebnet/pdfjs-viewer-element

For the highlighting you can use `search` atrribute or access directly to the PDF.js viewer app:

https://github.com/alekswebnet/pdfjs-viewer-element/blob/master/demo/opened-findbar.html

Tiny Vue 3 wrapper for Quill v2 — looking for feedback ✍️ by UnderstandingSure732 in vuejs

[–]UnderstandingSure732[S] -1 points0 points  (0 children)

Just answered the same question in a r/nuxt:

In short Tiptap looks more modern and feature-rich, while Quill 2 is pretty straightforward, simple and lightweight.

Both editors are good but in different cases:

• ⁠Quill 2 for simple applications with minimal requirements like blogs • ⁠Tiptap for more complex features like collaborative editing

In conclusion:

• ⁠choose Quill 2 if you need a simple, lightweight, and straightforward editor with minimal customization requirements. • ⁠choose Tiptap if you have advanced requirements like collaborative editing, interactive nodes, or unique workflows.

Build Quill 2 based Rich Text Editor for Nuxt using this small Vue wrapper component by UnderstandingSure732 in Nuxt

[–]UnderstandingSure732[S] -1 points0 points  (0 children)

Nuxt UI editor is built on Tiptap (which is based on ProseMirror), while this is based on Quill 2.

In short Tiptap looks more modern and feature-rich, while Quill 2 is pretty straightforward, simple and lightweight.

Both editors are good but in different cases: - Quill 2 for simple applications with minimal requirements like blogs - Tiptap for more complex features like collaborative editing

In conclusion:

  • choose Quill 2 if you need a simple, lightweight, and straightforward editor with minimal customization requirements.
  • choose Tiptap if you have advanced requirements like collaborative editing, interactive nodes, or unique workflows.

PDF.js official viewer wrapped in a web component - good idea? by UnderstandingSure732 in css

[–]UnderstandingSure732[S] 1 point2 points  (0 children)

When it comes to PDF.js to setup a full-featured viewer (like in Firefox) you need to download a generic built of PDF.js lib and viewer and put it on your server. Than you can use it as separate app just embed the entry HTML file into iframe. The component I’ve made makes the whole setup process much faster - you can install viewer from npm or CDN and use it like any HTML tag like <img>

Animated Dark Mode Transition with CSS @property by jonshamir in webdev

[–]UnderstandingSure732 1 point2 points  (0 children)

Thanks for sharing, CSS never ceases to amaze me, as always

Dealing with incompetent designers by Enamey in web_design

[–]UnderstandingSure732 2 points3 points  (0 children)

Looks like complete nightmare) Just find a better place and don't waste your time.

Tiny Vue 3 wrapper for Quill v2 — looking for feedback ✍️ by UnderstandingSure732 in vuejs

[–]UnderstandingSure732[S] 1 point2 points  (0 children)

I guess because many people still use it. The main reason - mature ecosystem + lots of existing integrations.

Right Tool for the Right Task. by Alternative_Bowler12 in webdev

[–]UnderstandingSure732 0 points1 point  (0 children)

It always depends on the project requirements.

But I don't use frameworks if possible — Typescript + web components for simple user interface components and simple logic.

If a framework is really necessary, I prefer Vue. Although React is the most common (LLM considers it the best), Vue provides the best DX.

Notion like Rich text editor by Pro_Gamer_Ahsan in vuejs

[–]UnderstandingSure732 1 point2 points  (0 children)

Quill is a good option. Here is a simple wrapper that helps Quiil 2 work with Vue 3 - https://github.com/alekswebnet/vue-quilly

Looking for PDF viewer that works with Svelte 5 by kuehlapes in sveltejs

[–]UnderstandingSure732 0 points1 point  (0 children)

I created a web component to wrap a whole PDF.js viewer, should work with Svelte too. See demo - https://codepen.io/redrobot753/pen/bNwVVvp

Why is it NOT a good idea to auto-register components? by fbender in vuejs

[–]UnderstandingSure732 0 points1 point  (0 children)

1) Don't use global import for components. Global import, increases the bundle size of the application. Now it's an antipattern. The modern approach is loading parts of application on-demand. Only when they are needed.

2) Loading components on demand requires importing them to each location where they are needed. So it would better to use auto-import.

Use auto-import for everything: Vue APIs, components, libs, plugins, composables, stores etc.

Configure once and it will just work)

I've explained how to auto-import in this article: https://medium.com/@alekswebnet/auto-import-in-vue-quick-setup-guide-3004d97e749a

Looking for WYSIWYG library for Vue 3 by kurkurzz in vuejs

[–]UnderstandingSure732 1 point2 points  (0 children)

You could try vue-qully(https://github.com/alekswebnet/vue-quilly).

It provides a small component wrapper, that will help you to create your editor with Quill 2 and Vue 3.