I came up with this quick solution using only GF filters and jQuery.

What the editor will look like

What the form will look like

The code

Add the placeholder option to the editor

/* In the functions.php file */
/* Add a custom field to the field editor (See editor screenshot) */
add_action("gform_field_standard_settings", "my_standard_settings", 10, 2);
function my_standard_settings($position, $form_id){
	// Create settings on position 25 (right after Field Label)
	if($position == 25){
		?>
		<li class="admin_label_setting field_setting" style="display: list-item; ">
			<label for="field_placeholder">Placeholder Text
				<!-- Tooltip to help users understand what this field does -->
				<a href="javascript:void(0);" class="tooltip tooltip_form_field_placeholder" tooltip="&lt;h6&gt;Placeholder&lt;/h6&gt;Enter the placeholder/default text for this field.">(?)</a>
			</label>
			<input type="text" id="field_placeholder" class="fieldwidth-3" size="35" onkeyup="SetFieldProperty('placeholder', this.value);">
		</li>
		<?php
	}
}

/* Now we execute some javascript technicalitites for the field to load correctly */
add_action("gform_editor_js", "my_gform_editor_js");
function my_gform_editor_js(){
	?>
	<script>
		//binding to the load field settings event to initialize the checkbox
		jQuery(document).bind("gform_load_field_settings", function(event, field, form){
			jQuery("#field_placeholder").val(field["placeholder"]);
		});
	</script>
	<?php
}

Use jQuery to inject the placeholder value to the fields

/* In the functions.php file */
/* We use jQuery to read the placeholder value and inject it to its field */
add_action('gform_enqueue_scripts',"my_gform_enqueue_scripts", 10, 2);
function my_gform_enqueue_scripts($form, $is_ajax=false){
	?>
	<script>
	jQuery(function(){
		<?php
		/* Go through each one of the form fields */
		foreach($form['fields'] as $i=>$field){
			/* Check if the field has an assigned placeholder */
			if(isset($field['placeholder']) && !empty($field['placeholder'])){
				/* If a placeholder text exists, inject it as a new property to the field using jQuery */
				?>
				jQuery('#input_<?php echo $form['id']?>_<?php echo $field['id']?>').attr('placeholder','<?php echo $field['placeholder']?>');
				<?php
			}
		}
		?>
	});
	</script>
	<?php
}

That’s it! take it for a spin and let me know how it goes.

Issues

Right now it only works with single lines, textareas and the other simple fields. But that’s usually the only places where you will ever need them.

Internet Explorer support update

Angela Bowma wrote a post with a solution that works in Internet Explorer or browsers that don’t support the placeholder property.

$pages = get_pages(array(
	'meta_key' => '_wp_page_template',
	'meta_value' => '<Insert your template file name here>'
));

Example of use

List all the published pages that use the template “page-quote.php”:

$pages = get_pages(array(
	'meta_key' => '_wp_page_template',
	'meta_value' => 'page-quote.php'
));
foreach($pages as $page){
	echo $page->post_title.'<br />';
}

How does it work?

The template assigned to the page is stored as a meta data by the key ‘_wp_page_template’. Using the get_pages() WordPress function, we can ask for the page where ‘_wp_page_template’ equals our template name.

More Info

get_pages() documentation

Hope this helps, post a comment if you have any questions.

<script>
my_url_object = document.location;
</script>

That code yields out something like this in Chrome’s Javascript console:

Example of use:

You can show certain section of your code depending on a hash tag in the URL:

<div id="section-1" class="section">Section 1</div>
<div id="section-2" class="section">Section 2</div>
<script>
$(function(){
	// Get the hash parameter from the URL.
	active_section = document.location.hash;
	// Hide ALL the sections
	$('.section').css('display','none');
	// Show the section specified in the URL
	// The URL can be:
	// - http://localhost/example/index.html#section-1 , or
	// - http://localhost/example/index.html#section-2
	$(active_section).css('display','block');
});
</script>

Post a comment if you need help!

What’s the current problem?

Once you’ve uploaded images to the media library, it’s impossible to resize them to the new sizes that you’ve added using add_image_size() function.

How does AJAX Thumbnail Rebuild solves the problem?

Although the name is a little bit misleading, ATR (AJAX Thumbnail Rebuild) goes through all the images that you have uploaded before and creates the new image sizes that you’ve added using the add_image_size() function.

Other similar plugins used to do all this process in the backend, which often timed out for large image libraries. That’s where ATR came up with a way to do it using AJAX and that’s why the plugin name is AJAX Thumbnail Rebuild.

How to use it?

1. Add the image sizes that you’re going to use across your site using add_image_sizes() WordPress function
2. Download and install the AJAX Thumbnail Rebuild plugin on your WordPress site
3. Go to “Tools > Rebuild Thumbnails”
4. Select the thumbnail sizes that you want to re-generate and click “Regenerate all Thumbnails”

This is a great plugin and its functionality should really be considered to be included in WordPress.

Contact Ray Villalobos

@planetoftheweb
http://planetoftheweb.com/

Although, I wasn’t a big fan of the website, I admire the work and thought that was put into it and its development. It was also an excellent learning experience to see the workflow of the project

Check out their site here: http://6q.com/

Quotes

Links

6q — The site that they developed

Popplet — The application with the big diagram that Mark was using the explain the project process

