<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>FireSign News</title>
	<atom:link href="http://firesign.net/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://firesign.net/blog</link>
	<description>The latest information from the FireSign world</description>
	<lastBuildDate>Tue, 29 Jun 2010 14:43:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Anode launches do-it-yourself Touchscreen Applications for FireSign™ Dynamic Digital Signage</title>
		<link>http://firesign.net/blog/2010/05/26/anode-launches-do-it-yourself-touchscreen-applications-for-firesign%e2%84%a2-dynamic-digital-signage/</link>
		<comments>http://firesign.net/blog/2010/05/26/anode-launches-do-it-yourself-touchscreen-applications-for-firesign%e2%84%a2-dynamic-digital-signage/#comments</comments>
		<pubDate>Wed, 26 May 2010 18:21:46 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=586</guid>
		<description><![CDATA[Anode, Inc. has announced a revolutionary new suite of applications for building touchscreen content. Using the company’s FireSign™ Dynamic Digital Signage software, customers can now create, maintain and schedule interactive content for touch-enabled displays.
FireSign’s Touchscreen Applications allow customers to create interactive experiences such as digital scrapbooks, video jukeboxes, high definition galleries, virtual donor walls, guided [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://anode.com" target="_blank"><img class="alignright size-full wp-image-588" title="FireSign Content Editor_small" src="http://firesign.net/blog/wp-content/uploads/2010/05/FireSign-Content-Editor_small.jpg" alt="FireSign Content Editor_small" width="175" height="121" />Anode, Inc.</a> has announced a revolutionary new suite of applications for building touchscreen content. Using the company’s <a href="http://firesign.net" target="_blank">FireSign™ Dynamic Digital Signage</a> software, customers can now create, maintain and schedule interactive content for touch-enabled displays.</p>
<div id="attachment_594" class="wp-caption alignleft" style="width: 260px"><img class="size-full wp-image-594" title="FireSign Interactive Guide" src="http://firesign.net/blog/wp-content/uploads/2010/05/FireSign-Interactive-Guide2.jpg" alt="FireSign Interactive Guide" width="250" height="188" /><p class="wp-caption-text">FireSign Interactive Guide</p></div>
<p>FireSign’s Touchscreen Applications allow customers to create interactive experiences such as digital scrapbooks, video jukeboxes, high definition galleries, virtual donor walls, guided tours and much more. A number of these applications are already in production for customers, and the first installations will be completed in the coming weeks.</p>
<p>Content editing tools eliminate the need for complex programming and navigational design. FireSign users simply upload existing media assets into pre-defined application templates with customizable design elements such as fonts and background colors. Changes and edits are then deployed directly to any number of touchscreens running on the FireSign system.</p>
<p>“Our customers are very familiar with media creation tools for producing things like blogs, photos and movies,” commented Chris Lee, Vice President of Technology. “Now, we have unlocked that same creation process for interactive kiosks and touchscreen displays.”</p>
<div id="attachment_597" class="wp-caption alignright" style="width: 260px"><img class="size-full wp-image-597" title="FireSign Gallery" src="http://firesign.net/blog/wp-content/uploads/2010/05/FireSign-Gallery.jpg" alt="FireSign Gallery" width="250" height="187" /><p class="wp-caption-text">FireSign Gallery</p></div>
<p>From the beginning of the development process, Anode has worked closely with customers to develop these Touchscreen Applications. “Our customers have been delighted with the capabilities we have built into these applications,” stated Richard Bess, VP Sales and Marketing. “Thanks to them, we are developing applications that pinpoint their exact needs in a format that is extremely easy to use.”</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2010/05/26/anode-launches-do-it-yourself-touchscreen-applications-for-firesign%e2%84%a2-dynamic-digital-signage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What&#8217;s New in FireSign 4.0</title>
		<link>http://firesign.net/blog/2010/04/01/whats-new-in-firesign-4-0/</link>
		<comments>http://firesign.net/blog/2010/04/01/whats-new-in-firesign-4-0/#comments</comments>
		<pubDate>Thu, 01 Apr 2010 18:41:55 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=569</guid>
		<description><![CDATA[This month, Anode, Inc. is proud to introduce FireSign 4.0 as the first major upgrade to the FireSign Dynamic Digital Signage platform since May 2008. This full version upgrade includes numerous enhancements to both the usability and functionality of the FireSign software.
Redesigned User Interface

FireSign now has a more consistent look and feel across multiple browsers [...]]]></description>
			<content:encoded><![CDATA[<p>This month, <a href="http://anode.com" target="_blank">Anode, Inc.</a> is proud to introduce FireSign 4.0 as the first major upgrade to the FireSign Dynamic Digital Signage platform since May 2008. This full version upgrade includes numerous enhancements to both the usability and functionality of the FireSign software.</p>
<p style="text-align: left;"><strong>Redesigned User Interface</strong></p>
<ul style="text-align: left;">
<li>FireSign now has a more consistent look and feel across multiple browsers for users with multiple computing environments.</li>
<li>The FireSign interface is cleaner and more intuitive with a redesigned Home screen that provides more useful information and direct links to common tasks.</li>
<li>Data tables have been completely overhauled to include checkboxes where you can select multiple rows for operations like Delete. In addition, data tables are now &#8220;paged&#8221; to show 20 records per screen with Prev/Next and page number links.</li>
<li>Media groups have been eliminated in favor of new &#8220;Tags&#8221; which are more flexible and less restrictive. Each media item can have up to 8 tags, such as &#8220;backgrounds&#8221;, &#8220;outdoor shots&#8221; etc.</li>
<li>FireSign 4.0 also includes a greatly improved media import screen with progress bars.</li>
</ul>
<p style="text-align: left;"><strong>Redesigned Layout Editor</strong></p>
<ul style="text-align: left;">
<li>Message segments no longer have individual scenes. Layout now has a more advanced timeline-based editor to simplify the creation of segments without the cumbersome Scene Sorter used in previous versions.</li>
<li>Within Layout, media items are now listed by their &#8220;Tags” for faster access to relevant assets.</li>
</ul>
<p style="text-align: left;"><strong>Exciting New <a href="http://firesign.net/touchscreen.php" target="_blank">Touchscreen Applications</a></strong></p>
<ul style="text-align: left;">
<li>New Touchscreen Application editors make it easy to create and maintain interactive content such as <a href="http://firesign.net/imagebrowser.php" target="_blank">Image  Browsers</a>, <a href="http://firesign.net/gallery.php" target="_blank">Galleries</a>, <a href="http://firesign.net/scrapbook.php" target="_blank">Scrapbooks</a>, <a href="http://firesign.net/jukebox.php" target="_blank">Jukeboxes</a> and many more.</li>
<li>Touchscreen Application editors can be used on Windows or Macintosh browsers to create and edit content.</li>
</ul>
<p style="text-align: left;"><strong>Other Interface Changes</strong></p>
<ul style="text-align: left;">
<li>New status listings identify when a segment is “In Use” by a schedule or as an override for a Player. Likewise, the schedule list screen now shows which schedules are &#8220;In Use&#8221; by a Player.</li>
<li>Schedules can now be modified by simply dragging a schedule item to change its playback priority or order.</li>
<li>More feedback prompts appearing at the top of the browser window have been built into the system on all operations.</li>
<li>A new Comments feature allows user-to-user dialog about media, segments or schedules with direct links to the referenced items.</li>
<li>No more confusing vertical or horizontal screen orientations, just width and height dimensions throughout the system.</li>
<li>Two new reports are available: a summary report for segment playback and a Player status report.</li>
</ul>
<p style="text-align: left;"><strong>Hardware Changes</strong></p>
<ul style="text-align: left;">
<li style="text-align: left;">The hardware USB keys for Players have been eliminated, and Players are now authenticated by the server. New Players can now be deployed faster and more efficiently.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2010/04/01/whats-new-in-firesign-4-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Considerations for Interactive Wayfinding in Airports</title>
		<link>http://firesign.net/blog/2010/03/25/5-considerations-for-interactive-wayfinding-in-airports/</link>
		<comments>http://firesign.net/blog/2010/03/25/5-considerations-for-interactive-wayfinding-in-airports/#comments</comments>
		<pubDate>Thu, 25 Mar 2010 15:15:51 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=561</guid>
		<description><![CDATA[1.  The type of wayfinding information to present
Does your airport need to present all Points of Interest (POI) available in the airport, concourse or property such as emergency, medical, administration, etc.? Or, is the primary focus on specific passenger needs such as Quick Serve Restaurants (QSR) and other retail concessionaires? By understanding the focus of [...]]]></description>
			<content:encoded><![CDATA[<p><strong><img class="alignright size-full wp-image-564" title="FireSign_Interactive_Digital_Signage_in_Airports" src="http://firesign.net/blog/wp-content/uploads/2010/03/FireSign_Interactive_Digital_Signage_in_Airports.jpg" alt="FireSign_Interactive_Digital_Signage_in_Airports" width="270" height="400" />1.  The type of wayfinding information to present</strong><br />
Does your airport need to present all Points of Interest (POI) available in the airport, concourse or property such as emergency, medical, administration, etc.? Or, is the primary focus on specific passenger needs such as Quick Serve Restaurants (QSR) and other retail concessionaires? By understanding the focus of your wayfinding signage, you can more precisely define the required capabilities you need.</p>
<p><strong>2 . The efficiency of a single-user experience vs. a multi-user experience</strong><br />
Airport patrons have become accustomed to both public and private media experiences. On 	one hand, passengers have traditionally consumed directional wayfinding information through large public signage. More recently, travelers have learned to enter or verify very private information through flight check-in and rental car kiosks. When providing interactive wayfinding information, does the screen size leave people feeling exposed, knowing that others may eavesdrop on their experience? Personalized wayfinding is more aptly handled in a manner that gives users some sense of personal space.</p>
<p><strong>3. Management of interactive wayfinding systems</strong><br />
Printed wayfinding signs have traditionally proven to be costly and have very limited life cycles. While digital signage and interactive wayfinding are significant steps in alleviating some of those costs, Administrators should realize and appropriate resources for continued management of these systems. Manufacturers, resellers or agencies that provide design and content management services should be favored when weighing these considerations. Systems that also offer the simplicity and flexibility of being managed by Airport Staff should also be given weighted consideration.</p>
<p><strong>4. Using an interactive wayfinding system as a value-add or revenue generating mechani</strong>sm<br />
Investment in interactive wayfinding is not an inconsequential expenditure. How do Airport Administrators maximize that investment and shorten the ROI realization term? Many interactive wayfinding systems will allow for value-added options like wireless coupons or ad-driven content. Administrators can also take advantage of interaction metrics that are reported back by the digital signage system. These metrics can be used to improve user interface design, spot search trends and to discover hidden user behavior patterns.</p>
<p><strong>5. Buying vs. leasing an interactive wayfinding system</strong><br />
Today, more progressive agencies and manufacturers realize the effect of Moore’s law on technology and hardware; a cutting-edge product this year may be obsolete two years after implementation.  So how do airport administrators protect themselves from this effect? More and more end-users are electing to lease equipment for terms of 3-5 years, depending on use. The market will begin to see more facilities choose lease options that allow them to return equipment at the end of a limited term in exchange for updated equipment. The service model will continue to trend towards a Software as a Service (SaaS) model that has been popularized within other business markets.</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2010/03/25/5-considerations-for-interactive-wayfinding-in-airports/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How We Used Mobile Tagging to Share Our New Address</title>
		<link>http://firesign.net/blog/2009/11/20/how-we-used-mobile-tagging-to-share-our-new-address/</link>
		<comments>http://firesign.net/blog/2009/11/20/how-we-used-mobile-tagging-to-share-our-new-address/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 15:49:18 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=544</guid>
		<description><![CDATA[We’re moving to East Nashville, and we wanted to make it simple for visitors to download our new contact information. Since most of our visitors are App-savvy mobile phone users, we decided to add a mobile tag to the FireSign digital signage displays in our lobby.
What is a Mobile Tag? Mobile tags, also called QR [...]]]></description>
			<content:encoded><![CDATA[<p>We’re moving to East Nashville, and we wanted to make it simple for visitors to download our new contact information. Since most of our visitors are App-savvy mobile phone users, we decided to add a mobile tag to the FireSign digital signage displays in our lobby.</p>
<p>What is a Mobile Tag? Mobile tags, also called QR barcodes, use your camera phone (or other mobile device) to capture and decode data embedded in two-dimensional barcodes. The data in these barcodes may instruct your phone to launch a web site, place a phone call, or in our case, download contact information.</p>
<p>Here is a snapshot of the message we created for the FireSign digital signage in our current lobby:</p>
<p><img class="aligncenter size-full wp-image-557" title="Mobile-Tag-on-FS-Digital-Signage" src="http://firesign.net/blog/wp-content/uploads/2009/11/Mobile-Tag-on-FS-Digital-Signage1.jpg" alt="Mobile-Tag-on-FS-Digital-Signage" width="500" height="393" /></p>
<p>Use this close-up of our mobile tag to see how the technology works. Just download the mobile app by visiting <a href="http://gettag.mobi/" target="_blank">http://gettag.mobi</a>, snap a picture of the barcode and voila! You now have complete contact information for our new location.</p>
<p><img class="aligncenter size-full wp-image-548" title="Mobile Tag with Anode Contact Information" src="http://firesign.net/blog/wp-content/uploads/2009/11/Anode-Mobile-Tag.jpg" alt="Mobile Tag with Anode Contact Information" width="300" height="250" /></p>
<p>In a future blog post, we will share more information on how to create your own mobile tags. But for now… we should get back to packing.</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/11/20/how-we-used-mobile-tagging-to-share-our-new-address/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Purchasing Stock Photography for your FireSign Digital Signage System</title>
		<link>http://firesign.net/blog/2009/08/25/purchasing-stock-photography-for-your-firesign-digital-signage-system/</link>
		<comments>http://firesign.net/blog/2009/08/25/purchasing-stock-photography-for-your-firesign-digital-signage-system/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 15:54:14 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=494</guid>
		<description><![CDATA[Adding new images to your digital signage is a great way to keep your messages fresh and relevant. Several online sources make it easy to update images, icons and even video elements with royalty-free stock at very affordable prices (many between $1 and $20). However, there are a couple of points to consider before purchasing [...]]]></description>
			<content:encoded><![CDATA[<p>Adding new images to your digital signage is a great way to keep your messages fresh and relevant. Several online sources make it easy to update images, icons and even video elements with royalty-free stock at very affordable prices (many between $1 and $20). However, there are a couple of points to consider before purchasing your first image.</p>
<p>1.	Make sure the graphic image is consistent with your overall brand image and messaging. This is a very subjective process, and you will have to rely on your own judgment as to which visual elements work together. One suggestion is to look for an artist with a portfolio of related images.</p>
<table style="height: 66px;" border="0" width="419" align="center">
<tbody>
<tr>
<td style="text-align: left;">For example, perhaps you want to promote healthy eating habits among students or drive visitors to the fresh produce in your café.  Here is an <a href="http://www.istockphoto.com/file_search.php?action=file&amp;lightboxID=5405997" target="_blank">artist with over a dozen related images</a> that give you flexibility and consistency.</td>
</tr>
</tbody>
</table>
<p>2.	Remember that pixels count. Purchase the correct file size to make certain your brand message stays in focus. Start by determining the resolution of your monitor. The quickest way to do this is to check your “Player Format” from within FireSign Studio.  From the home screen, click the “Where” circle.  This selection will give you a list of your active Players and their formats.  A typical format is 1360 x 768 which denotes the pixel dimensions of your screen.  (This dimension should also be reflected in the format of the segments you have been creating.) With this information, you can now calculate the minimum pixel dimensions based on the the screen area you want to cover.  Here is a simple example:</p>
<p style="text-align: center;"><img class="size-full wp-image-509 aligncenter" title="Digital Signage Size Chart" src="http://firesign.net/blog/wp-content/uploads/2009/08/Digital-Signage-SizeChart.gif" alt="Digital Signage Size Chart" width="279" height="159" /></p>
<address><em>Note: Although you can save money by purchasing a smaller image size, we suggest you go ahead and purchase an image large enough to cover your entire screen.  By doing so, you will always have the flexibility to use the image at any size/location on the screen without having to repurchase a larger image.</em></address>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/08/25/purchasing-stock-photography-for-your-firesign-digital-signage-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FireSign Presentation from WhippleHill User Conference</title>
		<link>http://firesign.net/blog/2009/07/08/firesign-presentation-from-whipplehill-user-conference/</link>
		<comments>http://firesign.net/blog/2009/07/08/firesign-presentation-from-whipplehill-user-conference/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 21:26:11 +0000</pubDate>
		<dc:creator>FireSign</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=417</guid>
		<description><![CDATA[Independent schools continue to find innovative ways to communicate their brand image and value.  As a WhippleHill Ecosystem partner, FireSign strengthens a school’s overall brand strategy by bringing online and offline communications into the hallways of the school.  Download FireSign&#8217;s breakout presentation from the 2009 WhippleHill User Conference for an overview of FireSign [...]]]></description>
			<content:encoded><![CDATA[<p>Independent schools continue to find innovative ways to communicate their brand image and value.  As a WhippleHill Ecosystem partner, FireSign strengthens a school’s overall brand strategy by bringing online and offline communications into the hallways of the school.  Download FireSign&#8217;s breakout presentation from the 2009 WhippleHill User Conference for an overview of FireSign applications and installations in the educational environment.</p>
<p><a href='http://firesign.net/blog/2009/07/08/firesign-presentation-from-whipplehill-user-conference/whuc-presentation/' rel='attachment wp-att-485'>FireSign WhippleHill UC Presentation</a></p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/07/08/firesign-presentation-from-whipplehill-user-conference/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stay On-Message with FireSign&#8217;s Segment Workflow</title>
		<link>http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/</link>
		<comments>http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 15:23:17 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=408</guid>
		<description><![CDATA[The Segment Workflow feature in FireSign 3.3 facilitates the creation and approval of digital signage messaging prior to public display.
The basic workflow process follows these steps:
• 	A content author creates a new message segment then requests approval.
• 	An editor reviews the segment and either requests revisions or marks the segment as approved.
• 	Once the segment [...]]]></description>
			<content:encoded><![CDATA[<p>The Segment Workflow feature in FireSign 3.3 facilitates the creation and approval of digital signage messaging prior to public display.</p>
<p>The basic workflow process follows these steps:<br />
• 	A content author creates a new message segment then requests approval.<br />
• 	An editor reviews the segment and either requests revisions or marks the segment as approved.<br />
• 	Once the segment is approved, it can no longer be changed and it may be scheduled to play by either the author or the editor.</p>
<p><strong><br />
Setting up Projects and Users</strong></p>
<p>A user with FireSign Server access must first enable the Workflow process for each project. </p>
 <div id="attachment_409" class="wp-caption alignnone" style="width: 310px"><a href="http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/attachment/1/" rel="attachment wp-att-409"><img src="http://firesign.net/blog/wp-content/uploads/2009/07/1-300x265.png" alt="Workflow Enabled" title="1" width="300" height="265" class="size-medium wp-image-409" /></a><p class="wp-caption-text">Workflow Enabled</p></div>
<p>Next, the server administrator must define the creation and approval hierarchy by configuring the user rights on the User Detail Screen. An author has permission to “Alter Segments,” while an editor has the ability to “Approve Segments.” In scenarios where you may have more than one user with approval authority, segments will only need to be approved by one such user.  </p>
<div id="attachment_410" class="wp-caption alignnone" style="width: 310px"><a href="http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/attachment/2/" rel="attachment wp-att-410"><img src="http://firesign.net/blog/wp-content/uploads/2009/07/2-300x231.png" alt="Admin Rights" title="2" width="300" height="231" class="size-medium wp-image-410" /></a><p class="wp-caption-text">Admin Rights</p></div>
<p><strong>Using the Workflow Feature</strong></p>
<p>With your permissions in place, a content author is now able to create a new message segment in FireSign Studio. The status of the segment is shown as “In Production.” Once the author believes the segment to be complete, he or she may “Request Approval.” A dialog box appears with the title “Submit Request for Approval.” Any editors for this project are listed below the comments field with the option to include them in the approval process. </p>
<div id="attachment_411" class="wp-caption alignnone" style="width: 310px"><a href="http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/attachment/3/" rel="attachment wp-att-411"><img src="http://firesign.net/blog/wp-content/uploads/2009/07/3-300x243.png" alt="Approval Request" title="3" width="300" height="243" class="size-medium wp-image-411" /></a><p class="wp-caption-text">Approval Request</p></div>
<p>The editors chosen in the dialog will receive an email requesting approval for the segment. At this stage, the segment can no longer be edited using FireSign Layout, and the segment status is changed to “Pending Approval.”</p>
<p>Next, an editor must now log into FireSign Studio, and find the Segment Detail screen for the target segment. The editor has two choices at this point. They can (1) approve the segment or (2) send it back to the author for further revisions.</p>
<p>By clicking “Needs Revision,” the status of the segment reverts back to “In Production,” and the segment may be edited once again. A notification email is sent to the author along with any comments from the editor.</p>
<p>When the editor clicks “Mark As Approved,” the status of the segment changes to “Approved.” A confirmation email is sent to the author, and the segment can now be used in a schedule.</p>
<div id="attachment_412" class="wp-caption alignnone" style="width: 310px"><a href="http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/attachment/4/" rel="attachment wp-att-412"><img src="http://firesign.net/blog/wp-content/uploads/2009/07/4-300x232.png" alt="Pending Approval" title="4" width="300" height="232" class="size-medium wp-image-412" /></a><p class="wp-caption-text">Pending Approval</p></div>
<p>By enabling the Workflow feature, you add a powerful tool for keeping your messaging and branding consistent while allowing multiple users to create content for your FireSign digital signage system.</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/07/07/stay-on-message-with-firesigns-segment-workflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Anode Launches New FireSign Web Site</title>
		<link>http://firesign.net/blog/2009/06/04/anode-launches-new-firesign-web-site/</link>
		<comments>http://firesign.net/blog/2009/06/04/anode-launches-new-firesign-web-site/#comments</comments>
		<pubDate>Thu, 04 Jun 2009 19:30:47 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=398</guid>
		<description><![CDATA[FireSign.net Showcases the First Step Towards the Company’s Next Generation of Digital Signage Software
NASHVILLE, TN. June 4, 2009 – Anode Inc. has unveiled a newly redesigned web site for the company’s FireSign digital signage software product. FireSign.net features expanded content for both technical and marketing professionals who want to deliver the right message to the [...]]]></description>
			<content:encoded><![CDATA[<p>FireSign.net Showcases the First Step Towards the Company’s Next Generation of Digital Signage Software</p>
<p>NASHVILLE, TN. June 4, 2009 – Anode Inc. has unveiled a newly redesigned web site for the company’s FireSign digital signage software product. <a href="http://firesign.net" target="_blank">FireSign.net</a> features expanded content for both technical and marketing professionals who want to deliver the right message to the right audience at the right time.  A key feature of the new site is a streaming media micro site (<a href="http://FireSignApplications.com" target="_blank">FireSignApplications.com</a>) focusing on the system’s interactive capabilities.</p>
<p>“One of the key requirements of the new site was to provide updated information on how FireSign can be used to transform passive signage into interactive experiences,” noted Chris Lee, Vice President of Technology.  “The future of digital signage is about more than just hanging flat-panel displays on walls, and we feel this new site better communicates how FireSign can enhance the visitor experience and integrate with the overall communication strategy of our clients.”</p>
<p>First introduced in 2000, FireSign is the company’s proprietary digital signage platform for communicating and interacting with audiences in public spaces.  From its first installation at Colonial Williamsburg, FireSign has established a national presence.  FireSign is found in schools, libraries, transportation centers, corporations and museums.</p>
<p>“As a creative communications studio, we are in a unique position to offer FireSign as a digital messaging platform for our clients,” commented Richard Bess, Vice President of Sales and Marketing.  “We know how to apply technology, and we know how to create messages that educate, motivate and entertain visitors in a variety of industries.”</p>
<p>The updated FireSign web site gives the company a new platform for sharing examples of how FireSign is being used to attract new customers, drive revenue and reduce costs. Meanwhile, Anode continues to explore new screen-based technologies while preparing the next version of FireSign for release in 2010.  Access new the FireSign Web site at <a href="http://FireSign.net" target="_blank">FireSign.net</a>.</p>
<p>About Anode<br />
Located in Nashville, Tennessee, Anode Inc. is a visual communications studio where brand experiences are engineered in print and interactive media. For more than 18 years, Anode has been creating award-winning designs for corporations and cultural institutions. Anode developed its proprietary FireSign™ digital signage platform to deliver meaningful communications in public spaces.  From concept and installation to custom content and ongoing management, Anode’s FireSign software and services offer end-to-end solutions for enhancing the physical visitor experience.  More information is available at <a href="http://anode.com" target="_blank">Anode.com</a> and <a href="http://firesign.net" target="_blank">FireSign.net</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/06/04/anode-launches-new-firesign-web-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Displaying the Twitter Widget on a FireSign Player</title>
		<link>http://firesign.net/blog/2009/06/02/displaying-the-twitter-widget-on-a-firesign-player/</link>
		<comments>http://firesign.net/blog/2009/06/02/displaying-the-twitter-widget-on-a-firesign-player/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 17:59:00 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=352</guid>
		<description><![CDATA[Step 1: Create an HTML file that will call the Twitter widget.
Using a text editor, MS Word, Adobe Dreamweaver, Notepad, or other editor of your choice, create a basic HTML skeleton file with these lines:
&#60;!DOCTYPE html PUBLIC &#8220;-//W3C//DTD XHTML 1.0 Transitional//EN&#8221; &#8220;http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&#8221;&#62;
&#60;html xmlns=&#8221;http://www.w3.org/1999/xhtml&#8221;&#62;
&#60;head&#62;
&#60;meta http-equiv=&#8221;Content-Type&#8221; content=&#8221;text/html; charset=UTF-8&#8243; /&#62;
&#60;title&#62;twitter display page&#60;/title&#62;
&#60;/head&#62;
&#60;body&#62;
&#60;/body&#62;
&#60;/html&#62;
Step 2: Obtain the code snippet for [...]]]></description>
			<content:encoded><![CDATA[<p><strong><em>Step 1: Create an HTML file that will call the Twitter widget.</em></strong><br />
Using a text editor, MS Word, Adobe Dreamweaver, Notepad, or other editor of your choice, create a basic HTML skeleton file with these lines:</p>
<p style="padding-left: 30px;">&lt;!DOCTYPE html PUBLIC &#8220;-//W3C//DTD XHTML 1.0 Transitional//EN&#8221; &#8220;http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&#8221;&gt;</p>
<p style="padding-left: 30px;">&lt;html xmlns=&#8221;http://www.w3.org/1999/xhtml&#8221;&gt;</p>
<p style="padding-left: 30px;">&lt;head&gt;</p>
<p style="padding-left: 30px;">&lt;meta http-equiv=&#8221;Content-Type&#8221; content=&#8221;text/html; charset=UTF-8&#8243; /&gt;</p>
<p style="padding-left: 30px;">&lt;title&gt;twitter display page&lt;/title&gt;</p>
<p style="padding-left: 30px;">&lt;/head&gt;</p>
<p style="padding-left: 30px;">&lt;body&gt;</p>
<p style="padding-left: 30px;">&lt;/body&gt;</p>
<p style="padding-left: 30px;">&lt;/html&gt;<em><strong></strong></em></p>
<p><em><strong>Step 2: Obtain the code snippet for the Twitter widget.</strong></em><br />
The code snippet for the widget is obtained from Twitter using your account settings.<br />
Sign in to your twitter account, then go to: <a href="http://twitter.com/widgets">http://twitter.com/widgets.</a></p>
<p>Select “Other” and click “Continue”</p>
<p style="padding-left: 30px;"><a rel="attachment wp-att-289" href="http://firesign.net/blog/?attachment_id=289"><img class="alignnone size-medium wp-image-289" title="twitter-1" src="http://firesign.net/blog/wp-content/uploads/2009/06/picture-1-300x222.png" alt="twitter-1" width="300" height="222" /></a></p>
<p>Select “Flash Widget” and click “Continue”</p>
<p style="padding-left: 30px;"><a rel="attachment wp-att-290" href="http://firesign.net/blog/?attachment_id=290"><img class="alignnone size-medium wp-image-290" title="twitter-2" src="http://firesign.net/blog/wp-content/uploads/2009/06/picture-2-300x237.png" alt="twitter-2" width="300" height="237" /></a></p>
<p>Select “Interactive Widget” and click “Continue”</p>
<p style="padding-left: 30px;"><a rel="attachment wp-att-292" href="http://firesign.net/blog/?attachment_id=292"><img class="alignnone size-medium wp-image-292" title="twitter-3" src="http://firesign.net/blog/wp-content/uploads/2009/06/picture-31-300x248.png" alt="twitter-3" width="300" height="248" /></a></p>
<p>Select a style using the pop-up menu. There are three options.  (Don’t worry about the size option right now. We will adjust that in the next step to fit your FireSign Player screen’s format and pixel dimensions.)</p>
<p style="padding-left: 30px;"><a rel="attachment wp-att-293" href="http://firesign.net/blog/?attachment_id=293"><img class="alignnone size-medium wp-image-293" title="twitter-4" src="http://firesign.net/blog/wp-content/uploads/2009/06/picture-4-300x224.png" alt="twitter-4" width="300" height="224" /></a></p>
<p>Select and copy the HTML from the box in the web browser.</p>
<p style="padding-left: 30px;"><a rel="attachment wp-att-294" href="http://firesign.net/blog/?attachment_id=294"><img class="alignnone size-medium wp-image-294" title="twitter-5" src="http://firesign.net/blog/wp-content/uploads/2009/06/picture-5-300x220.png" alt="twitter-5" width="300" height="220" /></a></p>
<p>Go to the HTML page you created in Step 1, and paste this code between the &lt;body&gt; and<br />
&lt;/body&gt; tags.</p>
<p><strong><em>Step 3: Customize the widget code to fit your FireSign Player</em></strong></p>
<p>Edit the width and height parameters in the widget code to match the width and height of the pixel dimensions for your FireSign Player. See the <span style="color: #ff0000;">red tex</span><span style="color: #ff0000;">t </span>in the code block below. For instance, your Player format might be “1360&#215;768 16:9H”. The width is the number before the “x” (1360) and the height is the number after it (768). Do not change anything else.</p>
<p style="padding-left: 30px;">&lt;object classid=&#8221;clsid:d27cdb6e-ae6d-11cf-96b8-444553540000&#8243; codebase=&#8221;http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=9,0,124,0&#8243; width=&#8221;458&#8243; height=&#8221;822&#8243; id=&#8221;TwitterWidget&#8221; align=&#8221;middle&#8221;&gt;<br />
&lt;param name=&#8221;allowScriptAccess&#8221; value=&#8221;always&#8221; /&gt;<br />
&lt;param name=&#8221;allowFullScreen&#8221; value=&#8221;true&#8221; /&gt;<br />
&lt;param name=&#8221;movie&#8221; value=&#8221;http://static.twitter.com/flash/widgets/profile/TwitterWidget.swf&#8221; /&gt;<br />
&lt;param name=&#8221;quality&#8221; value=&#8221;high&#8221; /&gt;<br />
&lt;param name=&#8221;bgcolor&#8221; value=&#8221;#FF6600&#8243; /&gt;<br />
&lt;param name=&#8221;FlashVars&#8221; value=&#8221;userID=16436568&amp;styleURL=http://static.twitter.com/flash/widgets/profile/velvetica.xml&#8221;&gt;<br />
&lt;embed src=&#8221;http://static.twitter.com/flash/widgets/profile/TwitterWidget.swf&#8221; quality=&#8221;high&#8221; bgcolor=&#8221;#FF6600&#8243; <span style="color: #ff0000;">width=&#8221;1360&#8243; height=&#8221;768&#8243;</span> name=&#8221;TwitterWidget&#8221; align=&#8221;middle&#8221; allowScriptAccess=&#8221;sameDomain&#8221; allowFullScreen=&#8221;true&#8221; type=&#8221;application/x-shockwave-flash&#8221; pluginspage=&#8221;http://www.macromedia.com/go/getflashplayer&#8221; FlashVars=&#8221;userID=16436568&amp;styleURL=http://static.twitter.com/flash/widgets/profile/velvetica.xml&#8221;/&gt;<br />
&lt;/object&gt;</p>
<p>Save your HTML file, making sure it has the proper .html file extension.</p>
<p><strong><em>Step 4: Import your HTML file into your Media Library in FireSign Studio</em></strong><br />
You may want to also create a separate Media group for HTML files, just to keep them organized.</p>
<p><strong><em>Step 5: Place the HTML file into a Segment</em></strong><br />
Create and edit a new Segment (or use an existing one) in FireSign Layout.</p>
<p>Place the HTML file into a Scene. Adjust the Scene duration to be 15 seconds or longer – long enough for someone to be able to read all the tweets on the page.</p>
<p>Resize the HTML file in the Scene so that it covers the entire display area.</p>
<p>Save your work, exit Layout, and go back to Studio.</p>
<p><strong><em>Step 6: Set the Segment to play</em></strong><br />
Either add the Segment to a Schedule, or assign it as an override to your Player for a quick check.</p>
<p>Now step back and admire your work!</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/06/02/displaying-the-twitter-widget-on-a-firesign-player/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kiski School Deploys FireSign for News Updates</title>
		<link>http://firesign.net/blog/2009/03/02/kiski-school-deploys-firesign-for-news-updates/</link>
		<comments>http://firesign.net/blog/2009/03/02/kiski-school-deploys-firesign-for-news-updates/#comments</comments>
		<pubDate>Mon, 02 Mar 2009 13:00:57 +0000</pubDate>
		<dc:creator>jpeden</dc:creator>
				<category><![CDATA[Recent News]]></category>

		<guid isPermaLink="false">http://firesign.net/blog/?p=109</guid>
		<description><![CDATA[Established in 1888, the Kiski School is one of the oldest all-boys college preparatory boarding schools in the United States. Kiski&#8217;s beautiful, 350-acre campus is located in Saltsburg, Pennsylvania, 30 miles east of Pittsburgh.  Kiski is a technology-leader among high schools, and FireSign continues that tradition by delivering important news and announcements to more [...]]]></description>
			<content:encoded><![CDATA[<p>Established in 1888, the <a href="http://www.kiski.org" target="_blank">Kiski School</a> is one of the oldest all-boys college preparatory boarding schools in the United States. Kiski&#8217;s beautiful, 350-acre campus is located in Saltsburg, Pennsylvania, 30 miles east of Pittsburgh.  Kiski is a technology-leader among high schools, and FireSign continues that tradition by delivering important news and announcements to more than 200 students.</p>
]]></content:encoded>
			<wfw:commentRss>http://firesign.net/blog/2009/03/02/kiski-school-deploys-firesign-for-news-updates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
