From 93166f7b528ea75869351128e1f52df85d91aa4d Mon Sep 17 00:00:00 2001 From: Thomas Ruoff Date: Mon, 16 Sep 2019 00:14:36 +0200 Subject: [PATCH] add org presentation v1 --- .export/bw-functions.html | 236 ----------------------- .export/emacs.html | 382 -------------------------------------- 2 files changed, 618 deletions(-) delete mode 100644 .export/bw-functions.html delete mode 100644 .export/emacs.html diff --git a/.export/bw-functions.html b/.export/bw-functions.html deleted file mode 100644 index 6155ca5..0000000 --- a/.export/bw-functions.html +++ /dev/null @@ -1,236 +0,0 @@ - - - - -bw-cloud-functions - - - - - - - - - - - - - -
-
-

bw-cloud-functions

Thomas Ruoff

Created: 2019-08-13 Tue 23:18

-
- -
-
-

Logos in Analytics

-

-A Logo Query contains a set of logo versions. -

- -

-Our backend identifies them by an URL that resolves with a PNG of that logo -version. -

- -

-The URL and the PNG is controlled by Logograb (our logo detection provider). -

- -
-
-
-
-

Showing Logos in Analytics

-

-We show the logo versions in various places in Analytics, also in the chart exports. -

- -

-Though the PNGs used by Logograb are not optimized for displaying, especially -not on a whitish background. -

- -
-
-
-
-

1st try

-

-Detect whitish logos in the client and add a dark background if it’s a whitish -logo. -

- -
-
-
-
-

Problems

-

-Detection runs every single time a logo is shown. -

- -

-It runs on the client. -

- -

-We couldn’t make it work in certain places, especially in highcharts and -obviously exported charts. -

-
-
-
-
-

2nd try

-

-Move the detection and conversion to the server. -

- -
-
-
-
-

Wins

-

-Browser caches converted image. -

- -

-Client stays slim. -

- -

-We can just use an image URL in the frontend and chart export service. -

- -
-
-
-
-

Problems left

-

-Requested logos are cached only in memory. -

- -

-Not seperate -

- -
-
-
-
-

3rd try

-

-Frontend was moved to CDN while this happend. -

- -

-Cloudfront seemed to support what we needed: execute some JS when the response -of an origin came back, so we could place detection and conversion before -returning it to the client and storing it in the CDN. -

- -
-
-
-
-

no wins, just problems

-

-Turns out no way even access on the body, so no way to detect nor modify that -body. :( -

- -
-
-
-
-

4th try

-

-CDN directs logo URL calls directly to a cloud function. -

- -

-We use bw-cloud-functions to implement conversion and detection. -

- -
-
-
-
-

wins

-

-Re-used detection and conversion we already wrote in JS in the 2nd try. -

- -

-Super easy deployment -

- - -

-Still makes it’s way into the CDN store -

-
-
-
-
-

problems left

-

-Well, we misunderstood how a CDN actually works. It’s NOT a storage as it -removes content that is not requested often enough in a region, so just a very -small TTL in the cache. -

- -

-To be fair, it’s not too bad the costs for all logo versions we currently get is -still pretty low and does not really justify to spend more time on it. -

- -
-
-
-
-

5th try (to be done)

-

-Use cloud storage to store converted images and check there first, before doing -a fetch, detect an maybe do a conversion dance. -

-
-
-
-
-

Created by Thomas.

- - - - - diff --git a/.export/emacs.html b/.export/emacs.html deleted file mode 100644 index dbf07d6..0000000 --- a/.export/emacs.html +++ /dev/null @@ -1,382 +0,0 @@ - - - - - - - - - - - - - - - -
-
-

Created: 2019-08-12 Mon 23:09

-
-
- -
-

-To get a list of packages type M-x list-packages -

- -
-
-

1 to research

-
-
-
-
-

1.1 backup file location configurable?

-
-
-

1.2 highlight line

-
-
-

1.3 git gutter needed

-
-
-

1.4 what the hell is that footer thing you cannot edit?

-
-
-

1.5 C-o does not open last file, not sure why yet

-
-
-

1.6 persistant undo possible?

-
-
-

1.7 helm/ivy - dash?

-

-Still trying to figure what use-case each of these tries to -solve. I’m primarily looking for something that offers me an nice -interface to deal with all kind of lists of elements, like files, -buffers, commits, tags, grepper etc. -

- -

-I used to cover that all with vim.fzf and would again like to have -something like that. -

- -

-Though it seems, that I just need some inteface for lists of any -kind that I can easily fuzzy search. -

- -

-And other plugins to actually provide the content. -

- -
-
-

1.8 gruvbox-theme

-
-
-

1.9 which-key

-

-Seems great for learning the editor commands. But could also be -distracting -

- -
-
-

1.10 magit

-
-
-

1.11 language server protocol

-

-Mainly for my JS work, but probably worth to look at something -generic if there is something out there. -

- -
-
-

1.12 vim-unimpaired ?

-

-Couln’t find something replicating unimpaired until now. -

- -

-Maybe I just need to roll most of these on my own -

- -
-
-

1.13 vim-abolish ?

-
-
-

1.14 ranger/dired-ranger

-
-
-

1.15 devdocs

- -
-
-
-
-

2 installed packages

-
-
-
-
-

2.1 general

-
-
-
-
-

2.1.1 editorconfig

-
-
-

2.1.2 helm

-
-
-

2.1.3 projectile

-
-
-

2.1.4 magit

-
-
-

2.2 evil related

-
-
-
-
-

2.2.1 evil

-

-evil uses “state” for the “modes” in vi. The term “mode” is already used in emacs -for a set of key bindings for a cetrain sort of text. A “mode’ may include custom -bindings for evil states. -

- -

-The state is shown in the status bar. -

- -

-There is also an emacs state <E>, basically turn off evil, which you can -toggle with ’C-z’. -

- -

-I’ve heard numerous times that people claim evil covers 99% of what they use in vim. -[[evil-maps.el][~/.emacs.d/elpa/evil-20190729.704/evil-maps.el] is a good place -to start looking if something does not work for you. -

- -
-
-

2.2.2 evil-escape

-
-
-

2.2.3 evil-leader

-

-I was first not sure if I should even start using the leader key -as I did in my vim config, as it would again not bring me further -in learning the standard key bindings vim offers. -

- -

-This is still a valid point, but I also feel it will slow me down -quite a bit, now that I’m considering to switch to Emacs. -

- -

-So I’ll start with using it, but keep it very high in my priorities -to finally getting rid of it. -

- -

-This is pretty important, as I’m pretty sure that I’ll still be using -Vim in quite some remote systems. -

- -
-
-

2.2.4 evil-surround

-
-
-

2.2.5 evil-magit

-
-
-

2.2.6 evil-org

-
-
-

2.3 org-mode related

-
-
-
-
-

2.3.1 org-bullets

-

-UTF-8 bullets -

- -
-
-
-
-

3 considering packages

-
-
-
-
-

3.1 general

-
-
-

3.2 evil related

-
-
-
-
-

3.2.1 evil-args

-
-
-

3.2.2 evil-matchit

-
-
-

3.2.3 evil-collection

-

-This seems to use vim like keybindings in most common emacs -places. Not sure yet if this is a good idea. -

-
-
-

3.3 org-mode related

-
-
-
-
-

3.3.1 org-download

-

-image d’n’d -

-
-
-

3.3.2 org-gcal

-
-
-

3.3.3 org-jira

-
-
-

3.3.4 org-projectile

-
-
-

3.3.5 org-pandoc

-
-
-

3.3.6 org-reveal

-
-
-
-
- - - - -