http://mayhem.codeplex.com/Mayhem Wiki Rss Descriptionhttps://mayhem.codeplex.com/documentation?version=19<div class="wikidoc"><h1>Mayhem Tutorials</h1> <ul><li><a href="https://mayhem.codeplex.com/wikipage?title=Setting%20Up%20Visual%20Studio%20To%20Write%20Modules&referringTitle=Documentation">Setting Up Visual Studio To Write Modules</a></li> <li><a href="https://mayhem.codeplex.com/wikipage?title=Creating%20a%20Reaction&referringTitle=Documentation">Creating a Reaction</a></li> <li><a href="https://mayhem.codeplex.com/wikipage?title=Creating%20an%20Event&referringTitle=Documentation">Creating an Event</a></li> <li><a href="https://mayhem.codeplex.com/wikipage?title=Debugging%20your%20module&referringTitle=Documentation">Debugging your module</a> </li> <li><a href="http://channel9.msdn.com/coding4fun/articles/Making-Mayhem-with-Volume-Control">Creating a Volume Control Reaction</a> (With code)</li></ul> <h1>API Reference</h1> <ul><li><a href="https://mayhem.codeplex.com/wikipage?title=Event%20API&referringTitle=Documentation">Event API</a></li> <li><a href="https://mayhem.codeplex.com/wikipage?title=Reaction%20API&referringTitle=Documentation">Reaction API</a></li></ul> <h1>Useful Articles</h1> <ul><li><a href="http://eli-white.com/2012/03/why-is-mayhem-so-basic-why-cant-we-make-it-more-complicated/">Why is Mayhem so simple? (Can&#39;t pass data or have loops)</a></li></ul> <h1>Project Information</h1> <ul><li><a href="https://mayhem.codeplex.com/wikipage?title=Testing%20Requirements&referringTitle=Documentation">Testing Requirements</a></li> <li><a href="https://mayhem.codeplex.com/wikipage?title=List%20of%20Mayhem%20Keywords&referringTitle=Documentation">List of Mayhem Keywords</a></li> <li><a href="https://mayhem.codeplex.com/wikipage?title=Stats%2010%2f26%2f11&referringTitle=Documentation">Stats 10&#47;26&#47;11</a> -- repository statistics</li></ul> <h1>Pages we Need</h1> Who is Mayhem For</div><div class="ClearBoth"></div>TheSaviorMon, 15 Apr 2013 00:01:45 GMTUpdated Wiki: Documentation 20130415120145Ahttp://mayhem.codeplex.com/documentation?&ANCHOR#C25427I have the exact same question. Once the Mayhem application has been installed and the user downloads and unzip&#39;s the add-on&#39;s How does one install or have them applied to the Mayhem application&#63;TekenWed, 31 Oct 2012 17:44:08 GMTNew Comment on "Documentation" 20121031054408Phttp://mayhem.codeplex.com/wikipage?title=Creating a Reaction&ANCHOR#C24011I get a message, that the resource ConfigLabel could not be resolved. Where is it located&#63;ChrisK91Sat, 09 Jun 2012 16:00:49 GMTNew Comment on "Creating a Reaction" 20120609040049Phttp://mayhem.codeplex.com/documentation?&ANCHOR#C24005Really unfortunate that when you download an add-on module in Firefox the default application to open it is the Windows compressed folder zip utility. You have to save the download as a file and then open it to get it to install.arrichSat, 09 Jun 2012 00:28:14 GMTNew Comment on "Documentation" 20120609122814Ahttp://mayhem.codeplex.com/documentation?version=18<div class="wikidoc"><h1>Mayhem Tutorials</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Setting%20Up%20Visual%20Studio%20To%20Write%20Modules&referringTitle=Documentation">Setting Up Visual Studio To Write Modules</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20a%20Reaction&referringTitle=Documentation">Creating a Reaction</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20an%20Event&referringTitle=Documentation">Creating an Event</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Debugging%20your%20module&referringTitle=Documentation">Debugging your module</a> </li> <li><a href="http://channel9.msdn.com/coding4fun/articles/Making-Mayhem-with-Volume-Control">Creating a Volume Control Reaction</a> (With code)</li></ul> <h1>API Reference</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Event%20API&referringTitle=Documentation">Event API</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Reaction%20API&referringTitle=Documentation">Reaction API</a></li></ul> <h1>Useful Articles</h1> <ul><li><a href="http://eli-white.com/archives/74">Why is Mayhem so simple? (Can&#39;t pass data or have loops)</a></li></ul> <h1>Project Information</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Testing%20Requirements&referringTitle=Documentation">Testing Requirements</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=List%20of%20Mayhem%20Keywords&referringTitle=Documentation">List of Mayhem Keywords</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Stats%2010%2f26%2f11&referringTitle=Documentation">Stats 10&#47;26&#47;11</a> -- repository statistics</li></ul> <h1>Pages we Need</h1> Who is Mayhem For</div><div class="ClearBoth"></div>TheSaviorThu, 07 Jun 2012 22:20:57 GMTUpdated Wiki: Documentation 20120607102057Phttp://mayhem.codeplex.com/documentation?version=17<div class="wikidoc"><h1>Mayhem Tutorials</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Setting%20Up%20Visual%20Studio%20To%20Write%20Modules&referringTitle=Documentation">Setting Up Visual Studio To Write Modules</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20a%20Reaction&referringTitle=Documentation">Creating a Reaction</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20an%20Event&referringTitle=Documentation">Creating an Event</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Debugging%20your%20module&referringTitle=Documentation">Debugging your module</a> </li> <li><a href="http://channel9.msdn.com/coding4fun/articles/Making-Mayhem-with-Volume-Control">http://channel9.msdn.com/coding4fun/articles/Making-Mayhem-with-Volume-Control</a>Creating a Volume Control Reaction<a href="http://mayhem.codeplex.com/wikipage?title=%2furl&referringTitle=Documentation">&#47;url</a> (With code)</li></ul> <h1>API Reference</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Event%20API&referringTitle=Documentation">Event API</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Reaction%20API&referringTitle=Documentation">Reaction API</a></li></ul> <h1>Useful Articles</h1> <ul><li><a href="http://eli-white.com/archives/74">Why is Mayhem so simple? (Can&#39;t pass data or have loops)</a></li></ul> <h1>Project Information</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Testing%20Requirements&referringTitle=Documentation">Testing Requirements</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=List%20of%20Mayhem%20Keywords&referringTitle=Documentation">List of Mayhem Keywords</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Stats%2010%2f26%2f11&referringTitle=Documentation">Stats 10&#47;26&#47;11</a> -- repository statistics</li></ul> <h1>Pages we Need</h1> Who is Mayhem For</div><div class="ClearBoth"></div>TheSaviorThu, 07 Jun 2012 22:20:23 GMTUpdated Wiki: Documentation 20120607102023Phttp://mayhem.codeplex.com/documentation?version=16<div class="wikidoc"><h1>Mayhem Tutorials</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Setting%20Up%20Visual%20Studio%20To%20Write%20Modules&referringTitle=Documentation">Setting Up Visual Studio To Write Modules</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20a%20Reaction&referringTitle=Documentation">Creating a Reaction</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20an%20Event&referringTitle=Documentation">Creating an Event</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Debugging%20your%20module&referringTitle=Documentation">Debugging your module</a> </li></ul> <h1>API Reference</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Event%20API&referringTitle=Documentation">Event API</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Reaction%20API&referringTitle=Documentation">Reaction API</a></li></ul> <h1>Useful Articles</h1> <ul><li><a href="http://eli-white.com/archives/74">Why is Mayhem so simple? (Can&#39;t pass data or have loops)</a></li></ul> <h1>Project Information</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Testing%20Requirements&referringTitle=Documentation">Testing Requirements</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=List%20of%20Mayhem%20Keywords&referringTitle=Documentation">List of Mayhem Keywords</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Stats%2010%2f26%2f11&referringTitle=Documentation">Stats 10&#47;26&#47;11</a> -- repository statistics</li></ul> <h1>Pages we Need</h1> Who is Mayhem For</div><div class="ClearBoth"></div>TheSaviorMon, 14 May 2012 21:01:26 GMTUpdated Wiki: Documentation 20120514090126Phttp://mayhem.codeplex.com/wikipage?title=Testing Requirements&version=5<div class="wikidoc"> <p>This page is designed to help you know what we look for when we are testing a module for usability as well as functionality.</p> <ul> <li>When clicking on the module in one of the module lists, the configuration window should open up right away. Do all of your start-up in a background thread </li><li>Your module should never cause a crash in the application </li><li>Blatant spelling mistakes </li><li>Save is disabled when not all of the settings are specified or settings are incorrect </li><li>Consistency between module names and other terminology in the event/reaction lists, configuration windows and display panel </li><li>Clear and concise error messages printed to Mayhem's error log when a user tries to do something that is not allowed (e.g. turning on a connection that uses a module that requires an internet connection when no internet connection is present) or when something has gone awry (e.g. a connection that opens a program from a specific location is turned on or triggered and then notices that said program cannot be found [an error regarding that situation should be printed to the error log]) </li><li>Configuration windows should not be able to pass the edge of a user's screen </li><li>Appropriate, reliable and timely responses for all modules </li><li>Settings and connection state for all modules should be saved when Mayhem is closed and reopened (possible exception is passwords or other private data. These should not&nbsp;be saved in plain text form)&nbsp; </li><li>Module descriptions should be as detailed and user-friendly as possible (i.e. contain little-to-no jargon) </li><li>Module titles and descriptions should remain consistent with preexisting Mayhem module formats and tense </li><li>If module is configurable, make sure that every option in the configuration window is clearly labeled and explained (if necessary) </li><li>Do not allow for contradiction or confusion in configuration windows (e.g. do not use checkboxes where radio buttons would be more appropriate for the module's functionality) </li></ul> </div><div class="ClearBoth"></div>TheSaviorMon, 14 May 2012 21:00:34 GMTUpdated Wiki: Testing Requirements 20120514090034Phttp://mayhem.codeplex.com/wikipage?title=Testing Requirements&version=4<div class="wikidoc"> <p>This page is designed to help you know what we look for when we are testing a module for usability as well as functionality.</p> <ul> <li>When clicking on the module in one of the module lists, the configuration window should open up right away. Do all of your start-up in a background thread </li><li>Your module should never cause a crash in the application </li><li>Blatant spelling mistakes </li><li>Save is disabled when not all of the settings are specified </li><li>Consistency between module names and other terminology in the event/reaction lists, configuration windows and display panel </li><li>Clear and concise error messages printed to Mayhem's error log when a user tries to do something that is not allowed (e.g. turning on a connection that uses a module that requires an internet connection when no internet connection is present) or when something has gone awry (e.g. a connection that opens a program from a specific location is turned on or triggered and then notices that said program cannot be found [an error regarding that situation should be printed to the error log]) </li><li>Configuration windows should not be able to pass the edge of a user's screen </li><li>Appropriate, reliable and timely responses for all modules </li><li>Settings and connection state for all modules should be saved when Mayhem is closed and reopened </li><li>Module descriptions should be as detailed and user-friendly as possible (i.e. contain little-to-no jargon) </li><li>Module titles and descriptions should remain consistent with preexisting Mayhem module formats and tense </li><li>If module is configurable, make sure that every option in the configuration window is clearly labeled and explained (if necessary) </li><li>Do not allow for contradiction or confusion in configuration windows (e.g. do not use checkboxes where radio buttons would be more appropriate for the module's functionality) </li></ul> </div><div class="ClearBoth"></div>erikm1Mon, 14 May 2012 20:51:22 GMTUpdated Wiki: Testing Requirements 20120514085122Phttp://mayhem.codeplex.com/wikipage?title=Testing Requirements&version=3<div class="wikidoc"> <p>This page is designed to help you know what we look for when we are testing a module for usability as well as functionality.</p> <ul> <li>When clicking on the module in one of the module lists, the configuration window should open up right away. Do all of your start-up in a background thread </li><li>Your module should never cause a crash in the application </li><li>Blatant spelling mistakes </li><li>Save is disabled when not all of the settings are specified </li><li>Consistency between module names and other terminology in the event/reaction lists, configuration windows and display panel </li><li>Clear and concise error messages printed to Mayhem's error log when a user tries to do something that is not allowed (e.g. turning on a connection that uses a module that requires an internet connection when no internet connection is present) or when something has gone awry (e.g. a connection that opens a program from a specific location is turned on or triggered and then notices that said program cannot be found [an error regarding that situation should be printed to the error log]) </li><li>Configuration windows should not be able to pass the edge of a user's screen </li><li>Appropriate, reliable and timely responses for all modules </li><li>Settings and connection state for all modules should be saved when Mayhem is closed and reopened </li><li>Module descriptions should be as detailed and user-friendly as possible (contain little-to-no jargon) </li><li>Module titles and descriptions should remain consistent with preexisting Mayhem module formats and tense </li><li>If module is configurable, make sure that every option in the configuration window is clearly labeled and explained (if necessary) </li><li>Do not allow for contradiction or confusion in configuration windows (e.g. do not use checkboxes where radio buttons would be more appropriate for the module's functionality) </li></ul> </div><div class="ClearBoth"></div>erikm1Mon, 14 May 2012 20:49:06 GMTUpdated Wiki: Testing Requirements 20120514084906Phttp://mayhem.codeplex.com/wikipage?title=Testing Requirements&version=2<div class="wikidoc">This page is designed to help you know what we look for when we are testing a module for usability as well as functionality.<br /> <ul><li>When clicking on the module in one of the module lists, the configuration window should open up right away. Do all of your startup in a background thread.</li> <li>Your module should never cause a crash in the application</li> <li>Blatant spelling mistakes</li> <li>Save is disabled when not all of the settings are specified.</li></ul> *Consistency between module names and other terminology in the event/reaction lists, configuration windows and display panel<br />*Clear and concise error messages printed to Mayhem’s error log when a user tries to do something that is not allowed (i.e. turning on a connection that uses a module that requires an internet connection when no internet connection is present) or when something has gone awry (i.e. a connection that opens a program from a specific location is turned on or triggered and notices that said program cannot be found <a href="http://mayhem.codeplex.com/wikipage?title=this%20message%20should%20be%20printed%20to%20the%20error%20log&referringTitle=Testing%20Requirements">this message should be printed to the error log</a>) <br />*Configuration windows should not be able to pass the edge of a user’s screen<br />*Appropriate, reliable and timely response times for all modules<br />*Settings and connection state for all modules should be saved when Mayhem is closed and reopened<br />*Module descriptions should be descriptive and user-friendly (contain as little jargon as possible)<br />*Module titles and descriptions should remain consistent with pre-existing Mayhem module formats and tense<br />*If module is configurable, make sure that every option in the configuration window is clearly labeled and explained (if necessary)<br />*Do not allow for contradiction or confusion in configuration windows (i.e. do not use checkboxes where radio buttons would be more appropriate to allow for only one option to be selected)<br /></div><div class="ClearBoth"></div>erikm1Mon, 14 May 2012 20:42:15 GMTUpdated Wiki: Testing Requirements 20120514084215Phttp://mayhem.codeplex.com/wikipage?title=DISCUSSION BOARD&version=1<div class="wikidoc"><table><tr><th> Topic </th><th> Description </th></tr> <tr><td> Mayhem Phone </td><td> fill </td></tr> <tr><td> Events </td><td> fill </td></tr> <tr><td> Reactions </td><td> fill </td></tr></table></div><div class="ClearBoth"></div>WillBeebeFri, 11 May 2012 19:33:14 GMTUpdated Wiki: DISCUSSION BOARD 20120511073314Phttp://mayhem.codeplex.com/wikipage?title=Testing Requirements&version=1<div class="wikidoc">This page is designed to help you know what we look for when we are testing a module for usability as well as functionality.<br /> <ul><li>When clicking on the module in one of the module lists, the configuration window should open up right away. Do all of your startup in a background thread.</li> <li>Your module should never cause a crash in the application</li> <li>Blatant spelling mistakes</li> <li>Save is disabled when not all of the settings are specified.</li></ul> </div><div class="ClearBoth"></div>TheSaviorSun, 29 Apr 2012 17:40:27 GMTUpdated Wiki: Testing Requirements 20120429054027Phttp://mayhem.codeplex.com/documentation?version=15<div class="wikidoc"><h1>Mayhem Tutorials</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Setting%20Up%20Visual%20Studio%20To%20Write%20Modules&referringTitle=Documentation">Setting Up Visual Studio To Write Modules</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20a%20Reaction&referringTitle=Documentation">Creating a Reaction</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Creating%20an%20Event&referringTitle=Documentation">Creating an Event</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Debugging%20your%20module&referringTitle=Documentation">Debugging your module</a> </li></ul> <h1>API Reference</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=Event%20API&referringTitle=Documentation">Event API</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Reaction%20API&referringTitle=Documentation">Reaction API</a></li></ul> <h1>Useful Articles</h1> <ul><li><a href="http://eli-white.com/archives/74">Why is Mayhem so simple? (Can&#39;t pass data or have loops)</a></li></ul> <h1>Project Information</h1> <ul><li><a href="http://mayhem.codeplex.com/wikipage?title=List%20of%20Mayhem%20Keywords&referringTitle=Documentation">List of Mayhem Keywords</a></li> <li><a href="http://mayhem.codeplex.com/wikipage?title=Stats%2010%2f26%2f11&referringTitle=Documentation">Stats 10&#47;26&#47;11</a> -- repository statistics</li></ul> <h1>Pages we Need</h1> Who is Mayhem For</div><div class="ClearBoth"></div>TheSaviorWed, 04 Apr 2012 22:14:02 GMTUpdated Wiki: Documentation 20120404101402Phttp://mayhem.codeplex.com/wikipage?version=32<div class="wikidoc"> <h1 style="text-align:center; font-size:26pt; margin-bottom:-20px">WELCOME</h1> <p><img title="dev-prev.jpg" src="http://i3.codeplex.com/Download?ProjectName=mayhem&DownloadId=313334" alt="dev-prev.jpg" style="float:right; padding-left:.5em; margin-top:55px"></p> <div> <h2 style="margin-bottom:0px">Project Description</h2> <p style="text-align:justify; width:50%"><a href="http://makemayhem.com">Mayhem</a> is an open source application with a near-zero learning curve. Mayhem provides a collection of triggers events and reactions, allowing non-programmers to use their computers to automate&hellip; anything! What sort of things? Chase your cat off the couch automatically. Receive a text message when your physical mail arrives. Advance to the next slide in your presentation when you wave your hand. Update your Facebook status when the weather changes. The possibilities are endless.<br> <br> The key to Mayhem is that it only supports a single programming construct &ndash; when an event happens, do a reaction. This is what makes it so easy for everyone to understand. Mayhem can easily tie together disparate things such as home automation devices, social networking sites, media devices, messaging, office productivity tools, webcams, musical instruments, etc. Virtually anything that can produce or receive a trigger can be easily incorporated into the Mayhem framework.<br> <br> </p> </div> </div><div class="ClearBoth"></div>WillBeebeSat, 31 Mar 2012 01:10:54 GMTUpdated Wiki: Home 20120331011054Ahttp://mayhem.codeplex.com/wikipage?version=31<div class="wikidoc"> <h1 style="text-align:center; font-size:26pt; margin-bottom:-20px">WELCOME</h1> <p><img title="dev-prev.jpg" src="http://i3.codeplex.com/Download?ProjectName=mayhem&DownloadId=313334" alt="dev-prev.jpg" style="float:right; padding-left:.5em; margin-top:55px"></p> <div> <h2 style="margin-bottom:0px">Project Description</h2> <p style="text-align:justify; width:50%"><a href="http://makemayhem.com">Mayhem</a> is an open source application with a near-zero learning curve. Mayhem provides a collection of triggers events and reactions, allowing non-programmers to use their computers to automate&hellip; anything! What sort of things? Chase your cat off the couch automatically. Receive a text message when your physical mail arrives. Advance to the next slide in your presentation when you wave your hand. Update your Facebook status when the weather changes. The possibilities are endless.<br> <br> The key to Mayhem is that it only supports a single programming construct &ndash; when an event happens, do a reaction. This is what makes it so easy for everyone to understand. Mayhem can easily tie together disparate things such as home automation devices, social networking sites, media devices, messaging, office productivity tools, webcams, musical instruments, etc. Virtually anything that can produce or receive a trigger can be easily incorporated into the Mayhem framework.<br> <br> </p> </div> &lt;!-- <div> <h2 style="margin-bottom:0px">Contribute</h2> <p>Looking for ways to contribute to Mayhem? There are many ways that you can help make Mayhem even better. If you are a coder at heart we recommended that you take a look at these helpful resources for more information about getting started.</p> <ul> <li><a href="/wikipage?title=Setting%20Up%20Visual%20Studio%20To%20Write%20Modules&referringTitle=Documentation">Setting Up Visual Studio To Write Modules</a> </li><li><a href="/wikipage?title=Creating%20a%20Reaction&referringTitle=Documentation">Creating a Reaction</a> </li><li><a href="/wikipage?title=Creating%20an%20Event&referringTitle=Documentation">Creating an Event</a> </li><li><a href="/wikipage?title=Debugging%20your%20module&referringTitle=Documentation">Debugging your module</a> </li></ul> <p>However, if writing code isn&rsquo;t quite your style, but you lovvve to put an app to the test and can&rsquo;t stand when something breaks, then perhaps testing / debugging is more your flavor. For documentation on how to report bugs please see these pages.</p> </div> --&gt;</div><div class="ClearBoth"></div>WillBeebeSat, 31 Mar 2012 01:10:22 GMTUpdated Wiki: Home 20120331011022Ahttp://mayhem.codeplex.com/wikipage?version=30<div class="wikidoc"> <h1 style="text-align:center; font-size:26pt; margin-bottom:-20px">WELCOME</h1> <p><img title="dev-prev.jpg" src="http://i3.codeplex.com/Download?ProjectName=mayhem&DownloadId=313334" alt="dev-prev.jpg" style="float:right; padding-left:.5em; margin-top:55px"></p> <h2 style="margin-bottom:0px">Project Description</h2> <div> <p style="text-align:justify; width:50%"><a href="http://makemayhem.com">Mayhem</a> is an open source application with a near-zero learning curve. Mayhem provides a collection of triggers events and reactions, allowing non-programmers to use their computers to automate&hellip; anything! What sort of things? Chase your cat off the couch automatically. Receive a text message when your physical mail arrives. Advance to the next slide in your presentation when you wave your hand. Update your Facebook status when the weather changes. The possibilities are endless.<br> <br> The key to Mayhem is that it only supports a single programming construct &ndash; when an event happens, do a reaction. This is what makes it so easy for everyone to understand. Mayhem can easily tie together disparate things such as home automation devices, social networking sites, media devices, messaging, office productivity tools, webcams, musical instruments, etc. Virtually anything that can produce or receive a trigger can be easily incorporated into the Mayhem framework.<br> <br> </p> </div> <h2>Home Page</h2> <p><a href="http://makemayhem.com">http://makemayhem.com</a></p> </div><div class="ClearBoth"></div>WillBeebeSat, 31 Mar 2012 00:04:19 GMTUpdated Wiki: Home 20120331120419Ahttp://mayhem.codeplex.com/wikipage?version=29<div class="wikidoc"> <h1 style="text-align:center; font-size:26pt; margin-bottom:-10px">WELCOME</h1> <p><img title="dev-prev.jpg" src="http://i3.codeplex.com/Download?ProjectName=mayhem&DownloadId=313334" alt="dev-prev.jpg" style="float:right; padding-left:.5em; margin-top:45px"></p> <h2 style="margin-bottom:0px">Project Description</h2> <div> <p style="text-align:justify; width:50%"><a href="http://makemayhem.com">Mayhem</a> is an open source application with a near-zero learning curve. Mayhem provides a collection of triggers events and reactions, allowing non-programmers to use their computers to automate&hellip; anything! What sort of things? Chase your cat off the couch automatically. Receive a text message when your physical mail arrives. Advance to the next slide in your presentation when you wave your hand. Update your Facebook status when the weather changes. The possibilities are endless.<br> <br> The key to Mayhem is that it only supports a single programming construct &ndash; when an event happens, do a reaction. This is what makes it so easy for everyone to understand. Mayhem can easily tie together disparate things such as home automation devices, social networking sites, media devices, messaging, office productivity tools, webcams, musical instruments, etc. Virtually anything that can produce or receive a trigger can be easily incorporated into the Mayhem framework.<br> <br> </p> </div> <h2>Home Page</h2> <p><a href="http://makemayhem.com">http://makemayhem.com</a></p> </div><div class="ClearBoth"></div>WillBeebeFri, 30 Mar 2012 23:51:52 GMTUpdated Wiki: Home 20120330115152Phttp://mayhem.codeplex.com/wikipage?version=28<div class="wikidoc"> <h1 style="text-align:center; font-size:larger">WELCOME</h1> <p><img title="dev-prev.jpg" src="http://i3.codeplex.com/Download?ProjectName=mayhem&DownloadId=313334" alt="dev-prev.jpg" style="float:right; padding-left:.5em; margin-top:55px"></p> <h1 style="margin-bottom:0px">Project Description</h1> <div> <p style="text-align:justify; width:50%"><a href="http://makemayhem.com">Mayhem</a> is an open source application with a near-zero learning curve. Mayhem provides a collection of triggers events and reactions, allowing non-programmers to use their computers to automate&hellip; anything! What sort of things? Chase your cat off the couch automatically. Receive a text message when your physical mail arrives. Advance to the next slide in your presentation when you wave your hand. Update your Facebook status when the weather changes. The possibilities are endless.<br> <br> The key to Mayhem is that it only supports a single programming construct &ndash; when an event happens, do a reaction. This is what makes it so easy for everyone to understand. Mayhem can easily tie together disparate things such as home automation devices, social networking sites, media devices, messaging, office productivity tools, webcams, musical instruments, etc. Virtually anything that can produce or receive a trigger can be easily incorporated into the Mayhem framework.<br> <br> </p> </div> <h1>Home Page</h1> <p><a href="http://makemayhem.com">http://makemayhem.com</a></p> </div><div class="ClearBoth"></div>WillBeebeFri, 30 Mar 2012 23:50:02 GMTUpdated Wiki: Home 20120330115002Phttp://mayhem.codeplex.com/wikipage?version=27<div class="wikidoc"> <h1 style="text-align:center; font-size:larger">WELCOME</h1> <p><img title="dev-prev.jpg" src="http://i3.codeplex.com/Download?ProjectName=mayhem&DownloadId=313334" alt="dev-prev.jpg" style="float:right; padding-left:.5em"></p> <h1 style="margin-bottom:0px">Project Description</h1> <p style=""><a href="http://makemayhem.com">Mayhem</a> is an open source application with a near-zero learning curve. Mayhem provides a collection of triggers events and reactions, allowing non-programmers to use their computers to automate&hellip; anything! What sort of things? Chase your cat off the couch automatically. Receive a text message when your physical mail arrives. Advance to the next slide in your presentation when you wave your hand. Update your Facebook status when the weather changes. The possibilities are endless.<br> <br> The key to Mayhem is that it only supports a single programming construct &ndash; when an event happens, do a reaction. This is what makes it so easy for everyone to understand. Mayhem can easily tie together disparate things such as home automation devices, social networking sites, media devices, messaging, office productivity tools, webcams, musical instruments, etc. Virtually anything that can produce or receive a trigger can be easily incorporated into the Mayhem framework.<br> <br> </p> <h1>Home Page</h1> <p><a href="http://makemayhem.com">http://makemayhem.com</a></p> </div><div class="ClearBoth"></div>WillBeebeFri, 30 Mar 2012 23:30:17 GMTUpdated Wiki: Home 20120330113017P