An IRC Channel would be nice to provide help and to talk.

This shouldn't be an issue for us since we never have gotten on the front page of the App Store or an App Store Editor Choice

My objc_tools library has view's for AV players which can do autoplay

https://github.com/scj643/objc_tools/blob/master/objc_tools/ui/av.py

You would want to use a PlayerLayerView

I am looking for people that are willing to contribute to my objc module that I've been making.

https://github.com/scj643/objc_tools

My plan is to have it be the definitive module for bridging with objc with simple python functions.

Also it could be used to store data that needs to survive an app reinstall potentially.

A dialog view with a side letter slider to quickly find items starting with a letter would be nice. Like how it works in the stock music app.

If anyone needs a bridge for SceneKit I have https://github.com/scj643/objc_tools/blob/master/objc_tools/scenekit/sk_scene.py

I've been working a lot with private libs and this one has stumped me.
THe way true tone overriding works is on the Info.plist as defined at https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW31

I want to be able to make it so I can change this during the runtime (sometimes i notice flickers of true tone turning off which is probably an iOS issue)

It doesn't actually say what type it wants
example

v = UIView.new()
v.setAlpha_('t')

Might be able to hack it in with objc_util Also one can install fonts system wide as well. Using a configuration payload.

It doesn't tell you what type it expected

I have found myself using objc_util a whole lot. Heck my pride and joy of a library is made with it

Some things I wish objc_util had are

Better ways of responding to blocks.

A block should have it's own accessible class that functions within the block can access. Also a block should be self contained and not having to push to a global variable

class Block(object):
    def __init__(self):
        self.someValue = 1
    def callOnFinish(self, passed_value):
        self.someValue = passed_value

Better type error handling

Currently objc_utils throws very cryptic errors when a type issue happens with an objc function. The type expected should be stated in the error

Error objects

If something has an option that is an NSError a built in part of objc_util should provide that. (I currently have an implementation but it's strange)

Though in all I'm still really happy with objc_util

I have started a really really rough base for an objc header parser. You would give it headers and it would give you formated enums for the constants in it.

http://nshipster.com/uikeycommand/ Seems subclasses need to be able to become first responders

@Evan03Davis I wouldn't use wikidot I would have some sort of github wiki

I plan on adding this feature to my objc_tools lib like many other features.