<?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: Extending existing widgets in Web AppBuilder Custom Widgets Questions</title>
    <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846505#M10464</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; My preferred method is to copy the parent widget and rename it (be sure to change all the references in the manifest.json). In the video you linked he is extending the existing widget through sub classing. And that would require the parent widget to exist in your deployed app along with the extended widget (that does not mean that the parent widget has to be added to the app though).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Oct 2017 16:27:36 GMT</pubDate>
    <dc:creator>RobertScheitlin__GISP</dc:creator>
    <dc:date>2017-10-23T16:27:36Z</dc:date>
    <item>
      <title>Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846504#M10463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to extend a existing widget, using as a parent widget, the OverviewMap widget. The problem that I have is how to load or how to refer the widget parent files without loading the parent widget in the app.&lt;/P&gt;&lt;P&gt;I was following the &lt;A href="https://community.esri.com/migrated-users/42891"&gt;Nick Brueggemann&lt;/A&gt;‌ demo in&amp;nbsp;&lt;A href="https://www.youtube.com/watch?v=gDuuNTeMDlQ&amp;amp;feature=youtu.be&amp;amp;t=28m53s"&gt;their presentation&lt;/A&gt;. But I think that he load the parent and the enhanced widget in the app.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone can help me? &lt;A href="https://community.esri.com/people/rscheitlin"&gt;rscheitlin&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Oct 2017 16:17:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846504#M10463</guid>
      <dc:creator>Joan_PereAvariento_Vicent</dc:creator>
      <dc:date>2017-10-23T16:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846505#M10464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; My preferred method is to copy the parent widget and rename it (be sure to change all the references in the manifest.json). In the video you linked he is extending the existing widget through sub classing. And that would require the parent widget to exist in your deployed app along with the extended widget (that does not mean that the parent widget has to be added to the app though).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Oct 2017 16:27:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846505#M10464</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2017-10-23T16:27:36Z</dc:date>
    </item>
    <item>
      <title>Re: Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846506#M10465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;P&gt;Coping parent widgets and modifying code is the way that i usually use. I would like to develop anything that allow you to separate your code to the original one to make it easier maintaining code.&lt;/P&gt;&lt;P&gt;Thankyou very much. If i develop or find something interesting, i will try to publish and share it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Oct 2017 20:04:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846506#M10465</guid>
      <dc:creator>Joan_PereAvariento_Vicent</dc:creator>
      <dc:date>2017-10-23T20:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846507#M10466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/180371"&gt;Gavin Rehkemper&lt;/A&gt;&amp;nbsp;refer me to his &lt;A href="https://gavinr.com/2017/02/15/extending-widgets-arcgis-web-appbuilder/"&gt;post&lt;/A&gt; in a blog where he talk about it. Anyway i would like to develope something that automate the parent widget files to the app when you extend a widget.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Oct 2017 20:31:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846507#M10466</guid>
      <dc:creator>Joan_PereAvariento_Vicent</dc:creator>
      <dc:date>2017-10-24T20:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846508#M10467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I would go with the help you get from Gavin then as I do not use that technique or workflow.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Oct 2017 20:37:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846508#M10467</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2017-10-24T20:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846509#M10468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/44829"&gt;Jianxia Song&lt;/A&gt;‌ /&amp;nbsp;&lt;A href="https://community.esri.com/migrated-users/53998"&gt;Lemao Wu&lt;/A&gt;‌, would you recommend a different&amp;nbsp;technique to&amp;nbsp;&lt;A href="https://community.esri.com/migrated-users/47370"&gt;Joan Pere Avariento&lt;/A&gt;‌?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Oct 2017 13:28:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846509#M10468</guid>
      <dc:creator>Raul_Jimenez</dc:creator>
      <dc:date>2017-10-30T13:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: Extending existing widgets</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846510#M10469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Copy and modify is my recommendation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2017 02:22:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/extending-existing-widgets/m-p/846510#M10469</guid>
      <dc:creator>JunshanLiu</dc:creator>
      <dc:date>2017-10-31T02:22:15Z</dc:date>
    </item>
  </channel>
</rss>

