More than that, I think each directory should have a README file that
explains the goal or intended use of that component set.
On Wed, Oct 21, 2020 at 10:46 AM Andrew Wetmore wrote:
> I think we should list the component sets that are not complete in a
> separate list below the mention of
I think we should list the component sets that are not complete in a
separate list below the mention of Basic and Jewel...and MDL?
I can get to that later today.
Andrew
On Wed, Oct 21, 2020 at 5:57 AM Hugo Ferreira
wrote:
> Thank you again.
> It is all clear for me now :)
>
> C
> > > > app.
> > > > >
> > > > > - Express: Is Basic with beads applied. While Basic is all about
> PAYG
> > > and
> > > > > the foundation of other sets, Express uses to configure the most
> > needed
> > > > > beads
; > and
> > > > the foundation of other sets, Express uses to configure the most
> needed
> > > > beads so is not PAYG. For example if enabling/disable a component is
> > > > something we think it could be very needed, the components in Express
> > >
eeded
> > > beads so is not PAYG. For example if enabling/disable a component is
> > > something we think it could be very needed, the components in Express
> > have
> > > the Disabled bead attached by default while in Basic you need to add
> it.
> > >
> > >
> &g
. For example if enabling/disable a component is
> > something we think it could be very needed, the components in Express
> have
> > the Disabled bead attached by default while in Basic you need to add it.
> >
> >
> >
> > El mié., 21 oct. 2020 a las 2:4
gt; Hi:
> >
> > Brief descriptions of the component set are here:
> > https://apache.github.io/royale-docs/component-sets
> >
> > Andrew
> >
> > On Tue, Oct 20, 2020 at 8:20 PM Hugo Ferreira
> > wrote:
> >
> > > Hi,
> > >
()
escribió:
> Hi:
>
> Brief descriptions of the component set are here:
> https://apache.github.io/royale-docs/component-sets
>
> Andrew
>
> On Tue, Oct 20, 2020 at 8:20 PM Hugo Ferreira
> wrote:
>
> > Hi,
> >
> > For a while that I have
Hi:
Brief descriptions of the component set are here:
https://apache.github.io/royale-docs/component-sets
Andrew
On Tue, Oct 20, 2020 at 8:20 PM Hugo Ferreira
wrote:
> Hi,
>
> For a while that I have a question to make about current components set :)
>
> If search for TextIn
Hi,
For a while that I have a question to make about current components set :)
If search for TextInput.as, I found the following projects:
- HTML5
- Basic: I know that this is the smallest and 100% PAYG core components
from the framework
- Express
- Jewel: I know that this extends from Basic and
Hi Alex,
that would be cool. Jewel is not as purist as Basic in terms of PAYG and
other royale concepts, and don't think it should be. While Basic is the
foundation and should try to focus on that kind of concepts and is at the
start of the chain, Jewel is at the end and that implies to solve
Forking for this particulare topic:
On 12/24/19, 6:46 AM, "Carlos Rovira" wrote:
...Why I think we need to solve is if we have a better way
to extend UIBase, better than StyledUIBase path, since I'm not very happy
with it.
The worst problem I see is that all we can do in
Hi Chris,
although we get a much better docswith the work in the latest months,
there's still many missing points to cover, some with its own reserved
place, but still empty, and others will need to reserve its place. As
always we'll try our best to cover it as soon as possible. To be fastest we
There is not such a document yet, no. Help creating one would be welcome.
On Tue, Oct 8, 2019 at 4:22 AM Chris Velevitch
wrote:
> There doesn't seem to be an all-encompassing document describing, MX,
> Spark and Jewel components and as well as the pros and cons of each
> nor is there a
There doesn't seem to be an all-encompassing document describing, MX,
Spark and Jewel components and as well as the pros and cons of each
nor is there a discussion on using third party web components,
creating custom web components and how to the material design
components.
HTML too.
>
> > On Feb 1, 2018, at 5:36 PM, Andrew Wetmore <cottag...@gmail.com> wrote:
> >
> > I have started the help docs page about Components, which I suppose we
> > should specify are UI components.
> >
> > Am I correct that there are three
HTML too.
> On Feb 1, 2018, at 5:36 PM, Andrew Wetmore <cottag...@gmail.com> wrote:
>
> I have started the help docs page about Components, which I suppose we
> should specify are UI components.
>
> Am I correct that there are three component sets a user might
17 matches
Mail list logo
