HexaPDF VS zeitwerk

An example for a very simple setup is the cmdparse gem documentation. It only has a few additional documentation files that accompany the main API documentation. The other end of the spectrum is the documentation for HexaPDF which encompasses many additional documentation files besides the API documentation and deeply integrates the API docs into the whole documentation website.

HexaPDF is a Ruby OSS library with a commercial version available and profitable.

So I'm collecting feature ideas for that table implementation at https://github.com/gettalong/hexapdf/discussions/231.

Hi there! I'm the author of HexaPDF.

git clone https://github.com/gettalong/hexapdf.git

You can use this HexaPDF script to do this:

I have just released my new gem hexapdf-extras which provides additional functionality on top of the HexaPDF library.

You can use HexaPDF together with a small script to do this (see the third line on how to use the script):

TrueType subsetting mainly consists of generating the necessary glyph and various index tables, and copying over all the other necessary tables which don't need to be adjusted. See https://github.com/gettalong/hexapdf/blob/master/lib/hexapdf/font/true_type/subsetter.rb for what is needed to subset.

for all my PDF processing needs, courtesy of HexaPDF,

To setup it's pretty simple, you just need to create a file inside bin/console and require all the files you want to use on a REPL, most of the times we use gems like zeitwerk to provide the auto requiring, but if you want to do it manually, refer to the example below:

zeitwerk

Zeitwerk takes a directory and makes every file underneath it available to load. The convention is that every new sub-directory is a new module, and every file defines a class with the same name as the file.

There is a gem that does that used by Rails and multiple other gems:

https://github.com/fxn/zeitwerk

It is pretty easy to set it up in any Ruby project.

I actually prefer auto-loading, which lets you iterate through a package manager much easier/faster - PHP iterated through PSR-0[0] before landing on PSR-4[1], and you can always build your own (which is what most frameworks pre-composer were doing).

With Rails 7 and Zeitwerk, the Ruby community has landed on a very similar auto-loading system as PHP now[2] with constants translating to paths by convention.

[0]: https://github.com/php-fig/fig-standards/blob/master/accepte...

[1]: https://www.php-fig.org/psr/psr-4/

[2]: https://github.com/fxn/zeitwerk#the-idea-file-paths-match-co...

If you're working on non-Rails apps and need to deal with loading code, zeitwerk can be used anywhere, unlike the old Rails autoloader. It's also really easy to set up.

https://github.com/fxn/zeitwerk#collapsing-directories

Zeitwerk

With a few modifications in the gem source code, we could easily integrate Auth0 into our Rails API, but that on Rails 5. Rails 6 brought Zeitwerk code loader together, which makes it harder to perform the alterations suggested in my previous post.