Hi,
for me the best options today are:
* AIR: If you don't need the browser, you can still have more years to
avoid a more time consuming migration. Harman seems taking the torch to
manage Adobe AIR in a good way. Maybe to early to say anything now, but AIR
seems in good hands.
* Apache Royale:
Also note that in examples/mxroyale/tourdeflexmodules, I used the emulation
components to migrate over 100 screens by not rewriting them much at all.
There are still some bugs to be ironed out, but if volunteers pitch in, they
will be resolved.
-Alex
On 6/24/19, 2:25 AM, "Olaf Krueger" wrot
Olaf
I Totally agree, back in 2009 I spend 1 year looking a frameworks, going
round and round reading all the stuff trying to balance one evangelist vs
another evangelist, then o read something that said there is no answer pick
want works for you, in my case I needed rich UX, at the time
Hi,
>I am wondering if I should consider AIR
As already mentioned, if you don't need to target the browser, AIR probably
means the least effort.
Notice that since AIR was taken over by Harman [1], the license changed and
they introduced a pricing strategy in order to be able to drive AIR
forward
Hi,
> Royal is ... IMHO a dead end, in a few years your be porting again
I think this is valid for all of the tech stacks/frameworks out there.
Depending on the use case, Royale could be the best option... or even not.
But it's always worth to give it a try like any other tech stack or
framework
On 6/23/19, 11:51 AM, "Scott Matheson" wrote:
Alex
I fully understand and wish you all the best, but as a small
developer i need to look at what is best for my development, i will keep a eye
on Royal
For sure, you have to do what's best for you. Another good thing about
Alex
I fully understand and wish you all the best, but as a small developer i
need to look at what is best for my development, i will keep a eye on Royal
> On 23 Jun 2019, at 06:26, Alex Harui wrote:
>
> One of the reasons Flex and Royale are at Apache is so no corporation can
> pull t
One of the reasons Flex and Royale are at Apache is so no corporation can pull
the plug. Apache specifically does not allow corporations to have any say in
their projects. If Adobe decides to stop paying me to work on Flex and/or
Royale, if I can find some other way to get paid to do it, I can
Yes with 450 screen that’s a big job, air or the local wed browse is the simple
approach
We went with royal, the design approach is the same as flex, we started by
creating 1 to 1 components, the new compounded are JS CSS SVGS in our case
about 30 components
The royal component architecture
So I am an old program 60 so I would say I have seen it all many time over, we
have tried/looked at royal a number of times
As for royal, sorry it is late, we needed royal to be in full production 2
years ago, when we tried royal we kept finding new issues or missing elements,
yes I know this
Hi. Thanks for the response. I have some questions below.
On Sat, Jun 22, 2019 at 10:42 AM Scott wrote:
> AIR is a good option but you have the update install problems, the
> solutions are out there and air will do auto update etc ...
>
> Google web frame work well, you install a browser, tha
Hi Scott,
I'm curious why are thinking that Royale is a dead end?
Thanks,
Piotr
On Sat, Jun 22, 2019, 4:42 PM Scott wrote:
> AIR is a good option but you have the update install problems, the
> solutions are out there and air will do auto update etc ...
>
> Google web frame work well, you ins
AIR is a good option but you have the update install problems, the solutions
are out there and air will do auto update etc ...
Google web frame work well, you install a browser, that looks a desk top app
but run the flex app like today, I have tried this and it work well the WebKit
stuff is no
Hi Blake,
Well AIR would be the easiest cause in best case you won't change single
line in your core app.
Another option is Apache Royale, but if you are saying about fast option
it's probably don't fit to that.
Thanks,
Piotr
On Sat, Jun 22, 2019, 4:25 PM Blake McBride wrote:
> Greetings,
>
Greetings,
I have a large Flex(3.5)/Flash app that (obviously) runs under a browser.
Since the Flash player is going away, I am wondering if I should consider
AIR. What are my other options? What's easiest?
Thanks.
Blake McBride
15 matches
Mail list logo
