Nullctipus

<bpy>
  <Theme>
    <user_interface>
      <ThemeUserInterface
        menu_shadow_fac="0.3"
        menu_shadow_width="4"
        icon_alpha="1"
        icon_saturation="0.5"
        widget_emboss="#524f6705"
        editor_outline="#524f67"

attacus

This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.

Running your own encrypted chat service with Matrix and Riot

Workshop Instructor:

• Lilly Ryan @attacus_au

This workshop is distributed under a CC BY-SA 4.0 license.

What are we doing here?

trungdq88

Handling Page Transitions on Single Page Web Apps

Real world application with a lot of pages (or "screens") have to deal with problem managing the pages' DOM and memory efficiently and at the same provide a nice smooth transition effect between pages. This is not a real problem when you do it in native apps since Android or iOS already handle the hard work for you, but when come to JavaScript, HTML, and CSS, running on mobile browsers, this is the real challenge.

There are 2 common approaches to solve this problem:

• Approach 1: Keep all the pages in the DOM tree, use CSS (for example display) to transit between pages.

confiks

# Not extensively tested
# Put this script in the action_plugins directory of your playbook directory 
# If you have issues, please report it in the comments (or fork and fix)

# Usage:
# - name: "Ask the user if we should continue."
#   action: ask_key prompt="Continue? Yes / No / Random (y/n/r)?" accepted_keys="['y', 'n', 'r']"
#   register: answer
#
# The pressed key is now in answer.key