import java.awt.FlowLayout;
import com.sun.java.swing.*;

public class SwingExample {
  public static void main(String[] args) {
 SwingUtilities.invokeLater(new Runnable() {
      public void run() {
        JFrame f = new JFrame("Swing Example Window");

        f.setLayout(new FlowLayout());

        f.add(new JLabel("Hello, world!"));
        f.add(new JButton("Press me!"));

        f.pack();

        f.setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);

        f.setVisible(true);
      }
    });
  }
}

Web Services:

• Standard defined by the W3C
• Protocol for applications to communicate over HTTP
• Defined by a WSDL
• Clients communicate with SOAP messages
• XML Serialization of messages
• Typically implements Remote Procedure Calls

• Too Complex
• Based on large software vendors' technologies (very few open source implementations)
• When created by toolkits, web services often break when changes to code or the SOAP stack are made due to changes in the WSDL
• Performance concerns due to use of XML for messages & SOAP/HTTP for enveloping and transport

Well, then... What are our other options?!?!

Web APIs: RESTful Web Services

• A set requests
• The structure of response messages

• HTTP requests
• XML or JSON reponse messages

What is REST?

Constraints described by the REST architectural style

• Client–server
• Stateless
• Cacheable
• Layered system
• Code on demand (optional)
• Uniform interface

Benefits of the REST architectural style

• Performance
• Independence
• Generality
• Scalability
• Simplicity

• Modifiability
• Visibility
• Portability
• Reliability
• Intermediary Components

Integrated into Google infrastructure, including:
• Gmail
• Google Calendar
• iGoogle
• orkut
• Google Maps
• Google Sites
• And now: Google Hangouts!

<?xml version="1.0" encoding="UTF-8" ?>
<Module>
  <ModulePrefs title="Hello Sammiches example" />
  <Content type="html">
     <![CDATA[ 
       Hello, Sammiches!
     ]]>
  </Content>
</Module>

<?xml version="1.0" encoding="UTF-8" ?>
<Module>
  <ModulePrefs title="User Preferences for __UP_username__" height="400" />
  <UserPref name="username" display_name="Name" required="true"/>
  <Content type="html">
     <![CDATA[ 
       <div id="content"></div>
       <script type="text/javascript" 
           src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.4/jquery.min.js">
       </script>
       <script type="text/javascript">
         // Get userprefs
         var prefs = new gadgets.Prefs();
         
         $('#content').html('Hello, ' + prefs.getString('username') + 
                            '<br> Would you like a Sammich?');
       </script>
     ]]>
  </Content>
</Module>

<?xml version="1.0" encoding="UTF-8" ?>
<Module>
  <ModulePrefs title="User Preferences for __UP_username__" height="400">
    <Require feature="tabs"/>
  </ModulePrefs>
  <Content type="html">
     <![CDATA[ 
       <script type="text/javascript">
         // gadgets.TabSet(opt_moduleId, opt_defaultTab, opt_container)
         var tabs = new gadgets.TabSet();
         for(var x = 0; x < 4; x++){
            var tab_Id = tabs.addTab("tab" + x); // String addTab(tabName, opt_params)
            document.getElementById(tab_Id).innerHTML = "Content for tab " + x;
         }
       </script>
     ]]>
  </Content>
</Module>

Google+ Plugins

• +1 Button
• Badge

Make it easy for users to share content on your website on Google+

<script type="text/javascript" src=
"https://apis.google.com/js/plusone.js"></script>


<g:plusone></g:plusone>		

<!-- YAY (HTML5) COMPLIANCE! -->
<div class="g-plusone" data-size="tall" ... ></div>

<!-- Async Loading - Huzzah! Non-blocking! -->
<script type="text/javascript">
  (function() {
    var po = document.createElement('script'); 
    po.type = 'text/javascript'; 
    po.async = true;
    po.src = 'https://apis.google.com/js/plusone.js';
    
    var s = document.getElementsByTagName('script')[0]; 
    s.parentNode.insertBefore(po, s);
  })();
</script>

+Snippet = Information posted to G+ Profile when page is +1'ed

1. Schema.org microdata (recommended)
2. Open Graph protocol
3. Title and Description meta tags
4. Google's best guess from page content (not recommended)

Where does the +1 Button get the URL from?

1. The href attribute on the button
2. The <link rel="canonical" ... /> of the page
3. The URL retrieved by document.location.href (not recommended)

Google: "Not yet fully available, but will be coming soon"

1. Only Static Icons (No Dynamic Badges Yet)
2. Dynamic Badges and Static Icons!!!
3. Links your website to your Google+ Page
4. Helps consolidate all your +1's
5. Eligibility for Google+ Direct Connect

