Fork me on GitHub

hi @alandipert here i am. you advised me to come here on twitter


i am quite impressed by hoplon and i was wondering how it could be helpful in mobile cross platform dev


could anyone please give me some hints/methods/frameworks ? much appreciated. thank you


hi @jouerose , Alan is in a different time zone, you'll have to wait for him a bit. Could you elaborate on your question? What exactly is your use case?


thanks @xifi . basically, i would like to use clojure(script) to create cross platform mobile applications. if the method/framework works also for destop web then it is a dream come true.


being really a beginner, I was wondering what were the possibilities and ways to achieve such thing


if it has a "it just works" easiness for beginning, then it is another dream come true


hoplon is a collection of clojurescript libraries. Its main purpose is to aid building SPAs (single page applications), although you can really build anything web related


you're speaking of mobile, so you're probably thinking of JVM right? Or can one build js apps for android as well


i am thinking cross platform, no native stuff, so something js based is ok


I'm a newcomer in hoplon and web dev myself so I might not be able to help you too much. Hoplon is for building web pages, so I'm not sure if that's what you're looking for


is there a way to use hoplon to make mobile apps ?


i hope it is better formulated now


not that I know of, but I would let Micha or Alan answer that. Or maybe @onetom if he's around


not much to thank for really 😞


@jouerose: i think it's suitable, @micha built a mobil app with hoplon using


@alandipert: are you not in the US right now?


@xifi: i'm in the US, but was up really late debugging server problems 😞


@jouerose: You can definitely do a mobile app with hoplon using as alan indicated. Worked with @micha on one.


You get a bit of a hit on load time - but after that it’s pretty snappy. let’s you tap into some native code as well — like push notifications, etc.


Now that hoplon6/boot2 is stabilizing - hoping to get another simple hoplon app going soon.


@jouerose: ionic framework is tied in tightly with angular, isn’t it?


for the app - we used castra to communicate to the backend and stored data in datomic


@donmullen: yes i have read it is tied to angular


@jouerose: as dnolan indicated - diving into React Native if you’re just getting started is going to be a steep learning curve. @onetom ramped up his team with hoplon pretty quickly and has had some success with mobile - though I don’t think they have done the native wrapper - but you’d need to check with him. hoplon is very approachable - less complex than react — if you are thinking use mobile tech on mobile — best bet to learn quickly and dev quickly.


Hi all, is it possible to have a hoplon component attach to a div rather than replacing the whole page?


like, for example if I want to create a widget with defelem and then use it in some legacy html


@alandipert: sorry to hear that. Out of curiosity what language were you debugging and did you succeed?


@donmullen: thanks for your input. I find hoplon indeed approachable and if there is a way as i must dev quickly, at least it can get tied to clojure for the moment.


@jouerose: sorry to mislead you this morning, as I said I'm quite new in the web dev and didn't hear of stuff like or phonecap


@onetom: could you please let me know about how to use hoplon for mobile cross platform dev ? i would love to use clojure here onwards.


maybe one day clojure will parasite on more runtimes, like this


@upgradingdave: I believe that is part of future work — see — third item on API.


do I need to run a server in order to work with sqlite db files or is there an "offline" method one can use? I'm only doing things locally so the only reason I'd be running a server would be to serve db files, create new files etc, but all locally


@jouerose: my colleague, @peterromfeld was doing the hoplon mobile app, so he is the best to ask about it. it was just wrapped with not sure what donmullen meant by native wrapper though.


Allows you to write native modules as well - and call from w/in javascript


jouerose: re hoplon vs react: it's a lot easier and faster to learn hoplon than react. in fact i was not sure about which react wrapper should i use and spent a few days on learning about and trying out reagent, om, etc. then over night i've learnt and tried hoplon and later my colleagues picked it up in days too (after just learning clojure for about 2 weeks)


@jouerose: i will update the readme and make a example repo public, for react OM seems nice, but like @onetom said using hoplon is streight forward and you have your first app packaged and on the market in no time


only thing i didnt had time to look into was touch-events to improve performance on iOS devices


ill let you know tomorrow, i try to get our boss approval to open-source one of our apps (app-cost-calc), then you have real-life example, worst case i fire up something simple just to have an example for the workflow


@peterromfeld: did you integrate hammer.js at all?


i did not had time to dig deeper into it


but i wanted, just had other more pressing things to work on in the end


but there is cljsjs/hammer package if i remember so if you know hammer.js it should be super simple


@alandipert: Thanks for your work - finally got up and running locally - moving ahead with a Hoplon6 App:clap:


@micha : can you point me to the markdown code used in the hoplon website — (md ;;{{{ markdown here ;;;}}}) — it’s a macro right?


@micha: hoplon used to have a function val-id for getting the value of an input. how do we go about that now?


@raywillig: (deref evt) or just @evt


oh wait, i'm confused


for that i use (.val (js/jQuery "#id"))


@alandipert: cool thx for that. It's what I ended up doing but I thought there might be something idiomatic. Makes sense. I suppose I could just wrap that in some fn


yeah.. i find myself using it a lot less than in the beginning, preferring now to get val from event objects in callbacks


Oh yeah that makes sense. I was using inputs that weren't in a form trying to just do something quick and dirty.


(input :change #(doit @%))