Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
danschlet committed Oct 26, 2016
1 parent d7a4442 commit c8023fc
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,10 @@
# seb-mac
Safe Exam Browser for Mac OS X
Safe Exam Browser for macOS

Open SafeExamBrowser.xcodeproj in a recent version of XCode. For building you have to switch off code signing or add your own code signing identities. Currently on master the upcoming version 2.1 is being developed, after releasing this we will create branches for future versions.
While in development, the deployment target is set to OS X 10.8 to be able to use Base Localization, upon release Localizable Strings will be converted to xib files and the deployment target will be set back to OS X 10.7.
Open SafeExamBrowser.xcodeproj in a recent version of XCode (currently 8.0). For building you have to switch off code signing or add your own code signing identities.

Currently master reflects version 2.1.x. The iOS version of SEB is being developed on branch SEB-iOS and will be merged later with master (as it is a shared Xcode project with both macOS and iOS targets).

All information about Safe Exam Browser you'll find at http://safeexambrowser.org. Search discussions boards if you don't find information in the manual and SEB How To document (see links on page Support).

For your information: There is only ONE correct way how to spell SEB (all three letters in CAPS). That's why even in camel case classes, methods and symbols should be named SEBFilterTreeController.m for example or SEBUnsavedSettingsAnswerDontSave. If you find SEB written as seb, then that's ok if it's some symbol users will never see (but better would have been to use SEB). If you find SEB written as Seb, then that is definitely WRONG (unfortunately some of our past developers were not strict about following naming rules)! But both cases are no reason to file a pull request, please concentrate on real problems...
For your information: There is only ONE correct way how to spell SEB (all three letters in CAPS). That's why even in camel case classes, methods and symbols should be named SEBFilterTreeController.m for example or SEBUnsavedSettingsAnswerDontSave. If you find SEB written as seb, then that's ok if it's some symbol users will never see. If you find SEB written as Seb, then that is definitely WRONG (unfortunately some of our past developers were not strict about following naming rules)! But both cases are no reason to file a pull request...

0 comments on commit c8023fc

Please sign in to comment.