"
Team:Wellesley Desyne/Tips Tricks
From 2013.igem.org
(Difference between revisions)
| (8 intermediate revisions not shown) | |||
| Line 13: | Line 13: | ||
<!-- Title Area --> | <!-- Title Area --> | ||
<li class="name"> | <li class="name"> | ||
| - | <h1><a href=" | + | <h1><a href="https://2013.igem.org/Team:Wellesley_Desyne">WHCI</a></h1> |
</li> | </li> | ||
<!-- Remove the class "menu-icon" to get rid of menu icon. Take out "Menu" to just have icon alone --> | <!-- Remove the class "menu-icon" to get rid of menu icon. Take out "Menu" to just have icon alone --> | ||
| Line 66: | Line 66: | ||
<div class="row"> | <div class="row"> | ||
<div class="large-12 columns"> | <div class="large-12 columns"> | ||
| - | + | <a href="https://2013.igem.org/Team:Wellesley_Desyne" class="header-link"><h2><img src="https://static.igem.org/mediawiki/2013/0/03/Wellesley_logo.png">Wellesley HCI iGEM 2013</h2></a> | |
</div> | </div> | ||
</div> | </div> | ||
| Line 79: | Line 79: | ||
<h3>Tips & Tricks</h3> | <h3>Tips & Tricks</h3> | ||
| - | <p>This section is intended to help future iGEM teams with | + | <p>This section is intended to help future iGEM teams or developers intending to work with the software and platforms we used over this summer. </p> |
<h4>Microsoft Surface Development</h4> | <h4>Microsoft Surface Development</h4> | ||
| Line 90: | Line 90: | ||
<a href="http://www.wpftutorial.net/">Another WPF tutorial</a> - A necessary model to understand in order to create rich and interesting user interfaces for the Surface, which is built on WPF. | <a href="http://www.wpftutorial.net/">Another WPF tutorial</a> - A necessary model to understand in order to create rich and interesting user interfaces for the Surface, which is built on WPF. | ||
<li> MVVM, based on the model-view-controller model, is another crucial model to understand. Also helpful for organizing the architecture of your code. <a href="http://blogs.msdn.com/b/erwinvandervalk/archive/2009/08/18/implementing-the-model-view-viewmodel-pattern.aspx">A brief overview of data MVVM can be found here.</a> | <li> MVVM, based on the model-view-controller model, is another crucial model to understand. Also helpful for organizing the architecture of your code. <a href="http://blogs.msdn.com/b/erwinvandervalk/archive/2009/08/18/implementing-the-model-view-viewmodel-pattern.aspx">A brief overview of data MVVM can be found here.</a> | ||
| - | <li><a href="http://stackoverflow.com/"> Stack Overflow</a> - A very helpful resource for debugging and understanding more about software development. In particular, <a href="http://stackoverflow.com/questions/129772/how-to-begin-wpf-development">this</a> Stack Overflow page is useful for tips on starting WPF development. | + | <li><a href="http://stackoverflow.com/"> Stack Overflow</a> - A very helpful resource for debugging and understanding more about software development. In particular, <a href="http://stackoverflow.com/questions/129772/how-to-begin-wpf-development">this</a> Stack Overflow page is useful for tips on starting WPF development.</li> |
| - | The <a href="http://msdn.microsoft.com/en-us/vstudio/hh341490.aspx, http://msdn.microsoft.com/en-us/library/vstudio/67ef8sbd.aspx">basics of programming in C#</a> ,whether you need to learn or just brush up.</li> | + | <li>The <a href="http://msdn.microsoft.com/en-us/vstudio/hh341490.aspx, http://msdn.microsoft.com/en-us/library/vstudio/67ef8sbd.aspx">basics of programming in C#</a> ,whether you need to learn or just brush up.</li> |
<li> In the process of building your application, you’ll most likely need to pull information from the <a href=" http://parts.igem.org/Registry_API?title=Registry_API"> iGEM registry</a> for specific parts. Make use of the Registry API, which allows you to extract information about a particular part efficiently. | <li> In the process of building your application, you’ll most likely need to pull information from the <a href=" http://parts.igem.org/Registry_API?title=Registry_API"> iGEM registry</a> for specific parts. Make use of the Registry API, which allows you to extract information about a particular part efficiently. | ||
</ul> | </ul> | ||
| Line 105: | Line 105: | ||
<h4>Web Development</h4> | <h4>Web Development</h4> | ||
<ul class="list_default"> | <ul class="list_default"> | ||
| - | <li> <a href = "http://www.w3schools.com">W3 Schools </a> - | + | <li> <a href = "http://www.w3schools.com">W3 Schools </a> -A helpful resource for HTML, CSS and JavaScript</li> |
<li><a href = "http://www.hongkiat.com/blog/48-excellent-html5-demos">HTML5 animation demos</a></li> | <li><a href = "http://www.hongkiat.com/blog/48-excellent-html5-demos">HTML5 animation demos</a></li> | ||
| - | <li><a href = "https://dev.twitter.com">Twitter API</a> which we used to retrieve tweets</li> | + | <li>The <a href = "https://dev.twitter.com" >Twitter API</a>, which we used to retrieve tweets</li> |
<li> <a href = "https://developers.google.com/appengine/">Google App Engine</a> for our javascript framework</li> | <li> <a href = "https://developers.google.com/appengine/">Google App Engine</a> for our javascript framework</li> | ||
</ul> | </ul> | ||
| Line 120: | Line 120: | ||
<script src="http://eastmaninteractive.com/igem/whci_zepto.js"></script> | <script src="http://eastmaninteractive.com/igem/whci_zepto.js"></script> | ||
<script src="http://eastmaninteractive.com/igem/whci_foundation.js"></script> | <script src="http://eastmaninteractive.com/igem/whci_foundation.js"></script> | ||
| - | |||
<script src="http://eastmaninteractive.com/igem/whci_foundation.dropdown.js"></script> | <script src="http://eastmaninteractive.com/igem/whci_foundation.dropdown.js"></script> | ||
| - | |||
| - | |||
<script src="http://eastmaninteractive.com/igem/whci_foundation.topbar.js"></script> | <script src="http://eastmaninteractive.com/igem/whci_foundation.topbar.js"></script> | ||
| + | |||
<script> | <script> | ||
$(document).foundation(); | $(document).foundation(); | ||
Latest revision as of 15:28, 27 September 2013
Wellesley HCI iGEM 2013Tips & Tricks
This section is intended to help future iGEM teams or developers intending to work with the software and platforms we used over this summer.
Microsoft Surface Development
- Microsoft's intro to Surface development
- Intro to building a multi touch application
- CodePlex - allows you to see open source projects and download open source software.
- Intro to WPF, Another WPF tutorial - A necessary model to understand in order to create rich and interesting user interfaces for the Surface, which is built on WPF.
- MVVM, based on the model-view-controller model, is another crucial model to understand. Also helpful for organizing the architecture of your code. A brief overview of data MVVM can be found here.
- Stack Overflow - A very helpful resource for debugging and understanding more about software development. In particular, this Stack Overflow page is useful for tips on starting WPF development.
- The basics of programming in C# ,whether you need to learn or just brush up.
- In the process of building your application, you’ll most likely need to pull information from the iGEM registry for specific parts. Make use of the Registry API, which allows you to extract information about a particular part efficiently.
Z Space
- Unity3D
- Google helps with developing in Unity
- The zSpace forums are helpful when getting started and developing for zSpace..
- Cassie created a post on the zSpace forum which highlights what she learned from Unity and zSpace development over the summer.
Web Development
- W3 Schools -A helpful resource for HTML, CSS and JavaScript
- HTML5 animation demos
- The Twitter API, which we used to retrieve tweets
- Google App Engine for our javascript framework
