Just CSS. All the code is in the components.
> On Nov 6, 2020, at 1:37 PM, Carlos Rovira <carlosrov...@apache.org> wrote:
>
> It's just CSS or JS too?
> MDL had both
>
> El vie., 6 nov. 2020 a las 12:21, Harbs (<harbs.li...@gmail.com
> <mailto:harbs.li...@gmail.com>>) escribió:
> Yup. The reason I made Spectrum external to Royale is because it relies on
> third party CSS.
>
>> On Nov 6, 2020, at 11:56 AM, Carlos Rovira <carlosrov...@apache.org
>> <mailto:carlosrov...@apache.org>> wrote:
>>
>> hehe,
>>
>> yeah! that's good :)
>>
>> I think approaches are different. I see Spectrum like Material Design Lite
>> (MDL) library I did some years ago (and another option Bilbosax can check,
>> that is complete and can be found in Royale libs).
>>
>> In Spectrum and MDL components, styles and behaviours come from a third
>> party and component dev must accommodate what's done by the provider. We are
>> basically wrapping a JS/CSS library with the Royale logic to make it work
>> inside Royale.
>>
>> Jewel is more native to royale, and we control every aspect. We're not
>> wrapping external sources, but creating our own components that have its
>> own styling.
>>
>> Each path has pros and cons. One good thing on the Spectrum/MDL approach is
>> that third party takes care of usability and CSS/JS use to solve any
>> problem, we just need to wrap it to make it usable in MXML/AS3, in the other
>> hand the look and feel is only the one they offer and it's more difficult to
>> change.
>>
>> The good thing about Jewel is that we control the behaviours and are more
>> integrated inside the royale logic and use to be more near to what Flex
>> provided also is more suitable to look and feel changes through themes. In
>> exchange we need to fight with all kinds of implementation aspects. What
>> this means is more work to be done and sometimes more time to reach where
>> others already reach the goal.
>>
>> In the end, each set has its own path and timing. For example, in comparison
>> with latest additions to Spectrum, keyboard navigation is already in Jewel
>> List, but we still don't have a Menu component.
>>
>>
>>
>> El vie., 6 nov. 2020 a las 9:44, Harbs (<harbs.li...@gmail.com
>> <mailto:harbs.li...@gmail.com>>) escribió:
>> Possibly, but I’m pretty sure Spectrum has components that Jewel is missing.
>> ;-)
>>
>> Right now, we’re pretty much finished with a Tag Field component. We’re also
>> working on keyboard navigation on lists and menus, etc.
>>
>> Just some friendly competition to keep us both on our toes… ;-p
>>
>>> On Nov 5, 2020, at 6:08 PM, Carlos Rovira <carlosrov...@apache.org
>>> <mailto:carlosrov...@apache.org>> wrote:
>>>
>>> Also probably is the set more developed in the Royale ecosystem.
>>
>>
>>
>> --
>> Carlos Rovira
>> Apache Member & Apache Royale PMC
>> Apache Software Foundation
>> http://about.me/carlosrovira <http://about.me/carlosrovira>
>>
>
>
>
> --
> Carlos Rovira
> Apache Member & Apache Royale PMC
> Apache Software Foundation
> http://about.me/carlosrovira <http://about.me/carlosrovira>
>
