As the VP of Development for SoftArtisans, Sam Haddad leads a team of developers to bring enterprise software to a global customer base. With a degree in Information Technology from Rochester Institute of Technology, Sam’s expertise lies in .NET programming. In the past Sam has worked with both web and desktop applications, ranging from e-commerce sites to Office document processing tools.
In this conversation, Sam discusses PowerPointWriter.
Geetesh: What is PowerPointWriter? Is it a desktop application or is it a code-driven program.
Sam: In its simplest form, PowerPointWriter is a tool that allows you to take data from any data source and integrate it with your PowerPoint files. PowerPointWriter is a .NET library and API. With a little bit of code, it allows you to dynamically populate PowerPoint presentations on the fly from your own applications. You design the presentation in PowerPoint, and then merge data using the PowerPointTemplate object, just like using Word’s mail merge. PowerPointTemplate lets you do a Word mail merge type of behavior without the need to actually have Microsoft Office on your server. Microsoft recommends avoiding automating Office on the server, so this is a great alternative. Since we are designed to run on servers you get great performance and stability.
To help customers gain a better understanding of what this all means, we put together a quick video overview of the product and what it does.
Geetesh: What motivated you to create this product?
Sam: A lot of our customers have their data in several different data sources, such as SQL and Oracle databases, Office Documents, and other existing applications. We wanted to provide an easy way for them to export their data into PowerPoint.
We were currently doing this with our ExcelWriter and WordWriter tools, and so brought that same technology to PowerPoint. We focused on bringing our template model to PowerPoint because that meant customers could get their reports up and running with as little as 5 lines of code. This means less coding and development time, less maintenance of the code, and more time designing your report in an application with which you are already familiar, such as Excel, Word, or in this case PowerPoint.
Overall the final process looks like this:
Geetesh: What's the profile of a typical PowerPointWriter user? And is there a learning curve?
Sam: PowerPointWriter users are typically those who need to make data-driven PowerPoints on a consistent basis. For instance, say you have a client presentation and need to update your slide deck with the most current numbers from the database minutes before the meeting. PowerPointWriter will provide that capability without much time or effort involved. Often those that use this product are sales representatives, financial analysts, project managers, and any professional who needs a great visual display of data. The best part is the learning curve is short as there are only a few concepts you would need to learn in order to start producing numbers-focused slide decks.
Categories: interviews, powerpoint
April 2003 | May 2003 | December 2003 | January 2004 | February 2004 | March 2004 | April 2004 | May 2004 | June 2004 | July 2004 | August 2004 | September 2004 | October 2004 | November 2004 | December 2004 | January 2005 | February 2005 | March 2005 | April 2005 | May 2005 | June 2005 | July 2005 | August 2005 | September 2005 | October 2005 | November 2005 | December 2005 | January 2006 | February 2006 | March 2006 | April 2006 | May 2006 | June 2006 | July 2006 | August 2006 | September 2006 | October 2006 | November 2006 | December 2006 | January 2007 | February 2007 | March 2007 | April 2007 | May 2007 | June 2007 | July 2007 | August 2007 | September 2007 | October 2007 | November 2007 | December 2007 | January 2008 | February 2008 | March 2008 | April 2008 | May 2008 | June 2008 | July 2008 | August 2008 | September 2008 | October 2008 | November 2008 | December 2008 | January 2009 | February 2009 | March 2009 | April 2009 | May 2009 | June 2009 | July 2009 | August 2009 | September 2009 | October 2009 | November 2009 | December 2009 | January 2010 | February 2010 | March 2010 | April 2010 | May 2010 | June 2010 | July 2010 | August 2010 | September 2010 | October 2010 | November 2010 | December 2010 | January 2011 | February 2011 | March 2011 | April 2011 | May 2011 | June 2011 | July 2011 | August 2011 | September 2011 | October 2011 | November 2011 | December 2011 | January 2012 | February 2012 | March 2012 | April 2012 | May 2012 | June 2012 | July 2012 | August 2012 | September 2012 | October 2012 | November 2012 | December 2012 | January 2013 | February 2013 | March 2013 | April 2013 | May 2013 | June 2013 | July 2013 | August 2013 | September 2013 | October 2013 | November 2013 | December 2013 | January 2014 | February 2014 | March 2014 | April 2014 | May 2014 | June 2014 | July 2014 | August 2014 | September 2014 | October 2014 | November 2014 | December 2014 | January 2015 | February 2015 | March 2015 | April 2015 | May 2015 | June 2015 | July 2015 | August 2015 | September 2015 | October 2015 | November 2015 | December 2015 | January 2016 | February 2016 | March 2016 | April 2016 | May 2016 | June 2016 | July 2016 | August 2016 | September 2016 | October 2016 | November 2016 | December 2016 | January 2017 | February 2017 |
Microsoft and the Office logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.