wwwwwwwww.jodi.org/ — Just check out that page source code

I can’t remember what was the other link that they showed with the funky flash animations. If you remember it, please post it in the comments

http://daxo.de — Creative flash site with funky animations (Thanks to Priscille for sending the URL)

Contact Mark Reale

@markreale
http://markreale.net/ — Haha, love his website picture

Javascript is the most widely deployed language ion the world. People are creating more apps in JavaScript than before because:

• Computers are faster
• All the raising JavaScript libraries that standardize and make JS a lot cooler

JavaScript and PHP similarities

• Dynamic and loose
• C-like syntax
• Curly braces
• if, else, for, etc.
• Garbage collection
• Post-web

JavaScript and PHP differences

• Everything is an object
• Objects and inheritance
• Scope and this

Lint

• Bad parts are simple mistakes
• JSLint, JavaScript Lint, JSHint
• Auto lint

WordPress

The function wp_enque script helps you load common libraries like jQuery, Scriptaculous, jQUI, TinyMCE, and it lets let load your own js files. You can also specify if you want your files to load in the footer to optimize loading speed . Thanks @apike for answering my question.

JavaScript Libaries

• DOM (jQuery, Prototype) — Most popular libraries for manipulating the DOM
• MVC (Backbone, JSMBC, Spine) — Libraries that helps you write JavaScript in a more organized and MVC way
• Everything (ExtJS, YUI, SproutCore)  — They do everything
• microjs.com — Recently launched library where you can chose what you want

Debugging JavaScript

• console.log(), and console.trace()
• stack traces, step debugging

Other resources for learning JavaScript

• Learning Advanced JavaScript — http://ejohn.org/apps/learn/
• Douglas Crockford — javascript.crockford.com
• VanJS: — vanjs.com

Get in touch with Allen Pike

www.antipode.ca
www.steamclocksw.com
@apike

• Cart66
• Shopp
• WordPress Ecommerce

Shopp

http://shopplugin.net/

Pros

• Very solid plugin, backed up by strong businesses
• 7 cool widgets
• Payment gateways integration, you can download additional ones for a small fee
• Good support for inventory & stock alert
• Complete shipping modules
• Supports product variations
• Promotions
• Shortcodes for products, categories, etc.

Cons

• Doesn’t follow coding conventions, they have they’re own conventions.
• Doesn’t use WordPress features for functionality.

Cart66

http://cart66.com/

Pros

• Support most payment gateways, only pluggin that supports Authorize.net natively
• Good inventory management
• Complete shipping module
• Promotions support
• Shortcodes for shopping cart, products, category, etc.
• SEO — Automatically integrated with mayor SEO plugins like All-in-one SEO
• Very solid documentation and customer service
• Great support for digital products
• GPL

Cons

• Poor implementation for product variations, hard to follow syntax and feels incomplete
• They fall behind on the widgets, only comes with one.
• Doesn’t use WordPress features for functionality, has its own code convenctions.
• Only 4 filters, so it doesn’t allow for much customization
• Poor Internationalization
• Not too many widgets

WPEC (WordPress eCommerce)

http://wordpress.org/extend/plugins/wp-e-commerce/

Pros

• Lots of widgets — best seller, recent purchases, categories, child categories, etc.
• Payment Gateways — Supports most payment gateways
• Good inventory management
• Very complete shipping modules
• Supports Product Variations
• Support Shortcodes
• SEO
• Used to suck before, but now it’s getting awesome after 3.8 was launched
• Tons of actions and filter (+180) (+200 counting WordPress natives)
• Internationalization support, compatible with WordPress native functionality
• 8 widgets
• Great Community

Cons

• Lots of legacy bloat for backward compatibility

Contact Justin Sainton

@JS_Zao
http://zaowebdesign.com/
office@zaowebdesign.com

• Take ownership of your code, know what your site is really doing
• Build your own library of code and techniques for future projects
• “Make WordPress fo crazy things nobody else has thought of yet” — Sometimes there isn’t a plugin that does exactly what you want.
• Makes a great topic for a WordCamp talk (haha)

Benefits of taking control of your code

• Less bloat better performance
• Cleaner and simpler HTML/CSS/JS
• Plugins can confuse your visitors

Some benefits of using plugins

• Not always worth custom coding one-offs
• Some pluggins fo offer great functionality out-of-the-box
• Budget / Time constraints
• Standardization
• Upgrade compatibility — Some plugins are ver well maintained and are compatible with newer versions of WP

Examples & Interesting Ideas

• Extend WordPress’s image handling, galleries — This section can be improved a lot. It’s not intuitive.
• AJAX-ify parts of your theme and functions — Using AJAX to load sections of your site, instead of loading everything at the same time.
• Integrate a WP site with web services APIs — Integrating WordPress with external services, i.e.: Interacting with a CRM API

The (Image) Slider

Cameron showed a sample of a slider that he created for one of his clients. Not sure what was his point in showing all his code and the examples. It’s simple to

The map

He showed a 3 cool examples of custom made map applications that he’d developed in the past. He promised to post links to the examples. (Will update when he does)

The AJAX

He ran out of time to talk about AJAX-ify, but he showed some cool examples of posts that load on-the-fly with a modal window.

Follow Cameron Cavers on Twitter