hansenccc/ypuikit-objc

Purpose and Entry Points

YPUIKit-ObjC is an Objective-C iOS CocoaPods library for rapidly assembling UIKit-based applications: reusable UI controls, presentation controllers, device/layout conventions, debugging/file tools, and selected platform services. Consumers import the umbrella API at YPUIKit-ObjC/Classes/YPUIKit.h; package definition is YPUIKit-ObjC.podspec. The runnable integration/sample app enters at Example/YPUIKit-ObjC/main.m and is bootstrapped by Example/YPUIKit-ObjC/YPAppDelegate.m.

Library Composition Boundary

Production code is organized as independently consumable UIKit modules beneath YPUIKit-ObjC/Classes. Most modules wrap or subclass UIKit rather than forming a single application domain. The pod boundary exposes the library; the Example/ application demonstrates integration and vendors CocoaPods dependencies, including LookinServer, which is not core library code.

• YPUIKit-ObjC/Classes/YPUIKit.h

• YPUIKit-ObjC.podspec

• Example/Podfile

Presentation and Input Stack

The primary reusable UI flow is: host view controller instantiates a component, configures properties/callbacks, then presents or embeds it in UIKit. YPPopupController supplies middle/bottom modal presentation and animated transitions; picker/date/color alerts are specialized popup consumers. Alert, loading, text input, and button controls provide common interaction primitives.

• YPUIKit-ObjC/Classes/YPPopupController/YPPopupController.m

• YPUIKit-ObjC/Classes/YPPopupController/YPPopupAnimatedTransitioning.m

• YPUIKit-ObjC/Classes/YPInputViewController/YPInputHeader.h

Shared UI Foundation

Layout/device adaptation is centralized in YPKitDefines, while YPViewController provides the project’s base controller abstraction. Category extensions add cross-cutting UIKit/Foundation behavior directly to standard types; this is a broad API surface and an important coupling boundary because extensions affect all importing code. Visual components such as progress, badges, floating controls, waterfall layout, and swipe views build atop UIKit.

• YPUIKit-ObjC/Classes/YPKitDefines/YPKitDefines.m

• YPUIKit-ObjC/Classes/YPViewController/YPViewController.m

• YPUIKit-ObjC/Classes/YPCategory/YPCategoryHeader.h

File Inspection and Local Persistence

The file-browser subsystem separates filesystem access/modeling from table-oriented presentation: file items and manager represent local content; proxy/view model/controller drive browsing UI and likely preview handoff. It operates against app-accessible local paths, providing a developer/debugging capability rather than a network-backed storage service.

• YPUIKit-ObjC/Classes/YPFileManager/YPFileManager.m

• YPUIKit-ObjC/Classes/YPFileListViewController/YPFileListViewModel.m

• YPUIKit-ObjC/Classes/YPFileListViewController/YPFileListViewController.m

Media and Device Services

Video playback is divided into source model, playback manager, container/controller, and composited controls for timeline, sound, brightness, and navigation. Separate managers expose iOS platform integrations: StoreKit-style purchase handling, Keychain-backed secrets, network reachability, and device shake feedback. These form explicit boundaries to Apple runtime services and device state.

• YPUIKit-ObjC/Classes/YPVideoPlayer/YPVideoPlayerManager.m

• YPUIKit-ObjC/Classes/YPPurchaseManager/YPPurchaseManager.m

• YPUIKit-ObjC/Classes/YPKeychain/YPKeychain.m

Runtime, Build, and External Infrastructure

The runtime is native Objective-C on iOS/UIKit, built through Xcode and distributed by CocoaPods. The sample workspace resolves the local pod and bundles LookinServer, an external in-app inspection server using Peertalk/USB transport; it is isolated under Example/Pods/ and should not be treated as a dependency architecture of YPUIKit itself.

• Example/YPUIKit-ObjC.xcworkspace/contents.xcworkspacedata

• Example/Pods/LookinServer/Src/Main/Server/LookinServer.h

• Example/Pods/LookinServer/Src/Main/Shared/Peertalk/Lookin_PTUSBHub.m