mturley

Start with a fresh Ubuntu Server 16.04 installation. NOTE: In the commands and files below, be sure to replace <yourusername> with your username and <yourgroupname> with your group name (probably the same as your username). Also, replace <yourhostname> with your server's hostname.

Install Dependencies:

• Add the latest mono apt source (from instructions at http://www.mono-project.com/download/#download-lin-ubuntu):

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/ubuntu xenial main" | sudo tee /etc/apt/sources.list.d/mono-official.list
sudo apt update

mturley

I just wanted to write down my thoughts about a possibly-naive but simple approach we could theoretically take to support PF4/PF5/Next component styles existing on the same page.

To be clear: I have not learned much about CSS layers or CSS modules, so this may be better achieved with something fancier. However, this would work without any browser compatibility concerns.

Proposal:

• We release a transitional compatibility-version of PF4 that is identical to the last PF4 version except for the addition of .pf-v-4 version classes on every component/layout style rule.
  • This is technically a breaking change for core CSS/HTML consumers, but React consumers could simply upgrade the packages and not have to change their usage at all (component APIs would remain identical, the rendered DOM would match the new CSS).
• If we are adhering to proper BEM classes for descenant elements of a component/layout, we should only need to apply this special class to the top of each component/layout unless we need to suppo

mturley

#!/bin/sh

minikube config set memory 10240
minikube config set cpus 4

minikube stop

minikube delete

minikube start --addons=dashboard --addons=ingress --addons=olm

mturley

OpenShift Console Extension Types

1. console.action/filter
2. console.action/group
3. console.action/provider
4. console.action/resource-provider
5. console.alert-action
6. console.catalog/item-filter
7. console.catalog/item-metadata
8. console.catalog/item-provider

mturley

This is copied from https://unpkg.com/browse/@openshift-console/dynamic-plugin-sdk@0.0.3/doc/console-extensions.md Pasted here to render the markdown for easier reference before it is published somewhere official.

---

OpenShift Console Extension Types

1. console.action/filter
2. console.action/group
3. console.action/provider

mturley

/*
  Jenn, I was looking back on the github examples I gave you and realized one more thing:
  If you didn't know it already, the ES6 arrow function syntax, has two shorthands
  the first one I showed in my example already:
*/

const arrowFn = () => { };

const arrowFn = () => { return thing; };

mturley

Hi guys, let me know if there is a more appropriate channel for this but I figured we could have a place for async discussion around the Kogito PF stuff within UXD.

For those who want to set up and run the Kogito UI code locally, it's pretty simple. Here's how you can pull down the branches I've been working on with Ajay:

git clone https://github.com/kiegroup/kogito-apps
cd kogito-apps
git remote add mturley https://github.com/mturley/kogito-apps
git fetch mturley
git checkout KOGITO-new-tabledesign

mturley

#!/usr/bin/env bash

pwd
mkdir -p ./__tests__
for file in *
do
  if test -f "$file" && [[ $file == *.js ]]
  then
    testfile="./__tests__/${file/\.js/.test.js}"
    if test -f "$testfile"

mturley

Imperative vs Declarative Programming

The Value of React for Developers

Writing code for what we want the page to do, not how we want the browser to do it.

Basic concepts

I've been working on how to try and explain the fundamental difference between the following two concepts of how programming the interactions on a web page can be done. It's important to grasp both in order to understand the main benefit of React from a developer's perspective. There are also design benefits of React such as the ability to reuse and compose isolated components, but that is beyond the scope of this document.

mturley

ERROR in /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-utils/dist/validateWithCustomRules.js
Module not found: Error: Can't resolve 'graphql/validation/rules/ExecutableDefinitions' in '/Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/node_modules/graphql-language-service-utils/dist'
 @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-utils/dist/validateWithCustomRules.js 20:18-75
 @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-utils/dist/index.js
 @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-interface/dist/getDefinition.js
 @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-interface/dist/index.js
 @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/codemir