Want to be Searchable with +PageName?

<link href="{plusPageUrl}" rel="publisher" />

<a href="{plusPageUrl}" rel="publisher"></a>

<script type="text/javascript" src=
"https://apis.google.com/js/plusone.js"></script>

<g:plus href="{plusPageUrl}" size="badge"></g:plus>

<!-- HTML5 Compliant -->
<div class="g-plus" data-href="{plusPageUrl}" data-size="badge">
</div>	

<!-- Place this tag in the <head> of your document-->
<link href="{plusPageUrl}" rel="publisher" />

<!-- Place this tag where you want the badge to render-->
<a href="{plusPageUrl}?prsrc=3" 
  style="text-decoration: none; color: #333;">
  <div style="display: inline-block; *display: inline;">
    <div style="text-align: center;">
      <img src="https://ssl.gstatic.com/images/icons/gplus-64.png"
        width="64" height="64" style="border: 0;"/>
    </div>
    <div style="font: bold 13px/16px arial,sans-serif; 
      text-align: center;">Blaine Bublitz</div>
    <div style="font: 13px/16px arial,sans-serif;">
     on Google+ </div>
  </div>
</a>

Just a Sample

Why? Feedback and Learning

Restrictions? Read Only, Public Data, Usage Quota

GET https://www.googleapis.com/plus/v1/people/102147307918874735077
?key=API_KEY&alt=json

• People
• Activities
• Comments

• But only when they are Public! <LAME!>

get

Get a person's profile.

GET https://www.googleapis.com/plus/v1/people/{userId}

search

Search all public profiles.

GET https://www.googleapis.com/plus/v1/people?query=SEARCH_STRING

listByActivity

List all of the people in the specified collection for a particular activity.

GET https://www.googleapis.com/plus/v1/activities/{activityId}/people/{collection}

list

List all of the activities in the specified collection for a particular user.

GET https://www.googleapis.com/plus/v1/people/{userId}/activities/{collection}

get

Get an activity.

GET https://www.googleapis.com/plus/v1/activities/{activityId}

search

Search public activities.

GET https://www.googleapis.com/plus/v1/activities?query=SEARCH_STRING

list

List all of the comments for an activity.

GET https://www.googleapis.com/plus/v1/activities/{activityId}/comments

get

Get a comment.

GET https://www.googleapis.com/plus/v1/comments/{commentId}

No authentication = No API access

Types of Authentication:

• API Key - Public
• OAuth 2.0 - Private (or Public)

Still a Preview/Beta = No Private Data

Basically just a Google Gadget

What makes them special?

<?xml version="1.0" encoding="UTF-8" ?>
<Module>
  <ModulePrefs title="Your App Name">
    <Require feature="rpc"/>
    <Require feature="views"/>
  </ModulePrefs>
  <Content type="html">
    <![CDATA[
      <script src="https://hangoutsapi.talkgadget.google.com
      	/hangouts/api/hangout.js?v=0.1">
      </script>
      <!-- Your application code -->
    ]]>
  </Content>
</Module>

Events

• Event = Object containing 2 functions: add & remove
• on*.add(callback) and on*.remove(callback)
• Pro-Tip: start your app's code by passing a callback to onApiReady.add(), such as:

gapi.hangout.onApiReady.add(function(eventObj){
  if (eventObj.isApiReady) {
    startMyApp();
  }
));

Application State

• State object = single instance shared across all apps in Hangout
• Restriction: data values must be stored as strings
• Pro-Tip: use JSON.stringify(obj) and JSON.parse(obj)
• Access and manage using API functions in the gapi.hangout.data namespace

namespace gapi.hangout

Provides basic information such as the list of participants, the locale, and whether the app is initialized and visible.

namespace gapi.hangout.av

Provides functions for controlling hangout microphones, cameras, and speakers.

namespace gapi.hangout.data

Provides functions for sharing data (getting and setting gadget state) between every instance of a gadget in a hangout.

namespace gapi.hangout.layout

Provides functions for getting and setting layout elements in the Hangout user interface.

Special Thanks to Mohamed Mansour

Author of the Unofficial G+ API (Just Released on Sunday!)

Find it on Github: mohamedmansour/google-plus-extension-jsapi

Would You Like to Read or Write:

• Circles?
• Followers?
• Profile (Public or Private)?
• Streams (Public or Private)?

All of This is Yours! --- With the Unofficial APIs!

Reverse Engineering

Mohamed spent a LOT of time using the Chrome Developer Tools to capture the XHRs and parsed the obfuscated data.

The API captures the data, parses it, and adds it to a WebSQL DataStore. Also, it exposes methods for easy access to that DataStore.

More Info on G+

And on Github