I'd completely agree. It'd allow developer to solve his/her own problems (by
re-using existing css/html snippets), instead of using the Royale forum to walk
up the learning curve. New converts to Flex/Royale would find this more natural
as well.
> On November 22, 2017 at 3:28 AM Olaf Krueger w
I'd recommend toolTips in the first set. Other components of interest would be
a drop down list or combo box, and some kind of tabbed panel (e.g. Spark
NavigatorContainer).
> On November 11, 2017 at 3:39 AM Carlos Rovira wrote:
>
>
> Hi
>
> to avoid mixing conversations, I create thi
I completely agree. If it is open for more than one person to contribute, it
should build up fairly quickly.
> On November 10, 2017 at 2:30 PM Carlos Rovira wrote:
>
>
> Hi,
>
> One thing I think it would be great would be to have something like Peter
> deHaan blogs (Flex Examples,
I largely agree with your comments here.
My enterprise/corporate web app actually used the default styling -- neutral
(gray) buttons/etc. with corporate blue highlights for selection etc. found in
default Spark. I didn't want the components to stand out and be distracting.
They're necessary, a
Love the logo, as is. Love the fresh, modern, distinctive feel/colors/fonts of
the website. Amazing job Carlos, really!!!
I'm not a software expert, but I needed to create an extensive enterprise web
app years ago, and what initially drew me to Flex was the availability of (1)
extensive compon
