The C4WorkSpace class used to respond to touch events coming from its main view. It seems like these aren't being passed properly through the responder chain anymore.

The in C4WorkSpace.m following doesn't run (i.e. print to the console) when I touch the canvas.

-(void)touchesBegan {
    C4Log(@"workspace responding");
}

In C4UIControl.m the following works:

-(void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
    C4Log(@"C4UIControl responding");
}

The original pattern in C4Control.m was:

-(void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
    [super touchesBegan:touches withEvent:event];
    [self postNotification:@"touchesBegan"];
    [self touchesBegan];
}

-(void)touchesBegan {
}

I think a link between the C4WorkSpace.m and its main view has been disconnected.

I took the compiled frameworks from the C4iOS project, added them the Library > Frameworks and then linked them into a new project. (NOTE: I'm setting up a project that links libs so that I can recreate it as a template that we can load from an installer).

My main ViewController looks like:

import UIKit
import C4Core
import C4UI
import C4Animation

class ViewController: C4CanvasController {
    override func setup() {

    }
}

I get the following two errors:

'C4CanvasController' is unavailable: cannot find Swift declaration for this class

Method does not override any method from its superclass

Also, I receive the following warning when only linking the projects (i.e. not calling any classes or methods from them):

(null): Ld: warning: ld: warning: ignoring file /Library/Frameworks/C4Core.framework/C4Core, missing required architecture x86_64 in file /Library/Frameworks/C4Core.framework/C4Core (2 slices)ignoring file /Library/Frameworks/C4UI.framework/C4UI, missing required architecture x86_64 in file /Library/Frameworks/C4UI.framework/C4UI (2 slices)ignoring file /Library/Frameworks/C4Animation.framework/C4Animation, missing required architecture x86_64 in file /Library/Frameworks/C4Animation.framework/C4Animation (2 slices)

Instead of setting the background of a specific shape, it might be better to use pattern images to fill the shape, instead of the current approach.

However, I see a problem with using pattern images: They default to rendering from {0,0}, and depending on the shape's current location (ie. in cases like C4Star, the layer origin of the shape often isn't at {0,0}. This results in the following:

override func setup() {
    let star = C4Star(center: canvas.center, pointCount: 10, innerRadius: 50, outerRadius: 80)
    let g = C4Gradient(frame: star.frame, colors: [C4Blue, C4Pink])
    let i = g.render()!
    star.fillColor = C4Color(UIColor(patternImage: i.uiimage))
    canvas.add(star)
}

4s

5

6

The same code produces varying effects on different screen sizes.

I cannot get C4 running in my new Xcode project. Since the installer isn't working for (the current version of) Xcode anymore, how can I set up a project? I don't find any instructions for that. Can you give me some instructions how I accomplish adding the dependencies?

Thanks!

When adding a gesture to a view, and setting the target as self (i.e. C4View)

internal var tapRecognizer: UITapGestureRecognizer = UITapGestureRecognizer(target: self, action: Selector("handleTap:"))

I get the following error:

Type 'C4View -> () -> C4View!' does not conform to protocol 'AnyObject'

I tried the following:

internal var tapRecognizer: UITapGestureRecognizer = UITapGestureRecognizer()

public var interactionEnabled: Bool = true

public func onTap(run: TapAction) {
    self.tapAction = run
    tapRecognizer = UITapGestureRecognizer(target: self, action:Selector("handleTap:"))
    tapRecognizer.delegate = self
    self.view.addGestureRecognizer(tapRecognizer)
}

internal func handleTap(gesture: UITapGestureRecognizer) {
    C4Log("handle")
}

The view loads onto the canvas, but when I tap it I get a general crash that looks like:

I also tried:

    internal lazy var tapAction: TapAction = { (location: C4Point) -> Void in }
    internal lazy var tapRecognizer: UITapGestureRecognizer = {
        let recognizer = UITapGestureRecognizer(target: self, action:Selector("handleTap:"))
        recognizer.delegate = self
        return recognizer
    }()

    public func onTap(run: TapAction) {
        self.tapAction = run
        self.view.addGestureRecognizer(tapRecognizer)
    }

    internal func handleTap(gesture: UITapGestureRecognizer) {
        C4Log("handle")
    }

We should have a list of new simple apps that we can upload to the store.

They NEED TO BE shit-hot.

• let's make a list of ideas
• let's evaluate that list and identify the best concepts, easiest to make
• let's come up with a potential schedule for working on simple things and releasing them

I have tested the following with C4Button, C4Slider, UIButton and UISlider.

Problem: When I touch and hold on a UI element, the object automatically cancels the touch after approximately 0.25s. This happens with all the objects above.

Here is some code that replicates this:

#import "C4WorkSpace.h"

@implementation C4WorkSpace {
    UIButton *button;
    UISlider *slider;
}

-(void)setup {
    [self addButton];
//    [self addSlider];
}

-(void)down {
    C4Log(NSStringFromSelector(_cmd));
}

-(void)upInside {
    C4Log(NSStringFromSelector(_cmd));
}

-(void)cancel {
    C4Log(NSStringFromSelector(_cmd));
}

-(void)upOutside {
    C4Log(NSStringFromSelector(_cmd));
}

-(void)addButton {
    button = [UIButton buttonWithType:UIButtonTypeRoundedRect];
    button.frame = CGRectMake(0, 0, 100, 44);
    [button setTitle:@"button" forState:UIControlStateNormal];
    button.center = self.canvas.center;

    [button addTarget:self action:@selector(down) forControlEvents:UIControlEventTouchDown];
    [button addTarget:self action:@selector(upInside) forControlEvents:UIControlEventTouchUpInside];
    [button addTarget:self action:@selector(upOutside) forControlEvents:UIControlEventTouchUpOutside];
    [button addTarget:self action:@selector(cancel) forControlEvents:UIControlEventTouchCancel];
    button.exclusiveTouch = YES;

    [self.canvas addSubview:button];
}

-(void)addSlider {
    slider = [[UISlider alloc] initWithFrame:CGRectMake(0, 0, 320, 44)];
    slider.center = self.canvas.center;

    [slider addTarget:self action:@selector(down) forControlEvents:UIControlEventTouchDown];
    [slider addTarget:self action:@selector(upInside) forControlEvents:UIControlEventTouchUpInside];
    [slider addTarget:self action:@selector(upOutside) forControlEvents:UIControlEventTouchUpOutside];
    [slider addTarget:self action:@selector(cancel) forControlEvents:UIControlEventTouchCancel];

    [self.canvas addSubview:slider];
}

@end

I have tried adding a UIButton to a raw iOS Single-View project and the bug didn't happen.

I believe what's happening is that the Canvas (or some other object) is triggering cancel events for the buttons / sliders.

There is a logo and there are some colours. There is also a "tone" to the documentation (examples / tutorials). Are they all sufficient for reuse? Should we revisit these things, and if so:

• what does a modernized colour scheme look like?
• what does a modernized logo concept look like?
• what does a modernized tone for the project look like?
• let's describe a roadmap for evaluating the current state of the "look" of C4
• let's define a roadmap for re-inventing the look of C4

We should have a new plan for rebuilding an alpha-version of the Swift branch.

Questions:

• what does an architecture plan for this look like?
• can we use this plan to build out other components?
• can we include options for "plug-ins"?
• what does the current architecture plan look like? (i.e. i know there isn't one, but if there were one for the current version...)
• what holes are there in the current plan?
• what strengths are there in the current plan? and, can we reuse those?

I'm not sure how to submit a issue to Spec repo of CocoaPods.

I'm using:

• Xcode 7.3.1
• C4 1.1.0 (Pods)
• CocoaPods 1.0.1

My app is workng on iOS 9. But, on iOS 8, my app is crashed with logs:

dyld: Library not loaded: /System/Library/Frameworks/ReplayKit.framework/ReplayKit
  Referenced from: /path/to/myapp.app/Frameworks/C4.framework/C4
  Reason: image not found

Should C4.podspec.json file link a ReplayKit as optional framework?

  "weak_frameworks": [
    "ReplayKit"
  ],

This commit: https://github.com/C4Framework/C4iOS/commit/e41c71f560898b9a9454c9c802ec3a55ddba0857

Fixed #573, however it also added a new bug.

This is a 2-part problem.

First, I'm working with this in my main application setup():

override func setup() {
    let c = C4Circle(center: canvas.center, radius: 20)
    canvas.add(c)
}

I expect this to be placed in the center of my canvas.

However, I was getting this window:

In setup, I ran:

print(NSApplication.sharedApplication().windows[0].frame)

Which produced:

(235.0, 289.0, 480.0, 292.0)

Which is NOT where the window appears:

Turns out that my application's main window has a Restorable option in Interface Builder:

So I unchecked that and I get:

Which is ALSO not what the window should look like...

So, to HACK this I had to do the following:

In C4CanvasController, modify the import to include a variable for AppKit

#if os(iOS)
import UIKit
#elseif os(OSX)
import AppKit
var applicationDidLoad = false
#endif

Then, modify loadView() to the following:

public override func loadView() {
    #if os(OSX)
        if applicationDidLoad == false {
            let window = NSApplication.sharedApplication().windows[0]
            var bounds = window.frame
            bounds.origin = CGPointZero
            view = LayerView(frame: bounds)
            applicationDidLoad = true
        } else {
            view = LayerView(frame: CGRect(x: 0,y: 0,width: 50,height: 50))
        }
    #endif
}

Now I get:

Which is expected.

HOWEVER, the window alway reappears in the original spot determined by IB. Not, quite, what, I expect.

POSSIBLE SOLUTION

Implement a restorationClass per the NSWindow Reference

Yo my hard working amigos. Just a holler and notifying about this branch, with classic C4 and some all around goodies for creative fun. Packaged and fived.

If needing a set of hands to help, or up for noble price dynamite, don't be shy. This is for personal convenience and use. 🧨

Dynamite if together?

There is a lot of warning and errors when trying to build with xCode 9.2. Do you plan to release a new version ?

I'm a bit disappointed as I was really interested by the library...

addCompletionObserver warning: probably something it doesn't like about C4's implementation

Hack a UI switch errors: When importing the "hack a UI switch" tutorial files, there are a number of errors. Access modifier error that SwitchThumb cannot inherit from Circle because Circle is public, not open. Can be fixed by changing Circle class to open, but I suspect there are many such issues in the framework (ellipse is also a public class, but shape is open) addTarget method needs to be changed to the following: self.addTarget(self, action:#selector(toggle), for: UIControlEvents.valueChanged) toggle function needs to be exposed to objective-C -> @objc func toggle() { ... }

Swift 4 is out, and Xcode wants to upgrade it. There are ~8 warnings from not upgrading, but once it is upgraded, there will likely be more warnings/errors.

I'm pretty new to Swift, so please bare with!

Is it possible with c4 to 'export' as a project (I think with a .framework...?), to be imported into other xcode projects?

I've been referencing Swift -> React Native via this tutorial http://browniefed.com/blog/react-native-how-to-bridge-a-swift-view/

However am unsure whether C4 can be used like this, or whether it was intended for standalone use only.