Labels: git

Chrome may lack features, but it doesn’t poop on my code.

Slides and code from “Build Your Own Programming Language with JavaScript”

Labels: FUN, javascript

Labels: Randmo, SFBC

Launchpad is great for finding an application when I forget it’s name or isn’t properly indexed by Alfred yet.

[To set up a keyboard shortcut for Launchpad, which doesn't have one by default...] Go to System Preferences > Keyboard > Keyboard Shortcuts. Click on Launchpad & Dock. You’ll see that Show Launchpad is selected but there is no shortcut associated with it. In a fit of usability awkwardness (very un-Apple), it’s not clear how to set the shortcut. Double-click to the right of the row below the dock hiding shortcut, and an input field will appear. Perform your shortcut input there (I chose to use CMD-OPT-L). It’s set and will trigger now.

Labels: os x

To see the commits you have in HEAD that are not in origin/master:

git log origin/master..

To blow them away and make your HEAD the same as origin/master:

git reset --hard origin/master

Labels: git

Labels: noteToSelf, oracle

Sorry, that was a PEBKAC (Problem Exists Between User And Chair)

All I needed to do was turn on "auto commit" in SQL Developer.
Tools -> Preferences
Click next to Database,
Select Worksheet Parameters
Click checkbox to mark "Autocommit in SQL Worksheet"
Close SQL Developer and re-launch.

Problem solved.

Labels: oracle, problem solved, SQL Server

I highlight it in the SQL*Developer Object Navigator, invoke the right-click menu and chose Run. (I could use ctrl F11.) This spawns a pop-up window with a test harness. (Note: If the stored procedure lives in a package, you'll need to right-click the package, not the icon below the package containing the procedure's name; you will then select the sproc from the package's "Target" list when the test harness appears.)

Labels: oracle

Calling stored procedures using execute as above is specific to SQL*Plus. In fact, SQL*Plus converts execute some_proc() into BEGIN some_proc(); END;...

Labels: oracle

Labels: noteToSelf, oracle

Labels: noteToSelf, problem solved, vim

What Schiller is telling Isaacson is that prior to Jobs’s return to Apple, design was what happened at the end of the engineering process. Post-Jobs, engineering became a component of the design process. This shift made all the difference in the world.

Isaacson does not understand this, and his telling of the Antennagate saga illustrates this perfectly. Again, the aforequoted bit from Chapter 26:

On occasion this could backfire, such as when Jobs and Ive insisted on using a solid piece of brushed aluminum for the edge of the iPhone 4 even when the engineers worried that it would compromise the antenna.

The edge of the iPhone 4 (and now 4S) is the antenna. And it’s not made of brushed aluminum — it’s bead-blasted stainless steel. ... The trade-off was that moving the antennas to the outside left more room on the inside — room for a bigger battery, other components, and allowed for the device to be thinner. Isaacson paints Jobs and Ive as being concerned only with how it looked and felt, with engineers left to worry about how it worked. The truth is that the design was how it worked.

private static object _LogLock = 0;     // needs to be at the containing object's level
                                        // so, in this case, static object global

// Convenience function to log jive.
public static void logStuff(string strToLog)
{
        // obviously C:\temp must exist
        string strLogFile = "C:\\temp\\appLog.log";
        string strDateFormat = "MM/dd/yyyy hh:mm:ss.fff tt";

        try
        {
                // When you have multiple AJAX (because, duh, asynchronous)
                // calls going at once which, each of which might be calling
                // parts of your .NET website that log stuff, you're likely to
                // eventually run into concurrent logStuff calls.  And since
                // one "logStuff" might have your log file locked when the
                // second comes along and also wants to log some stuff, you're
                // going to want to lock the process so that you don't throw
                // exceptions.  Now, the second logStuff call will wait
                // patiently until the lock on _LogLock is released.

                // More information here:
                // http://stackoverflow.com/questions/7419172/streamwriter-lock-not-working
                // http://msdn.microsoft.com/en-us/library/c5kehkcz(v=vs.71).aspx
                lock (_LogLock)
                {
                        if (!File.Exists(strLogFile))
                        {
                                // Create a file to write to.
                                using (StreamWriter sw = File.CreateText(strLogFile))
                                {
                                        sw.WriteLine("Our application's log file.");
                                        sw.WriteLine("Created " 
                                                + DateTime.Now.ToString(strDateFormat));
                                        sw.Close();
                                }
                        }

                        // This text is always added, making the file longer over time
                        // if it is not deleted or cleaned up.
                        using (StreamWriter sw = File.AppendText(strLogFile))
                        {
                                sw.WriteLine(DateTime.Now.ToString(strDateFormat) + ":");
                                sw.WriteLine("\t" + strToLog.Replace("\n", "\n\t"));
                                sw.Close();
                        }
                }
        }
        catch (Exception e)
        {
                // probably b/c C:\temp\ doesn't exist or isn't accessible.
                System.Diagnostics.Debugger.Break();    

                // insure that's the problem.
                // In production, if you forget to remove this exception handler
                // or to move log location to something valid on the server/box, 
                // it'll quietly fail.
        }

}

Labels: c#, code, noteToSelf

class Package
{
     public string Company { get; set; }
     public double Weight { get; set; }
     public long TrackingNumber { get; set; }
}

//...

// Create a Dictionary of Package objects, 
// using TrackingNumber as the key. 
Dictionary dictionary = 
     packages.ToDictionary(p => p.TrackingNumber);

Labels: c#, noteToSelf

Labels: Other Stuff, Spider-Man

Nesting ExtJS 2.0 TreePanel inside Accordian
The Accordian panel in ExtJS 2.0 javascript framework, will error out if an item (Ext.Component) does not possess a header. The easiest way to create an header is to set the title property.

Labels: ExtJS, noteToSelf

Note that a declared type of "FLOATING POINT" would give INTEGER affinity, not REAL affinity, due to the "INT" at the end of "POINT".

Labels: noteToSelf, oracle

Put this all together, and you get this:
lsof | grep /Volumes/Workspace

In English: Get a list of all the open files, and show me a list of those results that are on this particular volume.

//doesn't accurately test for existence
if (person.name){
    //yay! property exists!
}

At first glance, this seems okay. However, understanding how JavaScript works reveals some problems with this approach. First, this will only succeed if the value of person.name is truthy, meaning it’s an object, a non-empty string, a non-zero number that’s not NaN, true, and not null or undefined. That means if person.name is the empty string (“”), this check will fail. Failing, in this case, doesn’t mean that the property doesn’t exist. In fact, the property does exist and contains a value, but the value is falsy and so doesn’t pass this test. [emph mine -mfn]

Labels: colbert, javascript

As others have said, the iteration through the array is probably the best way, but it has been proven that a decreasing while loop is the fastest way to iterate in JavaScript. So you may want to rewrite your code as follows:

function contains(a, obj) {
    var i = a.length;
    while (i--) {
       if (a[i] === obj) {
           return true;
       }
    }
    return false;
}

   1 //==============================================
   2 // Use the reader to create the data store
   3 //==============================================
   4 // note that I've subclassed Store (as MyQueryDataStore) here. 
   5 // No operational difference in this code, however.
   6 var myStore = new MyQueryDataStore({
   7         url: './json/gridValues.json',
   8         reader: myReaderTest
   9 });
  10 
  11 // How to iterate the data once it's returned, remembering that we're
  12 // dealing with an asynchronous paradigm here.
  13 myStore.on("load", function(s,rs) {
  14         console.log("and we're back");
  15         this.each(function(record) {
  16             //var strFieldName = this.fields.get(3).name;
  17             //console.log('record data from callback: ' + record.get(strFieldName));
  18         });
  19 });
  20 myStore.load(); // AJAX call to get the data happens now.
  21 // the Store is going to call the load method of its local
  22 // HttpProxy...
  23 // this.proxy.load(p, this.reader, this.loadRecords, this, options);
  24 // ... the request sent to the server has a callback referenced to
  25 // the store's loadRepsonse method, which includes a call to read
  26 // the response with the referenced DataReader.
  27 //
  28 // Afterwards, the proxy calls the Store's loadRecords method.
  29 // The already Read response is passed with that call as [o] in
  30 // loadRecords' first parameter.
  31 //      loadRecords : function(o, options, success){
  32 //          ...
  33 //          var r = o.records, t = o.totalRecords || r.length;
  34 //
  35 // And voila.  That's the life of a JSON return to DataStore request.

 * In Ext.data.JsonReader, for some reason, the equivalent variable in readRecords
 * for [fieldManager] (in that case, named [f]) was used to perform the tasks of both
 * [fldColumnArchetype] and [fieldCurrent] variables here.  I think it's just an
 * obfuscation technique (like the reused [v] throughout), as the use here seems
 * to have no relationship with the original fieldManager declaration.  That is,
 * you could have used [foo] in either spot if you'd wanted, but they strangely
 * and unintuitively recycled instead. (Or I've missed something important!) The
 * kingdom for a strongly typed language...
 *
 * There were other occurrences of poorly scoped variables and var choices, like...
 *  var s = this.meta;    // This var only made things *less* self-commenting.  Gone.
 * ... that have been removed from the JsonReader codebase.  It's like the code
 * had been minimally minimized and purposely obfuscated, but only partially so --
 * and that obfuscation done by hand.

Labels: code, ExtJS, javascript, noteToSelf

var x = 10;
var o = { x: 15 };
function f(message)
{
    alert(message);
    alert(this.x);
}

f("invoking f");
f.call(o, "invoking f via call");

    initComponent:function() {
        // call parent initComponent    
        Ext.ux.IconCombo.superclass.initComponent.call(this);
    } // end of function initComponent

Labels: ExtJS, javascript, problem solved