Hi Hugo

El sáb., 17 nov. 2018 a las 14:03, hferreira (<[email protected]>)
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. Jewel main dependency on Basic is UIBase,
that is like UIComponent in Flex.

Jewel is an UI set that support themes. I started creating Jewel since I
love flex, but think that we need a fresh UI set since more than 15 years
has passed since Flex was created. Today we need to have things from flex,
but as well new things like new kind of components (Drawer, TopBarApp,
Wizard,...) and features like responsiveness and adaptiveness. So I want
best of both world, a flex development model with all the good points and
be able to create an app that works across multiple browsers and devices
without the need for the developer to make anything, so for example if you
open a ComboBox, the popup list will show as normal on desktop browser
size, but thanks to css we can make it slide from bottom in phones, and
things like that.


> Jewel it's like a UI implementation using Basic like mx ou spark for Flex,
> correct ?
>

is a UI implementation based on the principles of Basic, but both are UI
sets.
Basic keeps PAYG at 100% since Jewel is PAYG, but doesn't try to be very
exhaustive (maybe at 90%) and is evolving to be in a point where PAYG is a
core concept but looking into be usable for development, so if a bead that
now is composed is used most of the time, maybe in future versions could be
defined by default like in Express. So Jewel is not black or white,
sometimes is good some breaking I the rules.


>
> So, what happens if I'm using Jewel and at some point I would like to
> completely change my UI aspect ?
>

Jewel is designed with themes in mind. I created a system of jewel themes,
but you can create something completely different.
It's using SASS and JewelTheme is a "master" theme. Then since is based on
variables, the rest of themes (about 144 I think) are generated. So Jewel
themes are a combination of 12 colors, light/dark modes and flat/no flat
modes.

I ccmmitted half of that themes and since I'm working on making Jewel work
right and be ok in production, I'm updating themes, but still need more
work for versions like flat or dark modes. In our repo we have 12
colors/light themes working and dark is committed, but I'm sure that needs
work to look really dark.


>
> Or Jewel is the first implement, a set of UI with a default skin that I can
> change with CSS ?
>
>
Jewel uses JewelTheme as the "master" theme. You can duplicate and start to
work in other visuals, you only need to use the structure
JewelTheme uses SASS to generate css (sass generation is only set up when
use maven). The css in JewelTheme wires the needed beads and some aspect of
css that are needed.

If you use some concrete theme (not the master), is done to combine up to 3
themes. For example if you want light, but blue as main color, and red for
secondary and green for emphasys, you can uses the 3 themes that make that
combination works. The same can be generated by you just updating some few
SASS vars in JewelTheme (for that reason is a "master" theme).

HTH

-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to