<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://experience.fellowshipone.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Intelligent Design : .NET MVC</title><link>http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/.NET+MVC/default.aspx</link><description>Tags &amp; Topics: .NET MVC</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61120.2)</generator><item><title>DC09 - DevCon Code, Slides, Videos</title><link>http://experience.fellowshipone.com/blogs/intelligentdesign/archive/2009/05/26/dc09-devcon-code.aspx</link><pubDate>Tue, 26 May 2009 04:50:00 GMT</pubDate><guid isPermaLink="false">87eee960-b871-44cb-8a98-02588a960c04:14412</guid><dc:creator>FTProductDev</dc:creator><slash:comments>2</slash:comments><comments>http://experience.fellowshipone.com/blogs/intelligentdesign/comments/14412.aspx</comments><wfw:commentRss>http://experience.fellowshipone.com/blogs/intelligentdesign/commentrss.aspx?PostID=14412</wfw:commentRss><description>&lt;p&gt;We have wrangled all of the devs and gathered all of the content that you saw at the DC09 DevCon.&amp;nbsp; Since we are community focused, we wanted you to have as much code and information that you'd need to get jump started for the RESTful API BETA so that you'll be able to discuss / communicate your ideas on consuming the REST API throughout the Social-Sphere.&amp;nbsp; We've got much more to come with the upcoming launch of our developer community site and the general release of the REST API.&amp;nbsp; Please take a moment to check out the goodies below - the whole dev team really "&lt;a href="http://dreams.honda.com/#/video_la"&gt;kicked out the ladder&lt;/a&gt;" so that we could give you real world, ministry focused code.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Application #1: &lt;/b&gt;F1Touch (Team Fire - iPhone) – &lt;a href="https://demo.staging.fellowshiponeapi.com/v1/Util/AuthDocs.help#1creds"&gt;1st Party&lt;/a&gt;&lt;br&gt;&lt;b&gt;Developers&lt;/b&gt;: &lt;a href="http://twitter.com/cmv"&gt;Matt Vasquez&lt;/a&gt;, &lt;a href="http://twitter.com/chadmeyer"&gt;Chad Meyer&lt;/a&gt;&lt;br&gt;&lt;b&gt;Description&lt;/b&gt;:&lt;br&gt;Our app is an iPhone application as a first party vendor open to all churches that opt in. Our application will provide the ability for church portal users to quickly look up congregants and contact them via phone or email as well as pull up Google maps to assist in directions to their house.&lt;br&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Content&lt;/b&gt;&lt;br&gt;&lt;a href="http://chadillac-meyer.blogspot.com/2009/05/consume-f1-api-for-iphone.html"&gt;Chad Meyer's blog post&lt;/a&gt; | &lt;a href="https://experience.fellowshipone.com:443/Developers/artifacts/DC09_iPhone_PDF.pdf"&gt;Slide Deck&lt;/a&gt; | &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/FTOAuth/ObjectiveC/"&gt;OAuth Lib&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;b&gt;Application #2&lt;/b&gt;: Outreach (Team Air - Facebook) – &lt;a href="https://demo.staging.fellowshiponeapi.com/v1/Util/AuthDocs.help#3oauth"&gt;3rd Party&lt;/a&gt; &lt;br&gt;&lt;b&gt;Developers&lt;/b&gt;: &lt;a href="http://twitter.com/ryanchamp_ice"&gt;Ryan Champ&lt;/a&gt;, &lt;a href="http://twitter.com/juskys"&gt;Jas Singh&lt;/a&gt;, &lt;a href="http://twitter.com/kleinke49"&gt;Kelly Klein&lt;/a&gt;&lt;br&gt;&lt;b&gt;Description&lt;/b&gt;:&lt;br&gt;Facebook is a social networking website with over 200 Million active users. How does the church engage, minister to, and help people through this social medium? Furthermore, is there a way to convert connections made in Facebook into potential church members? &lt;br&gt;&lt;br&gt;We tackle the problem with a prototype of application that functions with the overarching concept of “Virtual Outreach over Virtual Church.” Not only do we aim to build an ecology of people helping each other, but by reaching out to people and helping them deal with issues that affect their lives, church ministers and lay leadership can build “social capital” and trust in the digital world. This, in turn, will make their invitations to check out the church family much more appealing. Prospects, thus invited via the Outreach app, will then be routed directly into the church’s Fellowship One database.&lt;br&gt;&lt;br&gt;&lt;b&gt;Content&lt;/b&gt;&lt;br&gt;&lt;a href="http://www.vimeo.com/4840202"&gt;Video &lt;/a&gt;| &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/FTOutreach/trunk/Slides/"&gt;Slide deck&lt;/a&gt; | &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/FTOutreach/trunk/FTOutreach/"&gt;Code &lt;/a&gt;| &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/FTOAuth/PHP/"&gt;OAuth Lib&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;b&gt;Application #3&lt;/b&gt;: Listee (Team Earth – Expression Engine) – &lt;a href="https://demo.staging.fellowshiponeapi.com/v1/Util/AuthDocs.help#2creds"&gt;2nd Party&lt;/a&gt;&lt;br&gt;&lt;b&gt;Developers&lt;/b&gt;: &lt;a href="http://twitter.com/nathansmith"&gt;Nathan Smith&lt;/a&gt;, Jingyi Wang&lt;br&gt;&lt;b&gt;Description&lt;/b&gt;:&lt;br&gt;This module allows a web designer to easily include F1 data using the ExpressionEngine content management system. The benefit of this is that EE is a very popular CMS for high-end designers, because it's templating language is so intuitive.&lt;br&gt;&lt;br&gt;&lt;b&gt;Content&lt;/b&gt;&lt;br&gt;&lt;a href="http://www.vimeo.com/4639724"&gt;Video &lt;/a&gt;| &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/Listee/slides/"&gt;Slide deck&lt;/a&gt; | &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/Listee/"&gt;Code &lt;/a&gt;| &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/Listee/listee_v1.0/listee/f1_oauth.php"&gt;OAuth Lib&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;b&gt;Application #4&lt;/b&gt;: IWANTTOSERVE.COM (Team Water - .NET MVC) – 3rd Party&lt;br&gt;&lt;b&gt;Developers&lt;/b&gt;: &lt;a href="http://twitter.com/timhardy"&gt;Tim Hardy&lt;/a&gt;, Tudor Lupan&lt;br&gt;&lt;b&gt;Description&lt;/b&gt;:&lt;br&gt;We’ve developed a “Needs board” application that allows church members (anyone with a WebLink login) to post needs and search needs to minister to each other.&amp;nbsp; There is a tremendous need for a technical tool that can direct member’s willingness to serve to the valid needs of others.&amp;nbsp; While several tools have attempted to provide this functionality, none have taken advantage of the tried-and-true community self-monitoring patterns established by services such as ebay.&amp;nbsp; We’ve implemented a double opt-in system – the need submitter has to “Accept” a helper’s willingness to help, and the helper has to then “Commit”.&amp;nbsp; Both the submitter and the committed helpers can then rate each other to curb service abuses once the need has been met or the due date expired.&amp;nbsp; It completely leverages WebLink logins for authentication, and it contains a fully functional user profile editor &lt;br&gt;&lt;br&gt;&lt;b&gt;Content&lt;/b&gt;&lt;br&gt;&lt;a href="http://www.vimeo.com/4840294"&gt;Video &lt;/a&gt;| &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/iServe/Slides/"&gt;Slide deck&lt;/a&gt; | &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/iServe/"&gt;Code &lt;/a&gt;| &lt;a href="https://fellowshiptech.sourcerepo.com/fellowshiptech/FTOAuth/C%23/"&gt;OAuth Lib &lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.twitter.com/nickfloyd"&gt;Nick Floyd&lt;/a&gt; - Integration Architect&lt;br&gt;&lt;/p&gt;&lt;img src="http://experience.fellowshipone.com/aggbug.aspx?PostID=14412" width="1" height="1"&gt;</description><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/development/default.aspx">development</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/conference/default.aspx">conference</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/REST/default.aspx">REST</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/RESTful+API/default.aspx">RESTful API</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/OAuth/default.aspx">OAuth</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/DevCon/default.aspx">DevCon</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/Facebook/default.aspx">Facebook</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/DC09/default.aspx">DC09</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/ExpressionEngine/default.aspx">ExpressionEngine</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/iPhone/default.aspx">iPhone</category><category domain="http://experience.fellowshipone.com/blogs/intelligentdesign/archive/tags/.NET+MVC/default.aspx">.NET MVC</category></item></channel></rss>