A seasonal Elm podcast where we will dive deep into specific problems to help the Elm community get better together by listening to real implementation stories from the Elm community.
Today I am talking to Dan about Screenplay By Elm. An editor built by and for screenplay writers. Dan shared his process in a conference talk at Elm Conf and today we are going dive into that implementation story and hopefully learn a few things about building a custom text editor in Elm.
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
Today I am talking to Dan about Screenplay By Elm. An editor built by and for screenplay writers. Dan shared his process in a conference talk at Elm Conf and today we are going dive into that implementation story and hopefully learn a few things about building a custom text editor in Elm.
Dan's company is hiring! You can join what Reaktor is doing by applying at the link below:
Reaktor Careers
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
Although elm-ui may be what he is most known for publicly its not why I am talking to Matthew. Matthew has also created elm-markup. A custom markup syntax for Elm. It gives you the power of the Elm compiler and types that you can apply to a completely custom syntax that you define. Today he and I sit down to talk about how he achieved that and how it he built the editor example he used to show it off at Oslo Elm Day.
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
Although elm-ui may be what he is most known for publicly its not why I am talking to Matthew. Matthew has also created elm-markup. A custom markup syntax for Elm. It gives you the power of the Elm compiler and types that you can apply to a completely custom syntax that you define. Today he and I sit down to talk about how he achieved that and how it he built the editor example he used to show it off at Oslo Elm Day.
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
Another fun conversation after the implementation story stops. Jim has a lot of experience and wisdom to share so buckle up and enjoy the conversation.
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
This episode covers how Jim brought LaTex and markdown together into a single editor on the web using the elm parser. The secret sauce??? Community and finding help from those around you. We do not always have to have the right answers ourselves to every engineering problem. Other perspectives can help approach a problem in a new way that gets the job done not only sooner but a lot of times better as well.
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
BONUS! I asked Martin a number of extra questions that fell outside of the context of how the text editor is implemented, but still wanted to share those answers so here they are!
🔗 Show Links
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
This episode covers how the editor in elm-browser is implemented. Martin walks us through what made him decide to tackle a custom Elm text editor and why it was the right solution for his use case.
🔗 Show Links
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
BONUS! I asked Brian a number of extra questions that fell outside of the context of how NoRedInk implements text editing, but still wanted to share those answers so here they are!
🔗 Show Links
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
This episode covers how NoRedInk implements text editing for their application using Quill, a JavaScript rich text editing library, and a custom element. Brian Hicks show us an interesting look into how Elm only is not always they best option in a business context, but covers how the guarantees Elm gives us can be leveraged to still create a wonderful solution.
🔗 Show Links:
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★
Why do I think this is important?
Well, because this is what I wish I had right now. Elm has come along way from the idea of centering rectangles on a screen and the community has grown right along with it. But, the language and the community is still young. Especially in comparison to other languages like JavaScript and Python. I'm not saying being a young community is bad but there is a cause and effect that comes with it.
Because Elm and the community are young the amount of resources and examples from teams and individuals in the community could be better, and that is what I want to help with.
📬 Reply to the podcast or give feedback:
📣 Thank you to the sponsors:
🙌 Big shoutout to the monthly supporters:
💸 Support Implementing Elm in Patreon
🎧 Music By
★ Support this podcast on Patreon ★