Carlos
I think the work you have done is outstanding, however as a small
developer, is there a real long team future, I know we always say yes, but we
where let’s down big time by Adobe with these poor management of the flex issue
and the abandonment of flex
Flex is a great language, however most languages have a life expedience
JS in versions , C in versions, python seems to be good long terms bets
I started in this industry in 1980’s so I have seen lots of stuff come and go
IMHO royal is a side road that may run out if tar some time in the future, then
your back to start
After looking are royal last you we spent the last year moving our app to react
it is very close to flex in a lot of ways
Just me thoughts
Scott
Sent from my iPhone
> On 9 Aug 2020, at 11:22, leokan23 <[email protected]> wrote:
>
> Hi Carlos,
>
> of course Royale was my first try back in version 0.7.2. The reason I tried
> it was mostly for web but I had many issues starting with it. Piotr helped
> me a bit to start but at the time my main issues where:
>
> 1. Documentation was scarce (there were mostly examples, not documentation).
> 2. The first few times i tried to setup the sdk, I couldn't make it work.
> Actually Piotr spent like 50 minutes trying to setted up on my laptop a few
> years ago.
> 3. Another issue for me was that I had to rewrite all the UI as Sparks
> emulation wasn't available.
>
> One of the things I am not sure how it works, is the mobile part (which I am
> most interested for). In my understanding you need to use cordova which
> makes Royale comparable to Ionic, which is not the best option as it is
> basically a wrapped web site in an app. Not sure if you can export the
> Royale project directly to AIR apk or ipa.
>
> After Jewel was released, I thought about giving it another go, but due to
> lack of time I never did. I am not sure if the issues above still stand, but
> if you can clarify the mobile thing, I would be glad. :)
>
>
>
> --
> Sent from: http://apache-flex-users.2333346.n4.nabble.com/
