Skip to end of metadata
Go to start of metadata

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Service_Facebook Component Proposal

Proposed Component Name Zend_Service_Facebook
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_Facebook
Proposers Ian Warner
Zend Liaison TBD
Revision 1.0 - 17th November 2008: Initial Draft. (wiki revision: 15)

Table of Contents

1. Overview

Zend_Service_Facebook will be a set of Helper Classes to OOP the Facebook FBML Components. These consist of elements such as
FB:Dialog
FB:TypeAhead

One thing Facebook does require also is JS to be written in its own proprietary FBJS and these helpers would also create FBJS components also to handle tasks such as AJAX
 
Something to take note of though is that Bebo also use the Facebook Platform and Helpers good for Facebook will be good for Bebo in most parts, Bebo is several generations behind. So the naming of this component may need to reflect that is can be cross site, but will utilise the Facebook Open Platform

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will create Helper Classes for all Facebook FBML elements.
  • This component will strive to provide Helpers for common FBJS tasks.

4. Dependencies on Other Framework Components

  • Zend_Exception

5. Theory of Operation

Helpers classes are simply called from the View, replacing the usualwith a nice OOP way of doing things $this->facebookDialog();
This will allow the application developer to concentrate on the application and not worry about Facebook changing there platform on a far too regular cycle.

6. Milestones / Tasks

  • Milestone 1: Community Feedback on already coded Helpers required to progress
  • Milestone 2: Based on the above create the required Unit Tests for all the Helpers
  • Milestone 3: Add any missing Helpers
  • Milestone 4: Document all Helpers and best practice use
  • Milestone 5: Working prototype checked into the incubator when requirements are met.
  • Milestone 6: Finalise Documentation and Testing and deploy.

7. Class Index

  • Zend_View_Helper_Facebook_Dialog
  • Zend_View_Helper_Facebook_Board
  • Zend_View_Helper_Facebook_Comments

etc

8. Use Cases

This demonstrates the Facebook Comments UI Component Use Case:

9. Class Skeletons

 
This demonstrates the actual Helper I use now for the Facebook comments component other Helpers are written in a similar way.

]]></ac:plain-text-body></ac:macro>

]]></ac:plain-text-body></ac:macro>

Labels:
proposal proposal Delete
facebook facebook Delete
social social Delete
helpers helpers Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Aug 06, 2009

    <p>is this still alive?</p>

    <p>i liked your idea about helpers for facebook services, but i din't see anything about <a href="http://wiki.developers.facebook.com/index.php/API">FacebookAPI</a> implementation as a service library like amazon, twitter, yahoo... i didn't see any class in incubator as well</p>

    <p>i think facebook-helpers should use facebook-service classes</p>

    <p>we could have two proposals:</p>
    <ul class="alternate">
    <li>Zend_Service_Facebook (that implements the facebook rest api)</li>
    <li>Zend_View_Helper_Facebook (that uses previous one)</li>
    </ul>

    <p><a class="external-link" href="http://wiki.developers.facebook.com/index.php/API">http://wiki.developers.facebook.com/index.php/API</a></p>

    <p>regards,</p>

    1. Aug 07, 2009

      <p>Hi</p>

      <p> Yes still live and I am creating and tuning my helpers all the time that I use in my apps.</p>

      <p>The reason this hasnt progressed is that it hasnt been reviewed or assigned a liason so I assume the powers that be do not like the idea.</p>

      <p> PEAR have a good Service library as well as Facebook providing a class - I would love to provide a Zend one utilising all the core classes such as HTTP - CACHE etc</p>

      <p> So I can see the helpers and the service class being one proposal - much like how DOJO is layed out but in the services folder</p>

      <p>Ian </p>

  2. Jan 11, 2010

    <p>I'm also wondering if this is still alive in any form?</p>

    <p>I've worked up a semi-complete Zend_Service_Facebook (extends Zend_Service_Abstract), porting some methods from the PEAR library as well as the official Facebook PHP library. I'll be putting it up on google code soon. </p>

    <p>If this proposal isn't going anywhere, should I start another?</p>

  3. Feb 08, 2011

    <p>Archiving this proposal, feel free to recover it when you want to work on it again. For more details see <a href="http://framework.zend.com/wiki/display/ZFDEV/Archiving+of+abandoned+proposals+(Feb+5+2011)">this email</a>.</p>