Skip to content

Instantly share code, notes, and snippets.

<template>
<promised :promise="itemPromise">
<template v-slot:pending>
<b-spinner type="grow" class="w-25"/>
</template>
<template v-slot="item">
<b-row>
<b-col cols="12" lg="8" class="mb-3">
<b-card header="Edit">
<b-form>
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@02JanDal
02JanDal / Ovning_1.ipynb
Last active November 13, 2019 12:25
Python för Geodata
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@02JanDal
02JanDal / settings.yml
Created October 17, 2017 18:33
sportsed travis yml
os:
Windows:
Linux:
Macos:
Android:
api_level: ANY
iOS:
version: ["7.0", "7.1", "8.0", "8.1", "8.2", "8.3", "9.0", "9.1", "9.2", "9.3", "10.0", "10.1", "10.2", "10.3"]
FreeBSD:
SunOS:

Det vi har på Trossen just nu:

  • 2st Alto TS212 (aktiv fullrange, 550W RMS, 12")
  • 2st D.A.S. Factor12 (passiv fullrange, 200W RMS, 12") (i förrådet) inklusive passande slutsteg
  • 1st the t.racks. DS 2/4 x-cover (2in 4out)

Det vi hyrde till tältet under insparken (och vilket vi alltså vet fungerar bra):

update_url = ""
version = "0.0.1"
name = "LiteLoader"
author = "MultiMC authors"
id = "org.multimc.liteloader"
register_entity_provider({
id = "com.liteloader",
static_entities = {
{

How should versions be referenced internally?

Currently we have 2 attributes for version identification: name and timestamp. The name is used for cosmetic purposes; displaying in the UI etc., while the timestamp is used for ordering.

Now, the question is: how should versions be referenced internally? The available options are:

  • Using the name
  • Using the timestamp
  • Using a new attribute; ID
@02JanDal
02JanDal / Project Argonauts - Format.md
Last active August 29, 2015 14:26
Project Argonauts - Format

Project Argonauts - Format

This file contains thoughts, ideas and hopefully a format for Project Argonauts.

  • It should wrap around existing data as much as possible

Contents

  • Strictly declarative; nothing that "runs"
  • Type system with simple templates
for (int i = 1; i < argc; ++i)
{
const std::string arg = argv[i];
if (expectedArgument && arg[0] != '-')
{
items.back().hasArgument = true;
}
else
{
if (arg[0] == '-' && !noMoreOptions)
#!/usr/bin/env groovy
import groovy.json.internal.JsonFastParser
import groovy.transform.CompileStatic
import groovy.transform.Field
@Field
JsonFastParser jsonParser = new JsonFastParser(false, false, false, false)
@Field
char[] data = new File("json.json").text.toCharArray()