<?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 Can we freely modify client.js without legal concerns? in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Can-we-freely-modify-client-js-without-legal-concerns/m-p/1240059#M24586</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Posts like &lt;A href="http://https//community.qlik.com/blogs/qlikviewdesignblog/2016/12/09/themes-in-qlik-sense-3-and-the-use-in-extensions#comment-54660"&gt;this one &lt;/A&gt;give us workarounds (I know they're "hacky", I know they're temporary, but... they work!).&lt;/P&gt;&lt;P&gt;That post in particular tells us we must modify client.js -- the main entry point for Qlik Sense apps! -- (you must be careful if client.js is minified, but it can be done!)&lt;/P&gt;&lt;P&gt;So there are technical reasons to be careful (minification, etc), and common-sense reasons (don't change the core client.js code since a Qlik Sense update will ignore our change.), &lt;STRONG&gt;but are there legal reasons?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any legal reasons that restrict our usage to edit client.js?&lt;/P&gt;&lt;P&gt;Can we modify our own cleint.js? Can we advise clients to modify client.js, if they accept the above risks/considerations? Will any EULA or terms&amp;amp;conditions prevent us from modifying, or advising to modify? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Feb 2017 02:07:28 GMT</pubDate>
    <dc:creator />
    <dc:date>2017-02-09T02:07:28Z</dc:date>
    <item>
      <title>Can we freely modify client.js without legal concerns?</title>
      <link>https://community.qlik.com/t5/App-Development/Can-we-freely-modify-client-js-without-legal-concerns/m-p/1240059#M24586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Posts like &lt;A href="http://https//community.qlik.com/blogs/qlikviewdesignblog/2016/12/09/themes-in-qlik-sense-3-and-the-use-in-extensions#comment-54660"&gt;this one &lt;/A&gt;give us workarounds (I know they're "hacky", I know they're temporary, but... they work!).&lt;/P&gt;&lt;P&gt;That post in particular tells us we must modify client.js -- the main entry point for Qlik Sense apps! -- (you must be careful if client.js is minified, but it can be done!)&lt;/P&gt;&lt;P&gt;So there are technical reasons to be careful (minification, etc), and common-sense reasons (don't change the core client.js code since a Qlik Sense update will ignore our change.), &lt;STRONG&gt;but are there legal reasons?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any legal reasons that restrict our usage to edit client.js?&lt;/P&gt;&lt;P&gt;Can we modify our own cleint.js? Can we advise clients to modify client.js, if they accept the above risks/considerations? Will any EULA or terms&amp;amp;conditions prevent us from modifying, or advising to modify? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Feb 2017 02:07:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Can-we-freely-modify-client-js-without-legal-concerns/m-p/1240059#M24586</guid>
      <dc:creator />
      <dc:date>2017-02-09T02:07:28Z</dc:date>
    </item>
  </channel>
</rss>

