Updates

Author: eoinkelly

capybara/capybara.md

@@ -34,15 +34,15 @@ Capybara has 2 main parts
     * imporant methods
         * `#visit`
         * `#current_path`
-    * delegates many methods to `Capybara::Document`
+    * delegates many methods to `Capybara::Document` so essentially you can
+      think of a Session as having a superset of the Document|Element API
     * `page` in your test is an instance of `Capybara::Session`
 * `Capybara::Document`
     * represents the HTML document
 * `Capybara::Result`
-    * A Result represents a collection of `Capybara::Element` on the page. It
+    * A Result represents a collection of `Capybara::Node::Element` on the page. It
       is possible to interact with this collection similar to an `Array`
-      because it implements Enumerable and offers the following Array methods
-      through delegation
+      because it implements Enumerable and offers Array methods through delegation
 * `Capybara::Node::Base`
 * `Capybara::Node::Element`
 * `Capybara::Query`
@@ -96,11 +96,11 @@ Element and Document are both children of Node::Base. They share 3 kinds of meth
         * => They inherit `find` wait behaviour
 3. Matchers
     * these methods fall into 2 categories:
-        1. predicate methods
-            * return true|false
-        2. asserts
+        1. asserts
             * return true if pass
             * return Capybara::ExpectationNotMet if fail
+        2. predicate methods
+            * return true|false
     * examples
         1. `#assert_no_selector`
         2. `#assert_no_text`
@@ -132,6 +132,7 @@ Element and Document are both children of Node::Base. They share 3 kinds of meth
 4. Node methods
     * These are stubbed out in capybara but must be implemented by whatever driver you use
     * It seems like drivers subclass Driver::Node
+    * The "action" methods above use #find to get the Node::Element and then manipulate it with these
     * => they have a different implementation in different drivers
     * Examples:
         1. `==(other)`
@@ -157,6 +158,88 @@ Element and Document are both children of Node::Base. They share 3 kinds of meth
        21. `visible?`
        22. `visible_text`
 
+
+
+## Drivers
+
+Inheritance Heirarchy
+
+```
+Object
+    Capybara::Driver::Base
+        RackTest::Driver
+        Selenium::Driver
+    Capybara::Driver::Node
+        RackTest::Node
+        Selenium::Node
+```
+
+* Driver::Base methods:
+    ```
+    accept_modal
+    browser_initialized?
+    close_window
+    current_url
+    current_window_handle
+    dismiss_modal
+    evaluate_script
+    execute_script
+    find_css
+    find_xpath
+    go_back
+    go_forward
+    html
+    invalid_element_errors
+    maximize_window
+    needs_server?
+    no_such_window_error
+    open_new_window
+    reset!
+    resize_window_to
+    response_headers
+    save_screenshot
+    status_code
+    switch_to_window
+    visit
+    wait?
+    window_handles
+    window_size
+    within_frame
+    within_window
+    ```
+* Driver::Node methods
+    ```
+    =
+    []
+    all_text
+    checked?
+    click
+    disabled?
+    double_click
+    drag_to
+    hover
+    initialize
+    inspect
+    path
+    right_click
+    select_option
+    selected?
+    set
+    tag_name
+    trigger
+    unselect_option
+    value
+    visible?
+    visible_text
+    ```
+
+
+
+You can get at the current driver (which will have real implementations of these methods) via `page.driver`
+
+
+# Getting stuff from a Capybara::Node::Element
+
 If you have an instance of Capybara::Node::Element, how do you find out stuff about it
 
 ```ruby

clojure/clojure.clj

@@ -0,0 +1,18 @@
+; Clojure
+; ;;;;;;;
+
+; clojure runs on the JVM and is nice for concurrent processes
+; my-program.clj
+
+; Start the repl
+java -cp clojure-1.4.0.jar clojure.main
+
+; Run some basic stuff
+(+ 1 2 3)
+(println "Hello world")
+
+; show an alert box
+(javax.swing.JOptionPane/showMessageDialog nil "Hi")
+
+; Exit the repl
+(System/exit 0)

ember/ember-cli.md

@@ -14,3 +14,17 @@ Conclusion: the main barrier to using it is that I don't know what they are doin
 # Ember-cli 101 book
 
 Express.js has middlewares that can be used for tricks
+* tests are run by Testem
+    * can run in "CI" or "development" mode
+* compiles down to AMD modules
+* files are named using "kebab case" so-they-look-like-this.thing
+* you can prefix apps with their type e.g. `/routes/index.js` or `routes/route-index.js` are acceptable
+
+
+# Watchman
+
+* runs as a daemon
+* watches for changes in "roots" (directory heirarchies)
+* treats symlinks as ordinary files, does not follow them
+* you can "subscribe" to file changes which occur under a "root"
+* is smart enough to wait for a root to settle down if it changes quickly

networking/dns.md

@@ -0,0 +1,42 @@
+# DNS records
+
+* http://en.wikipedia.org/wiki/List_of_DNS_record_types
+
+* each "resource record" (database row) is stored in a "zone file" and has the following fields
+
+1. hostname
+2. type
+3. value
+4. TTL
+
+# @ symbol
+
+* RFC 1035 defines @ as a shortcut for the "current origin"
+* it is a shortcut for the root of your domain e.g. `@` is a shortcut for `foo.com` if you are configuring DNS records for `foo.com`
+
+# Common DNS records
+
+* A
+    * address record
+    * maps the string in "hostname" to the IP address in "value" field
+* CNAME
+    * canonical name record
+    * aliase one hostname to another
+    * if the "hostname" matches then retry the lookup with the string in "value" as a query
+* TXT
+    * arbitrary text. originally just for human readable text but often machine
+      readable now e.g. Sender Policy Framework, keybase verification
+* MX {number}
+    * maps a domain to a list of "message transfer agents" (aka mail servers) for that domain
+    * {number} is the priority of that MTA
+* SRV {number}
+    * Service locator
+    * used for newer protocols instead of creating protocol specific records like MX
+    * works like a generalized MX record
+
+# dig
+
+```
+dig -t ANY interesting.com @some_name_server
+dig -t ANY interesting.com @8.8.8.8
+```

perl/perl-snippets.md

@@ -0,0 +1,9 @@
+# Perl Snippets
+
+Remove non-ascii from a file
+
+	perl -i.bk -pe 's/[^[:ascii:]]//g;' <filename>
+
+Search & Replace across all PHP files in current dir
+
+	perl -pi -w -e 's/wrong/right/g;' *.php