BigBagKbdTricks docs

DreymaR's Big Bag of Keyboard Tricks - The Web Pages

Web pages for dreymar.colemak.org

Info

  • See notes at the end of this page for more info.
  • Anchor links on the same page only need "#anchor", not the page url.

TODO/WIP for the BigBag Forum & web content (mostly for DreymaR's use):

  • Get help from Brick for formatting the image tables on the layers-base page.

    • Ask Brick for table formatting and CSS help!
    • Also some formatting (indent, auto-b/i, box?) on blockquotes.
    • HTML table notes:
      • The "title" property provides mouseover alt text for the different layout names.
      • The "caption" property is a heading. Need to sort out its color (for light/dark themes), though?
  • Convo w/ A-Brick on figure captions:

    • I just read a recommendation for figure text. On our BigBag pages, we've just used a

      under the image, with .

    • The recommendation was to use
      instead. Apparently, that makes images more searchable.
    • I suppose we'll need a little CSS magic then, to make the default italic and suchlike. [A-Brick: I'm gonna get on with it.]
  • Tabidots with an insight on why Keybr's progress algorithm is bad, on Reddit:

    • https://www.reddit.com/r/typing/comments/1lz2h84/comment/n2zxjc6/ It's based on your reaction time to the target key. This is especially important for non-home-row keys, because the algorithm will usually generate many words that start with the target key as well (so word + space + pause + word = no bueno). Your accuracy and speed for the rest does not matter.

      I realized this when I got stuck on P doing Colemak. Now that I've completed all the keys, I feel that this algorithm actually leads to bad habits because I stopped caring about accuracy just to unlock the next key. (And for a while I also got used to the fact the keybr simply ignores errors after the first one and freezes the cursor, so when you make a mistake you aren't "penalized" by having to press Backspace like you are IRL).

      [Sock_pup alias Nimi who develops Typecelerate commented:] You can cheat the algorithm by carefully approaching the combo and do them very fast. Doing everything else slow won't matter.

      That should tell you everything pretty much.

  • Platform box for Sequencing? And Modifiers?

    • Colemak-eD too?
    • Tarmak DOWNLOADS definitely should be boxed. But the Mac one doesn't show up?!
  • More likeable links?

  • Locale variants:

    • Add more of the Forum locale topic
    • I now put variant stuff in the EPKL repo, as that's where often I work with it. Link from the BBoT?
  • Contrast Compose to DKs.

    • DKs: Many, harder to reach them, single trigger. Help images in EPKL. Some positions hard to remember.
    • Compose: Often longer sequences, but more mnemonic. Can be kept on main layer.
  • Dictionary: Explain SFB, Curl/Angle/Wide, inward/outward/mixed rolls

  • Make Image2 and Image3 posts for the Image topic (topic 111)

    • Image2: Keyboard images. State licencing for SVG (CC) vs others (Public Domain)
    • Image3: Interesting designs, fun, logos, icons, etc
  • In tarmak.html, cannibalize part of the BIG BAG? HALP! section for a main page overview?

    • The rest of the bag is so easily and clearly accessible from the Tarmak page now
    • Also make platform boxes for the Tarmak implementations part

DONE

ON HOLD

  • Update some links with platform= syntax?
    • Maybe not necessary: The plaform files already have the platform selected, and other links are generally generic.

NOTES from symbols/colemak

These notes were in the symbols/colemak file, regarding Colemak_eD:

//  NOTE:
//  - Missing: U017F long s; chevrons; horizconnector; wynn/yogh; some African
//       d-tail; turned Cc/Ee++; latin epsilon/gamma (Berber); italic v;
//  - Rare/dropped: U25CA lozenge (Mac; rare); kra (deprecated Inuktitut & IPA);
//       union/intersection/includedin; integral (need a science/math deadkey; use esh in a pinch);
//       numerosign (mostly Cyrillic; use N + masc.); squareroot (unworkable); function (use hook-f);
//       U1E9E Capital German SS (disputed); U2033/U2032 double-/prime (cheat w/ acute/doubleacute?!)
//       U2639/U263A/U27E8/27E9 sadface/smilingface/brackets (poorly implemented)
//  - Oddly placed?: 'notsign'/'division' (placed by shape/association)?
//  TODO: Compose/deadkeys: ligatures (fi/fl/ij); fractions/superior/subscripts; latin/IPA/currencies
//  - For Currency: U2044 solidus/shilling; yen
//  - For IPA/Latin: U026A/028F SmCap-I/Y; U0251/0252 script-a/turned-script-a; U0283 esh
//       U028A lat-upsilon; U027E r-flap; U0294 glottal stop;  U025C turned open e
//  TODO: Make dead_stroke (for d/g/h/l/i/u) work!? Missing in compose files?
//        Also, l-tilde, s/c/j/z/schwa hook?
//  TODO: Unused dead_keys: iota, voiced_sound, semivoiced_sound
//        (could enhance them like Colemak user 'ghen' suggests, for keys 3/4/5?):
//  TODO: A Maths/science dead key? Latin/IPA? Greek? (Currency exists)
//  TODO: Add superior/subscript # to dead_acute/grave; fractions to slash/stroke!?
//      NB: This happens in the compose files under X11/locale, of which there are legion. :(
//      Can one get away with changing only the various iso8859-# ones? Or just en_US.UTF-8 ?
//      Since this lies outside the xkb folder, I might just post the code and where to paste it?
//  TODO: For extra dead key mappings, could dead_abovering and dead_doubleacute be augmented?
//      Make sure dead_hook has rhotic hooks for schwa and turned epsilon!
//      Similarly with smallcap letters and their turned counterparts?
//  TODO: Add IPA (broad English?) somewhere. Too few free slots, so it'll have to be by dead_keys.
//  TODO: Phonetic 'colemak_curl' layouts with Curl-DH (it's best to rewire the whole layout in this case).
//  DONE: Add Greek, Kyrillic and Hebrew phonetic Colemak layouts (nice for group 'switch' layout).
//  DONE: Update the Tarmak and Mirrored layouts when Colemak[eD] is changed, using search-replace.

