d4tocchini

Facbeook Graph API, what you need to know

The hello-world basics as of 9/20/12

Which is better, FQL or the Facebook Graph API?

Of the two ways to query, which is better? The answer is complicated... In the end, the Facebook Graph API is my preferred. It is simpler, the returned data is better formatted and its newer version. FQL can do more, but not much more since the addition Field Expansions, which were just added the end of last month!

What is the query for the Facebook Home Feed ?

d4tocchini

{{view Th.PageLayout id="home-page-layout" pageTemplates="[pageA,pageB]" contentBinding="App.homeTiles"}}

d4tocchini

I've already communicated this with you, Greg & Alex, but I thought I'd shoot the mailing list a summary...

Heads-up: code snippets are coffeescript

My focus has been on high-level declaration of constraints, not so much solver API. My API goals thus far:

• Chain-able, ie. 100 <= w <= 1000 <= w2...
• Close-as-possible resemblance to natural forms of equality and inequality equations. This also makes the Ometa language parsing pretty straightforward.
• Higher-ordered constraint objects that contain constraint primitives. Maybe current c.Constraint should be c.ConstraintPrimitive? A chained constraint equation would contain many constraint primitives. This would also allow subclassing of constraints that internally setup many constraint primitives.
• Convention & hooks for subclassing core Constraint object for implementing custom relationships such as "inside", "left-of", etc... I imagine a plugin-like eco-system, where the API can expand to include W3C's grid-layout templates and [Apples Visu

d4tocchini

$ ->
  # run quaddemo?
  #runit()
  
  global = window
  BP = (options) ->
    console.log options
    alert options
  
  ERROR = (options) ->

d4tocchini

$.templates.add([
  {
    name:'btn_gear'
    template:
      '''
        <div class="iconBtn iconBtn_gear circle50 vBox boxPackCenter boxAlignCenter">
  {{>icon_gear}}
</div>
      '''
  }  {

d4tocchini

$ = jQuery
$ ->

  $(window).responsive
    queries:
      [
          #1600
          if: (el) ->
            return $(el).width() > 1600 

d4tocchini

###

  One grid system to rule them all, and in the javascript bind them
  
  
  Concerns
  =====================================
  
    - IE positioning... see isotope.js and https://github.com/louisremi/jquery.transform.js#
      - needs to be absolue in relative? or absolute in absolute too?

d4tocchini

      $(window).responsive
        queries:
          [
            {
              query: (el) ->
                if $(el).width() > 960 then return true else return false

              response: (el) ->
                $('.G_main_grid')
                  .css

d4tocchini

    # intialize a grid on '.mainGrid' with default options using G's subclass of jQuery
    
    G.$('.superCoolGrid').grid({id:'super'})
    
    # now that the grid has been initialized you can access it via G[id]:
    
    alert 'this is the grid ' + G.super 
    
    # configure a grid's dimensions to have 12 fluid columns and a vertical baseline grid of 1.6em's
    

d4tocchini

  GDOM:
    nodes:
      id: 'mainGrid'
      $: {nodeLayout:{type:'float', options:''}, css:{margin:''} }
      nodes:
        [
          { 
            id: 'title',    
            $: {width:'100%', height:G.v(5)} 
          }