<?xml version="1.0"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>InnerOptics.net</title>
		<link>http://inneroptics.net</link> 
		<description><![CDATA[ New content (journal entries, concrete5 packages, and photography collections) by Tony Trupp ]]></description> 
				<lastBuildDate>Mon, 30 Jan 2012 17:29:23 CST</lastBuildDate>
		<atom:link href="http://inneroptics.net/rss/" rel="self" type="application/rss+xml" />
		
					
		<item>
			  <title>Rapid Paging Block Tutorial</title>
			  <link>http://inneroptics.net/toolbox/rapid-paging/instructions/</link>
			  <description>
&lt;div id=&quot;quick-edit_block915&quot; class=&quot;quick-edit_block &quot;&gt;

	&lt;DIV class=&quot;quick-edit_view&quot; id=&quot;quick-edit_view915&quot;  &gt;&lt;h3&gt;Basic Configuration&lt;/h3&gt;

&lt;p&gt;Here's a short tutorial on how it get the &lt;a href=&quot;http://inneroptics.net/toolbox/rapid-paging/&quot;&gt;Concrete5 Rapid Ajax Paging&lt;/a&gt; block up and running. 
&lt;/p&gt;


&lt;p&gt;
1) Add the Rapid Paging block to your page (the page that has the link on it, not the page that will be opened), &lt;strong&gt;into an area that is outside of the region that you'll be replacing&lt;/strong&gt;.   
&lt;/p&gt; 

&lt;p&gt;2) Just keep all the default settings.  It should say &quot;Based on link: Class Name&quot; and next to it, have the words &quot;ajaxLink&quot; in that field.  It also should have &quot;Main&quot; as the area name.  This is the area that will be shown in the popup.  The &quot;Page Load Target Selector&quot; field should be a css selector path to the element on the page that you want to replace. Setting that element to #body would cause the contents of the &amp;lt;div id=&quot;body&quot;&amp;gt; &amp;lt;div&amp;gt; tag to be replaced. 
&lt;/p&gt;

&lt;p&gt;
3) Create another page (anywhere on your site), and put some content in the &quot;Main&quot; area.  This is the page that will be loaded. In this example, my target page has a url of /my_target_page/.  Exit edit mode.
&lt;/p&gt;

&lt;p&gt;
4) Go back to the first page, add/edit the Content block that will have the link to the ajax target page.  Select the text that you want to turn into the ajax link, and click the link icon (the chain icon circled below).  Add the url of the popup page (the next image below), then click on the advanced tab, and enter the word &quot;ajaxLink&quot; in the Classes field (the third image below).  Then click the update button of both edit-dialog windows to save your changes.
&lt;/p&gt;

&lt;p&gt;
5) Take the page out of edit mode. The ajax loading should now be activated for that link.  
&lt;/p&gt;

&lt;h3&gt;Advanced Configuration&lt;/h3&gt;

&lt;p&gt;
While this approach works well for individual links, typically you'll want to use the &quot;CSS Selector&quot; instead of the &quot;CSS Class Name&quot; setting, since this will allow you to automatically activate a bunch of links at once.  For example, using the &quot;CSS Selector&quot; option, with &quot;#body a&quot;, will activate all of the links within the body area. 
&lt;/p&gt;

&lt;p&gt;
If there are certain links within an area that you've activate that you'd like to treat as normal links, you can add the css class &quot;ignoreAjaxLink&quot; to that link element or to any parent containing element.  
&lt;/p&gt;

&lt;p&gt;
To make setup rapid paging to work across a wide range of pages regardless of the entry page, it's recommended that you add the block to the global scrapbook, and reference it from that locations so that all the pages can include the same instance. If you hardcode the block display, be sure to also hardcode the required javascript and css files within the page.
&lt;/p&gt; 

&lt;a name=&quot;javascript&quot; /&gt;
&lt;h3&gt;Javascript within Ajax Loaded Pages&lt;/h3&gt;

