7 comments

  • dvt37 minutes ago
    Super cool. Working on a local AI tool specifically for document workflow automation (where context = screen&#x2F;web&#x2F;folders&#x2F;files), and this could come in super useful. I do most of the PDF&#x2F;DOCX&#x2F;etc. parsing natively in Rust, but having a nice way to see the output without spinning up Word or Powerpoint is a huge leap.<p>Thanks for releasing publicly.
    • andrewlu028 minutes ago
      nice - did you write a custom parser for PDF&#x2F;DOCX? we wrote one for XLSX after running into event loop issues with sheet JS
      • dvt22 minutes ago
        Using lopdf[1] for PDF parsing, rtf-parser[2] for RTF, calamine[3] for XLSX, and I&#x27;m sure you know that DOCX&#x2F;PPTX&#x2F;etc. is basically just a zip file of XML + text. The LLM cares about textual data (which just gets moderately cleaned up post-extraction), so I (thankfully) didn&#x27;t have to deal with rendering. But showing a preview or end-result to a user would be a huge plus, so I can see myself using your library.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;J-F-Liu&#x2F;lopdf" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;J-F-Liu&#x2F;lopdf</a><p>[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;d0rianb&#x2F;rtf-parser" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;d0rianb&#x2F;rtf-parser</a><p>[3] <a href="https:&#x2F;&#x2F;github.com&#x2F;tafia&#x2F;calamine" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tafia&#x2F;calamine</a>
  • spankalee2 hours ago
    These should really be web components. Leaving out every framework other than React is really bad for the web.
    • andrewlu01 hour ago
      thats fair and definitely something we can try supporting in the future. we started with React because of how familiar models are with shadcn and tailwind<p>we hope this can be useful for people building in React though!
  • CraigJPerry1 hour ago
    Those bounding box demos are decent.<p>By quirk of fate i&#x27;ve spent the past 2 days prototyping some stuff on pdfjs. Just trying to figure out a game plan for handling bounding boxes in the face of page zooming, different resolutions etc. etc. I can&#x27;t see it mentioned whether the components are virtualising pages (as in reusing dom elements as document pages scroll by). I guess i just learned what i&#x27;ll be exploring tomorrow then...
    • andrewlu01 hour ago
      yes - the pdf&#x2F;docx viewer use react-virtual to virtualize the pages<p>the zoom should work with the bounding box highlights, we&#x27;re working on adding rotation support
  • egeozcan55 minutes ago
    Why doesn&#x27;t it mention anywhere that they are React components?
    • andrewlu042 minutes ago
      we&#x27;ll try to make it more clear on the landing&#x2F;introduction page!
  • hobofan46 minutes ago
    Thanks, that looks awesome! We were looking to add DOCX and XLSX preview to our app, and were planning to do server-side conversion to PDF (which seems to be what most other apps resort to) due to the lack of good libraries to render it, and this is exactly what we were looking for! :)
    • andrewlu041 minutes ago
      thanks! would love to get your feedback<p>i can&#x27;t promise its visually 1:1 with Word&#x2F;Excel but its pretty close on the corpus we tested with
  • warthog2 hours ago
    really like these - curious how the xlsx editor and viewer is built in that what kind of headless spreadsheet?<p>could not have been easy
    • andrewlu02 hours ago
      Hi! I&#x27;m one of the engineers at Extend that worked on this - one of our other engineers created a Rust XLSX&#x2F;XLS parser that we ported to WASM to our @extend-ai&#x2F;react-xlsx package which handles the rendering&#x2F;charts. It exposes some hooks so users can use their own components for the toolbar
      • drivingmenuts1 hour ago
        How much was actual engineering and how much was telling an AI what to do?
  • KolmogorovComp1 hour ago
    &gt; This page could not load<p>On mobile Safari…
    • andrewlu01 hour ago
      hm seems to look ok on mine - is this on the root page?