The way I typically work is, I start the editor from the Terminal using lein run.
cd editor
lein runThen load a project as usual in the editor. If for example I wanted to explore the Sprite component, I'd create a new Sprite somewhere in the project and open it.
From Cursive, I have a Remote REPL run configuration set up, as detailed in our Cursive Setup Guide. When I run it, it will connect to the running editor process I started from the Terminal.
| Python - Competitive Programming Tricks |
| /* | |
| * Copyright (C) 2018 Square, Inc. | |
| * | |
| * Licensed under the Apache License, Version 2.0 (the "License"); | |
| * you may not use this file except in compliance with the License. | |
| * You may obtain a copy of the License at | |
| * | |
| * http://www.apache.org/licenses/LICENSE-2.0 | |
| * | |
| * Unless required by applicable law or agreed to in writing, software |
| api=28 | |
| branch=android-9.0.0_r3 | |
| mkdir android-sdk-source-build | |
| cd android-sdk-source-build | |
| mkdir -p frameworks/base | |
| # Fetch repositories that contain the sources we're interested in | |
| git clone --depth 1 https://android.googlesource.com/platform/frameworks/base -b $branch frameworks/base |
| [merge] | |
| tool = studio | |
| [mergetool "studio"] | |
| prompt = false | |
| cmd = /Applications/Android\\ Studio.app/Contents/MacOS/studio merge $(cd $(dirname "$LOCAL") && pwd)/$(basename "$LOCAL") $(cd $(dirname "$REMOTE") && pwd)/$(basename "$REMOTE") $(cd $(dirname "$BASE") && pwd)/$(basename "$BASE") $(cd $(dirname "$MERGED") && pwd)/$(basename "$MERGED") | |
| trustExitCode = true | |
| [diff] | |
| tool = studio | |
| [difftool "studio"] | |
| prompt = false |
The native UI toolkits on Android and iOS are frustratingly imperative. Unfortunately, there has been little architecture evolution (unlike the web). However, nothing(ish) is stopping us from bolting something "nice" on top. By nice I mean single-atom-state purely functional reactive composable UI components. In this post, I'll explain what this title means, the inspiration behind the design of the framework, an example component, and dive a little into the framework's implementation.
Right now, there only exists a Kotlin (Android) implementation, but a Swift port will be relatively straightforward and will happen soon.
| public class ExampleApplication extends Application { | |
| @Override public void onCreate() { | |
| super.onCreate(); | |
| try { | |
| Class<?> cls = Class.forName("android.sec.clipboard.ClipboardUIManager"); | |
| Method m = cls.getDeclaredMethod("getInstance", Context.class); | |
| Object o = m.invoke(null, this); | |
| } catch (Exception ignored) { } | |
| } | |
| } |
| #Check if an argument was supplied | |
| if [ -z "$1" ] | |
| then | |
| echo "No argument supplied, please provide video name" | |
| else | |
| # start recording | |
| adb shell screenrecord --bit-rate 6000000 /sdcard/$1.mp4 & | |
| # Get its PID | |
| PID=$! |
| #!/bin/bash | |
| ##################################################### | |
| # Name: Bash CheatSheet for Mac OSX | |
| # | |
| # A little overlook of the Bash basics | |
| # | |
| # Usage: | |
| # | |
| # Author: J. Le Coupanec | |
| # Date: 2014/11/04 |