&lt;p&gt;
The Rapid Paging block will attempt to execute any javascript being loaded, after loading any external javascript and css files it can detect for each block. However, some block's that rely on javascript won't work correctly when being loaded through the ajax paging.  This is typically because the javascript within those blocks is initiated during the pageload event, and by the time they are loaded via ajax, the pageload event has already been fired.&lt;/p&gt;

&lt;p&gt;If you'd like to try to customize the javascript within your other blocks to work with this package, you can hook into a event that's fired after the page has completed loading: 
&lt;/p&gt;

&lt;p&gt;
$(document).bind('rapid_page_load', function(e, data) { &lt;br&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;//add your block's javascript initialization code here &lt;br&gt;
});
&lt;/p&gt;


&lt;p&gt;« Back to the &lt;a href=&quot;http://inneroptics.net/toolbox/rapid-paging/&quot;&gt;Concrete5 Rapid Ajax Paging Block project page&lt;/a&gt;&lt;/p&gt;&lt;/DIV&gt;	
	 
	
	&lt;/div&gt; </description>  
			  <pubDate>Sat, 05 Nov 2011 23:23:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/rapid-paging/instructions/</guid>
		</item>
			
		<item>
			  <title>Kayaking Skookumchuck Tidal Rapids</title>
			  <link>http://inneroptics.net/journal/kayaking-skookumchuck-tidal-rapids/</link>
			  <description>A kayaker surfs the food at Skookumchuck Tidal Rapids, British Columbia </description>  
			  <pubDate>Tue, 25 Oct 2011 23:46:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/journal/kayaking-skookumchuck-tidal-rapids/</guid>
		</item>
			
		<item>
			  <title>Redwoods Elk Rut Slideshow</title>
			  <link>http://inneroptics.net/journal/redwoods-elk-rut/</link>
			  <description>If you happen to visit Redwood National Park during the early autumn you may have a chance to see the seasonal Elk Rut. Within the aptly named Elk Prairie, this impressive bull elk actively defends his harem of up to 20 cows from challengers. In order to maintain his peak position within the heard he quickly chases them off any other males who wander too close. The juvenile bull being pursued in these photos has just reach the age where it's seen as potential mating threat, and is forced away by the alpha male from his mother's protection.  </description>  
			  <pubDate>Sun, 02 Oct 2011 19:54:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/journal/redwoods-elk-rut/</guid>
		</item>
			
		<item>
			  <title>CSS snippet to reduce height of concrete5 edit bar</title>
			  <link>http://inneroptics.net/concrete5_blog/css-snippet-to-reduce-height-of-concrete5-edit-bar/</link>
			  <description>Tried of the concrete5 edit bar taking too much screen real-estate?  Then add this snippet to your CSS to shrink it's height.  </description>  
			  <pubDate>Sun, 31 Jul 2011 16:10:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/concrete5_blog/css-snippet-to-reduce-height-of-concrete5-edit-bar/</guid>
		</item>
			
		<item>
			  <title>Integration with ProPhoto or Image Search blocks</title>
			  <link>http://inneroptics.net/toolbox/file-image-details/integrating-file-image-details-with-the-prophoto-or-image-search/</link>
			  <description>
&lt;div id=&quot;quick-edit_block867&quot; class=&quot;quick-edit_block &quot;&gt;

	&lt;DIV class=&quot;quick-edit_view&quot; id=&quot;quick-edit_view867&quot;  &gt;&lt;p&gt;The File/Image Details block was designed to integrate with the ProPhoto &amp; Image Search blocks, allowing you to click through for an enlarged version of an image that displays further details.  You can set this up in one of two ways: &lt;/p&gt;

&lt;p&gt;1) use only one instance of the File/Image Details block to serve all of your images from one page, grabbing the file id from the url's query string. This approach requires less maintenance than the second option, so I recommend going this route.  Edit the file-details block, make sure the &quot;Load with URL Query String&quot; radio is selected, and leave &quot;fID&quot; for the query string variable name.  Then edit your ProPhoto block, &amp; on the interface tab check &quot;Link images to another page on your site&quot;, and select the page where the File/Image Details block is installed. &lt;/p&gt;