These notes are fairly old and outdated by now. They still contain some interesting elements.

HTML observations

HTML tips from aBrickInTheHallway

• https://developer.mozilla.org/ - documentation for everything that has to do with HTML and CSS

• tag=element – the most used tags are:
<p> - paragraph
    <p class="italic">
<a href="https://your.url"> - link
    <a class="underlined">
<div class="quote">
<b>, <strong>   - bold
<i>, <em>       - italic
<img src="content/images/img.png" class="img-small"> ('alt' attribute is optional - displays when image cannot be displayed)
    <img class="left"....
ul - unordered list
ol - ordered list (1,2,3/a,b,c)
    <ul class="disc">
    <ul class="circle">

<span> - separates a text so you can style it, for example if you want part of a sentence to be crossed with a line, go
    <span class="linethrough">

• <!-- comment -->

• Spoiler template:
<div class="spoiler">
    <p><span>Spoiler:</span></p>
    <div class="spoiler-body">
        SPOILER CONTENT HERE
    </div>
</div>

• Platform box template:
<div class="platform-content">
    <p>
        
    </p><p>
        
    </p>
</div>

• To display the characters '<' and '>', use &lt; and &gt; so that they're not interpreted as parts of a tag

• For blocks of code use <pre><code>...</code><pre> and remove all indentation(tabs) left of the code in between these tags 
    because the tabs will be shown as these tags format literally every space, tab and new line.

Jekyll and Ruby for GitHub pages

[Note: This is a copy of my Evernote document "Jekyll and Ruby"]

Check Linux (Ubuntu), Ruby and Jekyll versions:

lsb_release -a
jekyll -v && ruby -v

As of 2023-02, GitHub pages have these dependencies: Jekyll 3.9.3; Ruby 2.7.4 https://pages.github.com/versions/

Install Jekyll with Ruby on Windows WSL Bash using the Brightbox repo, Gem and Bundler:

sudo apt-get update -y && sudo apt-get upgrade -y
sudo apt-add-repository ppa:brightbox/ruby-ng && sudo apt-get update
sudo apt-get install ruby2.7 ruby2.7-dev build-essential dh-autoreconf

echo 'export GEM_HOME=$HOME/gems/' >> ~/.bashrc && echo 'export PATH="$PATH:$HOME/gems/bin"' >> ~/.bashrc
source ~/.bashrc

gem update && gem install jekyll bundler && bundler update

• WSL can be a little stupid as to which Ruby version it uses, so it may be best to be specific as above. • Using apt-get install bundler on WSL installed an outdated Ruby version (1.9.1) so I guess I shouldn't do that! • Turns out it was because the WSL Ubuntu hadn't been updated in ages.

To avoid permission errors on the gem commands (write permission for /var/lib/gems/2.6.0/): Using sudo gem seems to work but isn't recommended! Instead, add this to your ~/.bashrc file, as shown above:

export GEM_HOME=$HOME/gems
export PATH=$HOME/gems/bin:$PATH

Now, go to the web root folder in the BigBagKbdTrix repo (not repo root but docs!) and build with Jekyll:

source ~/.bashrc
jekyll build
jekyll serve --watch

• I didn't need bundle exec in front of the jekyll commands. • At a later point, there was a version mismatch between the Gemfile (with GitHub Pages settings) and local installs. • When that happened, using bundle exec jekyll etc worked.

When you see 'Server running...', you should be able to browse the site locally on 127.0.0.1: http://localhost:4000/

Word has it, GitHub Pages don't support Jekyll v4+? So edit your Gemfile for realistic local builds:

# This will help ensure the proper Jekyll version is running. 
# gem "jekyll", "~> 4.2.0" 
...
# If you want to use GitHub Pages, remove the "gem "jekyll"" above and 
# uncomment the line below. To upgrade, run `bundle update github-pages`. 
gem "github-pages", group: :jekyll_plugins

GitHub Pages don't use either Gemfile nor Gemfile.lock, but their own Jekyll settings. So these files are relevant for local builds only.

gem install github-pages

"A simple Ruby Gem to bootstrap dependencies for setting up and maintaining a local Jekyll environment in sync with GitHub Pages". Sounds useful. I couldn't install it because of some incompatible library error, though...