| // Consider, for example, parsing a large JSON string. Suppose that the data is large | |
| // enough that parsing takes at least 500 milliseconds. That is clearly too long to allow | |
| // JavaScript to run on the client, as it will interfere with the user experience. This particular | |
| // task is difficult to break into small chunks with timers, so a worker is the ideal solution. The | |
| // following code illustrates usage from a web page: | |
| var worker = new Worker("jsonparser.js"); | |
| //when the data is available, this event handler is called | |
| worker.onmessage = function(event){ |
| .gist-highlight { | |
| border-left: 3ex solid #eee; | |
| position: relative; | |
| } | |
| .gist-highlight pre { | |
| counter-reset: linenumbers; | |
| } | |
| .gist-highlight pre div:before { |
| // ---------- Messing around with sorting -------------- | |
| (function stableSort(v) { | |
| var dv = []; | |
| for (var i=0; i<v.length; i++) { | |
| dv[i] = [v[i], i]; | |
| } | |
| dv.sort(); |
| jQuery.extend({ | |
| myFunction: function (){ | |
| // jqglobal => Tab | |
| // this will add a global function that that can be accessed via the dollar sign does not work on elements | |
| // e.g. jquery.myFunction() | |
| } | |
| }); | |
| jQuery.fn.extend({ | |
| myFunction: function () { |
| // timedProcessArray | |
| // Since each new Date object is initialized with the current system time, you can time | |
| // code by creating new Date objects periodically and comparing their values. The plus | |
| // operator (+) converts the Date object into a numeric representation so that any further | |
| // arithmetic doesn’t involve conversions. This same basic technique can be used to op- | |
| // timize the previous timer patterns. | |
| function timedProcessArray(items, process, callback){ | |
| var todo = items.concat(); //create a clone of the original |
| // Beacons | |
| // This technique is very similar to dynamic script tag insertion. JavaScript is used to create | |
| // a new Image object, with the src set to the URL of a script on your server. This URL | |
| // contains the data we want to send back in the GET format of key-value pairs. Note that | |
| // no img element has to be created or inserted into the DOM. | |
| var url = '/status_tracker.php'; | |
| var params = [ | |
| 'step=2', | |
| 'time=1248027314' |
| <!-- | |
| Apache Ant provides the ability to combine several files via the concat task. It is im- | |
| portant, however, to remember that JavaScript files usually need to be concatenated in | |
| a specific order to respect dependencies. Once these dependencies have been estab- | |
| lished, using a filelist or a combination of fileset elements allows the order of the | |
| files to be preserved. Here is what the Ant target looks like: | |
| --> | |
| <target name="js.concatenate"> | |
| <concat destfile="${build.dir}/concatenated.js"> |
| public function getPostBackControl(page as Page) as string ' what control caused postback? | |
| dim control as control = nothing | |
| dim ctrlname as string = page.request.Params("__EVENTTARGET") | |
| if ctrlname isNot nothing andAlso ctrlname <> string.empty then | |
| control = page.findControl(ctrlname) | |
| else | |
| for each ctl as string in page.request.form | |
| dim c as control = page.findControl(ctl) |
| /* | |
| Similarly to the classical Holy Grail, you would use an empty temporary | |
| constructor function F(). You then set the prototype of F() to be the parent | |
| object. Finally, you return a new instance of the temporary constructor: | |
| */ | |
| function object(o) { | |
| function F() {} |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html