nikku

[
  {
    "$schema": "https://unpkg.com/@camunda/zeebe-element-templates-json-schema/resources/schema.json",
    "name": "REST Connector",
    "id": "io.camunda.connectors.HttpJson.v2",
    "description": "Invoke REST API",
    "version": 5,
    "icon": {
      "contents": "data:image/svg+xml;utf8,%3Csvg%20width%3D%2218%22%20height%3D%2218%22%20viewBox%3D%220%200%2018%2018%22%20fill%3D%22none%22%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%3E%0A%3Cpath%20d%3D%22M17.0335%208.99997C17.0335%2013.4475%2013.4281%2017.0529%208.98065%2017.0529C4.53316%2017.0529%200.927765%2013.4475%200.927765%208.99997C0.927765%204.55248%204.53316%200.947083%208.98065%200.947083C13.4281%200.947083%2017.0335%204.55248%2017.0335%208.99997Z%22%20fill%3D%22%23505562%22%2F%3E%0A%3Cpath%20d%3D%22M4.93126%2014.1571L6.78106%203.71471H10.1375C11.1917%203.71471%2011.9824%203.98323%2012.5095%204.52027C13.0465%205.04736%2013.315%205.73358%2013.315%206.57892C13.315%207.44414%2013.0714%208.15522%2012.5841%208.71215C12.1067%209.25913%2011.

nikku

Use Semantic HTML Elements

TLDR

Understand the semantic elements that HTML offers and use them in favor of divs

Clickable <div />? Try not to do it, if it clearly is a UI control.

Consider: Not every element that is clickable must be a UI control but every click action needs to be accessible from a UI control.

nikku

Learnings From Debugging the Undebuggable

TLDR: Do NOT Compile Java on the Fly

Nico Rehwaldt

---

Context

nikku

#!/usr/bin/env bash

shopt -s globstar

# loop all files to perform transformation
for i in lib/**/*.js
do
  echo "Processing $i"

  # we need to replace occurences of default function exports, as lebab does not support them:

nikku

XML (vs HTML)

• VALIDATED AGAINST XML SCHEMA (XSD)

Each element is attached to more or less wellknown (moddle/moddle-xml speak) namespace

Namespaces in BPMN (common) => We have our own schema for them (moddle descriptors)

• BPMN
• BPMNDI

nikku

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/" xmlns:dmndi="https://www.omg.org/spec/DMN/20191111/DMNDI/" xmlns:dc="http://www.omg.org/spec/DMN/20180521/DC/" id="Definitions_1" name="Definitions_1">
  <decision id="Decision_1" name="Decision_1" />
  <dmndi:DMNDI>
    <dmndi:DMNDiagram id="DMNDiagram_0docyxs">
      <dmndi:DMNShape id="DMNShape_1gx1owo" dmnElementRef="Decision_1">
        <dc:Bounds height="80" width="180" x="100" y="100" />
      </dmndi:DMNShape>
    </dmndi:DMNDiagram>
  </dmndi:DMNDI>

nikku

Proposal: Improve Test Result Context Representation

It's currently harder than it should be to interpret the test results in the DMN TCK.

Context

The following expected test result

nikku

Bundled Sizes of bpmn-js

Version	Modeler	Viewer	Changes
1.0.0			v1.0.0...v2.0.0
2.0.0			v2.0.0...v3.0.0
3.0.0		![size](https://badgen.net/badgesize/gzip/https://unpkg.com/browse/bpmn-js@3.0.0/dist/bpmn-viewer

nikku

import { React, ReactDOM, Fill, registerBpmnJSPlugin } from 'camunda-modeler-plugin-helpers';

function BpmnModelerPlugin(eventBus, tabContext) {

  class AppPlugin extends React.Component {

    constructor(props) {
      super(props);

      this.tabContext = props.tabContext;

nikku

#!/bin/bash

TMP_NAME=$(mktemp -u ~/Downloads/capture.XXXXXX)

TMP_AVI="${TMP_NAME}.avi"
TMP_GIF="${TMP_NAME}.gif"
TMP_GIF_OPTIMIZED="${TMP_NAME}_optimized.gif"

print_usage()
{