create convenience methods to update frame

[kambala-decapitator]

adding a category with convenience methods would simplify writing commonly used code to update one or more parameters of a frame, example:

// interface declaration is left to the reader as an exercise
@implementation UIView (FrameHelpers)

// this one could be called setOrigin
- (void)setX:(CGFloat)x y:(CGFloat)y {
  CGRect frame = self.frame;
  frame.origin = CGPointMake(x, y);
  self.frame = frame;
}

@end

// usage
[someView setX:42 y:someOffset];

you could also create a helper class like GeometryHelper to do the same but with any CGRect (if you have a need to operate on arbitrary rects and not just view frames) and then utilize it in the above category. In relation to this there're already some helper functions to modify CGRect: https://developer.apple.com/documentation/coregraphics/cggeometry?language=objc#Modifying-Rectangles

P.S. But with AutoLayout this is not needed :)

[wutschel]

Besides the frame manipulations, there are more possible candidates for extensions -- especially in the Utilities class, e.g. animations for UIView, average color or colorization of UIImage or even getting or modifying certain colors for UIColor. Most would be instance methods which even will improve code readability, example:

Before:

@implementation Utilities
+ (void)SetView:(UIView*)view Alpha:(CGFloat)alphavalue XPos:(int)X {
    view.alpha = alphavalue;
    CGRect frame = view.frame;
    frame.origin.x = X;
    view.frame = frame;
}
@end

// Use
[Utilities SetView:activeLayoutView Alpha:1.0 XPos:viewWidth];

After:

@implementation UIView (Extensions)
- (void)setX:(CGFloat)x alpha:(CGFloat)alpha {
    CGRect frame = self.frame;
    frame.origin.x = x;
    self.frame = frame;
    self.alpha = alpha;
}
@end

/ / Use
[activeLayoutView setX:viewWidth alpha:1.0];

Even for static methods I would prefer adding some for code readability. It is easier to grasp what the method is related to:

Before:

@implementation Utilities
+ (UIColor*)get1stLabelColor {
    if (@available(iOS 13.0, *)) {
        return UIColor.labelColor;
    }
    else {
        return RGBA(0, 0, 0, 1.0);
    }
}
@end

/ / Use
[Utilities get1stLabelColor];

After:

@implementation UIColor (Extensions)
+ (UIColor*)get1stLabelColor {
    if (@available(iOS 13.0, *)) {
        return UIColor.labelColor;
    }
    else {
        return RGBA(0, 0, 0, 1.0);
    }
}
@end

/ / Use
[UIColor get1stLabelColor];

@kambala-decapitator , should I go ahead with this?

[kambala-decapitator]

there are more possible candidates for extensions -- especially in the Utilities class

true. When I suggested to create those as categories, you weren't willing to ;)

should I go ahead with this?

absolutely!

[wutschel]

Not sure why I didn't recognize the elegance of this ...