&lt;p&gt;2) If you'd rather you can also create a new instance of the File/Image Details block on its own page for each image on your site.  In this case, through your dashboard-&gt;files-&gt;attribute section, you'd create a file attribute (of type &quot;text&quot;) with a handle of proPhoto_linkURL, and then for each image edit it's properties and assign a value for that proPhoto_linkURL attribute containing a relative URL path or a cID for the enlarged image page. &lt;/p&gt;
&lt;/DIV&gt;	
	 
	
	&lt;/div&gt; </description>  
			  <pubDate>Sat, 30 Jul 2011 13:59:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/file-image-details/integrating-file-image-details-with-the-prophoto-or-image-search/</guid>
		</item>
			
		<item>
			  <title>Canonical URLs</title>
			  <link>http://inneroptics.net/concrete5_blog/canoncial-urls/</link>
			  <description>Duplicate URLs to access the same page can hurt your SEO.  Add the new canonical link tag to your header to let the search engines know which is the correct address.   </description>  
			  <pubDate>Thu, 31 Mar 2011 00:36:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/concrete5_blog/canoncial-urls/</guid>
		</item>
			
		<item>
			  <title>Flamenco &amp; Classical Guitar</title>
			  <link>http://inneroptics.net/journal/flamenco-and-classical-guitar/</link>
			  <description>A collection my favorite flamenco and classical guitar videos, with performances by Paco De Lucia, Andre Segovia, Manolo Sanlúcar, Tomatito, Pepe Romero, &amp; Ana Vidovic </description>  
			  <pubDate>Thu, 25 Nov 2010 16:35:00 CST</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/journal/flamenco-and-classical-guitar/</guid>
		</item>
			
		<item>
			  <title>Real-Estate Package Tutorial</title>
			  <link>http://inneroptics.net/toolbox/real-estate/tutorial/</link>
			  <description>A tutorial for the concrete5 real-estate package </description>  
			  <pubDate>Thu, 28 Oct 2010 19:28:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/real-estate/tutorial/</guid>
		</item>
			
		<item>
			  <title>Link System</title>
			  <link>http://inneroptics.net/toolbox/link-system/</link>
			  <description>Let your users suggest links, and display thumbnails for each.  </description>  
			  <pubDate>Thu, 12 Aug 2010 21:40:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/link-system/</guid>
		</item>
			
		<item>
			  <title>Rapid Paging</title>
			  <link>http://inneroptics.net/toolbox/rapid-paging/</link>
			  <description>Automatically make links load through AJAX, without a full page refresh </description>  
			  <pubDate>Thu, 12 Aug 2010 00:03:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/rapid-paging/</guid>
		</item>
			
		<item>
			  <title>Running a Concrete5 Micro ISV</title>
			  <link>http://inneroptics.net/concrete5_blog/running-a-concrete5-micro-isv/</link>
			  <description>Sharing some of the lessons I've learned while selling and supporting packages through the concrete5 marketplace.   </description>  
			  <pubDate>Wed, 14 Jul 2010 01:12:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/concrete5_blog/running-a-concrete5-micro-isv/</guid>
		</item>
			
		<item>
			  <title>Custom Statistics Panels</title>
			  <link>http://inneroptics.net/toolbox/stats/custom-statistics-panels/</link>
			  <description>
&lt;div id=&quot;quick-edit_block718&quot; class=&quot;quick-edit_block &quot;&gt;

	&lt;DIV class=&quot;quick-edit_view&quot; id=&quot;quick-edit_view718&quot;  &gt;&lt;p&gt;The Concrete5 Traffic &amp;amp; Statistics package, from version 2.12, allows other package and block developers to integrate their own stats display panels directly on the stats page of the dashboard. &lt;/p&gt;


&lt;p&gt;Just follow these steps:&lt;/p&gt;


&lt;p&gt;1) Create a new folder than will hold you panel's files, like /packages/my_package_name/stats_panel/ &lt;/p&gt;


