Configuring Extension Output with TypoScript for Extensibility and Reusability

By: Lucas Thurston

5) Ok, now we need to get our records from the database. That should be easy enough:
  function getRecords() { $select = '*'; $table = 'tx_galist_pi1'; $where = 'tx_galist_pi1.hidden = 0 AND tx_galist_pi1.deleted = 0'; $groupBy = ''; $orderBy = ''; $limit = '';   $qres = $GLOBALS['TYPO3_DB']->exec_SELECTquery($select,$table,$where,$groupBy,$orderBy,$limit); while ($row = $GLOBALS['TYPO3_DB']->sql_fetch_assoc($qres)) { $rows[] = $row; } return $rows; }

  6) Now we need is to populate our template. At Cast Iron Coding we prefer to use TemplatePower to the TYPO3 template methods in tslib_cObj, but that's a simple matter of preference that shouldn't change the basic logic that follows. Here's how the marker arrays would be put into the template with TemplatePower.
  function getOutput($markerArrays) { $tpI = t3lib_div::makeInstanceClassName('templatePower'); $tp = new $tpI;   $tp->prepare('fileadmin/extTemplates/tx_ciclist_listView1.html');   foreach((array) $markerArrays as $markerArray) { $tp->newBlock('item'); $tp->assign($markerArray); }   return $tp->getOutputContent; }