<?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: Extracting the script behind addins in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/78580#M36472</link>
    <description>&lt;P&gt;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/2687"&gt;@txnelson&lt;/a&gt;,&amp;nbsp;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Is it possible to completely hide the script behind any addin except for the author&lt;/P&gt;</description>
    <pubDate>Wed, 10 Oct 2018 16:43:38 GMT</pubDate>
    <dc:creator>uday_guntupalli</dc:creator>
    <dc:date>2018-10-10T16:43:38Z</dc:date>
    <item>
      <title>Extracting the script behind addins</title>
      <link>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/53446#M30239</link>
      <description>&lt;P&gt;Is there any way I can extract the script behind add ins like the Table Attributes add in or Limits to data table add in?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Mar 2018 02:20:13 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/53446#M30239</guid>
      <dc:creator>Aam_jmp</dc:creator>
      <dc:date>2018-03-20T02:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Extracting the script behind addins</title>
      <link>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/53449#M30240</link>
      <description>&lt;P&gt;Addin have their JSL available in one of two structures.&amp;nbsp; And it turns out, the two Addins you referenced happen to cover both structures.&amp;nbsp; The JSL for the Table Attributes was saved as separate files for the Addin.&amp;nbsp; Because of that, you can go to the folder for the Addin and directly see the files.&amp;nbsp; To find the folder and to branch to it go to&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;View==&amp;gt;Addins&lt;/P&gt;
&lt;P&gt;It will popup a dialog box, where you can select the Addin you want, and then the selection will provide you with the folder(directory) the Addin is stored in.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The second Addin structure, has the JSL saved directly in the Addin menu definition.&amp;nbsp; To access this type of Addin, you will need to edit the .jmpaddin.&amp;nbsp; To access this file for the Limits to Data Table, you will need to save the Addin file to a local disk,&amp;nbsp; from the File Exchange, rather than just installing it.&amp;nbsp; Once it is saved, go to&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;File==&amp;gt;Open&lt;/P&gt;
&lt;P&gt;and navigate to the file you downloaded and saved.&amp;nbsp; Click on the file, and&amp;nbsp;then go to the down arrow next to the "Open" button and&amp;nbsp;select "Open using Add-in Builder".&amp;nbsp; Then click on OK.&amp;nbsp; The Add-in Builder will open the Addin and within the Menu item for the Addin, you will see the embedded JSL.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Mar 2018 03:54:07 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/53449#M30240</guid>
      <dc:creator>txnelson</dc:creator>
      <dc:date>2018-03-20T03:54:07Z</dc:date>
    </item>
    <item>
      <title>Re: Extracting the script behind addins</title>
      <link>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/78580#M36472</link>
      <description>&lt;P&gt;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/2687"&gt;@txnelson&lt;/a&gt;,&amp;nbsp;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Is it possible to completely hide the script behind any addin except for the author&lt;/P&gt;</description>
      <pubDate>Wed, 10 Oct 2018 16:43:38 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/78580#M36472</guid>
      <dc:creator>uday_guntupalli</dc:creator>
      <dc:date>2018-10-10T16:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: Extracting the script behind addins</title>
      <link>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/78680#M36503</link>
      <description>&lt;P&gt;The way you do this is to encrypt the script giving it a password that has to be specified for the user to view the source.&lt;/P&gt;
&lt;P&gt;See "Encrypt and Decript Scripts" in the Scripting Guide&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; Help==&amp;gt;Scripting Guide&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 02:05:44 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Extracting-the-script-behind-addins/m-p/78680#M36503</guid>
      <dc:creator>txnelson</dc:creator>
      <dc:date>2018-10-11T02:05:44Z</dc:date>
    </item>
  </channel>
</rss>

