Besides the Office Add-In that I'm currently working on, I have a project
from last year (a report engine) that we could add.
After I finish this add-in, I will go back to my port from Flex to Royale
that and for sure that new components will arrive and could go straight to
this central repository instead of creating separated projects.

Maria Jose Esteve <[email protected]> escreveu no dia segunda, 29/11/2021
à(s) 11:04:

> Yes, I think so too... And as Alina says, if we all know about it, maybe,
> we can do some good and learn from each other.
>
> Hiedra
>
> -----Mensaje original-----
> De: Hugo Ferreira <[email protected]>
> Enviado el: lunes, 29 de noviembre de 2021 11:47
> Para: Apache Royale Development <[email protected]>
> Asunto: Re: New project ExternsJS
>
> This is a very good idea to have a central project with all extern
> components.
>
> Maria Jose Esteve <[email protected]> escreveu no dia segunda, 29/11/2021
> à(s) 09:44:
>
> > Hi,
> > I need some help and advice with the structure and compilation of the
> > new ExternsJS project, "bear with me". 😝
> > First, I would like to tell you that I thought it was appropriate to
> > create a branch "feature/ExternsJS_InspireTree" for this
> > implementation, with the idea of not interfering in the general
> compilation of the SDK.
> >
> > As I see it, ExternsJS will include several "subprojects"
> > (InspireTree, VirtualSelect, Royale Office Add-In (Hugo), ...) but I
> > don't know how this structure should be set up inside the SDK. I've
> > checked the existing projects, but I don't see any like this: "a
> > library of libraries" (it would be like 'projects' itself).
> >
> > For now, the structure I have implemented within "projects" is:
> > ├───ExternsJS
> > │   ├───Echarts
> > │   ├───InspireTree
> > │   │   ├───src
> > │   │   │   └───main
> > │   │   │       ├───config
> > │   │   │       ├───resources
> > │   │   │       │   ├───inspiretree
> > │   │   │       │   ├───lodash
> > │   │   │       │   └───svg
> > │   │   │       └───royale
> > │   │   │           └───org
> > │   │   │               └───apache
> > │   │   │                   └───royale
> > │   │   │                       └───externsjs
> > │   │   │                           └───inspiretree
> > │   │   │                               ├───beads
> > │   │   │                               │   └───models
> > │   │   │                               ├───controls
> > │   │   │                               ├───supportClasses
> > │   │   │                               └───vos
> > │   ├───JsCalendar
> > │   └───VirtualSelect
> >
> > The first library that has been added is "InspireTree" although I have
> > created folders for some others that may be added in the future
> > (Echarts, JsCalendar and VirtualSelect as examples). How do you see this
> structure?
> >
> > My second question is about how to configure the configuration and
> > compilation files. I understand that the maven and ant builds must be
> > configured, but I know only "a little" about Maven, so I would need
> > help on this point as well.
> > These are the existing configuration files:
> >
> > ExternsJS
> > |   asconfig.json
> > |   build.xml
> > |   pom.xml
> > |
> > +---Echarts
> > +---InspireTree
> > |   |   asconfig.json
> > |   |   build.xml
> > |   |   pom.xml
> > |   |
> > |   +---src
> > |   |   \---main
> > |   |       +---config
> > |   |       |       compile-swf-config.xml
> >
> > I have created ExternsJS/pom.xml and ExternsJS/InspireTree/pom.xml,
> > for Maven compilation but I don't know how build.xml and asconfig.json
> > should be configured, at this point I would require help as well.
> > I have compiled the whole sdk with Maven and with ant and there were
> > no errors but I think they are not ok... I don't see ExternsJSJS "THIS
> > IS WHY I KNOW IT IS NOT OK". 😝
> >
> > I would be grateful for any help.
> >
> > Thx
> > Hiedra.
> >
> >
>

Reply via email to