nickdunn

#!/usr/bin/env node

/*
 * Install dependencies with:
 *     npm install request request-promise-native bottleneck
 *
 * Replace YOUR_TENANT_NAME, MGMT_TOKEN, and FILENAME
 * The input file (FILENAME) should contain a list of user ids to delete, separated by newlines
 */

nickdunn

//FightCode can only understand your robot
//if its class is called Robot
var go=120;

var Robot = function(robot) {
	
};

nickdunn

/* CSS States */
body {
	background: url(http://dabblet.com/img/noise.png);
	background-color: #F5F2F0;
	font-family: Georgia, serif;
	font-size: 18px;
	line-height: 1.6em;
	text-shadow: 0 2px 0 white;
	color: #222;
}

nickdunn

<data>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>
  <entry>Text</entry>

nickdunn

<?xml version="1.0" encoding="UTF-8" ?>
<extension id="search_index" xmlns="http://symphony-cms.com/extensions/1.0">

	<!-- string, required -->
	<name>Search Index</name>

	<!-- string, required (@lang optional) -->
	<description lang="en">Index text content of entries for efficient full-text search.</description>

	<!-- string, required (must be Github for clever API things to happen) -->

nickdunn

<?xml version="1.0" encoding="UTF-8" ?>
<metadata version="1.0">
	<extension id="search_index">
	
		<!-- string, required -->
		<name>Search Index</name>

		<!-- string, required (@lang optional) -->
		<description lang="en">Index text content of entries for efficient full-text search.</description>

nickdunn

All:
- Indent work with tabs. No spaces unless lining up variables or objects vertically.
- View your whitespace and make sure your editor cleans it up.
- Use UTF-8 encoding with UNIX line endings. No exceptions.

CSS:
- Indent your CSS to denote selector is a child of or extends the previous selector. Comment extensions.
- Name classes sensibly using hyphens if necessary. No CamelCase.
- Order properties sensibly - 1. layout 2. text 3. backgrounds - is a common pattern.
- No inline hacks or parsing bugs; put it in to the right stylesheet.

nickdunn

<?xml version="1.0" encoding="UTF-8" ?>

<extension id="search_index">
	
	<!-- string, required -->
	<name>Search Index</name>

	<!-- string, required (@lang optional) -->
	<description lang="en">Index text content of entries for efficient full-text search.</description>

nickdunn

Forms have been an integral part of any interactive site since the dawn of time — they promote interactivity and are usually the most common way users interact with a site. It's commonplace that when a form is submitted (input), the website will take 'action' and do something with the data (processing) and then provide a user with the result (output). Symphony provides this logic layer via events.

This tutorial assumes you have a basic understanding of how events work in Symphony (if not, this may be a good introduction) and are semi-comfortable writing some PHP code. I'll be showing you some of the lesser-known features of Symphony events, including event priority, event chaining, and a brief demonstration of how to write a custom event. The difficulty level progresses as we go through, but with any luck you'll be able to learn a thing or two :)

Getting Started

The Scenario

Our client requires a form that allows a user to submit some detai

nickdunn

Member: Password (Required)

• Extends FieldInput (Text Input)
• SHA1
• Has a salt
• Can have minimum strength/length

Member: Username

• Extends FieldInput (Text Input)