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

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

or a hoplon-native wrapper

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

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

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

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

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

oh, interesting

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

yes

that's a neat idea

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

thank you @jumblerg

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

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

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

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

it's not going to be available in all browsers

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

the polyfills are kind of lacking, last i checked

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

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

oh interesting

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

Safari now has partial support

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

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

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

well the best future proofing is DOM elements, no?

web components aren't even a thing yet

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

if they break the DOM API the whole web goes down

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

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

https://github.com/w3c/webcomponents

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

yep they are standard now

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

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

you dont want a multi GB html file

presumably you'd generate them via a JS API

agreed

from cljs or whatever

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

i like the idea of progressive web apps for sure

it's like the only way to really do cordova

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

yes

thats the goal i believe

10000% in favor of that

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

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

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

brave browser?

which tracking are you referring to?

https://www.bleepingcomputer.com/news/software/major-browsers-to-prevent-disabling-of-click-tracking-privacy-risk/

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