chriseidhof

//
//  ContentView.swift
//  DeleteMe
//
//  Created by Chris Eidhof on 02.02.21.
//

import SwiftUI

/*

markosjal

Reverse Engineering the Apple Airscan / eSCL Protocol

I am not certain of the origins, one person involved in IPP printing claimed it was proprietary of HP , but then again they have their own protocol. AirScan/eSCL is used by other manufacturers too like Xerox, Kyocera, Canon and more. Mopria also seems to claim some responsibility for it but then again it seems not completely. In any case it seems shrouded in such secrecy that to date several years after its implementation, unless someone wants to take it all apart.

I offer this as my contribution. It is not perfect but almost there.

As I began looking for information to make a scanner more compatible, I could only find fragments of information. Even Apple Developer Forums offered zero help. 

Server/Client in eSCL / AirScan:
There is a “server”and a “client” the client can be a desktop computer or mobile device. The server is a scanner or another device configured to emulate a hardware scanner, even a desktop computer. In my case I did this on Linux, so

kenthumphries

#!/bin/sh

# This script embeds (and codesigns) a framework within an iOS app binary, but only when the configuration is Debug.
# It must be called from, or copied into an Xcode Run Script build phase with following setup:
# Input Files:
#     - Path to framework within project folder (source path)
#     - For example: $(SRCROOT)/ThirdPartyFrameworks/SimulatorStatusMagiciOS.framework
# Output Files:
#     - Desired path to framework within ${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH} (destination path)
#     - For example: ${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}/SimulatorStatusMagiciOS.framework

markiv

import Foundation

extension URLComponents {
    /// Abstracts away URLComponent’s array of URLQueryItems into a simple dictionary
    var parameters: [String: CustomStringConvertible] {
        get {
            return queryItems?.reduce(into: [String: String]()) { $0[$1.name] = $1.value } ?? [:]
        }
        set {
            queryItems = newValue.map { URLQueryItem(name: $0.key, value: String(describing: $0.value)) }

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

zlbruce

#!/bin/bash
echo "*** SVG 2 ICNS ***"
if [ $# -ne 1 ]; then
    echo "Usage:   svg2icns filename.svg"
    exit 100
fi
filename="$1"
name=${filename%.*}
ext=${filename##*.}
echo "processing: $name"

pdanford

Launching iTerm2 from macOS Finder

(Based on info from Peter Downs' gitub but with modified behavior to open a new terminal window for each invocation instead of reusing an already open window.)

The following three ways to launch an iTerm2 window from Finder have been tested on iTerm2 version 3+ running on macOS Mojave+.

pdanford - April 2020

---

bastman

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

hollance

Barfdown: a Markdown-ish Parser Written in Swift

Goals for this project:

• Parse a simplified version of Markdown that is good enough for writing my blog posts.
• Be reasonably efficient. This means the parser shouldn't copy substrings around if not necessary. This is done by storing all the elements as indexes into the original text.
• Be small and therefore be easy to understand.
• No regular expressions. They are the lazy person's solution to parsing. ;-)

This is just a toy project for me to experiment with writing parsers in Swift. Because why not?

genadyo

{
    "491289025" : "ijinshan-kappmarket://",
    "301521403" : "fb103361823069955://",
    "492178411" : "ils492178411://",
    "346142396" : "fb234434003713://",
    "310633997" : "whatsapp://",
    "370614765" : "com.condenet.newyorker://",
    "325058491" : "rnmddisco://",
    "382952264" : "epichttp://",
    "477048487" : "predictwind://",