klassen-software-solutions / ksscore Goto Github PK

The module should initially include three modules:

1. KSSFoundation - items that depend only on Foundation
2. KSSCocoa - items that also depend on Cocoa
3. KSSUI - items that also depend on SwiftUI

The goal is to get a description of the differences between two texts in a manner that can be used to report on the differences.

See the Java Awaitility project

This will allow to be made consistent throughout our apps.

This should also involve deprecating the current error highlight values.

It seems the fix for bug 61 (empty standard input) has introduced a new bug where the standard input now appears to always be empty.

Implement a generic atomic property. See https://www.vadimbulavin.com/atomic-properties/ for some ideas.

The standalone="yes" item should only be included when there is a DTD. The XMLDocument class seems to default it to true.

In particular the action to be run when the button is clicked is added to a global list, and is not removed when the window is destroyed.

We may decide not to fix this since it is a very small amount of memory, however, if anyone does know of a way to handle it, we would be open to solutions.

Since test case methods now include "throws" it likely makes sense that our assertions also allow their lambdas to be throwable.

We can base this on Witness, but with a cleaner API.

This is mainly being done since Witness does not have a suitable tag and is small enough that writing our own is preferable to forking Witness just for the sake of adding a tag.

This should look and act similar to the chevron found in Numbers and other document type stuff.

Needed for WSTerminal

Extend the XCTest infrastructure to allow for more readable, lambda-based, tests.

At least for the easy items. Some of the UI stuff that needs a separate macOS and iOS implementation, but should have the same overall API, can wait.

See https://stackoverflow.com/questions/25207077/how-to-detect-if-os-x-is-in-dark-mode

The JSON standard states that escaping slashes is allowed, but is not necessary. So we should not do it as part of a pretty print. After all it definitely does not make the output "pretty".

The default icon should be the search (magnifying glass), but since the field may also be used as a filter, we should add that as an option. The correct icon for filter seems to be line.horizontal.3.decrease.circle from the SF Symbols. See the filter at the bottom of Xcode for an example.

This will involve the following:

• update the build system to support Swift modules
• add the license dependencies
• add the CI

With an Xcode build, opening the standard input with no input works properly, identifying the input stream as empty. However the command line build does not identify it as empty, but does report that 0 bytes were read.

Specifically, instead of using an estimate for the time frames, use Calendar and DateComponents to provide a more accurate result.

See DateExtension in EbedCore for an example.

Currently in swift the default initializers for classes (and structs) are internal.

Wrapper needs to have a public initializer.

By using let expectation = XCTestExpectation() and then wait(for: [expectation], timeout: timeout) these methods do not fit in as well as they should with other XCTestCase expectations.

These should be changed to use let expectation = self.expectation(... and waitForExpectations(....

In addition, adding a new method that does not automatically build an expectation, but just wraps the wait would also be useful.

• Case insensitive dictionary subscript
• Input stream reader
• Runtime platform identification
• Wrapper for passing pass-by-value objects
• Random test data generation

This should be given the following:

• an error
• a binding to a boolean that will cause the view to be dismissed

This will show the following:

• a warning icon
• an "An error has occurred" title
• a message based on the error, and
• a button that will dismiss the view

Perhaps an implementation of os_log?

Perhaps as an enum?

This would be a non-back-compatible API change, so for now we will deprecate the current API until the next major version.

Needed as an NSRange in order to work with NSRegularExpression

In KSSFoundation:

• AutoIncrementingInt (perhaps rename to 'Counter')

In KSSCocoa:

• NSFontExtension
• NSMenuExtension
• NSViewExtension
• NSWindowExtension
• NSApplicationExtension

In KSSUI:

• CommandTextField (rename to KSSCommandTextField)
• KSSTextView
• KSSWebView
• NativeButton (rename to KSSNativeButton)
• KSSURLTextField

I guess I've never done this, although I had promised it.