<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		
		<title>Noggin's Notebook</title>
		<link>http://www.busynoggin.com/</link>
		<description>This is Busy Noggin's little corner to chronicle his adventures in all things web including CSS, HTML, TYPO3, PHP and whole host of other acronyms.</description>
		<language>en</language>
		<image>
			<title>Noggin's Notebook</title>
			<url>http://www.busynoggin.com/typo3conf/ext/tt_news/ext_icon.gif</url>
			<link>http://www.busynoggin.com/</link>
			<width>18</width>
			<height>16</height>
			<description>This is Busy Noggin's little corner to chronicle his adventures in all things web including CSS, HTML, TYPO3, PHP and whole host of other acronyms.</description>
		</image>
		<generator>TYPO3 - get.content.right</generator>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		
		
		
		<lastBuildDate>Thu, 11 Feb 2010 06:44:00 -0600</lastBuildDate>
		
		
		<item>
			<title>Adding a Subject Line to an Email Link</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/adding-a-subject-line-to-an-email-link/</link>
			<description>I am always surprised with the little simple things I learn about web development. After years of...</description>
			<content:encoded><![CDATA[I am always surprised with the little simple things I learn about web development. After years of working with HTML&nbsp;I had not yet seen the simple coding for adding a subject line to an email link.
Normally the code for an email link looks like this:
<pre>&lt;a href=&quot;mailto:friend@yourdomain.com&quot;&gt;mailto&lt;/a&gt;</pre>
If you write it like this:
<pre>&lt;a href=&quot;mailto:friend@yourdomain.com?My Special Subject&quot;&gt;<br />mailto&lt;/a&gt;</pre>
Then when it is clicked the email will have a subject of &quot;My Special&nbsp;Subject.&quot;
]]></content:encoded>
			<category><a href="noggins-notebook/select_category/6/" title="HTML">HTML</a></category>
			
			
			<pubDate>Thu, 11 Feb 2010 06:44:00 -0600</pubDate>
			
		</item>
		
		<item>
			<title>The Year of the Lightbox</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/the-year-of-the-lightbox/</link>
			<description>It seems like the requirements for every site I do this year include lightboxes, video players and...</description>
			<content:encoded><![CDATA[<h3>NyroModal</h3>
I have just completed a major project with this jQuery lightbox plugin and it is AWESOME!
Both easy to configure and powerful, NyroModal can keep itself within the browser window adding scrollbars when needed for small monitors. If you resize the browser window while the lighbox is open, it will also resize on the fly.
If you AJAX new content into an already open lightbox, the lightbox will gracefully resize to accommodate the new content. This includes form responses.
This lightbox solution has several callbacks available. I recently had to serve alternate content in the lightbox when a user was on IE7 and had their page zoom set to something other than 100%. I was able to write JavaScript in one of the NyroModal callbacks to sense that scenario and accommodate it.
For TYPO3 projects I like to create a page template that will serve only its content between the body tags and nothing else (no head, html or body tags). I use this page template for content I am serving into the lightbox.
Find NyroModal at <link http://nyromodal.nyrodev.com>nyromodal.nyrodev.com.</link> 
<h3>Flow Player</h3>
Nice, open-source Flash video player. Has a well-documented API for controlling via JavaScript and is very skinnable.
Find Flow Player at <link http://flowplayer.org - external-link-new-window "Opens external link in new window">flowplayer.org.</link>
<h3>SlideShowPro and SlideShowPro Director</h3>
These two programs offer a great one-two punch in the slide show arena. SlideShowPro can handle video and / or still images. It is very skinnable, can be controlled with external JavaScript / HTML controls and has a well-documented API. SlideShowPro Director allows provides a very friendly interface for managing albums and images for serving to SlideShowPro
I recently completed a project where a TYPO3 extension automatically generates the images and XML for&nbsp; SlideShowPro from product brands. While in a slideshow users can click on images to add them to a cart. You do have to pay a small fee for SlideShowPro but it is worth it. It is Flash-based so you will need Flash to customize the look and options.
Find SlideShowPro at <link http://slideshowpro.net - external-link-new-window "Opens external link in new window">slideshowpro.net.</link>
<div></div>]]></content:encoded>
			
			
			<pubDate>Tue, 10 Nov 2009 00:00:00 -0600</pubDate>
			
		</item>
		
		<item>
			<title>Hungry for a System Mashup? Try a HTML Sandwich served by TYPO3.</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/hungry-for-a-system-mashup-try-a-html-sandwich-served-by-typo3/</link>
			<description>An easy way to mashup another system with TYPO3</description>
			<content:encoded><![CDATA[I recently launched a website for Fogo De Chão (<link http://www.fogodechao.com/ - external-link-new-window "Opens external link in new window">www.fogodechao.com</link>), a very nice steak restaurant with locations in both the U.S. and Brazil. Fusion Advertising provided the visual design and content while my company, Busy Noggin, Inc., handled the front-end coding and TYPO3 integration. Jeff Segars contributed an extension for customer comments and helped with server tweaking.
The site is graphically rich with with several interesting features including lightboxes and a scrolling JavaScript map of locations.
One of the project requirements was for the site to connect to a separate ASP site used to purchase gift cards. Additionally, the gift card site needed to be visually identical to the main site.
When on the main site (<link http://www.fogodechao.com/ - external-link-new-window "Opens external link in new window">www.fogodechao.com</link>) clicking on gift cards brings you to the ASP site (<link https://gc.fogodechao.com/ - external-link-new-window "Opens external link in new window">gc.fogodechao.com</link>). Notice it is visually identical to the main site (<link fileadmin/blog/2009/07/html_sandwich.jpg 800x370 external-link-new-window "Opens external link in new window">see comparison</link>). It is identical because much of its code is supplied by TYPO3.
Here is how it is done. TYPO3 is programmed to supply three pages of code that are used by the ASP site as server-side includes. None of these pages include any header data. This is the code they supply to the ASP site.
<ul><li>Include #1: The style sheet links that are included in the head of the ASP pages.</li><li>Include #2: The code for the design that falls after the opening body tag but before the main content of the page. This includes main menu and header image.</li><li>Include #3: The code for the design that falls after the main content but before the ending body tag.</li></ul>
In effect this creates an HTML sandwich in which the TYPO3 supplied code from the main site surrounds the content on the ASP site. This means that when TYPO3 updates items such as menus and promotional items on the main site thee the changes will automatically be reflected on the second ASP site. Also, CSS and background image changes can be managed from the main web site.
Of course, care must be taken that the paths in the supplied code are full URL paths (including the domain of the main site) so that links and images do not break on the second site.
One of the includes contains this in its TypoScript template:
config {<br />disableAllHeaderCode = 1<br />absRefPrefix = http://www.fogodechao.com/<br />}
This will produce&nbsp;a page&nbsp;without the head section or a body tag and will make all links full paths.
This is a very easy way to mashup two systems while keeping ongoing maintenance simple and presenting a unified experience to the front-end user.&nbsp;
Ron Hall<br />Busy Noggin, Inc.]]></content:encoded>
			
			
			<pubDate>Mon, 27 Jul 2009 00:00:00 -0500</pubDate>
			
		</item>
		
		<item>
			<title>Resize Browser Windows to Specific Size with One Click and More</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/resize-browser-windows-to-specific-size-with-one-click-and-more/</link>
			<description>Very simple technique for one-click resizing of a browser window to a specific size.</description>
			<content:encoded><![CDATA[This is one of those &quot;non-TYPO3 specific, but handy for developer&quot; kind of posts.
I bounce back and forth between Firefox and Safari alot. One of the things I like about the Firefox web developer toolbar is the ability to set custom window sizes for the browser.
Well, I found out you can easily do the same with Safari (and other browsers). Basically, you set up a bookmark in your bookmarks bar and instead of entering an address for your bookmark, you enter JavaScript.
If you consistently need a window size of 1100x1600 for one monitor and 1100x900 for another, then you can set up a bookmark for each.
Since you can set position as well as size, you can set up bookmarks that will size and position windows side by side in a monitor.&nbsp;
You can find out how to do it <link http://artofgeek.com/2008/02/29/set-safaris-window-size-with-one-click-of-the-mouse/comment-page-1/ - external-link-new-window "Opens external link in new window">here.</link> The link says it is for Safari but it can also be done in Firefox (and probably other browsers as well). And read the comment from the guy who figured out you could access the bookmark with a keyboard command (command-1, command-2, etc.)
<h3>Now for the more part.</h3>
The newest version of QuickKeys for Mac (version 4) has taken window resizing and positioning to a whole new level. It will allow you to assign shortcuts to resize and position the windows of ANY application. This is only a fraction of what this powerful macro program does. I have been using it for the better part of a decade and highly recommend it.
I just set up QuickKeys macros today for window resizing and this is what I did. For each application I set up a macro for for each of the window sizing and positioning I wanted. I named them &quot;Window 1&quot;, &quot;Window 2&quot;, &quot;Window 3&quot;,&nbsp; etc. (clever, yes?)
For each application I used the same keyboard shortcut for each window position (e.g. &quot;Window 1&quot; is always &quot;control-F1&quot; and &quot;Window 2&quot; is always &quot;Control-F2&quot;).
Even though the shortcut triggers are the same the window sizes and positions need not&nbsp;be the same between apps. For instance, &quot;Window 1&quot; may be 500x600 pixels in my text editor but 800x1000 pixels in Photoshop.
By the way, this is only a small symptom of the macro fetish I alluded to in my post on multiple monitors, <link noggins-notebook-archive/article/10-million-pixels-and-counting/ - external-link-new-window "Opens external link in new window">10 Million Pixels and Counting.</link>
Ron Hall<br />Busy Noggin, Inc.
<div></div>]]></content:encoded>
			
			
			<pubDate>Mon, 20 Jul 2009 00:00:00 -0500</pubDate>
			
		</item>
		
		<item>
			<title>A Framework for TemplaVoila and the Busy Noggin QuickSite</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/a-framework-for-templavoila-and-the-busy-noggin-quicksite/</link>
			<description>A workflow, code base and set of best practices for integrating a wide range of visual designs into...</description>
			<content:encoded><![CDATA[I am pleased to announce the public release of <link http://templavoila.busynoggin.com - external-link-new-window "Opens external link in new window">templavoila.busynoggin.com.</link> This site explains the framework I use for building sites with TemplaVoila and also provides a download of the Busy Noggin QuickSite which is a TYPO3 starter site built on the framework.
I presented a tutorial on this framework at T3CON09-Dallas which was well received. I will be presenting a refined version of that tutorial at T3CON09-Frankfurt. Since the Dallas conference over 100 developers received login access to the pre-release version of <link http://templavoila.busynoggin.com/ - external-link-new-window "Opens external link in new window">templavoila.busynoggin.com.</link> With the public release login access is no longer required.
The framework does not rely upon any special extensions and developers can use as much or as little of its techniques as they wish. I have been careful to call it &quot;a&quot; framework for TemplaVoila not &quot;the&quot; framework for TemplaVoila.
You can find out what this framework can do by watching a six minute video on the home page of <link http://templavoila.busynoggin.com/ - external-link-new-window "Opens external link in new window">templavoila.busynggin.com.</link> The middle of the video will be of particular interest as it demonstrates how editors can modify page layouts through the use of the utility FCEs in the framework.
Using this approach has cut down the time I spend mapping TemplaVoila templates by 75%. The time I do spend mapping is in constructing special FCEs for the unique needs of a particular site.
Look at the photo of the four layouts attached to this post (click image at top of post&nbsp;to see larger), you might be interested to know that they all run off the same page template code. The skinning approach in this framework supplies the variations in look and code. Were they all for the same client I could have setup up multiple domains in a single install and had them all use the same core page template files and could switch between them without remapping page templates.
I think this package will be of most interest to developers who build a number of sites with TemplaVoila and spend a significant amount of time dealing with CSS, TypoScript and datastructures. They will most quickly understand why I have approached site building the way I have.
If you look at the framework, pay particular attention to explanations of the header, footer, precode and postCode TypoScript objects as they are the keying to adapting the QuickSite to virtually any visual design without remapping page templates.
OK, now now for a seemly insane statement. I believe that 85% of the visual designs on the web can be accommodated&nbsp; in the QuickSite without remapping page templates. Don't believe me? Then see me in Frankfurt. :)
Ron Hall<br />Busy Noggin, Inc.]]></content:encoded>
			
			
			<pubDate>Wed, 15 Jul 2009 00:00:00 -0500</pubDate>
			
		</item>
		
		<item>
			<title>10 Million Pixels and Counting</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/10-million-pixels-and-counting/</link>
			<description>At our last TYPO3 user group meeting, Jeff Segars laughed at me. In and of itself, this is not...</description>
			<content:encoded><![CDATA[I have actually been intending to write this post before with titles such as &quot;A Tale of Two Monitors&quot; or &quot;Surprised by the Mini.&quot;
You see, I am a firm believer in using multiple machines and multiple monitors when working at my desk. I actually believe an additional monitor is more important for productivity than a faster processor.
This is what Jeff was laughing about. He added up the pixels on my monitors on my desk and they came up to 9,984,000.
To be honest, this multiple machines / monitors interest (compulsion and obsession are such negative terms) started with my previous employer. I was primarily doing graphic design for print and found that by adding an additional monitor my layout could remain uncluttered in one monitor while all of my palettes were open in the other. This eliminated the continual shifting of windows and opening and closing of palettes. And, of course, if two monitors is good then three monitors is great, correct?
As I started to work back and forth between two locations, I acquired a laptop. I kept all my data files on it and had all my applications installed to be able to work anywhere with it. But when at the office I would use it strictly for things like e-mail and serving the data files to my big desktop. This meant that for graphics work I could take advantage of the desktop's multiple monitors, big RAM and fast processors (keep in mind that some of my Photoshop files for banners could easily run into the hundreds of megabytes each).
Therefore I had everything with me at all times with the laptop but when at the office could use the big machine. Since all the data files were on the laptop I had no file synchronization issues.
Now, let me say that if you start using multiple monitors you must be able to track across them quickly. I use a Kensington trackball. Not one of the girlish, marble-sized trackballs, but the <link http://us.kensington.com/html/2200.html - external-link-new-window "Opens external link in new window">Expert Mouse</link> with a trackball the size of a pool ball and four programmable buttons. Spin that with the bottom of your hand and you will move across 40 inches of monitors in a split second.
Anyway back to my tale.
When I began my business I bought a MacBook Pro and a 30&quot; Apple Monitor. I wanted as much screen real estate as possible and would normally buy cheap third-party 24&quot; monitors. However, since I could only have one monitor attached, I sprung for the mighty 30&quot;.
This worked well for the first 18 months, but as I needed to be even more efficient, I started thinking about expanding. Attached to this post is a shot of what I have now and the following is how I use the setup when doing something like front-end coding.
24&quot; monitor on a 15&quot; MacBook Pro which runs:
<ol><li>all my communications (e-mail, IM, etc.) on the 15&quot; screen (everything else is on the 24&quot;).</li><li>Photoshop for slicing, measuring distances, and sampling the colors on the layouts I am coding in CSS.</li><li>browser and PDF reader for any documentation I am needing to access. I can refer docs on the laptop while coding on the other machine.</li><li>all my data files so I can do any task off site with just the laptop.</li></ol>
24&quot; and 30&quot; monitors on a Mac Mini (yes, I said Mini) which runs:
<ol><li>skEdit for coding HTML</li><li>multiple browser windows with front-end and back-end views of TYPO3. Hitting the show icon on the back-end refreshes the front-end in the other window.</li><li>my CSS editor with its preview window</li></ol>
Additionally, the machines run a bunch of other things like FTP client, MAMP server setup, etc.
Since the files I edit for web are much smaller that with my former print work, I am able to get by with the Mac Mini. I was pleasantly surprised when I learned that by adding the Mini DisplayPort adaptor to drive the 30&quot; that I could add an additional 24&quot; on its normal display port. The 24&quot; monitors are among the least expensive I found and I bumped the RAM on the MIni to 4 gigs.
Setting up multiple monitors on a desktop is not as expensive as you might think. Surprisingly, you can buy a Mac Mini and outfit it with 4 gigs of RAM and two 24&quot; monitors for less than $1,500 U.S.
Anyway, that is my geek confession for today. Perhaps someday I will feel the need to unburden my soul about my fetish for external keypads and macros.
Keeping a broad vision,<br />Ron]]></content:encoded>
			<category><a href="noggins-notebook/select_category/9/" title="General">General</a></category>
			
			
			<pubDate>Mon, 06 Jul 2009 00:00:00 -0500</pubDate>
			
		</item>
		
		<item>
			<title>Find TypoScript Properties Quickly</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/find-typoscript-properties-quickly/</link>
			<description>I often find myself needing to look up the properties of a particular TypoScript object. Of...</description>
			<content:encoded><![CDATA[<div>I often find myself needing to look up the properties of a particular&nbsp;TypoScript object. Of course, I search through TSref and when I need the &nbsp;<br />details of the object it is great. But if all I need is to be &nbsp;<br />reminded of the properties available and their spelling then searching &nbsp;<br />and scrolling through TSref is a bit of a pain and slows me down.
I posted this on the TYPO3 English list the other day. I explained that I was thinking of making an outline of TypoScript objects and their properties to use as a cheat sheet but wondered if anyone had anything like that already.
Among the responses was from Martin Holtz who directed me to a solution he has put together using OpenSearch within the TSref section of the TYPO3 Wiki. It is very nice and just what I wanted.
After adding it to your browser, simply select &quot;TYPO3 Search&quot; just like you would Google or Yahoo. Next enter the object or function you are looking for. For instance, type in &quot;stdWrap&quot; and you will get the page for that function with a list of all its properties. Search for &quot;image&quot; and you get the same for the IMAGE object. Much faster the searching and scrolling through a PDF of TSref.
You can find out more about this and how to install it at&nbsp;<link http://wiki.typo3.org/index.php/OpenSearch - external-link-new-window "Opens external link in new window">wiki.typo3.org/index.php/OpenSearch.</link>
Thanks, Martin for sharing.</div>]]></content:encoded>
			<category><a href="noggins-notebook/select_category/4/" title="TypoScript">TypoScript</a></category>
			
			
			<pubDate>Tue, 02 Jun 2009 19:23:00 -0500</pubDate>
			
		</item>
		
		<item>
			<title>Report on T3CON09-Dallas</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/report-on-t3con09-dallas/</link>
			<description>11 Countries, 4 continents, 20 states. A short report on T3CON09-Dallas</description>
			<content:encoded><![CDATA[<div>
<div><div>Well, everyone has gone home and the organizers are now all rested, so I believe now is the time to give a short report on the first official TYPO3 event to occur in North America.
Let me first say that the attendance and response was far beyond expectations particularly as&nbsp;this was a first-time event.
There were&nbsp;80 attendees and they came from 11 countries on 4 continents. This international diversity was particularly encouraging to me as I have always seen TYPO3 as a global system not a regional one.
The U.S. participants came from 20 different states (that’s our challenge, we are too spread out).
I recognized many TYPO3 “celebrities” whom I have seen in various podcasts, but also met others running significant sites previously unknown to me, like a lady from North Dakota who oversees a university’s TYPO3 site with 20,000 front end users.
The presentations were excellent and we had many positive comments about the venue. Overall, folks were very positive. We often heard, “I hope you are planning another for next year, I really want to come again.” We do indeed intend to make this an annual event.
Thanks to everyone--the organizers, those who travelled so far, and particularly our European presenters who brought so much expertise (though I sensed you gained something from our “local” presenters as well).</div></div></div>]]></content:encoded>
			<category><a href="noggins-notebook/select_category/1/" title="TYPO3">TYPO3</a></category>
			
			
			<pubDate>Wed, 22 Apr 2009 19:06:00 -0500</pubDate>
			
		</item>
		
		<item>
			<title>Photoshop Text Wrap: Faking Text Wrap In Photoshop</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/photoshop-text-wrap-faking-text-wrap-in-photoshop/</link>
			<description>When mocking up a web design today, I ran into the need to represent an image floated inside text....</description>
			<content:encoded><![CDATA[<div>When mocking up a web design today, I ran into the need to represent an image floated inside text. When doing this for print work it is just an easy matter of wrapping the text around the image. However, Photoshop is not as robust in its text handling as InDesign or even Illustrator and does not have text wrapping capability. A quick search on Google came up with&nbsp;<link http://www.photoshopessentials.com/photoshop-text/text-effects/text-wrap/ - external-link-new-window "Opens external link in new window">this technique for simulating text wrapping in Photoshop.</link>&nbsp;Not as slick as an InDesign wrap but decent.</div>]]></content:encoded>
			<category><a href="noggins-notebook/select_category/9/" title="General">General</a></category>
			
			
			<pubDate>Wed, 07 Jan 2009 15:47:00 -0600</pubDate>
			
		</item>
		
		<item>
			<title>Generate AJAX &quot;Loading in Progress&quot; Graphics the Easy Way</title>
			<link>http://www.busynoggin.com/noggins-notebook-archive/article/generate-ajax-loading-in-progress-graphics-the-easy-way/</link>
			<description>How to produce an AJAX &quot;loading in progress&quot; graphic that matches your site's look.</description>
			<content:encoded><![CDATA[<div>Sometime back I was putting together a jQuery carousel that was loading data via AJAX and I needed a animated graphic to indicate the data was in the process of loading. A search on google quickly produced&nbsp;<link http://www.ajaxload.info/ - external-link-new-window "Opens external link in new window">www.ajaxload.info</link>. This is an extremely easy way to produce a &quot;loading in progress&quot; graphic that matches your site's look. Those of you working extensively with AJAX probably already have a bunch of resources for this. But if you are new to AJAX,&nbsp;<link http://www.ajaxload.info/ - external-link-new-window "Opens external link in new window">www.ajaxload.info</link>&nbsp;is a great site to bookmark.</div>]]></content:encoded>
			<category><a href="noggins-notebook/select_category/8/" title="Front-end Coding">Front-end Coding</a></category>
			<category><a href="noggins-notebook/select_category/9/" title="General">General</a></category>
			
			
			<pubDate>Mon, 27 Oct 2008 15:19:00 -0500</pubDate>
			
		</item>
		
	</channel>
</rss>