-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for code highlighting #238
Comments
There is a project called lowlight which integrates highlight.js with vdoms. It might be useful to do the same here where there is another project for integrating with jsoo vdom implementations. |
Hi, I am using Omd to make a static site generator. One of the features I wanted for my static site generator was syntax highlighting, so I went and implemented it myself. I have published the |
Hi, @alan-j-hu, thanks! I'll take a look at your package to get an idea. As @shonfeder suggests, this might be a good opportunity to think about extensions more concretely. |
I guess one place to start is with this question: Is it (a) sufficient for our purposes that "extension" be through OCaml library APIs, or (b) do we need a plugin system that would allow different external executables to serve as extension mechanisms? My current inclination is that (a) will suffice for current needs. The cost is that using a plugin means that you are either leveraging omd as a library, or you are building a new executable. Would this be satisfactory for your current needs @alan-j-hu? If (a) is the right target for now, I propose we expore implementing it via a functorial interface. Later, we might consider adding something which is midway between (a) and (b) via ocaml_plugin (this would allow dynamically loading ocaml modules as plugins, but wouldn't work with arbitrary executables). |
Yes, accessing the extension mechanism through the OCaml library should be sufficient for my needs. |
Requested in #236 (comment). This should probably be implemented in a lightweight way that takes advantage of the clean extension mechanism we want (but don't yet have) ;)
The text was updated successfully, but these errors were encountered: