Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
MIME-Version: 1.0
In-Reply-To: <CACK5iZfPYjywM7JDtKG9wqoX-htuup3Kof0qGaNambzLK0x4nQ@mail.gmail.com>
References: <D4911565.7FC1B%aharui@adobe.com> <CANFYvfcHUOxAxw8mD_yKydwvFuqCMvzg028otRGBkyYagrjkPw@mail.gmail.com>
 <D4915708.1F9E3%pent@adobe.com> <D4912E9D.7FD14%aharui@adobe.com> <CACK5iZfPYjywM7JDtKG9wqoX-htuup3Kof0qGaNambzLK0x4nQ@mail.gmail.com>
From: Dev LFM <developerlfm@gmail.com>
Date: Tue, 3 Jan 2017 19:13:18 +0000
Message-ID: <CANFYvff-rbaycFaGEL7m+KME2CmT9-1uqBFm6TvCKqmVjXJYZA@mail.gmail.com>
Subject: Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why
 binding is not working in MDL example)
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=94eb2c04c6a236675f0545357796
archived-at: Tue, 03 Jan 2017 19:13:45 -0000

--94eb2c04c6a236675f0545357796
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Maybe this indecision is related to how each one of us translate to our
native language "default/standard/basic"..

I really feel like the basic should indeed be called basic, like on Flex a
ButtonBase. Hardly is used directly... and the Button is a component.

If I will use flexjs, I'll use for sure a set of components with all the
beads needed for do the job fast and without breaking walls on debugger
just to see that I was missing some bead.

I have a suggestion to make: It is possible to "parse" the component first
and inject the beads when and where they are needed? that way there is no
need for different component sets.


2017-01-03 18:55 GMT+00:00 OmPrakash Muppirala <bigosmallm@gmail.com>:

> Sorry, I am a bit late into this thread, but I like 'default' for heavy a=
nd
> 'lightweight' for the basic ones.
>
> Thanks,
> Om
>
>
>
> On Tue, Jan 3, 2017 at 10:39 AM, Alex Harui <aharui@adobe.com> wrote:
>
> > IMO, "Express" is the best idea so far.  I also thought of "Loaded" (wi=
th
> > beads), "Beaded", "Quickstart".
> >
> > Peter, if you want to get started, make a folder called Express.  We ca=
n
> > always change it later.
> >
> > -Alex
> >
> > On 1/3/17, 10:31 AM, "Peter Ent" <pent@adobe.com> wrote:
> >
> > >I think "Express" isn't a bad name for this. It implies that you can g=
et
> > >something running quickly.
> > >
> > >Another name I thought of was "Star" (FlexJS Star).
> > >
> > >A third choice might be "Prime", meaning the main one to use.
> > >
> > >=E2=80=B9peter
> > >
> > >On 1/3/17, 12:14 PM, "Dev LFM" <developerlfm@gmail.com> wrote:
> > >
> > >>I've been listening this thread, sorry my intrusion..
> > >>
> > >>Why not simply:
> > >>
> > >>- ComponentBase for the current set without beads, and "Component" fo=
r
> > >>the
> > >>ones with default beads included?
> > >>
> > >>I like "Express" too but not making much sense to me.
> > >>
> > >>My 2 cents ^^
> > >>
> > >>2017-01-03 16:53 GMT+00:00 Alex Harui <aharui@adobe.com>:
> > >>
> > >>> Hi,
> > >>>
> > >>> The original thread is another example of where PAYG becomes PITA.
> On
> > >>> another thread, Om wants to bake in HTML sanitization by default.
> IMO,
> > >>> these are things that should go in a heavier component set with mor=
e
> > >>> things baked in.  IMO, this new, heavier component set would be the
> > >>> default for FlexJS.  No more forgetting to add DataBinding beads, o=
r
> > >>> SimpleCSSValuesImpl, etc.  Fewer tags to write.
> > >>>
> > >>> I've asked Peter to start on it so you can see how to bake stuff in
> and
> > >>> how much simpler it will make our examples.  I think it will help i=
n
> > >>> getting folks started with fewer problems.  I think we've proven th=
at
> > >>>we
> > >>> can composite basic things into more complex things.
> > >>>
> > >>> But, we need a good name for this set.  I don't like "Heavy".  Make=
s
> me
> > >>> think it would be too fat and slow.  I've ruled out for now "Kitche=
n
> > >>> Sink", and "Full" (because it won't contain every bead).  I've
> thought
> > >>> about "Medium", "Typical", "Common", "Popular", "POC" (Proof of
> > >>>Concept)",
> > >>> "RP" (Rapid Prototyping).  Don't like any of them.  What name would
> > >>> suggest that it is not on the place to start but that you could use
> it
> > >>>in
> > >>> production if you don't run into size/performance issues?
> > >>>
> > >>> Thoughts?
> > >>> -Alex
> > >>>
> > >>> On 1/2/17, 11:20 PM, "piotrz" <piotrzarzycki21@gmail.com> wrote:
> > >>>
> > >>> >Alex,
> > >>> >
> > >>> >That's what I'm missing. It's a bit better cause when I add bead
> > >>> >"ItemRendererDataBinding" my getter has been fired, although bindi=
ng
> > >>>is
> > >>> >still not working. I've just pushed my code. - Not sure what can b=
e
> > >>> >wrong.
> > >>> >
> > >>> >I have to admit I'm still thinking to much Flex instead of FlexJS =
:)
> > >>> >
> > >>> >Piotr
> > >>> >
> > >>> >
> > >>> >
> > >>> >-----
> > >>> >Apache Flex PMC
> > >>> >piotrzarzycki21@gmail.com
> > >>> >--
> > >>> >View this message in context:
> > >>> >http://apache-flex-development.2333347.n4.nabble.
> > >>> com/FlexJS-MDL-Why-bindin
> > >>> >g-is-not-working-in-MDL-example-tp57738p57795.html
> > >>> >Sent from the Apache Flex Development mailing list archive at
> > >>>Nabble.com.
> > >>>
> > >>>
> > >
> >
> >
>

--94eb2c04c6a236675f0545357796--