<?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: Generating a new component for ADF 2.2.0 in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3389#M1269</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My final purpose is to understand how the Addons ecosystem will work in the future. I'm trying to port some old code to the new framework to provide compatibility with ADF based applications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From my point of view, an electronic signature feature it's not and ADF feature as it's not required for everyone. So I'd say that this should be an external component. However this "external component" has to be closer to Alfresco Content Apps, as it will be included or excluded from applications depending on the use case. Also, this component is consuming custom Web Scrips from repo, so all the JavaScript Api feature from Alfresco ADF can be re-used (including login an so).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So probably this is a missing target, as is an "external" component to be used "internally".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Mar 2018 16:20:45 GMT</pubDate>
    <dc:creator>angelborroy</dc:creator>
    <dc:date>2018-03-26T16:20:45Z</dc:date>
    <item>
      <title>Generating a new component for ADF 2.2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3387#M1267</link>
      <description>I'm trying to create new "esign-cert-adf" component to port existing&amp;nbsp;code from Share addon at&amp;nbsp;https://github.com/keensoft/alfresco-esign-cert/tree/master/esign-cert-shareI've seen that Yeoman Generator for Alfresco Angular 2 Component seems stopped since ADF 1.9.0:&amp;nbsp;https://github.com/Alfresco/genera</description>
      <pubDate>Mon, 26 Mar 2018 15:16:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3387#M1267</guid>
      <dc:creator>angelborroy</dc:creator>
      <dc:date>2018-03-26T15:16:25Z</dc:date>
    </item>
    <item>
      <title>Re: Generating a new component for ADF 2.2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3388#M1268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Angel, I think it depends if your final purpose is :&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;1. to create an external component to share with other people and deploy in npm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;or&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;2. Add a new feature in ADF&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Mar 2018 15:40:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3388#M1268</guid>
      <dc:creator>eugenio_romano</dc:creator>
      <dc:date>2018-03-26T15:40:08Z</dc:date>
    </item>
    <item>
      <title>Re: Generating a new component for ADF 2.2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3389#M1269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My final purpose is to understand how the Addons ecosystem will work in the future. I'm trying to port some old code to the new framework to provide compatibility with ADF based applications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From my point of view, an electronic signature feature it's not and ADF feature as it's not required for everyone. So I'd say that this should be an external component. However this "external component" has to be closer to Alfresco Content Apps, as it will be included or excluded from applications depending on the use case. Also, this component is consuming custom Web Scrips from repo, so all the JavaScript Api feature from Alfresco ADF can be re-used (including login an so).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So probably this is a missing target, as is an "external" component to be used "internally".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Mar 2018 16:20:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/generating-a-new-component-for-adf-2-2-0/m-p/3389#M1269</guid>
      <dc:creator>angelborroy</dc:creator>
      <dc:date>2018-03-26T16:20:45Z</dc:date>
    </item>
  </channel>
</rss>

