4 ms·
You definitely have access to something we don't, and that might changes how you view Elm. For example a normal Elm user can only send/receive values to/from JS
by b123400 10y ago
You definitely have access to something we don't, and that might changes how you view Elm. For example a normal Elm user can only send/receive values to/from JS via ports, and that is not scalable, e.g. you are not suppose to use ports in library. But at NoRedInk I guess you have some sort of native module wrapper (https://github.com/NoRedInk/take-home/wiki/Writing-your-first-Elm-Native-module https://github.com/NoRedInk/take-home/wiki/Writing-your-firs...) that we cannot access?
- elbear 10y agoAnyone can write a native module. You can't publish it, but you can use it in your project.[1] [1] http://faq.elm-community.org/#why-doesnt-the-elm-compiler-find-the-native-code-in-a-module-that-i-cloned-from-github http://faq.elm-community.org/#why-doesnt-the-elm-compiler-fi...
- lgas 10y agoNative modules are accessible to anyone. Unfortunately the link you provided is a little out of date despite being the top hit on google. Here is an example of a native module that works with 0.17 though: https://github.com/evancz/elm-markdown/blob/master/src/Native/Markdown.js https://github.com/evancz/elm-markdown/blob/master/src/Nativ...
- b123400 10y agoYeah I figured the "rules" to write a native module for a while, but there is no tutorial, no support at all, which makes me rather uncomfortable, and I am never confident with that code.