flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harbs <harbs.li...@gmail.com>
Subject Re: [FlexJS] PAYG definitions and guidance, Please participate
Date Sun, 02 Jul 2017 16:23:54 GMT
I think Alex was talking about default components.

MDL is a pretty good example. An MDL app has a certain look and feel. All the necessary functionality
is built into the component set by default.

The point is that there are different classes of applications. Each class of applications
should have its own set of components which have their own defaults. Some ideas (not necessarily

1. Skin swappable need to have their skinning changeable at runtime.
2. Widget heavy
3. Visualization apps.
4. Animation heavy apps.
5. Performance sensitive apps

Until FlexJS starts being used for real, we’re not going to know exactly how the component
sets need to be structured. MDL is designed for a specific app that’s (sort of) well defined.
Express is an attempt at a “general” app requirement, but who knows if it’s really the
right default for a specific class of apps.

So basically, if I’m building a “foo” app, I’d pick the “foo” widget set as the
starting point and that gets me pretty fart along to where I need to be. For this to be realistic,
the Basic set needs to be as modular as possible. Hence PAYG and extremely modular bead architecture
is critical. The thing to keep in mind is that Basic is not a default for anything by design.
It’s a collection of “smallest useful functionality” that can be put together like lego.
And that’s really the point of PAYG.

This is a really critical piece and I think some folks are not quite getting this and that’s
creating confusion about the goals and benefit of PAYG. It’s not like we’re doing a bad
job with Basic, so we have Express to fix that. Basic is the goal of the framework and Express
is just one way of many possible ways of using it.

I don’t think I got it either when I started with FlexJS. I thought Alex was being extreme
with his use of PAYG and splitting up of beads. However, I went along with it, and with time,
I see the wisdom of this approach.


> On Jul 2, 2017, at 4:44 PM, yishayw <yishayjobs@hotmail.com> wrote:
> Alex Harui-2 wrote
>> One thing I wanted put up
>> for discussion now is the notion of "defaults".  Really, I'm trying to get
>> away from the notion that there is one default we have to decide on.  IMO,
>> that's another old way of thinking from Flex.  FlexJS is designed to
>> support multiple component sets.  Express will have different defaults.
>> MDL has different defaults.  The Basic set has a particular design goal
>> (feature parity with SWF) and thus will have different defaults.  There is
>> often no one right answer, so we build different component sets and folks
>> will try them and decide for themselves.
>> Thoughts?
>> -Alex
> Probably needs to be in a separate thread, but I'm not sure what you're
> asking. Default beads? Default attribute values? My intuition is that the
> default value matches the most common use case. Hence, UIBase is by default
> visible.
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-PAYG-definitions-and-guidance-Please-participate-tp62738p62759.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message