Skip to content

Instantly share code, notes, and snippets.

Jan Dalheimer 02JanDal

  • Sweden
Block or report user

Report or block 02JanDal

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@02JanDal
02JanDal / Ovning_1.ipynb
Last active Oct 17, 2019
Python för Geodata
View Ovning_1.ipynb
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 Oct 17, 2017
sportsed travis yml
View settings.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:
View jans-ljud-tankar.md

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):

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

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 Aug 29, 2015
Project Argonauts - Format
View Project Argonauts - Format.md

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
View cmdparser.cpp
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)
View json.groovy
#!/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()
View 4.0.0.192.json
{
"formatVersion": 0,
"uid": "net.minecraftforge",
"version": "4.0.0.192",
"time": 1345030349,
"requires": [
{
"uid": "net.minecraft",
"version": "1.3.2"
}
View 1.3.2.01.json
{
"formatVersion": 0,
"uid": "net.minecraftforge",
"version": "1.3.2.01",
"time": 1328269373,
"requires": [
{
"uid": "net.minecraft",
"version": "1.1"
}
You can’t perform that action at this time.