Since the recent release of Catalina, macOS has shipped with the ability to allow iOS/iPAD apps to run on macOS without any modification via a featureset known as Project Catalyst.
This is exciting, as writing React Native + Clojurescript apps as a target for the desktop is much more compelling than a pure Electron app (imo).
| (ns frontend-re-frame.core | |
| (:require | |
| [re-frame.core :as re-frame] | |
| [reagent.core :as reagent] | |
| [reitit.core :as r] | |
| [reitit.coercion :as rc] | |
| [reitit.coercion.spec :as rss] | |
| [reitit.frontend :as rf] | |
| [reitit.frontend.controllers :as rfc] | |
| [reitit.frontend.easy :as rfe])) |
ClojureScript master now has cljs.core/eval. This delegates to cljs.core/*eval* which, by default throws, but you can bind it to any implementation that can compile and evaluate ClojureScript forms.
If you require the cljs.js namespace (which is the main support namespace for self-hosted ClojureScript), then cljs.core/*eval* is set to an implementation that uses self-hosted ClojureScript for this capability. This means that all self-hosted ClojureScript environments will now have a first-class eval implementation that just works. For example, Planck master:
$ planck -q
cljs.user=> (eval '(+ 2 3))
5
| ;; React supports "refs" as a way for a component to get a | |
| ;; handle to its children. Classically, refs were string-based. | |
| ;; Recent versions of React support callback attributes as a | |
| ;; more elegant variant of accessing DOM notes or components. | |
| ;; | |
| ;; This example uses a Form-3 component as per | |
| ;; https://github.com/Day8/re-frame/wiki/Creating-Reagent-Components | |
| ;; | |
| ;; For callback refs, see React's documentation | |
| ;; https://facebook.github.io/react/docs/more-about-refs.html |
| // paste in your console | |
| speechSynthesis.onvoiceschanged = function() { | |
| var msg = new SpeechSynthesisUtterance(); | |
| msg.voice = this.getVoices().filter(v => v.name == 'Cellos')[0]; | |
| msg.text = Object.keys(window).join(' '); | |
| this.speak(msg); | |
| }; |
| ''' | |
| Non-parametric computation of entropy and mutual-information | |
| Adapted by G Varoquaux for code created by R Brette, itself | |
| from several papers (see in the code). | |
| This code is maintained at https://github.com/mutualinfo/mutual_info | |
| Please download the latest code there, to have improvements and | |
| bug fixes. |
| { | |
| "metadata": { | |
| "name": "Three new matplotlib plots" | |
| }, | |
| "nbformat": 3, | |
| "nbformat_minor": 0, | |
| "worksheets": [ | |
| { | |
| "cells": [ | |
| { |
This was working on Vagrant 1.4.3 (Mac).
#HOST#
File: ~/.ssh/config
Host vagrant.*
ForwardAgent yes
File: Vagrantfile
| #! /usr/bin/env python2 | |
| # Requires: PIL, colormath | |
| # | |
| # Improved algorithm now automatically crops the image and uses much | |
| # better color matching | |
| from PIL import Image, ImageChops | |
| from colormath.color_conversions import convert_color | |
| from colormath.color_objects import LabColor | |
| from colormath.color_objects import sRGBColor as RGBColor |
http://amundsen.com/media-types/collection/examples/
This format takes into consideration collections (much like Siren). It also takes into consideration versioning. However, I'm not certain version matters in the data set if it pertains to an API version. That is best left being in the API URL. It could pertain to collection version, but I'm not sure the point. Documentation says each collection should have a version - but says nothing more about meaning or why.
Items are clearly distinct in this format and are organizationally positioned separate from links.
This is by far the most collision free structure.
However, the data format itself is a bit strange...Every field being an array. Data is always an array of objects. I understand the flexibility this presents and am not 100% against it. I just believe it's perhaps not needed as things could change based on the client application.