- List I
- Thing To Do
- Another Thing To Do
- This one has sub-items
- HALP I AM BROKEN
- ME TOO
- Totes OK
- List II
- But if I do this
- This works fine
Annotator.Plugin.Madison = function(element, options){ | |
this.options = options; | |
} | |
$.extend(Annotator.Plugin.Madison.prototype, new Annotator.Plugin(), { | |
events: {}, | |
options: {}, | |
pluginInit: function(){ | |
this.annotator.viewer.addField({ | |
load: load_fn.bind(this, user) |
<?php | |
/** | |
* The Law class, for retrieving data about individual laws. | |
* | |
* PHP version 5 | |
* | |
* @license http://www.gnu.org/licenses/gpl.html GPL 3 | |
* @version 0.8 | |
* @link http://www.statedecoded.com/ |
clearsolr() { | |
curl http://localhost:8983/solr/$1/update -H "Content-type: text/xml" --data-binary '<delete><query>*:*</query></delete>' | |
curl http://localhost:8983/solr/$1/update -H "Content-type: text/xml" --data-binary '<commit />' | |
curl http://localhost:8983/solr/$1/update -H "Content-type: text/xml" --data-binary '<optimize />' | |
curl http://localhost:8983/solr/$1/update -H "Content-type: text/xml" --data-binary '<commit />' | |
} |
#Status Messages
Status messages should be sent first thing in the morning, before the developer begins work. They should list all projects that they're currently actively involved with, as well as any side items that need to be addressed. For all tasks that fall outside the scope of project work, or for direct feedback, a Housekeeping
list item is recommended.
Messages should list the projects with their statuses at the top of each message. Underneath, include short descriptions of the status of each. The whole message should generally only be 5-10 sentences at most - be clear and to the point as much as possible. Make sure to list any items that are blocking you from completing work, and feel free to call out the responsible party.
Each project should list its status, from the following available options: OK
(everything is fine and progressing normally), HOLD
(waiting on something out of your control), WARNING
(something has gone wrong here), DANGER
(something has gone VERY wrong here), `F
<?xml version="1.0" encoding="UTF-8"?> | |
<law> | |
<structure> | |
<unit label="article" identifier="g95" order_by="g95" level="1">g95</unit> | |
</structure> | |
<section_number>g95-22F</section_number> | |
<catch_line/> | |
<order_by>22F</order_by> | |
<text> | |
<section prefix="(a)"> |
<?php | |
/** | |
* Wrapper to get terms in a nested fashion. | |
* This gets a little complicated. Basically, we're creating a placeholder in | |
* $children to hold the child terms of each parent term. Then we create a | |
* reference to that element in the parent term. So nesting happens via magic. | |
*/ | |
public function get_terms_nested($args) | |
{ | |
$temp_terms = $this->get_terms($args); |
<?php | |
/* | |
* Translate a non-standard object into an associative array object. | |
* Super-useful for dealing with simplexml objects. | |
*/ | |
function simpleXML_to_object($obj) | |
{ | |
$data = new StdClass(); | |
if( | |
(is_object($obj) && get_class($obj) == 'SimpleXMLElement') |
function get_top_level_page() { | |
global $top_level_page; | |
global $post; | |
// Get global page heading | |
if( is_page() && !$top_level_page) { | |
/* Get an array of Ancestors and Parents if they exist */ | |
$parents = get_post_ancestors( $post->ID ); | |
/* Get the top Level page->ID count base 1, array base 0 so -1 */ | |
if($parents) { | |
$id = $parents[count($parents)-1]; |
CREATE FUNCTION merge_kvstore(dkey character varying, ddata BYTEA) RETURNS VOID AS | |
$$ | |
BEGIN | |
LOOP | |
-- first try to update the key | |
UPDATE kvstore SET value = ddata WHERE key = dkey; | |
IF found THEN | |
RETURN; | |
END IF; | |
-- not there, so try to insert the key |