| license: mit |
| // Paste this in dev tools console at pypi.org to get the percentage of packages in the top 4000 (cccording to this list:https://hugovk.github.io/top-pypi-packages/) that have a downloadable .whl file. | |
| // to get latest list: | |
| //let topPythonPackages = await fetch("https://hugovk.github.io/top-pypi-packages/top-pypi-packages-365-days.min.json").then(r => r.json()); | |
| //topPythonPackages = topPythonPackages.rows.map(r => r.project); | |
| // list from April 2021: | |
| let topPythonPackages = ["urllib3","six","botocore","setuptools","requests","certifi","idna","python-dateutil","s3transfer","chardet","pyyaml","pip","boto3","docutils","jmespath","rsa","pyasn1","wheel","numpy","pytz","awscli","cffi","colorama","protobuf","markupsafe","jinja2","attrs","cryptography","pycparser","requests-oauthlib","oauthlib","importlib-metadata","zipp","pandas","click","pyparsing","packaging","pyasn1-modules","google-auth","cachetools","future","decorator","futures","google-api-core","jsonschema","scipy","pygments","werkzeug","pyrsistent","pil |
| h1 { | |
| font-size: 1.25em; | |
| } | |
| h2 { | |
| font-size: 1.125em; | |
| } | |
| h3 { | |
| font-size: 1.05em; |
Source: https://ios.gadgethacks.com/how-to/always-updated-list-ios-app-url-scheme-names-paths-for-shortcuts-0184033/
If you've ever customized your app icons or played around with Shortcuts (previously called Workflow), you probably know how important URL scheme names are. Nearly all iOS apps assign themselves one of these names, and you need to know them if you want to add custom icons to your home screen or create a Shortcuts workflow that opens an app on your iPhone up. Finding the URL scheme name, also known as a URI scheme, for a particular app is not easy. First, you have to download the IPA file for the app — a difficult task since the iTunes 12.7 update removed iOS apps from it. When you finally find the IPA, you have to turn it into a ZIP file, show the contents of the app package, then hunt for the specific PLIST file that contains the URL schemes. It's a lot of work.
This example
| *~ |
I made an HTML port of game of life made with a table of checkboxes based on Pluralsight's Play by Play: HTML, CSS, and JavaScript with Lea Verou (http://www.pluralsight.com/courses/play-by-play-lea-verou). I was able to create a cool mousedown interface that allowed the "player" to draw on the board by dragging the mouse while it was down, and wanted to do the same for touch devices.
Unfortunately, touch events only hold references to the DOM element where they began (i.e. where "touchstart" fired) and do not recognize the DOM elements that exist under them (a detailed explanation for this can be found here: http://stackoverflow.com/questions/4550427/prefered-alternative-to-onmouseover-for-touch).
Instead, touch events maintain several lists of Touch objects - which represent interactions with the touch screen. Among these objects' properties are clientX and clientY, which indicate the X and Y coordinates of the events relative to the viewport (go to http://www.javascriptkit.com/javatutors/touchevents.shtm
