cypres

<?php

/**
 * PHP class to convert Latitude & Longitude coordinates into UTM & Lambert Conic Conformal Northing/Easting coordinates.
 * 
 * This class encapsulates the methods for representing a geographic point on the earth in three different coordinate systema. Lat/Long, UTM and Lambert Conic Conformal.
 * 
 * Code for datum and UTM conversion was converted from C++ code written by Chuck Gantz (chuck.gantz@globalstar.com) from http://www.gpsy.com/gpsinfo/geotoutm/
 * This code was converted into PHP by Brenor Brophy (brenor@sbcglobal.net) and later refactored for PHP 5.3 by Hans Duedal (hd@onlinecity.dk).
 * 

rponte

QUESTION:

EntityManager.merge() can insert new objects and update existing ones.

Why would one want to use persist() (which can only create new objects)?

ANSWER:

Either way will add an entity to a PersistenceContext, the difference is in what you do with the entity afterwards.

jjt

// Not so DRY:

// module_1.js
define(["underscore", "zepto", "momentjs",...], function(_, $, Moment, ... ) {
  // ...
});

// module_2.js
define(["underscore", "zepto", "momentjs",...], function(_, $, Moment, ... ) {
  // ...

alexeds

Move your stashes from one repo to another

---

This was useful for me when we created a new branch for a new major release, but were still working on our current version as well. I cloned our repo again and kept the new project on our new branch, but also wanted to get my stashes there.

Download your stashes

git stash show -p > patch

You'll have to specify your stash and name your file whatevery you want. Do this for as all your stashes, and you'll have patch files in your pwd.

eyecatchup

// ABC - a generic, native JS (A)scii(B)inary(C)onverter.
// (c) 2013 Stephan Schmitz <eyecatchup@gmail.com>
// License: MIT, http://eyecatchup.mit-license.org
// URL: https://gist.github.com/eyecatchup/6742657
var ABC = {
  toAscii: function(bin) {
    return bin.replace(/\s*[01]{8}\s*/g, function(bin) {
      return String.fromCharCode(parseInt(bin, 2))
    })
  },

marcaube

A few days – or was it weeks – ago, I answered hastily to a question on the Symfony2 Google Group. The question is simple but the answer is not : How do your organise your code in a Symfony project?

I've had some time to think about it and wanted to elaborate on the subject. Writing makes me think, and thinking is good.

Everyone has their own way to do this. Some organize their code in a way that makes them faster – like in the RAD edition. Some others take the time and put the emphasis on making things isolated, modular and re-usable. Most of us fall somewhere in the middle, still trying to find the structure that suits us, our workflow or our organization the most.

My original answer to the question was to keep the domain logic separate from the bundle code, i.e. place it in a re-usable library. The reason is that your business logic should be encapsulated into models, outside of persistance concerns, logging and al

krisrybak

Please make sure you use Sublime 3 first:

• From the Sublime Tex Menu choose option About and make sure build is higher that 3xxx
• Navigate to your Sublime text packages directory: Sublime Text Menu > Preferences > Browse Packages...
• Copy PHP folder form Cache into Packages folder
• Locate PHP.tmLanguage file insde PHP folder and open in for edit:
• Inside yuor PHP.tmLanguage find: <key>php_doc</key> node and update the language file by adding the following snippet under the php_doc's patterns array:

    <dict>

mpj

The future is here: Classless object-oriented programming in JavaScript.

Douglas Crockford, author of JavaScript: The Good parts, recently gave a talk called The Better Parts, where he demonstrates how he creates objects in JavaScript nowadays. He doesn't call his approach anything, but I will refer to it as Crockford Classless.

Crockford Classless is completely free of class, new, this, prototype and even Crockfords own invention Object.create.

I think it's really, really sleek, and this is what it looks like:

function dog(spec) {

subfuzion

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

• Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
• Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

ace-dent

on run
	# TODAY - Returns today's date!
	# Create your own Service, to avoid 3rd Party software (WordService, etc.)
	# In Automator:
	# > Service receives 'no input' in 'any application'
	# > Output replaces selected text
	# Add Shortcut (e.g. Ctrl+Cmd+T - it's hard to find a free shortcut!):
	# > Preferences > Keyboard > Keyboard Shortcuts > Services
	# When setting up Keyboard Shortcut, *exit* the target app before testing. (It seems shortcuts are only refreshed when app is launched)
	# Adjust 'Short' Date format