muizidn / fastui Goto Github PK

Reproduce:
Potrait
Landscape
Potrait
Landscape

https://developer.apple.com/documentation/swiftui/offsetshape/3270918-edgesignoringsafearea

My first concern is to enable documentation generation using Linux machine #16
I don't want to waste their resource 😬

https://muizidn.github.io/FastUI

VStack {
  HStack()
}

This wont work https://forums.swift.org/t/function-builders/25167/53

As we don't really need ViewDSL in user facing API, we can safely remove them. It's better to implement inside the framework

https://texturegroup.org

https://developer.apple.com/documentation/swiftui/color

func configure is just a simple helper where direct method call to the api's causes confusion to the Swift compiler.

You may want to check it with

VStack {
  HStack()
    .foregroundColor(.blue)
    .flex_height(100)
}
.foregroundColor(.cyan)

Code above (with more view stacks being added) intermittently causes compiler to spits ambiguity error without clear direction to where the confusion occurs.

Sometimes, it can be resolved by switching the order of method call. Sure, it is very bad indeed. Because it hides the real problem and it will breaks soon. Once you change a code, it maybe won't compile again.

And also, the compiler seems to be confused and failed to interpret expression which normally will not happen. This is being investigated whether the source of problem is the lack of some keyword (because we can't use it) which results the abuse of protocol or the problem lies in the compiler itself.

Until the real fix shows up, we advice to use this function to configure SomeView instance. And yeah, this is the main source of @discardableResult attribute in all methods.

Try these?

1. https://github.com/google/EarlGrey
2. https://github.com/linkedin/bluepill

It seems user doesn't need it.
Remove!

The use of FastUIKit framework is to provide UIKit-subclasses that match the actual code description. This subclass will shows up in the Xcode view debugger hierarchy and we expect the there's no difference between the actual code and those that appear in the debugger navigator.

FastUI

FastUIKit Xcode Debugger Navigator

If it is possible to govern how Xcode display those classes, we can merge them to the main framework.

Flex Layout allows us to put margin to each sub-nodes.

Most interface are implemented for testing purpose. So most of them aren't completed yet.
Please file issues and if possible, your PR to complete those API's

User won't need it.

We can remove FlexLayout framework, but we need to implement Flex interface from inside the framework