<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Remote control for Autodesk Fusion 360 in Fusion API and Scripts Forum</title>
    <link>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6985077#M18379</link>
    <description>&lt;P&gt;Nice! I've&amp;nbsp;been working on a &lt;A href="https://github.com/studioFATHOM/limbforge" target="_self"&gt;remote control app&lt;/A&gt; for Fusion360 as well. Right now, the project is single-purpose - it generates STLs from a parametric design over a REST interface. My app&amp;nbsp;also using sockets to drive Fusion remotely, but&amp;nbsp;my approach to the client was different.&amp;nbsp;Rather than a small static plugin that handles the messaging between Fusion and the server, I&amp;nbsp;use a html client side redirect so&amp;nbsp;Fusion360 downloads the plugin from the web. It's a lot heavier than&amp;nbsp;your approach - the whole plugin is ~5MB minified and has to be downloaded every time the&amp;nbsp;plugin is started up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As soon as I wrap up the single-purpose app (hopefully in the next week), I'm planning on building&amp;nbsp;a general remote control&amp;nbsp;framework for Fusion. I'm planning on making it open-source (probably Apache).&lt;/P&gt;</description>
    <pubDate>Thu, 30 Mar 2017 16:24:49 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-03-30T16:24:49Z</dc:date>
    <item>
      <title>Remote control for Autodesk Fusion 360</title>
      <link>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6980803#M18378</link>
      <description>&lt;P&gt;Remote control for Autodesk Fusion 360.&lt;/P&gt;
&lt;P&gt;Allows to interact with Viewer using Natural Language or Speech Recognition interfaces to perform conversation in chat-like mode.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Feel free to check it on GitHub repository: &lt;A href="https://github.com/naturalDesign/fusion-remote" target="_blank"&gt;fusion-remote&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2017 09:49:50 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6980803#M18378</guid>
      <dc:creator>MiWaNiZa</dc:creator>
      <dc:date>2017-03-29T09:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Remote control for Autodesk Fusion 360</title>
      <link>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6985077#M18379</link>
      <description>&lt;P&gt;Nice! I've&amp;nbsp;been working on a &lt;A href="https://github.com/studioFATHOM/limbforge" target="_self"&gt;remote control app&lt;/A&gt; for Fusion360 as well. Right now, the project is single-purpose - it generates STLs from a parametric design over a REST interface. My app&amp;nbsp;also using sockets to drive Fusion remotely, but&amp;nbsp;my approach to the client was different.&amp;nbsp;Rather than a small static plugin that handles the messaging between Fusion and the server, I&amp;nbsp;use a html client side redirect so&amp;nbsp;Fusion360 downloads the plugin from the web. It's a lot heavier than&amp;nbsp;your approach - the whole plugin is ~5MB minified and has to be downloaded every time the&amp;nbsp;plugin is started up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As soon as I wrap up the single-purpose app (hopefully in the next week), I'm planning on building&amp;nbsp;a general remote control&amp;nbsp;framework for Fusion. I'm planning on making it open-source (probably Apache).&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 16:24:49 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6985077#M18379</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-30T16:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: Remote control for Autodesk Fusion 360</title>
      <link>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6985745#M18380</link>
      <description>&lt;P&gt;Thanks a lot for your response. Actually I was inspired by&amp;nbsp;&lt;A href="https://forge.autodesk.com/author/xiaodong-liang" target="_blank"&gt;Xiaodong Liang&lt;/A&gt;'s &lt;A href="https://forge.autodesk.com/cloud_and_mobile/2016/03/practise-with-fusion-360-and-socketio-javascript-api.html" target="_self"&gt;Practise with Fusion 360 and Socket.IO – JavaScript API&lt;/A&gt;. This project really helped.&lt;/P&gt;
&lt;P&gt;And yes - I decided to shift an accent of solution to the server side.&lt;/P&gt;
&lt;P&gt;Good luck with your project! It's very nice.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 20:32:10 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6985745#M18380</guid>
      <dc:creator>MiWaNiZa</dc:creator>
      <dc:date>2017-03-30T20:32:10Z</dc:date>
    </item>
    <item>
      <title>Re: Remote control for Autodesk Fusion 360</title>
      <link>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6997615#M18381</link>
      <description>&lt;P&gt;Hi Dmytro,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the link to the blog - I hadn't seen that post (or even the entire blog) before! So many blogs, so little time...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Carlo&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2017 15:26:09 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-api-and-scripts-forum/remote-control-for-autodesk-fusion-360/m-p/6997615#M18381</guid>
      <dc:creator>carloquinonez</dc:creator>
      <dc:date>2017-04-05T15:26:09Z</dc:date>
    </item>
  </channel>
</rss>

