ArthurClemens
Joined 14 years ago
Karma
12
Submissions
10
Member since
Apr 12
Recent submissions
Comment · 8 years ago
I hope not. It would be the end of original Netflix content as we’ve learned to love.
Comment · 11 years ago
An example is chessground [1], the UI for the lichess [2] chess game, written with Mithril [3].
[1] https://github.com/ornicar/chessground [2] http://lichess.org [3] http://mithril.js.org
Comment · 11 years ago
Great news that Google has started this library. This will help MD implementors like me.
"That said, the large, diverse number of implementations available are often quite liberal with their interpretation of the spec (not their fault!) and their opinions don’t always reflect what the Material Design team would consider ‘correct’."
Nevertheless I found a number of deviations from the design specs:
- Disabled buttons should not have a z level
- FAB ripples should originate from the center
- Icon buttons should have a touch area of at least 40px
- The same goes for slider knobs (at least 30px, already small)
- The scrollable tabs on the site are scrolled just a couple of pixels per arrow click, instead of scrolled per tab
- Scroll areas should have -webkit-overflow-scrolling: touch, the current site is not scrollable on Mobile Safari
Comment · 11 years ago
This cannot be solved by the infinite list itself, because by definition it needs to throw out unneeded content (otherwise it would just grow in memory). A search field on top of the list could talk to the server and retrieve the filtered elements.
Comment · 11 years ago
Just this morning I released a Mithril infinite list. It supports flexible heights, list/grid, and handles batches of results (basically "pages"):
https://github.com/ArthurClemens/mithril-infinite
Comment · 11 years ago
Mithril already uses a diffing algorithm: "diffs the new tree against the existing one and intelligently modifies only the portions that have changed": http://lhorie.github.io/mithril/mithril.render.html
Comment · 12 years ago
This seems related to Chuck
http://chuck.cs.princeton.edu
Comment · 12 years ago
Polish has 3 plural forms:
1: When the number is 1
2: When the number ends in 2,3,4, but not 12,13,14
3: For all other numbers
It beats me how translators would use "few" for plural form 2 (which includes 22, 33, 44). "Zero" and "other" are actually the same form. A good translation tool would spare the effort of entering the same information twice.
How would this work for Chinese, where all numbers are treated the same?
I would never present these keywords to translators, but instead show the full explanation like in the plural forms above.