opensource-apple / objc4 Goto Github PK

Is your feature request related to a problem? Please describe.
In ownCloud app we have a comprehensive set of settings which can be used for branding, MDM, configuration during development. AppConfig spec files are maintained manually.

When a new setting is added or an existing setting is changed in code, class settings metadata should be used to automatically generate an updated version of the AppConfig spec file.

Describe the solution you'd like
A script, unit test or tool using the OCClassSettings metadata to generate the AppConfig spec XML files automatically.

It should generate different versions with varying degrees of detail/sets of settings based on the status.

RELATED ISSUES

#755 on automatic generation of documentation from metadata.

TASKS

• Research (if needed)
• Create branch feature/feature_name
• Development tasks
  • Implement whatever
  • ...
• Code review and apply changes requested
• Design test plan
• QA
• Merge branch feature/feature_name into master

Originally posted by @felix-schwarz in owncloud/ios-app#842

Apple have moved the files on https://opensource.apple.com/ to GitHub, so official git history is now available in: https://github.com/apple-oss-distributions/objc4

Is it possible to calculate screen usage time with MDM?

Originally posted by @digitxo in mmorey/MDMCoreData#44

i want delete

Please provide instructions for compiling. I am struggling to compile the latest version (objc-647).

I tried to compile on OS X 10.10.5 with Xcode 7.0.1 using the MacOSX10.10.sdk (sdk 10.10 does not ship with Xcode 7 anymore) and the missing headers from https://github.com/samdmarshall/OSXPrivateSDK.

@aosm, @pajp, @Apple-FOSS-Mirror, @jevinskie, @bavarious, @cleexiang, @ConradIrwin, @csutanyu, @frtncr, @goreycn, @lafezhang, @Jeswang, @wpsteak, @j4n0, @UIKit0, @macmade, @brightsoftdev, @pljhonglu, @zqqf16, @KepenJ, @opensource-apple, @alexdonghang, @chenjiang3, @CyonLeu, @dqjk, @EvelynY, @fanliugen, @gavinkwoe, @guojin2020, @ilikeido, @imoldman, @J-Rojas, @kevleyski, @lexiaoyao20, @liufan321, @peakerWd, @syu6, @takanuva, @robertvojta:

There should only be one mirror of Apple's Objective-C repository here on GitHub, but I can currently attest to the existence of at least the following ten Objective-C mirrors on GitHub:

• aosm/objc4
• Apple-FOSS-Mirror/objc4
• bavarious/objc4
• chenniaoc/objc4-551.1
• j4n0/objc4-532
• Jeswang/objc4-532
• macmade/OBJC4-437.1-Runtime
• opensource-apple/objc4
• robertvojta/objc4

I have created a repository which I originally intended to use as a destination for a merger of all ten of the repositories listed above, but, being relatively new to GitHub, I initially had trouble doing so. My first problem was that I didn't originally know how to fetch the repositories I wanted to merge into my repository prior to going through such a merger, but I posted a question on Stack Overflow about this. The answer to it which I received was sufficient enough that I could then move on with my octopus merge by starting with the repository containing the oldest copy of any portion of Apple's Objective-C repository. This would be GitHub user macmade's OBJC4-437.1-Runtime repository. That repository, unfortunately, only contains the contents of Objective-C v4r437.1's 'runtime' folder. As such, I had to add it to this branch of my repository as this sub-module. I have already discussed how I might merge the branch containing this sub-module into my Objective-C repository's 'master' branch here.
I already tried going through the procedure outlined here to get the results which the last comment on the answer to that question said I would want, but I reverted this change because it looked to me as if I might have done something wrong in the process since it didn't reassign the original repository's forks to my target branch. I tried to ask the former repository's owner to help me figure out how I might do this in this issue, but, as you can see in his last post in the thread in which we've been discussing that issue, he hasn't been very forthcoming with any help. (In fact, he's actually been rather belligerent about it for who knows what reason….) In retrospect, I probably should, at any rate, have filed an issue like this one before I tried fixing it myself. If you like, I can hand my efforts up through now over to you so that you can merge them into your repository, thus relieving me of the responsibility of attempting such a large task. I wouldn't mind contributing some additional help; it's just that I'd rather have somebody who actually knows what they're doing work on this.