Antranig Basman amb26

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog. Infusion from v2.0.0 onwards adheres to Semantic Versioning.

[Unreleased]

Framework

forgiving-data

What is this?

Algorithms for processing and relating data in ways which promote ownership, representation and inclusion, maintaining rather than effacing provenance. See slide 2 in presentation Openly authored data pipelines for a recap of Project WeCount's pluralistic data infrastructure goals.

How to use it?

forgiving-data

What is this?

Algorithms for processing and relating data in ways which promote ownership, representation and inclusion, maintaining rather than effacing provenance. See slide 1 in presentation Openly authored data pipelines for a recap of Project WeCount's pluralistic data infrastructure goals.

How to use it?

The Elm Architecture is the wrong abstraction for the web

In this article, I'd like to explain why I think The Elm Architecture is fine for small components, but quite harmful for websites based on pages.

Definition and Pros/Cons

First, let's clarify what I mean by "The Elm Architecture".

The Elm Architecture's webpage describes it pretty well.

Textfield Controls Client-Side Demo

This is a simple replication of the existing Textfield Controls demo hosted at https://build-infusion.fluidproject.org/demos/textfieldcontrol/ for the rewrite of the textfield controls components using the new renderer. Since this is a serverless demo, includes are written out in the old literal style, but this is not anticipated to be a common use pattern. Due to the lack of a server side, the fluid.resourceLoader.staticMountTable needs to be written out inline in the code so that the component can locate its templates. It's imagined that in other serverless contexts, some kind of rollup or webpack plugin will take responsibility for these.

To see the demo, browse to index.html using some form of static hosting.

IMERSS Bioinformatics Working Group Data Archive, Pipelines and Visualisations

This repository houses the working data of the IMERSS biodiversity informatics working group together with algorithms for transforming, reconciling and projecting observation and checklist data into formats suitable for publication, submission to global authorities such as GBIF, as well as map-based and graphical visualisations.

Data Archive

All data is stored in CSV files in subdirectories under data although some unprocessed checklist data is a variety of

	Problems with syncretic promotion - we handled post-advice, but not pre-advice.
	Consider the following:

	elements: {
	output: {
	type: "fluid.csvFileOutput",
	input: "{joined}.data",
	filePath: "outputData/output.csv",
	writeProvenance: true
	// provenance: "provenance.csv",

	1 i=0
	5 CLS
	10 SCALE 256,-189.5,-128
	20 FOR a=0 TO 100 STEP 5E-2
	30 i=i+1
	40 x=(((SIN(SQRT(a))COS(a/20))+1)255)
	50 y=(((SIN(a/20)+SIN(a^.7)+2))*31.5)
	55 x=INT(x+.5):y=INT(y+.5)
	57 BLOCK 2,1,x,y,i
	60 BLOCK 2,1,511-x,y,i

	/*
	Copyright The Infusion copyright holders
	See the AUTHORS.md file at the top-level directory of this distribution and at
	https://github.com/fluid-project/infusion/raw/main/AUTHORS.md.

	Licensed under the Educational Community License (ECL), Version 2.0 or the New
	BSD license. You may not use this file except in compliance with one these
	Licenses.

	You may obtain a copy of the ECL 2.0 License and BSD License at

	fluid.tests.switchUI.makeSwitch = function (enabled) {
	var togo = fluid.promise();
	var that = fluid.tests.switchUI(".flc-switchUI", {
	model: {
	enabled: enabled
	},
	listeners: {
	onCreate: function (that) {
	togo.resolve(that);
	}