Hi Maria, Yes, I have integrated many technologies.
Perhaps, I explained myself wrong earlier. It's not a fork of the Royale (however could be way). It's my own set of libraries (some of the external as Calendar, Reports, etc ...), others done by my self using Royale and others with Royale components changed. So I instantiate directly from this libraries and not Royale in the final App. Any new Apps will share this set of libraries. This are very specific to be on Royale framework (ex: ConfirmDelete in attachment) and some implements many beads and ugly patch to be on Royale (ex: my extension of VirtualDataGrid in attachment). This kind of patches are necessary to the application behaviour with so many data as you can see in the DataGrid.as comments and of course in time if I found the optimum solution (it happened along this last year a few times) I will put in the Royale framework and free the file from this patch but meanwhile they are necessary I have many, many other specific component (ex: FileInput, ImageInput, etc ...) but all are a mix of other components and styles to be on Royale. Regards, Hugo. Maria Jose Esteve <mjest...@iest.com> escreveu no dia segunda, 24/04/2023 à(s) 12:42: > Hi Hugo, you have done very well, I like the design, it is modern, neutral > (it looks very similar to mine 😝 ). > Great job... > > Me, I'm going to be "positive".... > I see you have integrated several different technologies, like the > FullCalendar JS libraries and the ReportViewer, I LOVE this. > It is true that many beads are missing and that there are problems that > "I" have not been able to save but I see that "you" have been able to,..... > maybe you could share your fork of the SDK because maybe "your corrections > are of general interest", could it be? > > I am now making an example of integrity with FullCalendar, when I have it, > I will publish it in royale-community but I am interested in comparing "my > integration" with yours to leave the best one would you mind sharing it > with me? > > Congratulations. > Hiedra > > -----Mensaje original----- > De: Hugo Ferreira <hferreira...@gmail.com> > Enviado el: viernes, 21 de abril de 2023 12:51 > Para: Apache Royale Development <dev@royale.apache.org> > Asunto: After a year of development, my finished Royale App based on a > previous Flex version > > Hi, > > It's now been a long time with the Apache Royale community so, I want to > share my experience so far. > > I have a SAAS condominium management software based on Flex several years > ago (Desktop using Adobe AIR). > For more than an entire year, I have been rewriting from scratch (not > porting) this application using Apache Royale (Web based this time and > responsive). > During this process I faced many, many challenges. > Missing beads, features and bugs in Apache Royale framework that I fixed > and pushed to github. > I have my own Royale framework that extends from the standard Apache > Royale standard. > Everytime I have something new or fix to add, I have the paradigm to > decide if it is something generic enough and put directly in the Apache > Royale framework or on my own framework or a mix. > > If you are curious to see the difference, you can find the Desktop-AIR > version in the bottom of this site (also with demo credentials): > https://solidsoft.pt/software-de-gestao-de-condominios-gc/ > Soon, I will update the website and all references from the previous > version will be gone. > > And here you can login in the demo of the new version base on Apache > Royale: https://gc.solidsoft.pt/BackOffice?demo=1 > > Regards, > Hugo. >
