Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
composition-setup: Please enter a link to an attachment for defaults: Home^composition.properties

cloak.memory.duration = 3 #days
cloak.toggle.type = custom
cloak.toggle.open = ^open.gif
cloak.toggle.close = ^close.gif
deck.memory.duration = 0
deck.tab.location = 'top'

  1. deck.tab.active.border - The border for the active tab (CSS - eg. '1px dashed black')
  2. deck.tab.active.background - The background for the active tab (CSS - eg. '#ff0055')
  3. deck.tab.inactive.border - The border for inactive tabs (CSS)
  4. deck.tab.inactive.background - The background for inactive tabs (CSS)
  5. deck.tab.spacer - The distance between tabs (eg '5px')
  6. deck.card.border - The border for the active card.
  7. deck.card.background - The background for the active card.
  8. deck.width/deck.height - The width and/or height the content will be constrained to (not including any tabs). If not set, the tabs expand to display their content.
    deck.startHidden = 'false'
  9. deck.loopCards - If 'true', the deck will loop back to the beginning from the last card and vice versa. Defaults to 'false'.
  10. deck.nextAfter - The number of seconds the slides will stay visible before moving to the next one. By default the current slide will not transition until prompted by the user.
  11. deck.effect.type - The effect to use when moving to a new slide. May be 'fade' or 'none' (the default).
  12. deck.effect.duration - The number of seconds the transition will take to complete. Eg. '1.5'. Defaults to 1.
New Proposal Template
This page has been created from a template that uses "zones." To proceed:
  1. Edit the page
  2. Replace sample content within each zone-data tag with your own content
  3. Remove this notice
  4. Save the page
  5. When you are ready for community review, move this page to the Ready for Review section on the edit page.
No placeholders allowed!
Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.

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

Zend Framework: Zend_Service_Instagram Component Proposal

Proposed Component Name Zend_Service_Instagram
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_Instagram
Proposers Mauricio Cuenca
Zend Liaison TBD
Revision 1.0 - 06 March 2011: Initial Draft. (wiki revision: 4)

Table of Contents

1. Overview

Zend_Service_Instagram is a full implementation of the official Instagram API. It provides an object oriented interface to the API and returns data in JSON format or PHP data objects.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

Most requirements take the form of "foo will do ...." or "foo will not support ...", although different words and sentence structure might be used. Adding functionality to your proposal is requirements creep (bad), unless listed below. Discuss major changes with your team first, and then open a "feature improvement" issue against this component.

  • This component will fully implement Instagram official API.
  • This component should namespace the API methods as they are stated in Instagram's API documentation.
  • This component will not support real-time photo updates.

4. Dependencies on Other Framework Components

  • Zend_Oauth
  • Zend_Service_Exception
  • Zend_Http_Client
  • Zend_Http_Client_Adapter_Curl
  • Zend_Http_Client_Exception

5. Theory of Operation

Zend_Service_Instagram will allow a developer an easy interaction with the Instagram API in a object oriented manner, supporting such actions as getting users' information, browse through popular media, manage users' relationships, comments, likes, tags and locations. All data returned can be represented whether in JSON format or as php data objects. Zend_Service_Instagram creates a php client for the Instagram API.

6. Milestones / Tasks

  • Milestone 1: Proposal, Community Review and Acceptance.
  • Milestone 2: Unit tests exist, work, and are checked into versioning system.
  • Milestone 4: Initial documentation exists.

#If a milestone is already done, begin the description with "[DONE]", like this:

    • Milestone #: [DONE] Unit tests ...

7. Class Index

  • Zend_Instagram_Exception
  • Zend_Instagram

8. Use Cases

UC-01 - Users
deck: Please ensure that the composition-setup macro is placed before this location.

Get basic information about a user.

See the authenticated user's feed.

See the authenticated user's feed.

Get the most recent media published by a user.

Search for a user by name.

deck: Please ensure that the composition-setup macro is placed before this location.
UC-02 - Relationships
UC-03 - Media
UC-04 - Comments
UC-05 - Likes
UC-06 - Tags
UC-07 - Locations

... (see good use cases book)

9. Class Skeletons

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

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.