Thanks - I have added highlight.js now 
joerichsen
wolfiton
msaraiva
Broadway Core Team
ityonemo
thanks for this detailed explanation. I’ll admit that I, too, was too dense to understand the advantages, but I think I do now. I used to manage some programmers who were programming in react and also had to write react code myself, but didn’t have a full understanding of why it’s so good beyond ‘it’s functional and state management is sane’ so thanks for explaining react better than react does =D
0
hauleth
Only when support for this was coded. Remember that not everybody will use the same editor as you so it can look differently in different editors. Vim for example do not support that AFAIK.
Also not everyone is using syntax highlighting (for example visually impaired people).
But it can happen, for multiple of reasons:
- simpler transition
- inexperienced developer
- creation of new HTML tag by the w3c in the future
2
msaraiva
Broadway Core Team
@hauleth thanks for pointing those exceptions. It’s important that people have them in mind before adopting any technology. As I said before, there is always a tradeoff.
Vim does not support it yet. If nobody out there with the required skills to add syntax highlighting for vim gets interested in this library, that probably means that the library itself it’s not as useful as I thought. So if that happens, it’s probably a sign that I should move on and try something else.
Indeed. All of those things could happen. However, they can happen in any technology using the concept of “components”, including React, Vue, Svelte or any other that embraced a similar approach. As far as I know, that hasn’t been a problem for the adoption of those technologies. Those are really minor issues, IMO.
Lastly and probably the most important thing out of this discussion is that it helped me a lot to convince myself that we’ve chosen a good approach. Why? Because since Surface knows the structure of the code, we can easily add an option to the translator to check if a component has the same name of an existing HTML element and present a proper warning (or error) to the user.
See how powerful the abstraction is? Even some of the downsides of it can be properly handled in a way that guides the user to do the right thing. I think it’s just fantastic that we can do that, especially for the inexperienced developers you mentioned.
6
tme_317
Awesome library! I was already making some live components using Bulma (with inspiration from the excellent Buefy) and this will make the templating/props experience almost like React!
Quick question… I was reading this issue and is it true Surface.Component can be used to make standard stateless functional templates without LiveView being installed at all?? I just assumed Surface was completely coupled to LV but it would be awesome to be able to use it in my non-LV projects also.
3
msaraiva
Broadway Core Team
My initial intention for Surface.Component was to keep it as a sort of functional component that could work in both, LV and non-LV projects. The problem is that currently, LiveView does not allow nesting live components inside a functional component. A phoenix LiveComponent can only be initialized inside a LiveView or in other LiveComponent. So in order to allow nested components to work properly in LV I’m changing the implementation of Surface.Component to also rely on live_component/3 which will, unfortunately, make it incompatible with non-LV projects.
BTW, I also think it would be great to be able to use the same model in non-LV projects. However, since we’re currently focusing on LV, I think it’s better to remove the support for now. If in the future more people get interested in using Surface in non-LV projects, we can try to talk to the phoenix core team again and see if we can find an alternative solution for the problem.
2
elcritch
That’d be awesome! I’m using Bulma currently and built up an internal livecomponent like library using macros but livecomponents would be so much nicer. Still even as macros, a component library makes developing new pages a sinch. I’m excited to look into your library!
Do you wrap things like dropdowns/number selects/etc and handle their events? If there’s a way to add Bulma based live-components I’d take a look at that (rather than building my own).
0
Exadra37
It sounds like you are assuming that “everyone” is using VSCode, but many more editors exist, and each editor have many different themes you can choose from.
So his assumption is perfectly valid in thinking that it’s a typo, and he will not be alone for the many years to come, but I am not saying you should rename them.
And congrats for the great work and effort your are putting on this project
1