The :hoplon: ClojureScript Web Framework - http://hoplon.io/
flyboarder 2019-05-17T00:25:28.062800Z

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

flyboarder 2019-05-17T00:27:09.063700Z

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

flyboarder 2019-05-17T00:27:58.064600Z

or a hoplon-native wrapper

flyboarder 2019-05-17T00:31:01.065600Z

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

dave 2019-05-17T00:33:41.066100Z

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

dave 2019-05-17T00:33:56.066500Z

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

flyboarder 2019-05-17T00:36:08.067Z

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

flyboarder 2019-05-17T00:36:57.067900Z

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

dave 2019-05-17T00:39:32.068200Z

oh, interesting

dave 2019-05-17T00:40:41.069Z

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

flyboarder 2019-05-17T00:40:49.069200Z


dave 2019-05-17T00:40:57.069400Z

that's a neat idea

flyboarder 2019-05-17T00:49:55.070700Z

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

jouerose 2019-05-17T07:34:11.071100Z

thank you @jumblerg

jouerose 2019-05-17T07:37:10.071900Z

@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.

flyboarder 2019-05-17T15:27:16.001200Z

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

jouerose 2019-05-17T16:16:56.001400Z

@flyboarder thanks


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.

micha 2019-05-17T22:59:04.004500Z

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

micha 2019-05-17T22:59:15.004800Z

it's not going to be available in all browsers

micha 2019-05-17T22:59:45.005300Z

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

micha 2019-05-17T23:00:41.005700Z

the polyfills are kind of lacking, last i checked

flyboarder 2019-05-17T23:39:51.006500Z

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

flyboarder 2019-05-17T23:40:29.007500Z

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

micha 2019-05-17T23:40:45.007800Z

oh interesting

micha 2019-05-17T23:41:01.008200Z

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

flyboarder 2019-05-17T23:41:45.008700Z

Safari now has partial support

flyboarder 2019-05-17T23:42:07.009100Z

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

flyboarder 2019-05-17T23:42:37.009700Z

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

flyboarder 2019-05-17T23:49:24.010300Z

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

micha 2019-05-17T23:49:52.010600Z

well the best future proofing is DOM elements, no?

micha 2019-05-17T23:50:01.010900Z

web components aren't even a thing yet

micha 2019-05-17T23:50:20.011300Z

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

micha 2019-05-17T23:51:14.012Z

if they break the DOM API the whole web goes down

flyboarder 2019-05-17T23:51:36.012500Z

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

flyboarder 2019-05-17T23:52:02.013Z

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

flyboarder 2019-05-17T23:52:14.013200Z


micha 2019-05-17T23:52:41.013700Z

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

flyboarder 2019-05-17T23:52:48.014Z

yep they are standard now

micha 2019-05-17T23:53:03.014400Z

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

flyboarder 2019-05-17T23:53:36.015Z

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

flyboarder 2019-05-17T23:53:50.015300Z

you dont want a multi GB html file

micha 2019-05-17T23:54:11.015600Z

presumably you'd generate them via a JS API

flyboarder 2019-05-17T23:54:15.015900Z


micha 2019-05-17T23:54:16.016Z

from cljs or whatever

flyboarder 2019-05-17T23:54:35.016600Z

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

micha 2019-05-17T23:54:37.016700Z

i like the idea of progressive web apps for sure

micha 2019-05-17T23:54:47.017Z

it's like the only way to really do cordova

micha 2019-05-17T23:55:09.017400Z

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

flyboarder 2019-05-17T23:55:14.017600Z


flyboarder 2019-05-17T23:55:19.017900Z

thats the goal i believe

micha 2019-05-17T23:55:21.018Z

10000% in favor of that

flyboarder 2019-05-17T23:55:49.019Z

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

micha 2019-05-17T23:56:04.019400Z

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

flyboarder 2019-05-17T23:56:11.019700Z

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

flyboarder 2019-05-17T23:57:16.020300Z

brave browser?

micha 2019-05-17T23:58:13.020600Z

which tracking are you referring to?

flyboarder 2019-05-17T23:59:22.021200Z

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