&lt;p&gt;2) In that folder create a view.php file and a controller.php file&lt;/p&gt;


&lt;p&gt;3) You controller's class must be named according to your panel's directory, and must extend the ParticleTrafficPanel class.  So if it's placed within a folder called /my_package_statistics/, then it should have the class named MyPackageStatisticsParticleTrafficPanel.  Here's an example:&lt;/p&gt;      

&lt;p&gt;class MyPackageStatisticsParticleTrafficPanel extends ParticleTrafficPanel {&lt;br&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
	protected $title=&quot;My Package Stats&quot;;&lt;br&gt; 
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;	
	public function view(){&lt;br&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
		//optional - place any initiation logic here&lt;br&gt; 
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
	}&lt;br&gt;
}&lt;/p&gt;


&lt;p&gt;4A) Automatic installation:&lt;/p&gt;


&lt;p&gt;Just copy your folder into the /packages/tony_stats/panels/ directory, then visit the stats settings page.  It will notify you if there are any errors with your package.&lt;/p&gt;
 

&lt;p&gt;4B) Programatic Installation:&lt;/p&gt; 

&lt;p&gt;To register your new panel with the traffic and stats from within another package or application, add these lines to your code (not in the panel's view or controller) to include the required libraries: &lt;/p&gt;

&lt;p&gt;Loader::helper('stats',$packageHandle); &lt;br&gt;
Loader::model('panel',$packageHandle); &lt;/p&gt;

&lt;p&gt;…then register the panel by giving it the absolute file path to your panel's directory. &lt;/p&gt;

&lt;p&gt;$urlHelper = Loader::helper('concrete/urls');  &lt;br&gt;
$packageHandle='my_package_handle'; &lt;br&gt;
$statsPkg = Package::getByHandle($packageHandle);&lt;br&gt;
$absoluteFilePath = $urlHelper-&amp;gt;getPackageURL($statsPkg).'/stats_panel/'; &lt;br&gt;
$result = self::registerPanel( $absoluteFilePath ); &lt;/p&gt;

&lt;p&gt;The $result['msg'] will contain an error message if it detects any problems with your panel. &lt;/p&gt;


&lt;p&gt;5) Your package should now be displayed on the main stats page. &lt;/p&gt;&lt;/DIV&gt;	
	 
	
	&lt;/div&gt; </description>  
			  <pubDate>Wed, 16 Jun 2010 23:12:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/stats/custom-statistics-panels/</guid>
		</item>
			
		<item>
			  <title>Tutorial Video</title>
			  <link>http://inneroptics.net/toolbox/image-file-search/tutorial-video/</link>
			  <description>A video walk-through of the concrete5 image / files search block.   </description>  
			  <pubDate>Mon, 14 Jun 2010 23:40:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/toolbox/image-file-search/tutorial-video/</guid>
		</item>
			
		<item>
			  <title>2012 Prophecy</title>
			  <link>http://inneroptics.net/mayan_kingdom_book/2012-prophecy/</link>
			  <description>
Personally I believe that this date has been misinterpreted by those in the new-age spiritual movement, informed by Christian mythology, projecting their own beliefs of the end times onto Mayan culture. The Mayan's recorded time in cycles, and on 2012 one 5,000 cycle is said to finish and another will begin. No ancient Mayan artifacts refer to this as the apocolypse.  There is only one damaged Mayan inscription referencing this date.  It is located at the Tortuguero momument, and speaks of the descent of an unknown god.   </description>  
			  <pubDate>Fri, 11 Jun 2010 21:44:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/mayan_kingdom_book/2012-prophecy/</guid>
		</item>
			
		<item>
			  <title>The Mayan Kingdom eBook</title>
			  <link>http://inneroptics.net/journal/the-mayan-kingdom-ebook/</link>
			  <description>The Maya are one of the Mesoamerican cultures of this New World. They are descendants of the Olmecs, inhabiting Southern Mexico, the Yucatan Peninsula, and Central America. At their peak around 500-1000 C.E., Mayan society was one of the most advanced the earth had known, developing a complex culture, with a precise knowledge of astronomy, mathematics, and an intricate written language. </description>  
			  <pubDate>Fri, 11 Jun 2010 20:56:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/journal/the-mayan-kingdom-ebook/</guid>
		</item>
			
		<item>
			  <title>Reader Feedback</title>
			  <link>http://inneroptics.net/mayan_kingdom_book/reader-feedback/</link>
			  <description>
