Last updated on 2018-Abr-05.
The learning app creation tool available from this site is presented under Creative Commons License 4.0 by Coreliu. Coreliu is a Script City Ltd brand.
If you can create an annotated slide show, then you can create an Android App just like Slips and Falls which you can publish and distribute as you wish. Here is how:
Things you will need to create an interesting app
"Tutta la nostra conoscenza ha le sue origini nelle nostre percezioni" - Leonardo Da Vinci
"Die Grenzen meiner Sprache sind die Grenzen meiner Welt" - Ludwig Wittgenstein
The most important thing you will need to write an interesting app is interest and knowledge about a subject that you can illustrate with photos and describe with facts. For example: if you are know a lot about horses; have access to lots of illustrative photos of horses doing interesting things; and you can describe the important features of these photos in a few succinct words; then you have a good basis for writing an interesting app about horses. Or perhaps jet aircraft. Or growing roses.
The app generation process synthesizes speech from your facts, then packages the speech together with your photos to create an immersive Android app. The app teachs students by showing them the photos, gradually introducing the spoken facts, then using the facts as questions for which the student must choose the matching photos.
A Computer and an Android Phone or Tablet
You will need a small amount of computer equipment:
How to write a Coreliu Photo App
To create an app in the Coreliu format follow these instructions:
GitHub will then tell Coreliu to generate the app for you: GitHub will send you a notification via email when the app is ready for you to download and play.
You will be able to see all the notifications related to your repository under the Issues tab in the top centre left of your repository's home page:
and also in your email, depending on how quickly your email updates (possibly
under Spam):
If you get stuck, create an issue against your repository by clicking on the
word Issues in the top centre left of your repository's home page:
and the push the green "Create
Issue" button. Coreliu will be pleased to collaborate with you to resolve the
problem.
Go to GitHub and follow the instructions to create a free account, keeping
the alert below in mind:
Please make sure that your userid name on GitHub starts with an upper or
lowercase letter in the range A to Z and thereafter only
contains upper or lowercase letters A to Z and/or digits
0 to 9. The inclusion of any other letters will cause the app
generation process to fail.
Thus userid: user1 will work well.
While userids: 1user, user 1, user𝝰 will all fail
miserably.
The following actions will authorize CoreliuOrg to write files into
repositories in your account, to manage the web hooks which will connect your
repositories to CoreliuOrg and to create issues to tell you what is
happening.
Click the following link to go to the GitHub Tokens page for your
account.
You will see:
Click on Generate New Token in the top right corner.
In the first box below the name field, select: repo - Full control of
private repositories
In the fourth box down chose: admin:repo_hook
At the bottom of the page press the green button: Generate Token
You will then see your new token on a pale green background.
Please send this token and the userid of your GitHub account by
email to coreliuorg@gmail.com who will install it on Coreliu allowing coreliuorg@gmail.com
to generate apps for you. The easiest way to do this is to copy the token to
your clipboard by clicking on the clipboard sign next to it and then pasting it
into the email asfter your userid. Please include the following
statement in the email:
I understand that by sending coreliuorg@gmail.com this token I have compromised
the security of all the repositories under the userid associated with this
token: I can and do absolve coreliuorg@gmail.com from all responsibility for
maintaining the security of this data because it contains nothing confidential
and the data is fully backed up elsewhere.
You can withdraw the permissions associated with the token or change them at
any time with immediate effect by returning to this
page.
It is very helpful to have GitHub email you as events occur in your
repository. To enable this, click the following link to go to the: GitHub Notifications page
for your account.
You will see:
Click on Automatically watch repositories at the top and Include
your own updates right at the bottom.
If you wish to ensure that your email address is always kept private: go
to the email settings page and check the indicated items below.
You are now ready to create a new GitHub repository to contain your apps
and connect the repository to CoreliuOrg to generate the Android versions of
these apps for you.
Push the "plus" sign at the right hand end of the title bar and choose
new repository from the menu.
When you create your repository you can select public or
private for the type of repository (or repo). We advise you to
select public because:
Public repositories are free on GitHub
Apps created from both public and private repositories will not remain
private on publication because you have no control over the distribution of
your apps when you publish. Even if you publish on restricted circulation, the
people you publish to might redistribute your apps.
We cannot guarantee the security of data exchanged between you and
CoreliuOrg: Recent global IT security breaches (i.e. The Pentagon, the NHS,
the UK Information Commissioner and UK council websites) tell us that in the
world we live in, no IT system or website can be 100% secure. CoreliuOrg
works to industry standards of information security but this can not guarantee
the security of your app content prior to publishing. Any IT system can
be hacked!
Choose a simple, short name for your repository: please make sure that the
name of the repository contains only letters and numbers drawn from a
through z, A through Z, 0 through 9 and
_ (underscore). The name must start with a letter and must not contain
spaces, commas or any other punctuation characters else chaos will ensue.
Choose the option of initializing the repository with a README -
which once created can be left blank for the moment. At this point you can skip
the other options: GitIgnore and choosing a licence.
Press the green Create Repository button to create the repository.
Once you have created a repository on GitHub and before you add any files
to it, you should invite coreliuorg@gmail.com to be a collaborator by clicking the
word Settings in the top centre right of your repository's home page,
then click Collaborators at the top of the left side bar:
Enter CoreliuOrg as the name of the collaborator in the search box
and push the button: Add collaborator. CoreliuOrg will now be
able to answer any questions you pose by creating issues on GitHub. To create
an issue, click on the word Issues in the left top corner of your
repository's home page.
CoreliuOrg will respond to your invitation to collaborate by connecting
your newly created repository to Coreliu and creating some useful files and
folders in your new repository. You will receive a notification from GitHub
once this work has been done; usually it takes just a few moment.
Once notified by CoreliuOrg that the web hook has been created, you will
be able to see the web hook connecting your repository to Coreliu by clicking
as follows:
Go to repository settings:
Click on web hooks to get:
You can click on the web hook to see its details:
You can also see when the web hook last notified CoreliuOrg at the bottom
of the image above.
You can delete this web hook at any time to disconnect your repository from
Coreliu if you wish to end this collaboration.
If you have received notification from CoreliuOrg that the web hook is in
position as described above, you can then start to load your repository
with images and text as described in the next sections to actually create your
app.
Now that you have a repository ready to go you can start development of your
app. The first thing to do is to find some of photos that illustrate the points
you wish to make and load them into the images folder in your new repository.
To do this, click on images:
which will take you into the images folder.
Click on the upload files tab to get:
Click on the choose your files link:
On this page you can choose the files you wish to upload.
You will probably find it easiest to load a small number of images first,
say three or four, so that you can create a prototype app and then improve it
by adding more photos as you see fit.
Every time you save a photo into your repository Coreliu, being a
collaborator, will receive a message indicating that this has been done.
Coreliu responds to this message by creating or updating the file
sourceFile.sample.txt in your repository. This file shows what a very
basic app using these photos you have supplied might look like and so serves as
a useful template for further development.
You should write the facts for each photo in a file called You might find it helpful to use a text editor such as:
Geany to edit Each time you save a new version of any If the app generation process fails you will receive an issue via GitHub
that describes the problem allowing you to fix your An easy way to create the Here is a sample listing of the files in a GitHub repository:
You can see the images folder on the first line and the files
sourceFile.sample.txt and Here are the first few lines of a typical sourceFile.sample.txt file:
The file: A complete definition of the format of this file is given in section Layout of sourceFile.txt.
For your first app the easiest thing to do is use
sourceFile.sample.txt as an example and type the facts that you are
going to use over the text "First fact about" and "Another fact about" and save
the results in file: You are bound to make mistakes in the process of generating an app, but
such mistakes are not fatal because you can always try again. If Coreliu
cannot generate an app for you from the information you have provided in
If you get hopelessly stuck, just create an issue yourself by clicking on
the word Issues located in the top left corner of the home page for your
repository (just under then name of your repository) and someone at Coreliu
will be pleased to respond if Coreliu has been invited to act as a
collaborator on your app.
Coreliu will attempt to regenerate your app each time you commit, that is:
save a new version of If you wish to receive such notifications by email, then you should make
sure that you are watching your repository as described in:
Set up your notification preferences.
Or you can look in the issues section of your repository
and pick up the notifications from there as they come in.
If Coreliu successfully creates an app for you from the photos and facts
that you provided in
This repository contains the sourceFile.txt for
this app.
Please feel free to copy and modify it as you wish.
An app description tells Coreliu how to create a Coreliu Photo App for you using
commands in a well defined language. This language has been designed to be
simple to code by non technical authors yet powerful enough to express the
information required to fully define a Coreliu Photo App.
An app description starts with a single app command followed by
additional photo and fact commands. The action of each command is
defined by the values of its associated keywords. The commands and their
keywords tell Coreliu how to create the app for you. You can add notes to
yourself by coding a The action of each command is modified by its following keyword
Keywords cannot have spaces in them, so:
Values occupy the remainder of the line. Leading and trailing whitespace
around the value will be ignored. Spaces are allowed inside the value so:
You can turn a keyword Later on, if you change your mind and want Coreliu to take note of this
information, you can remove the # to bring the keyword and its
associated value back into play.
Here is a list of the current keywords, their possible values and what
happens if you code them:
The name of the person who wrote this app which should be the name of the
repository containing the app. Thus if the name of the repository is:
then the author of the app will be:
The app generation process will inform you of the correct name if you get it
wrong.
A slightly longer description for the app often used for the short description
on The email address of this app so that students have somewhere to send
suggestions, corrections or complaints
Generate slower, more emphatic speech for some items so that a student who
did not understand the normal fast speech version can be given a slower,
more comprehensible version on redirect.
Code a number for the value of this keyword: any phrase that has fewer
characters than this number will cause both normal and emphasized versions of
the speech to be generated. Phrases longer than this number will only cause a
normal version of the speech to be generated.
If you omit this keyword or code a value of zero then only normal speech
versions will be generated.
The names of apps that the user might enjoy playing after completing this
app. If the student appears to have mastered all the material in this app the
app will start playing one of these apps instead.
The full name of the the app on Use this keyword to change this name to something else in the unlikely event
that you want to use a different name on Google Play for your app.
Use this keyword to specify the URL of a web page where the student can find
more information about the app, its purpose, how to use it, who wrote it, the
sponsoring organizations, their contact details etc.
See also: the app.title= keyword
and the app.logoText= keyword.
If the URL starts with https?:// then this is the location of the
icon image on the World Wide Web from whence it will be copied and scaled to
the right size. If the URL starts with github: it comes from the
specified repository on GitHub. Otherwise it is the name of the file in the
images folder in the GitHub repository for this app which contains the icon
for this app.
By default use the jpx (jpeg extended) image format to display photos
at high resolution on the Android. Your jpg and png images
will be automatically converted to use the jpx format by the app build
process so no action is required of you to use this format.
If you do not want to use jpx, code this keyword with a value of
jpg to instruct the build process to use the jpg format to
represent images. If you supply photos in the png format the build
process will automatically convert them to jpg for you for use on
Android.
The two character code which
describes the language this app is written in. All the voices that speak this
language will be used to speak the app unless the app.speakers= keyword is used
to specify the speakers that you actually require.
The one exception to this rule is English, which is spoken by just
Amy and Brian unless you specify otherwise.
The number of levels in the game. Each photo has a level and only comes
into play when the student reaches that level of play. You can specify the
level for each photo manually using the
photo.level= keyword. Or you can use this
keyword to specify the number of levels in the game and have the app generation
system allocate photos to each level based on their position in If the number of levels is not specified it defaults to one: in this case all
the photos are in play as soon as the app starts.
When the app starts for the first time it downloads its content from the
Internet which might take a moment or two. The app covers any delay by showing
the name of the app and the name of the sponsoring organization on the splash
screen.
Use this keyword to show a small amount of text identifying your
organization. The app will scale this text to fit the screen, so if you want
the name to be in large visible letters it must contain only a few characters.
Conversely, long names will be shrunk down to fit the display and will probably
be unreadable.
See also: the app.title= keyword
and the app.help= keyword.
The maximum number of images to show in one selection at a time in the app:
choose a value that reflects how many images a competent student might
reasonably scan in 30 seconds
The maximum possible number of questions that can occur in
a race. Otherwise, the default is the total number of photo commands in
the app. However, the student will only be faced with the maximum possible
number of questions once they have made considerable progress through the
material in the app as races are restricted to information that the student has
already encountered.
then the name of the app will be:
The app generation process will inform you of the correct name if you get it
wrong.
The names of apps that perhaps the user ought to play first, listed in play
order separated by spaces. If the student does not appear to be making much
progress with the existing app, the app will start playing one of these apps
instead.
The number of questions the student must answer correctly in a row to trigger
race mode.
In normal play the student receives new items of
information every time they answer a question correctly the first time the
question is posed; otherwise answers are provided for questions that the
student is unable to answer correctly.
During a race, no new items of information are presented: the
race continues as long as the student does not make too many mistakes or until
all the items that the student has previously identified correctly have been
presented. Race mode questions are presented with less delay than normal
questions.
The race starts with well known items and with quiet background music. As the
race proceeds, the music gets louder and the questions become more difficult as
measured by how often the student has correctly identified the items in the
past.
The objective of a race is to set a personal best time for completing a race
through all the items in the app without errors.
At the end of race, the student is congratulated if they did not make too
many mistakes. Play then reverts to normal mode.
Code this keyword in the unlikely event that if you would like screen shots
taken in the app to be saved to a different GitHub repository. Code the
GitHub user name, followed by '/', the repository name, optionally followed by
a path which will be prefixed to the screen shot name.
This feature only works for the first two hours after an app has been
created: after that the app plays normally.
Screen shot mode is enabled if this keyword is present with any value or
indeed no value. See: the
photo.screenShot= keyword for full details.
See also the
app.saveScreenShotsTo= keyword for details of how to specify an alternate
repository in which to save screen shots.
The Ids of the voices to be
used to speak the app or all the speakers in the language set by app.language= keyword.
Once you have created and published an app any further successful changes to
this app will be transmitted directly to your active students. You might
prefer to test the new version of your app first before making the changes
publicly visible. To achieve this, code:
test = a description of the changes
Once you are satisfied with the changes you have made, you should comment
out this keyword as in:
# test = a description of the changes
so that a succcessful generation will update all active copies of the
app. You might find it helpful to update the app.version= to describe the new features in
the app for posterity.
Please note that test apps will be deleted without notice from
servers to free space if necessary.
The title for this app. This title will be displayed on the splash screen
when the app starts for the first time and also under the icon representing
this app on the student's phone or tablet. The title should be short, like a
newspaper headline, as in:
See the app.logoText= keyword for
details of how you can further modify the splash screen.
Offer the user a choice of languages in which the app can be played. The
If all is chosen as the value of this keyword, then all the languages
supported by Aws Polly will be offered.
A sentence describing what is in this version of the app. See all also the
app.test=
keyword.
One or two characters to display in the centre of the screen either in lieu
of a photo or on top of a photo in alphabet and number games
The level of play at which the student is introduced to this photo and
its related facts. If no level is associated with a photo or it has a level of
1 then the photo is introduced at the first level of play.
See also: app.levels= for an automated
way of setting the levels of all the photos in the app.
A short name for this photo which will be matched against fact names as
described in matching names.
Indicate points of interest in a photo by coding the fractional coordinates
of each point of interest as percentages from left to right and top to bottom
of the photo separated by white space.
For example, the centre of the upper right quadrant is:
The points of interest should be coded in order of decreasing interest, for
example: if the centre is the most interesting point in the photo followed by
the centre of the upper right quadrant, then code:
All characters that are not the digits 0..9 will be converted to white space,
which means that the above could be coded as:
Any missing coordinates will be assumed to have a value of 50
Points of interest are used (amongst other things) to centre screen shots,
as far as possible, on the most interesting point in the photo.
The actual sequence that should be said by Aws Polly if this is different
from the content of the photo.title=
keyword.
Aws Polly uses:
Speech Synthesis Markup Language
which can be supplied using this keyword
Please note that the title of the
photo is shown in text on some screens, so if this keyword is used the two
might diverge.
Code this keyword if you would like this photo to be made into a screen
shot. You will need screen shots to upload your app to distribution web sites.
This keyword gives you a convenient way to mark the photos in your app that
would make the best screen shots.
To actually take screen shots you will needs to code the app.screenShots= keyword to temporarily
enable screen shot mode. During screen shot mode, the app shows just the
indicated items either centered on their first point of interest or
moving so slowly that you can manually swipe the screen to take the shot when
the photo is best presented on the screen.
By default the screen shots will be placed in your GitHub repository in:
However, you can specify an alternate repository in to which screen shots
are to be saved, see the app.saveScreenShotsTo= keyword for
details.
This feature only works for the first two hours after an app has been
created: after that the app plays normally.
If you prefer to supply your own sound files instead of having
speech generated for you:
Alternatively specify urls starting with http(s): locating an mp3
file to use as the sounds for this photo.
The recorded sound will then be played instead of any generated speech.
See also fact.sounds= keyword
The title for this photo. Take care not to use a question! The title of the
photo will be used as both a question and an answer by the app and so if you
add words such "Is this" or punctuation such as "?" to make it a question then
the usage as a question might work, but the usage as an answer will not.
The title should be as short as is feasible. If the title contains redundant
text which is repeated from photo to photo, then the app becomes an app for
teaching the student the redundant text rather than the original material as it
is the redundant text that the student will hear the most and thus learn
the first.
This gives rise to the most important rule of educational game development:
everything must change except the truth.
Use the photo.say= keyword if you wish
to say something other than the title when describing the photo.
If the URL starts with https?:// then this is the location of the
image on the World Wide Web from whence it will be copied. For example:
If the URL starts with github:// then this is the location of the
image in another GitHub repository: code the user name, '/', repository name,
'/', followed by the path in the repository to the image file. For example:
Otherwise it is the name of a file in the images folder in the GitHub
repository for this app. For example:
Photos should be high resolution: crop the photo to centre the object of
interest and remove extraneous details.
The app will move long thin or tall narrow photos around on the screen so
that the student can see all of their contents. This leads to a motion effect
which is desirable for apps about skyscrapers, airplanes, bridges, boats, trees
etc. as it adds realism. To reduce this effect: crop the photos into squares,
to accentuate it: stick photos together in a long line.
The student will be able to pan and zoom the photos in the app to see fine
details so it is worth using high resolution photos to facilitate this
capability. Conversely, low resolution photos will pixellate if the student
zooms them.
If you include identifiable people in your photos in an app you should
get signed model releases from the persons involved.
The aspect of the photo under consideration which allows facts from
different photos to be matched during the wrong/right response display.
The aspect of each fact is also used in race mode to test the student once
the student has correctly recognized several photos and facts with the same
aspect. Thus if you were writing an app about horses, and an aspect of each
horse was its country of origin, then: once the student demonstrates that they
know the country of origin for several horses, one or more races will occur in
which the student is tested on just the country of origin for each horse.
The actual words that should be said by AWS Polly if this is different
from the fact.title= keyword.
If you prefer to supply your own sound files then use this keyword to
specify the location of the mp3 files to use instead of generated speech. See
photo.sounds= keyword for full details.
Normally you should place the command name alone on the first line and then
follow the command with one or more keyword can be combined to save space by writing it as:
An app is built from photos and facts. Each corresponding photo and
each fact should have a name the following matches will be made:
The student will be tested on the word sky and the phrase "The sky
above us" using all three photos.
However, with the above source code the student will never see "Rain will
fall soon" as the fact named sky.grey does not match the name
of any photo. Adding a photo with a name, for example,
sky.grey.rain would bring this fact into play by matching the name
of the photo with the fact's name of sky.grey.
Each app encourages its students to send a link for the app to their friends
so that they can play the app too. To reach the first set of students who can
seed this organic growth for you, please consider publishing your app on one of
the following public platforms:
Create a movie of your new app with a voice over explaining why you think
people might like to play your app and publish it on
YouTube.
In the description of your movie include a link to the app on Coreliu so
that students can download and play your app immediately.
Place a description of your app on your web site and provide a link to
Coreliu so that the student can download and play your app immediately.
Upload your app to:
Amazon App Store.
Your new app will work on Google Play.
Each app prompts its user, on occasion, to send a copy of the app to their
friends to encourage the organic growth of the app's user base:
The recommendation contains the Sha-256 encoding of a unique secret number that is only
known to the sender .
If such a recommendation results in a new download, the author will receive
a notification that this has happened via a GitHub issue. The successful
recommendation will also be recorded in the app's GitHub repository in a file
in the downloads folder as in:
To simplify compliance with:
European Union: General Data Protection Regulation we do not record any
information that might identify the parties to this transaction on our servers.
However, if you create a file in the rewards folder of your
repository using the From identity as in:
Then the app on the Android device containing the source of the unique secret number will notify the next
person to start that app of any text that was entered into the rewards file.
This notification will be via a pre-written email that the user of the app can
modify further:
The app user can then send this email to the app author if they wish:
If the email the app user sends contains the source of the unique secret number, then
the author can compute the Sha-256 of this number using Duck, Duck, Go as in:
to see whether it matches the unique secret number used for the rewards file name and the
From Identify number. As the source of the unique secret number is unique to each download and the
Sha-256 algorithm is believed to be cryprographically secure, this is very
difficult for any-one else to duplicate without knowing the source of the unique secret number in the first
place, i.e. without having access to the app on the sending Android device.
If the chain of recommendations leads to a person that the author wishes to
employ, the author might wish to work back along the chain rewarding some of
the people who contributed to this successful outcome to encourage them to
continue their helpful activities in the future.
Setting up a GitHub account and creating a first repository is a
complicated process. Here is a summary of the main interactions between the
author and CoreliuOrg:
Detailed Instructions for creating a Coreliu Photo App
Create a free account on GitHub
Authorize CoreliuOrg to access your GitHub account
Give the token a convenient name of your choosing.
Set up your notification preferences
Set up your email preferences
Create a new repository on GitHub to hold your apps
Security Disclaimer
Authorize CoreliuOrg to collaborate with you
Add some interesting photos to the images/ folder
Write the facts for each photo
app GoneFishing = DDD
maximages = 6
icon = https://avatars1.githubusercontent.com/u/36601762?v=4
author = lspfa
email = 36601762+lspfa@users.noreply.github.com
# Details of photo Blacktip shark
photo Blacktip_shark = Title of Blacktip shark
url = Blacktip shark.JPG
fact Blacktip_shark.1 = First fact about Blacktip shark
fact Blacktip_shark.2 = Another fact about Blacktip shark
# Details of photo Brown Trout
photo Brown_Trout = Title of Brown Trout
url = Brown Trout.jpg
fact Brown_Trout.1 = First fact about Brown Trout
fact Brown_Trout.2 = Another fact about Brown Trout
Layout and meaning of sourceFile.txt
Command Description
app
The first command should be
an app command whose keywords specify global values for the app.
photo
For each photo
that you want to include in a Coreliu Photo App, you should code one photo
command to give the photo a name and title and to tell
Coreliu where the photo is located on the Internet so that the photo
can be retrieved and displayed in the app.
fact
Use the fact command
to provide facts for each photo. These facts will be used to teach and
then test the users of the generated app.
if you wish.
fullPackageNameForGooglePlay
as:
full_package_name__for___Google______play
would not be regarded as a keyword causing the app generation to fail.
full Package Name For Google Play
would work well as a keyword value pair.
description = Robot descending from the sky
# maxImages = 12
Command Key Required Description Default Possibilities
app
Outline description of an app
author
author
philiprbrenan/GoneFishing
philiprbrenan
description
email
emphasis
enables
fullNameOnGooglePlay
help
icon
imageFormat
jpx jpg
language
en cy da de es fr is it ja ko nb nl pl pt ro ru sv tr
levels
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
logoText
maxImages
12 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
maximumRaceSize
name
name
A short name for this app which matches the path in your repository to the
relevant
philiprbrenan/GoneFishing/l/en/sourcefile.txt
GoneFishing.l.en
ordered
The next item to be presented to the student will be chosen in some kind of
order if this keyword is coded:
never always finally initially
prerequisites
rightInARow
7 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
saveScreenShotsTo
screenShots
speakers
test
title
title
Robots Invade London
translations
all cy da de en es fr is it ja ko nb nl pl pt ro ru sv tr
version
photo
Description of a photo that illustrates one or more facts
aFewChars
aFewChars or url level
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
maps
Optional URL showing a map of where this photo was taken
name
name
pointsOfInterest
75 25
50 50 75 25
(50x50), [75 25];
say
screenShot
out/screenShots/photoname.jpg.
sounds
title
title
url
aFewChars or url
https://upload.wikimedia.org/wikipedia/en/7/7d/Bliss.png
github://philiprbrenan/vocabulary-1/images/Ant.jpg
Ant.jpg
wiki
The URL of the Wikipedia article describing the concept this photo illustrates
fact
A fact about one or more of the photos that the student can be tested on
aspect
name
name A short name for this fact which will be matched against photo names as described in matching names
remark
An explanation of why this fact cannot be used as a question if, in fact, this fact cannot be used as a question
say
sounds
title
title The text of this fact
wiki
The URL of the Wikipedia article about this fact
photo
name = white.cliffs
title = The "White Cliffs of Dover" from an arriving ferry
photo white.cliffs = The "White Cliffs of Dover" from an arriving ferry
photo sky = The sky above us
photo sky.blue = Blue skies over the sea
photo sky.red = Sunset
fact sky = The heavens above us
fact sky.blue = Lots of sun shine soon
fact sky.grey = Rain will fall soon
Command Name Applies to
fact sky All three photos.
fact sky.blue The photos "The sky above us",
"Blue skies over the sea" but not "Sunset".
fact sky.grey None of the photos.
photo sky All three facts.
Upload a movie of the app to YouTube
Put a link to your app on your web site
Upload your app to Amazon App Store
App command keywords app
Example Apps example apps
Fact command keywords fact
GitHub Notifications page GitHub Notifications
GitHub Tokens page GitHub Tokens
Help coreliuorg@gmail.com
Photo command keywords photo
Sample app on Google Play Slips and Falls
Sha 256 Duck Duck Go
Source for sample app Slips and Falls
Speakers available Speakers available on Amazon Web Services
Text Editor Geany
Step Author CoreliuOrg
1 Sets up a GitHub account.
2 Creates a personal access
token and sends it by email to: coreliuorg@gmail.com
3 Installs token as described in savePersonalAccessTokens.pl
4 Sets up notifications
5 Creates a repository
6 Invites CoreliuOrg to collaborate on their
repository and waits for CoreliuOrg to notify them that their
repository has been set up.
7 Accepts the author's invitation and starts watching the repository.
8 Creates the web hook (aWebHook) and the images/ folder for
the author which sends a notification to the author confirming this has been
done. Follow up with an email or skype to confirm in case of GitHub email
problems.
9 Receives confirmation that the web hook has been created and starts to
create the app.
10 Adds photos to the images/ folder
11 Checks that sourceFile.sample.txt is being updated.
12 Writes sourceFile.txt
13 Watches the first app generation either via GitHub issues or email
copied to CoreliuOrg
14 Downloads new app to phone and tests