PDF.js
Introducing .NET Multi-platform App UI (MAUI)
PDF.js | Introducing .NET Multi-platform App UI (MAUI) | |
---|---|---|
84 | 273 | |
46,332 | 21,556 | |
1.1% | 0.8% | |
9.9 | 9.9 | |
1 day ago | 7 days ago | |
JavaScript | C# | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PDF.js
-
DEMO - Voice to PDF - Complete PDF documents with voice commands using the Claude 3 Opus API
readPdf: used for reading the dropped file and displaying it on the screen, it uses PDF.js to load the file, get all fields and display it on the browser.
-
Building W-9 Crafter
I first started building the app in the browser, using PDF.js and Download.js to take a PDF and edit it, and then download it to your computer.
-
Parsing PDFs in Node.js
pdf2json is a module that transforms PDF files from binary to JSON format, using pdf.js for its core functionality. It also incorporates support for interactive form elements, enhancing its utility in processing and interpreting PDF content.
-
Is it possible to port Edge's PDF Editor to other browsers or make your own custom one?
Why not PDF.js?
-
How to Write a Cold Email
I'd think opening a PDF in your browser would be at the same risk-level you associate with going to any random URL. On Firefox at least, I'm pretty sure the built-in PDF viewer is simply JS parsing and rendering the PDF anyway -- nothing with elevated permissions:
https://mozilla.github.io/pdf.js/
-
Firefox 119 unleashes PDF prowess and Sync sorcery
The PDF features are actually an extension, just one built in as Firefox's default pdf viewer.
It's called pdf.js https://github.com/mozilla/pdf.js/
You can actually use this pdf viewer in another browser like Chrome if you'd like, there's a demo URL on there.
-
PDF Chat with Node.js, OpenAI and ModelFusion
We use Mozilla's PDF.js via the pdfjs-dist NPM module to load pages from a PDF file. The loadPdfPages function reads the PDF file and extracts its content. It returns an array where each object contains the page number and the text of that page.
- Ask HN: Best toolkit to build custom pdf viewer?
-
Microsoft faces antitrust scrutiny from the EU over Teams, Office 365
The problem is that there simply wasn't a better option at the time.
Ogg Vorbis was a novelty at best, and it was the only decently widely adopted open source competitor for any of the items listed that was available at the time.
HTML5 was only just published when Chrome launched. So Flash was at that point the only option available to show a video in the browser (sure, downloading a RealPlayer file was always an option, but it was clunky, creators didn't like people being able to save stuff locally, and was also not open source). Chrome in fact arguably accelerated the process of getting web video open sourced: Google bought On2 in 2010 to get the rights to VP8 (the only decent H.264 competitor available at that point) so they could immediately open source it. The plan was in fact to remove H.264 from Chrome entirely once VP8/VP9 adoption ramped up[1], but that didn’t end up happening.
Flash was integrated into Chrome because people were going to use it anyway, and having Google distribute it at least let them both sandbox it and roll out automatic updates (a massive vector for malware at the time was ads pretending to be Flash updates, which worked because people were just that used to constant Flash security patches, most of which required a full reboot to apply; Chrome fixed both of those issues). Apple are the ones who ultimately dealt the death blow to Flash, and it was really just because Adobe could not optimize it for phone CPUs no matter what they tried (even the few Android releases of Flash that we got were practically unusable). That also further accelerated the adoption of open source HTML5 technologies.
PDF is an open source format, and has been since 2008. While I don't know if pressure from Google is what did it, that wouldn’t surprise me. Regardless, the Chrome PDF reader, PDFium, is open source[2] and Mozilla's equivalent project from 2011, PDF.js, is also open source.[3] Both of these projects replaced the distinctly closed source Adobe Reader plugin that was formerly mandatory for viewing PDFs in the browser.
Chrome is directly responsible for eliminating a lot of proprietary software from mainstream use and replacing it with high-quality open source tools. While they've caused problems in other areas of browser development that are worthy of criticism, Chrome's track record when it comes to open sourcing their tech has been very good.
[1]: https://blog.chromium.org/2011/01/html-video-codec-support-i...
[2]: https://github.com/chromium/pdfium
[3]: https://github.com/mozilla/pdf.js
-
How do Fix this issue while trying to save an edited PDF? (text gets really small and is rotated)(i'm using nightly)
Firefox Nightly is an unstable test version. You should report PDF issues to this GitHub repository.
Introducing .NET Multi-platform App UI (MAUI)
- Developers are not happy with .NET MAUI, but nobody in the team cares about it
-
Android predictive back support
I am migrating XF app into MAUI and writing a simple Navigation framework because Prism doesn't work well and I didn't use anything advanced anyway. So, I am surfing the code of MAUI to intercept all the back buttons, etc. I haven't found a single mention of apis related to predictive back "RegisterOnBackInvokedCallback", "OnBackInvokedDispatcher", "OnBackPressedDispatcher", "AddCallback", "android:enableOnBackInvokedCallback" Also I don't see any issue on github that would say "Support Android Predictive back". Only one kinda related https://github.com/dotnet/maui/issues/8680
-
Group List View And Collection View are not working In .NET MAVI For IOS
Below issue is still reproducing in Maui .net7.0 version also. #10163
-
.NET 8 – MAUI
Maui is Open Source, MIT License
https://github.com/dotnet/maui
.NET is Open Source
https://dotnet.microsoft.com/en-us/platform/open-source
I do share your skepticism of Microsoft, but it looks like the economics and cash flow dynamics have changed drastically after the advent of the cloud.
Microsoft is more focused on getting developers onto its ecosystem and help them with open source projects with the hope that they will use its Azure cloud services and bring in the money.
My skepticism is a bit relaxed now and I have no qualms using .NET.
I hope I am not wrong.
-
.NET 8 – .NET Blog
It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.
Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.
[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup
[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)
-
What's New in Final RC for .NET 8, .NET MAUI, Asp.net Core and EF8
While this is the quite endorsed by the community: https://github.com/dotnet/maui/discussions/339
I think the fundamental issue is that desktop Linux is way too fragmented. Not only just GTK2/3 and Qt but you have GNOME, KDE, XFCE, Cinnamon and then you have X11, Xorg, Wayland...
To be honest, all those craps are why desktop Linux never took off. I'm very safe to say MAUI for Linux will eventually renders components off its own using framebuffer and hardware acceleration APIs such as OpenGL or Vulkan just because of the market fragmentations...
If desktop Linux truly wants to get the attention, it will need to unify. Fixing dependency hell using Flatpak is the right direction.
There is an existing old fork of MAUI for Linux that uses GTK: https://github.com/jsuarezruiz/maui-linux
- MSFTbot: “We've moved this issue to the Backlog milestone”
-
Every other tab in Shell doesn't show Shell.TitleView on Android
First I came across this Github issue: https://github.com/dotnet/maui/issues/9687 - According to this issue, this is a known bug for MAUI iOS, but it works OK for MAUI Android. As I said, I target Android only and I have the exact same issue. It's apparantly fixed with some of the latest versions for MAUI but the problem still occurs to me even with MAUI version:
-
Bindable properties issue with Custom controls
I saw this and tried to imitate (ofc my lack of experience wouldn't allow me to do it in the exact way). Already found some documentation that allowed to understand better. Thanks for the insigh.
-
ASP.NET Core - how to create an IdentityUser account from an external login
I implemented the Auth controller following this sample code from Microsoft.
What are some alternatives?
jsPDF - Client-side JavaScript PDF generation for everyone.
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
pdfmake - Client/server side PDF printing in pure JavaScript
Avalonia - Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET UI client technology
PDFKit - A JavaScript PDF generation library for Node and the browser
WPF - WPF is a .NET Core UI framework for building Windows desktop applications.
Papa Parse - Fast and powerful CSV (delimited text) parser that gracefully handles large files and malformed input
maui-linux - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
diff2html - Pretty diff to html javascript library (diff2html)
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
pdf-lib - Create and modify PDF documents in any JavaScript environment
react-native-windows - A framework for building native Windows apps with React.