* If the current language is English, the second "English" column will
no longer display.
* Progress bars have percentages again.
* Some jade logic has been simplified.
* Add totally legit and optimised code to find the number of strings in
each language.
* Add this as an API call
* Add strings for ``na'vi``, ``es`` and ``nl`` for their own language
names
* Optimise CSS a bit
* Add classes for the languages, for testing purposes
+ Added dependency on underscore
+ Added displaying of some configuration options for dent, link, quotes,
report and web
+ Translated (badly) the word "Milestones"
* Translated and moved the github advert to below the milestones
## Additions
+ Add current branch to display
+ Pass Github repo through to the page
+ Add link to source
+ Differentiate "progress bar" and "milestone" headers again
+ Add Git ``h4``, renamed "version control" because it's more interesting
to translate
+ Add progress percentages to the progress bars
- Remove redundant short-hash placeholder
- Remove extraneous margins on ``ul``
- Simplify progress calculation code
* Change some variable names to be more forthcoming about what they
represent
* Fix links to the milestones
* Fix indentation of strings.json
+ Add a counter to the random imgur page.
+ Added functionality to the ``c`` key to toggle the counter display.
+ Added functionality to the ``r`` key to reset the counter to default.
+ Added a new configuration option for a quote category to get the
default 'highscore' from.
This commit adds a small decreasing counter to the corner of the
screen. Hidden by default, press ``c`` to toggle it.
The counter will begin at highscore + 1, and will decrease with every
new image. This is intended to be used during contests to see how many
images one can cycle through before, for example, finding a picture of
a cat. The counter can be reset using the ``r`` key.
The highscore is automatically set at page load to the most recent
quote added to the category specified in the configuration option.
Therefore it is important that only numeric data is placed in that
particular quote.
The score will not reset to a new highscore automatically, and nor
will a new highscore update the quote category.
## Changelog:
- Remove Github status call.
+ Closed issues
+ Localised <h1>
+ Add introductory paragraph
+ Add last diff to page
- Remove jade include to layout.jade
+ Dynamic language metadata
+ CSS
+ Progress bars
## Known issues:
* Loading the closed milestones raises an exception for some reason;
in a try-catch for now, unsure how to fix.
## Still to do:
* Style loaded modules section (columns?)
* Shrink footer
* Do we need a shorthand hash by the revision?
* Pull req count? (low priority)
Add throttle to the spacebar, so you can no longer load another image
whilst the old one is loading.
Hopefully this'll negate some of the API failures we've been getting.
* Added config.json to the party
* Moved API key (client ID) to the configuration file
* Added image link to random imgur image page
* Minimised loading message
* Added fade to loading message
* Added count to title attribute of webpage
* Removed font-size increase
* Added placeholders
This commit adds a new box to the imgur page, separating the
"Loading..." box with a new "details" box, which contains the
information found via the API.
The loading box appears on the left, and disappears when an image is
loaded, to be replaced with a box on the right.
API operations, such as a "report" or "submit to gallery" option, could
appear below the current right-aligned box, in a smaller font.
I'm undecided as to whether this commit is an improvement or not.
This commit adds functionality to the loading callout in the imgur
module.
The size of the font used in the loading callout now increases in a
linear fashion in proportion to the number of images viewed in a row.
The size starts at 12px, and will increase to 72px at image 2000, with
round figures at most "standard" font sizes.
This is largely an experiment to see what it looks like: it might not be
as nice looking now that the callout contains extra information (such as
the view count). It may be worth experimenting with just increasing the
count number and leaving the "a w with x views (y*z)" message at a
static size, or perhaps by editing the colour variant, or even the
position on the screen.
I really just wanted some feedback to make it a bit more interesting for
a heavy user that has reached high numbers of images.
Some figures:
* 12px is reached after 0 images
* 14px is reached after 66 images
* 16px is reached after 133 images
* 18px is reached after 200 images
* 21px is reached after 300 images
* 24px is reached after 400 images
* 36px is reached after 800 images
* 48px is reached after 1,200 images
* 60px is reached after 1,600 images
* 72px is reached after 2,000 images
* 144px is reached after 4,400 images.
