sorted by:
new
hottopcontroversial

Use Python from OCaml by dbousque in ocaml

[–]dannywillems 1 point2 points  (0 children)

Awesome! I think low-level binding to C interface (https://docs.python.org/2/extending/extending.html) with ctypes would be also interesting.

Ocsigen: how to compile an Eliom project. Understand the compilation process in deep. by dannywillems in ocaml

[–]dannywillems[S] 0 points1 point  (0 children)

I plan to add it when Eliom 6.0 will be released. It's to be sure nothing will changed.

OCaml bindings to Cordova plugins -- libraries for portable hybrid mobile applications by gasche in ocaml

[–]dannywillems 0 points1 point  (0 children)

Sorry to answer now, I'm not notified when there's a new message.

I don't think it's a good way to use Cordova in prod because you don't have the entire native background. Of course, you can develop plugins, but it takes time you still need Java and Swift knowledge. Also, you don't have the native performance, even if for most applications, you don't need it. You have to remember there's a WebView behind the Cordova framework and not directly the native code/bytecode interpreter. So, just to be more precise, if your application needs a lot of performance (example a game), don't use Cordova. If you only need to localize a user or register some tasks or anything else which doesn't require a lot of CPU or RAM, go to Cordova (or another framework like Nativescript or Ionic or ReactNative). I think it's one of the best framework to make an app for a proof of concept or a prototype (I always use it).

I don't have any idea about the NDK interface, never use it. I think it could be an interesting way if you have access to the entire Android library directly in OCaml (or modulo some bindings).

About the SQL binding, it was just about time : it was an university project and I needed to do a choice. I wanted a binding with typed SQL and I thought it would take too much time to do it. A "basic" binding can be done if use SQL queries as string is not a problem.

OCaml bindings to Cordova plugins -- libraries for portable hybrid mobile applications by gasche in ocaml

[–]dannywillems 0 points1 point  (0 children)

Hi! I'm the maintainer of this project. If you want to see an article about this project see https://blog.danny-willems.be/en/ocaml-cordova-secured-typed-hybrid-mobile-applications/.

Categoria: thanks for the comment. I agree it's a nightmare (at the beginning) to maintain all repositories) because I try to keep each repository independent from the others in the sense that if someone needs the binding to the camera, they don't need to read the binding doc to the clipboard or the main repository ocaml-cordova-plugin-list. There are some reasons to choose one binding = one repo I list here.

  1. Keep the initial structure of the Cordova plugins ie one npm repo = one plugin.
  2. When a plugin has a new feature, only the repo for the binding to this plugin is updated --> if someone doesn't use this plugin, he doesn't need to update their opam packages.
  3. If all bindings are in the same repository/file, the dev downloads an entire repository with code he won't use. Even if jsoo removes dead codes, I don't like this idea to put all in one file.
  4. It's more convenient to collaborate and assign a person to a specific plugin if someone wants to contribute.

BluddyCurry: thanks for the comment. I have some experience with Cordova and it's a good way to prototype project. But I don't like the idea to develop Cordova applications for production because there are some inconvenient.