Hi Hugo
El sáb., 17 nov. 2018 a las 14:03, hferreira ()
escribió:
> Basic cannot work without Jewel. It is correct ?
>
No. Basic works on its own, is like the minimum expression of pieces to
build a royale application. Jewel is based on that *basic* pieces, but
tries to be separated from basic.
IT was my hope that more of the experienced committers on Royale would help get
the emulation components to run and train the newcomers. Unfortunately, that
has not happened so far, and I don't have enough time to do all of it myself in
short order. I keep hoping our committers will step up
And the most important more of your code won't need as much changes.
> Yes. In a framework change perspective is the cheapest approach but for
> now is not there iet (let's see in a near future), meanwhile I will check
> Royale without emulation.
--
Sent from:
I believe you could think like that like mx and spark, but probably going
deeper it can be a bit more.
I see this like that - If you jump and learn emulation components and how
to create and make them visible for your needs - You earn deeper knowledge
what is behind the stage. You will gain the
Basic cannot work without Jewel. It is correct ?
Jewel it's like a UI implementation using Basic like mx ou spark for Flex,
correct ?
So, what happens if I'm using Jewel and at some point I would like to
completely change my UI aspect ?
Or Jewel is the first implement, a set of UI with a default
