This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aatree (1)
- # alda (1)
- # announcements (3)
- # beginners (10)
- # boot (44)
- # braid-chat (6)
- # cbus (5)
- # cider (19)
- # cljs-dev (5)
- # cljsrn (11)
- # clojure (203)
- # clojure-austria (1)
- # clojure-canada (1)
- # clojure-germany (2)
- # clojure-poland (46)
- # clojure-russia (38)
- # clojurescript (79)
- # clojuresque (2)
- # code-reviews (11)
- # core-async (6)
- # cursive (11)
- # datomic (12)
- # dirac (91)
- # hoplon (8)
- # juxt (14)
- # ldnclj (7)
- # lein-figwheel (6)
- # leiningen (18)
- # off-topic (3)
- # om (230)
- # om-next (7)
- # onyx (31)
- # parinfer (1)
- # proton (1)
- # re-frame (44)
- # reagent (2)
- # rethinkdb (10)
- # spacemacs (5)
- # yada (24)
@jaen: I did some exploration of chromium sources and there is no flag which should prevent device discovery/functionality in dirac. It seems that all the functionality is implemented on “backend” side, and devtools just query it over the protocol. There should be no difference between remote or bundled.
if you still have that diract setup, here is one thing you could try:
1) on <chrome://extensions> open Dirac DevTools options dialog and change it to open
as a new window
2) open dirac
3) in the url you should see something like:
replace it with
just keep the ws parameter
4) you should see internal (bundled) devtools running in external window instead of Dirac devtools using remote debugging protocol (the panel highlighting underline is blue instead of green)
5) now you can test it again
unfortunately I don’t have any android device, so I’m unable to test it here on my machine
@darwin: I don't even have any smartphone, I just test with an emulator, Chrome picks that up as a normal device, so this should be testable w/it. I'll try what you say today and see if that helps.
@jaen could you please point me to the emulator you are using? I’m not familiar with Cordova / Android development. Just tell me what to install so I can test it too
Just the usual Android emulator from the SDK. You can find sample Cordova app here - https://github.com/enterlab/cordevicljs/
After you install the Android SDK, create a VM with
android avd and run it, Cordova should be able to deploy inside it when you do
cordova run android.
I don't think I can say much more apart from "a hybrid mobile application client for someone".
Since you're here, is the 47 hard dependency for mobile formatters? I remember it working with older versions?
that feature had some development over 3-4 months early in 2015, it was hidden behind experimental flag, so it was present, but wasn’t exposed
I’m trying to create a new emulated device via that android avd gui, but the target select box is empty, how do I get some targets?, I used
brew install android-sdk
Also, make sure you have the appropriate paths in PATH:
It'll be of course somewhat different for a Mac, but probably the three same subdirectories
Cordova didn't work for me at first until I realised I missed one of the subdirectories that contained
adb I think.
BTW the user agent is: "Mozilla/5.0 (Linux; Android 6.0; Android SDK built for x86_64 Build/MASTER; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/44.0.2403.119 Safari/537.36"
cljs-devtools tests the user agent though, what do you think about a
:skip-version-check parameter to the install function?
You sure it doesn't test though?, I'm getting this:
core.js:15 Feature 'custom-formatters' cannot be installed. Unsupported browser Mozilla/5.0 (Linux; Android 6.0; Android SDK built for x86_64 Build/MASTER; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/44.0.2403.119 Safari/537.36.
you are right I do check for it here: https://github.com/binaryage/cljs-devtools/blob/master/src/devtools/custom_formatters.cljs#L13
from the top of my head:
(set! js/devtools.custom_formatters “available_QMARK_" (constantly true))
Well, it does skip the check, but they don't seem to be working unfortunately. Thanks for the help though!
Yes, I remember all that, been using
cljs-devtools back then too. It just seems there's no options in settings for that when I open device inspector.
btw. I was able to use custom formatters in pretty old Electron build (in Atom editor) back in Aug
I'm not sure what it's called, it's what happens when you do
More tools -> Inspect Device… then choose the device and click
ok, maybe you have slightly incompatible devtools with the “backend” running in the phone
you should try to refresh the page in the phone after you connect the devtools, that custom formatter enabling switch has to propagate somehow to the “backend"
Yeah, but the "inspect" devtools don't have option to enable them, so maybe it's just something that's not supported either in 44 or when inspecting a device.
ah, maybe 44 was release in Aug 2015, but it actually compiled much older code, let me see
I’m trying to figure out what exact version of code was compile in there. I think you could try to use older devtools build. Download chrome 44 and try to enable custom formatters there
I think matching version of chrome-devtools and remote backend has higher chance of success.
also if you don’t find custom formatters option there (after that shift trick), it means it is probably not yet avail
Yeah, I'll try that later; though probably I'll have to accept that debugging a hybrid app won't be as nice as debugging a web app after all.
I'm curious if it would be better with React Native or not, but I don't have anything to test that with ATM.
the support for CFs is just a question of time, until Android decides to include more recent version of Chrome
Yeah, but I'm running 6.0 in the emulator and it reports as 44, so it'll probably be a while yet.
maybe try this inside the phone? http://android-developers.blogspot.cz/2015/02/beta-channel-for-android-webview.html
The emulator doesn't seem to have Google Play but I'll keep experimenting, thanks for the pointers
The group (https://plus.google.com/communities/105434725573080290360) says it's currently 49 so if I get the store working it might be helpful