This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
i386 : iPhone Simulator | |
x86_64 : iPhone Simulator | |
arm64 : iPhone Simulator | |
iPhone1,1 : iPhone | |
iPhone1,2 : iPhone 3G | |
iPhone2,1 : iPhone 3GS | |
iPhone3,1 : iPhone 4 | |
iPhone3,2 : iPhone 4 GSM Rev A | |
iPhone3,3 : iPhone 4 CDMA | |
iPhone4,1 : iPhone 4S |
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.
- Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
- Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
- Once documentation has been written, development should commence, and test-driven development is preferred.
- Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
- When a feature is being modified, it should be modified documentation-first.
- When documentation is modified, so should be the tests.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import QtQuick 2.7 | |
import QtQuick.Window 2.2 | |
import QtQuick.Controls 2.0 | |
import Qt.labs.calendar 1.0 | |
Rectangle { | |
id: mainForm | |
height: cellSize * 12 | |
width: cellSize * 8 | |
property double mm: Screen.pixelDensity |
C++ links: Coroutines
https://github.com/MattPD/cpplinks / C++ Standard / C++20 / Coroutines
(draft; work in progress)
#coroutines (C++ Slack): https://cpplang.slack.com/archives/C5JS5JXT5
Date | 05-05-2021 - 10-17-2023 |
Revision | R3 |
Author | Guillaume Dua |
Reviewers | Loïc Joly, Antoine Morrier |
In order of first appearance in The Morning Paper.
- USB Overdrive
- A non-Apple keyboard with media keys (or keys you want to make "media" keys). For reference, I'm using a Microsoft Sidewinder X4
- Plug in your keyboard and install USB Overdrive.
- Open USB Overdrive. Click into the Settings tab.
- Click the dropdown and select "Any Keyboard, Any Application"
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
from django.db import connection, models | |
class MyManager(Manager): | |
def raw_as_qs(self, raw_query, params=()): | |
"""Execute a raw query and return a QuerySet. The first column in the | |
result set must be the id field for the model. | |
:type raw_query: str | unicode | |
:type params: tuple[T] | dict[str | unicode, T] | |
:rtype: django.db.models.query.QuerySet | |
""" |
NewerOlder