First push, totally rough structure

.gitignore

@@ -1,3 +1,164 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# OSX
+.DS_Store
+*.swp
+*~.nib
+# Thumbnails
+._*
+
 # Xcode
 #
 # gitignore contributors: remember to update Global/Xcode.gitignore, Objective-C.gitignore & Swift.gitignore

CODE_OF_CONDUCT.md

@@ -0,0 +1,59 @@
+# Apple Development Intensive 2024 Code of Conduct
+
+Adapted from: <https://github.com/processing/p5.js/blob/master/CODE_OF_CONDUCT.md>
+
+## Apple Development Intensive 2024 community statement
+
+Apple Development Intensive 2024 is a community interested in exploring the creation of art and design with technology.
+
+We are a community of, and in solidarity with, people from every gender identity and expression, sexual orientation, race, ethnicity, language, neuro-type, size, ability, class, religion, culture, subculture, political opinion, age, skill level, occupation, and background. We acknowledge that not everyone has the time, financial means, or capacity to actively participate, but we recognize and encourage involvement of all kinds. We facilitate and foster access and empowerment. We are all learners.
+
+We like these hashtags: #noCodeSnobs (because we value community over efficiency), #newKidLove (because we all started somewhere), #unassumeCore (because we don't assume knowledge), and #BlackLivesMatter (because of course).
+
+In practice:
+
+- We are not code snobs. We do not assume knowledge or imply there are things that somebody should know.
+- We insist on actively engaging with requests for feedback regardless of their complexity.
+- We welcome newcomers and prioritize the education of others. We strive to approach all tasks with the enthusiasm of a newcomer. Because we believe that newcomers are just as valuable in this effort as experts.
+- We consistently make the effort to actively recognize and validate multiple types of contributions.
+- We are always willing to offer help or guidance.
+
+In times of conflict:
+
+- We listen.
+- We clearly communicate while acknowledging other's feelings.
+- We admit when we're wrong, apologise, and accept responsibility for our actions.
+- We are continuously seeking to improve ourselves and our community.
+- We keep our community respectful and open.
+- We hear everyone.
+- We are mindful and kind in our interactions.
+
+In the future:
+
+- The future is now.
+
+## Apple Development Intensive 2024 Code of Conduct
+
+- **Be mindful of your language.** Any of the following behaviour is unacceptable:
+
+  - Offensive comments related to gender identity and expression, sexual orientation, race, ethnicity, language, neuro-type, size, ability, class, religion, culture, subculture, political opinion, age, skill level, occupation, or background
+  - Threats of violence
+  - Deliberate intimidation
+  - Sexually explicit or violent material that is not contextualized and preceded by a considerate warning
+  - Unwelcome sexual attention
+  - Stalking or following
+  - Or any other kinds of harassment
+
+  Use your best judgement. If it will possibly make others uncomfortable, do not post it.
+
+- **Be respectful.** Disagreement is not an opportunity to attack someone else's thoughts or opinions. Although views may differ, remember to approach every situation with patience and care.
+- **Be considerate.** Think about how your contribution will affect others in the community.
+- **Be open minded.** Embrace new people and new ideas. Our community is continually evolving and we welcome positive change.
+
+If you believe someone is violating the code of conduct, we ask that you report it by emailing [b.stopher@arts.ac.uk](mailto:b.stopher@arts.ac.uk). Please include your name and a description of the incident, and we will get back to you as soon as possible.
+
+Sometimes, participants violating the Code of Conduct are unaware that their behaviour is harmful, and an open conversation clears things up to move forward. However, if a participant continues with the behaviour, the Diploma in Apple Development team may take any action they deem appropriate.
+
+---
+
+This statement is licensed under a [Creative Commons license](https://creativecommons.org/licenses/by-sa/4.0/). Please feel free to share and remix with attribution.

README.md

@@ -1,2 +1,81 @@
-# AppleDevelopmentIntensive2024
+# Apple Development Intensive 2024
+
 Slides and other content for the Apple Development Intensive course given at the Creative Computing Institute, London from the 5th February - 9th February 2024.
+
+## Information
+
+- Location: [Creative Computing Institute(CCI)](https://www.arts.ac.uk/creative-computing-institute), Camberwell, London.
+- Lecturer: [Joel Gethin Lewis](https://joelgethinlewis.com/). Contact me via email via my website.
+- [Lecture and Workshop slides](https://github.com/JGL/AppleDevelopmentIntensive2024)
+- Please see the [course wiki for all non-lecture notes, reading lists and other resources](https://github.com/JGL/AppleDevelopmentIntensive2024/wiki).
+- Daily schedule:
+  - 1000-1100: Lecture
+  - 1100-1230: Workshop
+  - 1230-1300: Discussion
+  - 1300-1400: Lunch break
+  - 1400-1500: Lecture
+  - 1500-1630: Workshop
+  - 1630-1700: Discussion
+- Schedule for the week:
+  - Monday: Introduction, Constants and Operators - how can I demo this in SwiftUI?
+    - 1000-1100: Lecture 1: Introduction to the course. 1-01 Introduction to Swift and Playgrounds.key
+    - 1100-1230: Workshop 1: Introduction to GitHub. Introduction to GitHub. Introduction to Swift. Introduction to the Swift REPL. Lab - Introduction.playground
+    - 1230-1300: Discussion 1: What do you want to make?
+    - 1300-1400: Lunch break
+    - 1400-1500: Lecture 2: 1-02 Constants Variables and Data Types.key, 1-03 Operators.key
+    - 1500-1630: Workshop 2: Lab - Constants and Variables.playground, Lab - Operators.playground
+    - 1630-1700: Discussion 2: Different ways of counting?
+  - Tuesday: Control flow, Strings, Functions and Structures - how can I demo this in SwiftUI?
+    - 1000-1100: Lecture 3: 1-04 Control Flow.key, 2-01 Strings.key
+    - 1100-1230: Workshop 3: Lab - Control Flow.playground, Lab - Strings.playground
+    - 1230-1300: Discussion 3: ?
+    - 1300-1400: Lunch break
+    - 1400-1500: Lecture 4: 2-02 Functions.key, 2-03 Structures.key
+    - 1500-1630: Workshop 4: Lab - Functions.playground, Lab - Structures.playground
+    - 1630-1700: Discussion 4: ?
+  - Wednesday: Classes, Collections, Functions and Structures
+    - 1000-1100: Lecture 5: 2-04 Classes.key, 2-05 Collections.key
+    - 1100-1230: Workshop 5: Lab - Classes.playground, Lab - Collections.playground
+    - 1230-1300: Discussion 5: ?
+    - 1300-1400: Lunch break
+    - 1400-1500: Lecture 6: 2-02 Functions.key, 2-03 Structures.key
+    - 1500-1630: Workshop 6: Lab - Functions.playground, Lab - Structures.playground
+    - 1630-1700: Discussion 6: ?
+  - Thursday: Loops, Options, Type Casting, Guard, Scope and Enumerations
+    - 1000-1100: Lecture 7: 2-06 Loops.key, 3-01 Optionals.key, 3-02 Type Casting and Inspection.key
+    - 1100-1230: Workshop 7: Lab - Loops.playground, Lab - Optionals.playground, Lab - Type Casting.playground
+    - 1230-1300: Discussion 7: ?
+    - 1300-1400: Lunch break
+    - 1400-1500: Lecture 8: 3-03 Guard.key, 3-04 Scope.key, 3-05 Enumerations.key
+    - 1500-1630: Workshop 8: Lab - Guard.playground, Lab - Scope.playground, Lab - Enumerations.playground
+    - 1630-1700: Discussion 8: ?
+  - Friday: ?
+    - 1000-1100: Lecture 9:
+    - 1100-1230: Workshop 9:
+    - 1230-1300: Discussion 9:
+    - 1300-1400: Lunch break
+    - 1400-1500: Lecture 10:
+    - 1500-1630: Workshop 10:
+    - 1630-1700: Discussion 10:
+
+## Code of Conduct
+
+You can find the UAL Disciplinary Code For Students here: [Disciplinary Code For Students](https://www.arts.ac.uk/study-at-ual/academic-regulations/student-regulations/disciplinary-code-for-students).
+
+You can find our code of conduct here: [code_of_conduct.md](CODE_OF_CONDUCT.md), it was cloned from <https://github.com/processing/p5.js/blob/main/CODE_OF_CONDUCT.md>.
+
+[Golan Levin](https://www.flong.com/) also offers a useful thought from his children's school:
+
+> When communicating, ask yourself:
+>
+> - T – is it True?
+> - H – is it Helpful?
+> - I – is it Inspiring?
+> - N – is it Necessary?
+> - K – is it Kind?
+
+## Thanks
+
+Thanks 🙏🏻 to Abbie Vickress, Laura Knight, Rocio Rey Aloe, Becca Rose, Naho Matsuda, Cheska Lotherington, Véronique Bolhuis, Brenda Brierley, Lukas Alperowitz, Lise Hansen, Filippo Romeo, Herman Ho, Val Toro, Murad Khan, Matthew Plummer Fernandez, Alex Fefegha, Anna Troisi, Ben Kelly, Cathy Hoste, Charlotte Webb, Julia Makivic, Kenneth Lim, Matt Jarvis, Melisa Simpson, Rebecca Fiebrink, Sheldon Brown, Tom Lynch, Eva Wilkinson, Vali Lalioti, Indira Knight, Alice Stewart, Ben Stopher, Mick Grierson, Georgina Capdevila Cano, Alan Warburton, Rebecca Ross, Jaap de Maat, Lauren McCarthy, Kyle McDonald, Jonathan Harris, Zach Lieberman, Jessica Bland, Rick Walker, Graham Bennett, Toby Milner-Gulland, Liam Walsh, Golan Levin, Greg Smith, Mark Lundin, Xiaohan Zhang, Lia, Joshua Goldberg, Rosa Menkman, Daniel Shiffman, Tega Brain, Caitlin Morris, Harri Lewis and Rune Madsen.
+
+🖖🏻🇬🇧🏴󠁧󠁢󠁷󠁬󠁳󠁿🏴‍☠️🏳️‍🌈🏳️‍⚧️