&lt;div id=&quot;quick-edit_block686&quot; class=&quot;quick-edit_block &quot;&gt;

	&lt;H1 class=&quot;quick-edit_view&quot; id=&quot;quick-edit_view686&quot;  &gt;Reader Feedback&lt;/H1&gt;	
	 
	
	&lt;/div&gt;
&lt;div id=&quot;quick-edit_block685&quot; class=&quot;quick-edit_block &quot;&gt;

	&lt;P class=&quot;quick-edit_view&quot; id=&quot;quick-edit_view685&quot;  &gt;If you have comments, any thoughts or criticisms about this eBook, or if you'd just like to submit a link to your own research on Mayan culture, just use the comment form below. Comments are moderated.&lt;/P&gt;	
	 
	
	&lt;/div&gt; 
&lt;h4 class=&quot;guestBook-title&quot;&gt;Comments:&lt;/h4&gt;
 </description>  
			  <pubDate>Wed, 09 Jun 2010 22:59:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/mayan_kingdom_book/reader-feedback/</guid>
		</item>
			
		<item>
			  <title>References</title>
			  <link>http://inneroptics.net/mayan_kingdom_book/references/</link>
			  <description>Books &amp; links about the Maya </description>  
			  <pubDate>Wed, 09 Jun 2010 22:46:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/mayan_kingdom_book/references/</guid>
		</item>
			
		<item>
			  <title>Decline</title>
			  <link>http://inneroptics.net/mayan_kingdom_book/decline/</link>
			  <description>The causes for the Maya's decline are numerous, but one of the central causes is that the demands they placed upon their environment grew beyond the capacity of the land. At it's peak, there were about 15 million people occupying the Mayan world. Over-population of Mayan metropolises are suspected to have gone beyond levels that the Mayan political and social networks were able to support, resulting in social unrest and revolution.  Frequent skirmishes by warring clans, such as the Toltec invasion of Chichen Itza, are suspected to have forced the Mayan populace to flee their cities. </description>  
			  <pubDate>Wed, 09 Jun 2010 22:14:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/mayan_kingdom_book/decline/</guid>
		</item>
			
		<item>
			  <title>Tulum</title>
			  <link>http://inneroptics.net/mayan_kingdom_book/tulum/</link>
			  <description>By around 900 C.E., the Classical Mayan cities were in decline. Tulum peaked around 1200-1400 C.E. in the post-classic period, as an example of the smaller city-states that still remained at this point in Mayan history. It was a major trading hub, situated as a cliff top seaport, overlooking the turquoise waters of the Caribbean. A </description>  
			  <pubDate>Wed, 09 Jun 2010 21:53:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/mayan_kingdom_book/tulum/</guid>
		</item>
			
		<item>
			  <title>Chichen Itza</title>
			  <link>http://inneroptics.net/mayan_kingdom_book/chichen-itza/</link>
			  <description>Chichen Itza was first settled around 435 C.E., however, in later centuries it became subject to waves of attacks from semi-nomadic tribes from northern Mexico. This and a period of prolonged drought gradually weakened Mayan society. In the 900s, the Toltec Itza tribe conquered the city, radically changing its culture. The Mayan renaissance that followed brought with it a new militaristic ethic. </description>  
			  <pubDate>Wed, 09 Jun 2010 21:24:00 CDT</pubDate>
			  <guid isPermaLink="true">http://inneroptics.net/mayan_kingdom_book/chichen-itza/</guid>
		</item>
	</channel>
</rss>  
		
