Lucian Naie lnaie

#Four Ways To Do Pub/Sub With jQuery and jQuery UI (in the future)

Between jQuery 1.7 and some of work going into future versions of jQuery UI, there are a ton of hot new ways for you to get your publish/subscribe on. Here are just four of them, three of which are new.

(PS: If you're unfamiliar with pub/sub, read the guide to it that Julian Aubourg and I wrote here http://msdn.microsoft.com/en-us/scriptjunkie/hh201955.aspx)

##Option 1: Using jQuery 1.7's $.Callbacks() feature:

$.Callbacks are a multi-purpose callbacks list object which can be used as a base layer to build new functionality including simple publish/subscribe systems. We haven't yet released the API documentation for this feature just yet, but for more information on it (including lots of examples), see my post on $.Callbacks() here:

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

Recorded talks by Damian Edwards & David Fowler

	using System;

	namespace Nmea
	{
	class Parser
	{
	private enum STATES : byte
	{
	begin, body, checksum1, checksum2, checksum_lr, checksum_cf, cf
	}

	// knockout 2.2.1

	ko.utils.arrayFilter = function (array, predicate) { /* .. */ }

	ko.utils.arrayFirst = function (array, predicate, predicateOwner) { /* .. */ }

	ko.utils.arrayForEach = function (array, action) { /* .. */ }

	ko.utils.arrayGetDistinctValues = function (array) { /* .. */ }

	eXtreme Go Horse (XGH) Process

	Quelle: http://gohorseprocess.wordpress.com

	Übersetzung ursprünglich von https://gist.github.com/Neffez/f8d907ba8289f14e23f3855011fa4e2f

	1. Ich denke, also ist es nicht XGH.
	In XGH wird nicht gedacht, es wird das erste gemacht, was in den Sinn kommt. Es gibt auch keine zweite Option, die erste ist schneller.

	2. Es gibt 3 Wege ein Problem zu lösen: den richtigen Weg, den falschen Weg und den XGH Weg, welcher exakt wie der falsche ist, aber schneller.

	namespace Microsoft.AspNet.Builder
	{
	public static class MediatRExtensions
	{
	public static IServiceCollection AddMediatR(this IServiceCollection services, params Assembly[] handlerAssemblies)
	{
	services.AddTransient<IMediator>(x => new Mediator(x.GetService<SingleInstanceFactory>(), x.GetService<MultiInstanceFactory>()));
	services.AddTransient<SingleInstanceFactory>(x => t => x.GetRequiredService(t));
	services.AddTransient<MultiInstanceFactory>(x => t => x.GetServices(t));

	[TestInitialize]
	public void BeforeEach()
	{
	_fixture = new Fixture();

	// client has a circular reference from AutoFixture point of view
	_fixture.Behaviors.Remove(new ThrowingRecursionBehavior());
	_fixture.Behaviors.Add(new OmitOnRecursionBehavior());
	}

	using ProjectTest.MyModels;
	using SQLite.Net;
	using System;
	using System.Collections.Generic;
	using System.Linq;
	using System.Text;
	using System.Threading.Tasks;
	using Xamarin.Forms;

	namespace ProjectTest.Database

	using Microsoft.Extensions.Logging;
	using Moq;
	using System;
	using System.Collections.Generic;
	using System.Linq;
	using System.Threading.Tasks;
	using Xunit;

	namespace Knaap.Utilties
	{