03-26-2018 11:16 AM
I'm trying to create new "esign-cert-adf" component to port existing code from Share addon at https://github.com/keensoft/alfresco-esign-cert/tree/master/esign-cert-share
I've seen that Yeoman Generator for Alfresco Angular 2 Component seems stopped since ADF 1.9.0: https://github.com/Alfresco/generator-ng2-alfresco-component
Additionally, ADF application generator for Yeoman does not work as it is:
https://github.com/Alfresco/generator-ng2-alfresco-app
So, what's the better (and safer) approach to start coding a new ADF component?
03-26-2018 11:40 AM
Hi, Angel, I think it depends if your final purpose is :
1. to create an external component to share with other people and deploy in npm
or
2. Add a new feature in ADF
03-26-2018 12:20 PM
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.
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).
So probably this is a missing target, as is an "external" component to be used "internally".
Explore our Alfresco products with the links below. Use labels to filter content by product module.