Fork me on GitHub
#hoplon
<
2019-05-17
>
flyboarder00:05:28

^ I am with jumblerg on this, I think cordova is the best route currently available

flyboarder00:05:09

I think there is value in creating a webcomponents implementation of hoplon so you could use things like ionic

flyboarder00:05:58

or a hoplon-native wrapper

flyboarder00:05:01

However I feel like hoplon already does what webcomponents was trying to do, templates, encapsulated state, html-imports, etc.

dave00:05:41

a webcomponents implementation of hoplon is a very interesting idea. i feel like that could pick up traction with the webcomponents crowd

dave00:05:56

like, the idea behind hoplon is awesome, but it does require you to buy into clojurescript

flyboarder00:05:08

@dave my thought for wc version would be one that is generated from cljs

flyboarder00:05:57

so you would include your cljs file the same way you would any other js dependency in a web app and then anything below that would have access to your web components

dave00:05:32

oh, interesting

dave00:05:41

so you could build components in hoplon and then use them in other applications that aren't built in clojurescript? (react apps, etc.)

dave00:05:57

that's a neat idea

flyboarder00:05:55

I imagine you could already use web components initialized via JS in any hoplon project

jouerose07:05:10

@flyboarder @dave do you think it is something that would be long to make ? because if there is path from hoplon to native, that would be great.

flyboarder15:05:16

@jouerose I recommend going with the Cordova approach for the fastest implementation time, @jumblerg already provided a boot task

mynomoto17:05:22

Mobile apps are the reason I don't use Hoplon as much these days. I came to re-frame/reagent/react-native. 😞 It's good but I liked Hoplon better.

micha22:05:04

problem with web components is that it is a dead standard as far as i know

micha22:05:15

it's not going to be available in all browsers

micha22:05:45

also there are some problems with the architecture, mostly around the importing and so on

micha23:05:41

the polyfills are kind of lacking, last i checked

flyboarder23:05:51

@micha wc are alive and well, html-imports have been removed in favour of a new html-modules, which builds on es-modules

flyboarder23:05:29

the rest of the standard is now in Firefox and will be in MS Edge once it switches to the chromium engine

micha23:05:45

oh interesting

micha23:05:01

i hadn't thought about the MS Edge adoption of chrome engine

flyboarder23:05:45

Safari now has partial support

flyboarder23:05:07

so it will come eventually, but it’s going to be a slow process

flyboarder23:05:37

I think having a way to generate web components from hoplon components would give us the best future-proofing

flyboarder23:05:24

Interestingly, custom elements are now in the HTML standard and a few bits in the DOM standard

micha23:05:52

well the best future proofing is DOM elements, no?

micha23:05:01

web components aren't even a thing yet

micha23:05:20

if anything will last it'll be just the DOM elements

micha23:05:14

if they break the DOM API the whole web goes down

flyboarder23:05:36

yeah, seems the shadow dom, custom elements, html templates and some css things related to those are all upstreamed now

flyboarder23:05:02

html-modules is the only thing being reworked and not yet agreed on

micha23:05:41

the shadow dom and custom elements was what i was interested in

flyboarder23:05:48

yep they are standard now

micha23:05:03

the rest of it doesn't look that important, like the modules

flyboarder23:05:36

I kinda get modules, since google is pushing for progressive web apps over native

flyboarder23:05:50

you dont want a multi GB html file

micha23:05:11

presumably you'd generate them via a JS API

micha23:05:16

from cljs or whatever

flyboarder23:05:35

yeah that would be my way of doing it, but the web is run by designers…..

micha23:05:37

i like the idea of progressive web apps for sure

micha23:05:47

it's like the only way to really do cordova

micha23:05:09

like basically that's google making chrome into the equivalent of cordova

flyboarder23:05:19

thats the goal i believe

micha23:05:21

10000% in favor of that

flyboarder23:05:49

yeah but they are also removing the ability to disable tracking from chrome, ie and firefox so im not stoked on that

micha23:05:04

it's preposterous that projects like cordova and electron and so on exist

flyboarder23:05:11

will have to see what other browser takes some serious market share

flyboarder23:05:16

brave browser?

micha23:05:13

which tracking are you referring to?

flyboarder23:05:22

one step at a time, google makes money of tracking people