kikito

Single executable which works out-of-the box.

• Extra libraries could add extra features. I/e if no regex library available, then only text is available.
• Space for logs/temp files. If not available/writable, editor is still able to work, with diminished functions.

Plugin-based

• Core functionality is single-file, single-screen editing, with client-server. Almost everything else is plugins.
• Should have good defaults. Not minimal, but can be made minimal. Not an IDE either. Walk the thin line.
• You can replace core plubins with other plugins from the community

kikito

Thump, Pop, Sizzle

https://sb.bitsnbites.eu/?data=U0JveAwC7dkxSgNBFAbgf3Y3sRDs0ghKwGK9gQeIYONZbMTOIq1s-tReRDyHl1k1u6gB0cIiGL5vePMeU04zMH81Sw4yr9PflfQ3KWmmZ9mojlLa68n7eLrx8Db9VAAAAAAA7Eb3SwHwvTrL1JfLlJemaZNy0ZRqcXv_tJi25XiwT8_EMHdbHQAAAIB_bz3W577dAQC2VeerkqySfnI4G47qx-fMk6uSk4Fb2q1uTPO6j1SvG0M_IR8AAAAA_FU3rq9T_MAB7L1X

kikito

• a list

• of items with paragraphs

• another item with a paragraph

  and another line

• and now a last item

• this time with a subitem

kikito

[
  {
    "traceId": "5ab6dfe40fd2d7844cceed129c087c01",
    "parentId": "9258d475e01f9b85",
    "id": "5f65af42e0735adf",
    "name": "get (balancer try 1)",
    "timestamp": 1578931517364000,
    "localEndpoint": {
      "serviceName": "kong"
    },

kikito

kikito

Ok here's what I recommend for before watching Blade Runner 2049:

• Watch Blade Runner: The Final Cut (from 2007). Beware that there are other versions but they are worse. The original one that aired on the cinema was especially bad, since they changed the ending to make it "happy".

• Listen to this episode of iddle weekend (they start discussing BRTFC @ 54:40).

• There's actually more things you can watch before BR 2049; they created 3 free short movies as well. They "link" the events between the original one and the new one. Here they are:

  1. Black Out 2022

2. 2036: Nexus Dawn

kikito

An UI has several parts:

1. The "Layout": Defines the space each control takes. "This button is 32x32 px and is located in 100,100"
2. The "Function": what happens when a control is used. "This needs to happen when this button is pressed"
3. The "Skin": how each control is displayed. "This button, with this state, is a red circle"
4. Bells and whistles: Things like state animations, or playing a sound when a button is hovered.
5. Current focus.
6. A way to handle input: Move focus to next item. "There is a pointer pressing on this position".

Problems:

kikito

What I would change about busted

This document describes my thoughts on busted. My opinion on the tool is an ever-evolving thing, so these are not set in stone. I am writing them here to encourage discussion, more than to convince anyone.

1. Remove the "automatic Lua detection logic"

(This might have been removed on latest busted versions)

busted does this thing where it "tries to be smart" and use the "most appropiate" version of Lua available on your system.

kikito

Process:               love [50818]
Path:                  /Users/USER/Downloads/*/Wanderer.app/Contents/MacOS/love
Identifier:            com.RedCloakGames.Wanderer
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           love [50818]
User ID:               501

Date/Time:             2015-09-21 22:03:37.327 +0200

kikito

Kaminari.configure do |config|
  # config.default_per_page = 25
  # config.max_per_page = nil
  # config.window = 4
  # config.outer_window = 0
  # config.left = 0
  # config.right = 0
  # config.page_method_name = :page
  # config.param_name = :page
end