PageRenderTime 45ms CodeModel.GetById 12ms RepoModel.GetById 0ms app.codeStats 0ms

/papers/nyphp-2007-01/index.html

https://github.com/horde/horde-web
HTML | 438 lines | 367 code | 57 blank | 14 comment | 0 complexity | 1879968f229508b1e04e386862f9c4d0 MD5 | raw file
    

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    2. 

  2.     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    3. 

  3. 

  4. <html xmlns="http://www.w3.org/1999/xhtml">
    5. 

  5. 

  6. <head>
    7. 

  7. <title>Application Building With Horde</title>
    8. 

  8. <!-- metadata -->
    9. 

  9. <meta name="generator" content="S5" />
    10. 

  10. <meta name="version" content="S5 1.1" />
    11. 

  11. <meta name="presdate" content="2007-01-23" />
    12. 

  12. <meta name="author" content="Chuck Hagenbuch" />
    13. 

  13. <!-- configuration parameters -->
    14. 

  14. <meta name="defaultView" content="slideshow" />
    15. 

  15. <meta name="controlVis" content="hidden" />
    16. 

  16. <!-- style sheet links -->
    17. 

  17. <link rel="stylesheet" href="../s5/ui/slides.css" type="text/css" media="projection" id="slideProj" />
    18. 

  18. <link rel="stylesheet" href="../s5/ui/outline.css" type="text/css" media="screen" id="outlineStyle" />
    19. 

  19. <link rel="stylesheet" href="../s5/ui/print.css" type="text/css" media="print" id="slidePrint" />
    20. 

  20. <link rel="stylesheet" href="../s5/ui/opera.css" type="text/css" media="projection" id="operaFix" />
    21. 

  21. <!-- S5 JS -->
    22. 

  22. <script src="../s5/ui/slides.js" type="text/javascript"></script>
    23. 

  23. <!-- prototype + scriptaculous -->
    24. 

  24. <script src="../s5/ui/prototype/prototype.js" type="text/javascript"></script>
    25. 

  25. <script src="../s5/ui/scriptaculous/scriptaculous.js" type="text/javascript"></script>
    26. 

  26. <!-- Presentaculous JS -->
    27. 

  27. <script src="../s5/ui/presentacular.js" type="text/javascript"></script>
    28. 

  28. </head>
    29. 

  29. <body>
    30. 

  30. 

  31. <div class="layout">
    32. 

  32. 

  33. <div id="currentSlide"></div>
    34. 

  34. <div id="header"></div>
    35. 

  35. <div id="footer">
    36. 

  36. <h1>New York, New York &#8226; January 23rd 2007</h1>
    37. 

  37. <h2>Application Building With Horde</h2>
    38. 

  38. <div id="controls"></div>
    39. 

  39. </div>
    40. 

  40. 

  41. </div>
    42. 

  42. 

  43. 

  44. <div class="presentation">
    45. 

  45. 

  46. <div class="slide">
    47. 

  47. <h1>Application Building With Horde</h1>
    48. 

  48. <h3>Chuck Hagenbuch</h3>
    49. 

  49. <h4><a href="http://www.horde.org/">The Horde Project</a></h4>
    50. 

  50. 

  51.  <div class="handout">
    52. 

  52.   <p>You probably know that Horde does webmail. But Horde also provides a framework for building applications. Chuck Hagenbuch will demonstrate a mix of ORM, prototype + script.aculo.us, and mapping APIs that quickly assemble into an application using Horde (call it a mashup if you must). We'll also demonstrate building standalone pages that incorporate content from an existing Horde installation.</p>
    53. 

  53.   <p>Chuck Hagenbuch founded the Horde Project in 1998 and has been working with PHP and the world of web development ever since. He is currently an independent consultant, and has provided professional services to high-profile PHP users such as PayPal and Portugal Telecom.</p>
    54. 

  54.  </div>
    55. 

  55. </div>
    56. 

  56. 

  57. <div class="slide">
    58. 

  58.  <h1>Syllabus: Horde</h1>
    59. 

  59.  <ul>
    60. 

  60.   <li>What?</li>
    61. 

  61.   <li>Why?</li>
    62. 

  62.   <li>How?</li>
    63. 

  63.  </ul>
    64. 

  64. </div>
    65. 

  65. 

  66. <div class="slide">
    67. 

  67. <h1>&quot;What is Horde?&quot;</h1>
    68. 

  68. <ul class="incremental">
    69. 

  69.  <li>The Horde Project: an open source project driven by:</li>
    70. 

  70.  <li>The Horde Developers: volunteer developers providing:</li>
    71. 

  71.  <li>The Horde Application Framework: a PHP web application framework, consisting of:</li>
    72. 

  72.  <li>The Horde Libraries: PEAR-style packages powering:</li>
    73. 

  73.  <li>The Horde Applications: real-world integrated web applications</li>
    74. 

  74. </ul>
    75. 

  75. </div>
    76. 

  76. 

  77. <div class="slide">
    78. 

  78.  <h1>Why: Libraries</h1>
    79. 

  79.  <ul class="incremental">
    80. 

  80.   <li>Over 60 high quality PHP libraries in PEAR packages</li>
    81. 

  81.   <li>PHP4 and PHP5</li>
    82. 

  82.   <li>Authentication and Permissions to MIME handling to user preferences to XML transformations</li>
    83. 

  83.   <li>Coding standards that were the basis for the PEAR coding standards</li>
    84. 

  84.   <li>Initial PEAR packages including Log and Mail were contributed from Horde to PEAR</li>
    85. 

  85.  </ul>
    86. 

  86. </div>
    87. 

  87. 

  88. <div class="slide">
    89. 

  89.  <h1>Why: Standards</h1>
    90. 

  90.  <ul class="incremental">
    91. 

  91.   <li>XHTML/CSS Layout</li>
    92. 

  92.   <li>Comprehensive MIME standards support</li>
    93. 

  93.   <li>Groupware apps all handle iCalendar and vCard</li>
    94. 

  94.   <li>SOAP and XML-RPC access to all application APIs</li>
    95. 

  95.   <li>SyncML server</li>
    96. 

  96.   <li>WebDAV server</li>
    97. 

  97.  </ul>
    98. 

  98. </div>
    99. 

  99. 

  100. <div class="slide">
    101. 

  101.  <h1>Why: Backend Independence</h1>
    102. 

  102.  <ul class="incremental">
    103. 

  103.   <li>SQL drivers work for MySQL, PostgreSQL, Oracle, MSSQL, more</li>
    104. 

  104.   <li>LDAP support for contacts, preferences, users, more.</li>
    105. 

  105.   <li>VFS (virtual filesystem) support for local files, SQL, FTP, more</li>
    106. 

  106.   <li>Pluggable drivers for all backends</li>
    107. 

  107.  </ul>
    108. 

  108. </div>
    109. 

  109. 

  110. <div class="slide">
    111. 

  111.  <h1>Why: Applications</h1>
    112. 

  112.  <ul class="incremental">
    113. 

  113.   <li>Over 50 in CVS</li>
    114. 

  114.   <li>Used by MIT, Portugal Telecom, and many many more</li>
    115. 

  115.   <li>Groupware apps are all in at least 2nd major release</li>
    116. 

  116.   <li>All applications integrate users and their data</li>
    117. 

  117.   <li>Developer tools including Chora and Whups</li>
    118. 

  118.   <li>Access to APIs without tight coupling</li>
    119. 

  119.  </ul>
    120. 

  120. </div>
    121. 

  121. 

  122. <div class="slide">
    123. 

  123.  <h1>Why: Internationalization</h1>
    124. 

  124.  <ul class="incremental">
    125. 

  125.   <li>Full Unicode support in IMP and most apps</li>
    126. 

  126.   <li>Standards-compliant character set handling</li>
    127. 

  127.   <li>39 different translations</li>
    128. 

  128.  </ul>
    129. 

  129. </div>
    130. 

  130. 

  131. <div class="slide">
    132. 

  132.  <h1>Why: The Project</h1>
    133. 

  133.  <ul class="incremental">
    134. 

  134.   <li>Incredibly feature-rich</li>
    135. 

  135.   <li>Built through more than eight years of development ...</li>
    136. 

  136.   <li>... of real-world production web applications</li>
    137. 

  137.   <li>Constantly updated, improved, innovated, and refactored</li>
    138. 

  138.  </ul>
    139. 

  139. </div>
    140. 

  140. 

  141. <!-- Skeleton -->
    142. 

  142. <div class="slide">
    143. 

  143.  <h1>Building Your Own</h1>
    144. 

  144.  <p><em>In which the intrepid audience gets l33t</em></p>
    145. 

  145. </div>
    146. 

  146. 

  147. <div class="slide">
    148. 

  148.  <h1>Where to start?</h1>
    149. 

  149.  <p class="incremental"><img src="graphics/skeleton.gif" alt="With a skeleton!" /></p>
    150. 

  150. </div>
    151. 

  151. 

  152. <div class="slide">
    153. 

  153.  <h1>Horde Skeleton</h1>
    154. 

  154.  <p><em>Everything you need to write a standard Horde application</em></p>
    155. 

  155. </div>
    156. 

  156. 

  157. <!-- Demo 1: propertyTracker -->
    158. 

  158. <div class="slide">
    159. 

  159.  <h1>What if you want something like this?</h1>
    160. 

  160.  <p><a target="_blank" href="https://horde.org/papers/nyphpcon-2006-06/" title="Property Tracking Tutorial"><img src="graphics/tracker.png" alt="Property Tracking Tutorial" /></a></p>
    161. 

  161. </div>
    162. 

  162. 

  163. <div class="slide">
    164. 

  164.  <h1>Tools used</h1>
    165. 

  165.  <ul>
    166. 

  166.   <li>RDO</li>
    167. 

  167.   <li>Horde_Form</li>
    168. 

  168.   <li>RDO Helpers</li>
    169. 

  169.   <li><a href="http://www.prototypejs.org/" target="_blank">Prototype</a></li>
    170. 

  170.   <li><a href="http://script.aculo.us/" target="_blank">Scriptaculous</a></li>
    171. 

  171.   <li><a href="http://google.com/apis/maps/" target="_blank">Google Maps</a></li>
    172. 

  172.   <li><a href="http://developer.yahoo.com/maps/rest/V1/geocode.html" target="_blank">Yahoo! Geocoding</a></li>
    173. 

  173.  </ul>
    174. 

  174. </div>
    175. 

  175. 

  176. <div class="slide">
    177. 

  177.  <h1>Why, Continued</h1>
    178. 

  178.  <p><em>PHP 5 and the future of Horde</em></p>
    179. 

  179.  <ul class="incremental">
    180. 

  180.   <li>RDO: lightweight, PDO-based ORM</li>
    181. 

  181.   <li>Automatic generation of Model classes</li>
    182. 

  182.   <li>Override with customized Model</li>
    183. 

  183.   <li>Automatic generation of Horde_Forms from Model</li>
    184. 

  184.  </ul>
    185. 

  185. </div>
    186. 

  186. 

  187. <div class="slide">
    188. 

  188.  <h1>Introducing RDO</h1>
    189. 

  189.  <ul class="incremental">
    190. 

  190.   <li>ORM - Object-Relational Mapping</li>
    191. 

  191.   <li>Uses PDO drivers</li>
    192. 

  192.   <li>Full use of PHP 5 interfaces - Iterator, IteratorAggregate, ArrayAccess, Countable, etc.</li>
    193. 

  193.  </ul>
    194. 

  194. </div>
    195. 

  195. 

  196. <div class="slide">
    197. 

  197.  <h1>RDO Example Usage</h1>
    198. 

  198.  <pre>$um = new UserMapper();
    199. 

  199. 

  200. $userCount = $um-&gt;count(); // Count all users.
    201. 

  201. 

  202. $exists = $um-&gt;exists(1); // Check if id 1 exists.
    203. 

  203. 

  204. // Look for Alice
    205. 

  205. $user = $um-&gt;find(Horde_RDO::FIND_FIRST,
    206. 

  206.                      array('name' => 'Alice'));
    207. 

  207. if ($user) {
    208. 

  208.     echo "Found Alice: id $user-&gt;id\n";
    209. 

  209. } else {
    210. 

  210.     // Create a new user.
    211. 

  211. }
    212. 

  212.  </pre>
    213. 

  213. </div>
    214. 

  214. 

  215. <div class="slide">
    216. 

  216.  <h1>RDO: Creating &amp; Editing</h1>
    217. 

  217.  <pre>
    218. 

  218. $user = $um-&gt;create(array(
    219. 

  219.     'name' => 'Alice',
    220. 

  220.     'phone' => '212-555-6565'));
    221. 

  221. echo "Created new user with id: {$user-&gt;id}\n";
    222. 

  222. 

  223. // Change the name of the user and save.
    224. 

  224. $user-&gt;name = 'Bob';
    225. 

  225. $user-&gt;save();
    226. 

  226.  </pre>
    227. 

  227. </div>
    228. 

  228. 

  229. <div class="slide">
    230. 

  230.  <h1>RDO: More Find &amp; Delete</h1>
    231. 

  231.  <pre>
    232. 

  232. // List all users.
    233. 

  233. echo "Looking for all:\n";
    234. 

  234. foreach ($um-&gt;find(Horde_RDO::FIND_ALL) as $user) {
    235. 

  235.     echo "  (" . $user-&gt;id
    236. 

  236.         . ") " . $user-&gt;name . "\n";
    237. 

  237. }
    238. 

  238. 

  239. // Fetch id 2 and delete.
    240. 

  240. $user = $um-&gt;find(2);
    241. 

  241. $user-&gt;delete();
    242. 

  242.  </pre>
    243. 

  243. </div>
    244. 

  244. 

  245. <div class="slide">
    246. 

  246.  <h1>Form Generation</h1>
    247. 

  247.  <pre>
    248. 

  248. $vars = Variables::getDefaultVariables();
    249. 

  249. $form = new Horde_Form_Helper($mapper, $vars,
    250. 

  250.                               'My Form Title');
    251. 

  251. $form-&gt;renderActive(); // Edit form
    252. 

  252. $form-&gt;delete(); // process a delete action
    253. 

  253. $form-&gt;update(); // process an update form
    254. 

  254. $form-&gt;create(); // process a create form
    255. 

  255.  </pre>
    256. 

  256. </div>
    257. 

  257. 

  258. <!-- Lens slides -->
    259. 

  259. <div class="slide">
    260. 

  260.  <h1>Horde_RDO_Lens</h1>
    261. 

  261.  <h2>Motivation: How many times do I have to loop through this #*)&%% array?</h2>
    262. 

  262.  <pre>$data = array();
    263. 

  263. while ($row = mysql_fetch_array()) {
    264. 

  264.     $data[] = $row;
    265. 

  265. }
    266. 

  266. 

  267. foreach ($data as $index => $row) {
    268. 

  268.     $data[$index]['foo'] = format_somehow($row['foo']);
    269. 

  269. }
    270. 

  270. 

  271. foreach ($data as $row) {
    272. 

  272.     echo '&lt;p&gt;' . display($row) . '&lt;/p&gt;';
    273. 

  273. }
    274. 

  274.  </pre>
    275. 

  275. </div>
    276. 

  276. 

  277. <div class="slide">
    278. 

  278.  <h1>Remember Flyweight?</h1>
    279. 

  279.  <p><a target="_blank" href="http://en.wikipedia.org/wiki/Flyweight_pattern">http://en.wikipedia.org/wiki/Flyweight_pattern</a></p>
    280. 

  280. 

  281.  <div class="handout">
    282. 

  282.   <p>Flyweight is a software design pattern. When many objects must be
    283. 

  283.   manipulated and these cannot afford to have extraneous data,
    284. 

  284.   flyweight is appropriate.</p>
    285. 

  285. 

  286.   <p>In the flyweight pattern, the data has no pointers to the data
    287. 

  287.   type methods, because these would consume too much space. Instead,
    288. 

  288.   the subroutines are called directly. In some cases, flyweight
    289. 

  289.   inheritance is performed by &quot;shift-in&quot; and
    290. 

  290.   &quot;shift-out&quot; data markers as a higher-level operation
    291. 

  291.   cycles through an array of flyweight data.</p>
    292. 

  292. 

  293.   <p>One classic example of a flyweight pattern are the characters
    294. 

  294.   stored in a word processor. Each character represents an object that
    295. 

  295.   has a font face, font size, and other formatting data. As you can
    296. 

  296.   imagine, a large document with this data structure would bloat the
    297. 

  297.   memory footprint of the word processor. Moreover, since much of this
    298. 

  298.   data is repeated, there must be a way to reduce the footprint - the
    299. 

  299.   Flyweight pattern. Each of the character objects would contain a
    300. 

  300.   reference to a separate formatting object which contains the
    301. 

  301.   required properties. This greatly reduces the memory footprint by
    302. 

  302.   combining all of the like-formatted characters into simpler objects
    303. 

  303.   that reference a single formatting object.</p>
    304. 

  304.  </div>
    305. 

  305. </div>
    306. 

  306. 

  307. <div class="slide">
    308. 

  308.  <h1>Lens use</h1>
    309. 

  309.  <pre>
    310. 

  310. $items = $mapper-&gt;find(Horde_RDO::FIND_ALL);
    311. 

  311. $formattedItems = new Horde_RDO_Decorating_Iterator(
    312. 

  312.     $items, new Horde_RDO_Lens());
    313. 

  313. 

  314. echo '&lt;ul&gt;';
    315. 

  315. foreach ($formattedItems as $item) {
    316. 

  316.      echo '&lt;li&gt;' . $item-&gt;name
    317. 

  317.          . ' :' . $item-&gt;desc . '&lt;/li&gt;';
    318. 

  318. }
    319. 

  319. echo '&lt;/ul&gt;';
    320. 

  320.  </pre>
    321. 

  321. </div>
    322. 

  322. 

  323. <div class="slide">
    324. 

  324.  <h1>Lens Implementation</h1>
    325. 

  325.  <ul class="incremental">
    326. 

  326.   <li>OuterIterator implementation</li>
    327. 

  327.   <li>Lens interface</li>
    328. 

  328.   <li>Base Lens implementation</li>
    329. 

  329.   <li><a target="_blank" href="source.php?file=lens">Code</a></li>
    330. 

  330.  </ul>
    331. 

  331. </div>
    332. 

  332. 

  333. <!-- Demo 2: packages -->
    334. 

  334. <div class="slide">
    335. 

  335.  <h1>A Package Tracking Application</h1>
    336. 

  336.  <p><img src="graphics/package_tracking_1.png" /></p>
    337. 

  337. </div>
    338. 

  338. 

  339. <div class="slide">
    340. 

  340.  <h1>Package Tracking: Delivery Tracking</h1>
    341. 

  341.  <p><img src="graphics/package_tracking_2.png" /></p>
    342. 

  342. </div>
    343. 

  343. 

  344. <div class="slide">
    345. 

  345.  <h1>Package Tracking Code</h1>
    346. 

  346.  <p><a href="packages.tar.gz">The Code</a></p>
    347. 

  347.  <p>Drop the config/registry.d-packages.php file into your
    348. 

  348.  horde/config/registry.d/ directory with any appropriate changes, and
    349. 

  349.  use with Horde from CVS (3.2-CVS).</p>
    350. 

  350. </div>
    351. 

  351. 

  352. <!-- WebDAV -->
    353. 

  353. <div class="slide">
    354. 

  354.  <h1>Doing more with our data</h1>
    355. 

  355.  <p>Let's provide a different way to see the packages we're
    356. 

  356.  expecting. How about WebDAV?</p>
    357. 

  357. </div>
    358. 

  358. 

  359. <div class="slide">
    360. 

  360.  <h1>WebDAV browsing made simple</h1>
    361. 

  361.  <p><img src="graphics/webdav.png" /></p>
    362. 

  362. </div>
    363. 

  363. 

  364. <div class="slide">
    365. 

  365.  <h1>Obrowser, where art thou?</h1>
    366. 

  366.  <p>Alternate ways to see what WebDAV sees:</p>
    367. 

  367.  <p><img src="graphics/obrowser_1.png" /></p>
    368. 

  368.  <p><img src="graphics/obrowser_2.png" /></p>
    369. 

  369. </div>
    370. 

  370. 

  371. <div class="slide">
    372. 

  372.  <h1>Implementing /browse</h1>
    373. 

  373.  <ul class="incremental">
    374. 

  374.   <li>Single API method</li>
    375. 

  375.   <li>Takes a path and an optional list of property names</li>
    376. 

  376.   <li>Returns an array depending on the path</li>
    377. 

  377.   <li><a target="_blank" href="source.php?file=browse">Code</a></li>
    378. 

  378.  </ul>
    379. 

  379. </div>
    380. 

  380. 

  381. <!-- External page integration -->
    382. 

  382. <div class="slide">
    383. 

  383.  <h1>External use of Horde data</h1>
    384. 

  384.  <p><a target="_blank" href="source.php?file=weather"><img src="graphics/weather.png" /></a></p>
    385. 

  385. </div>
    386. 

  386. 

  387. <div class="slide">
    388. 

  388.  <h1>Setup Code</h1>
    389. 

  389.  <dl>
    390. 

  390.   <dt><code>@define('AUTH_HANDLER', true);</code></dt>
    391. 

  391.    <dd>Tell Horde not to throw someone to a login screen; you'll handle authentication.</dd>
    392. 

  392.   <dt><code>$session_control = 'none';</code></dt>
    393. 

  393.    <dd>Don't use sessions</dd>
    394. 

  394.   <dt><code>require_once '/var/www/horde/lib/base.php';</code></dt>
    395. 

  395.    <dd>Load a base Horde environment</dd>
    396. 

  396.  </dl>
    397. 

  397. </div>
    398. 

  398. 

  399. <div class="slide">
    400. 

  400.  <h1>Getting Block Content</h1>
    401. 

  401.  <pre>require_once 'Horde/Block/Collection.php';
    402. 

  402. $weather = Horde_Block_Collection::getBlock(
    403. 

  403.     'horde',
    404. 

  404.     'weatherdotcom',
    405. 

  405.     array('location' =&gt; 'Boston, MA',
    406. 

  406.           'days' =&gt; 3,
    407. 

  407.           'units' =&gt; 'standard'));
    408. 

  408.  </pre>
    409. 

  409. </div>
    410. 

  410. 

  411. <div class="slide">
    412. 

  412.  <h1>Showing Block Content</h1>
    413. 

  413.  <pre>echo $weather-&gt;getTitle();
    414. 

  414. echo $weather-&gt;getContent();</pre>
    415. 

  415. </div>
    416. 

  416. 

  417. <!-- Fin -->
    418. 

  418. <div class="slide">
    419. 

  419.  <h1>Questions?</h1>
    420. 

  420. </div>
    421. 

  421. 

  422. <div class="slide">
    423. 

  423.  <h1>Resources</h1>
    424. 

  424.  <ul>
    425. 

  425.   <li>The Horde website: <a href="http://www.horde.org/" target="_blank">http://www.horde.org/</a></li>
    426. 

  426.   <li>Developer Documentation: <a href="http://dev.horde.org/" target="_blank">http://dev.horde.org/</a></li>
    427. 

  427.   <li>Wiki: <a href="http://wiki.horde.org/" target="_blank">http://wiki.horde.org/</a></li>
    428. 

  428.   <li>Prototype: <a href="http://www.prototypejs.org/" target="_blank">http://www.prototypejs.org/</a></li>
    429. 

  429.   <li>Scriptaculous: <a href="http://script.aculo.us/" target="_blank">http://script.aculo.us/</a></li>
    430. 

  430.   <li>Google Maps: <a href="http://google.com/apis/maps/" target="_blank">http://google.com/apis/maps/</a></li>
    431. 

  431.   <li>Yahoo! APIs: <a href="http://developer.yahoo.com/maps/rest/V1/geocode.html" target="_blank">http://developer.yahoo.com/maps/rest/V1/geocode.html</a></li>
    432. 

  432.  </ul>
    433. 

  433. </div>
    434. 

  434. 

  435. <!-- End Slides -->
    436. 

  436. </div>
    437. 

  437. </body>
    438. 

  438. </html>
    439. 

  439.