royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlosrov...@apache.org>
Subject Re: Container change
Date Thu, 10 May 2018 09:34:19 GMT
Hi Harbs,

in the point you are discussing here, I'm with you, and as well proposed a
way to fix it in the other emails: Extract States/MXML functionality in
Core so Group and HTML elements can use it. GroupBase seems not a class
that should remain since seems does not apport nothing at the moment. I
think as well HTML needs States, or said in other way. Al most all visual
components declarable vía MXML, should be, since for users will be very
strange that some could do it and other not...
It's a matter of consistency all over Royale.


2018-05-10 8:31 GMT+02:00 Harbs <harbs.lists@gmail.com>:

> I don’t care that it should extend Group specifically, but it does need to
> extend (or implement) a "Group-esque” component. Without that, HTML element
> components can’t contain other elements in MXML.
>
> Which pieces are required for it to contain other elements in MXML? Not
> 100% sure about that.
>
> As far as what it needs? Not 100% sure but definitely:
> addElement
> addElementAt
> removeElement
>
> Pretty sure about DefaultProperty.
>
> Not sure about:
> Layout pieces
> States
> Transitions
> IMXMLDocument
>
> Various events? Dunno.
>
> I’d guess that Layout is probably something we *do* want to have.
> Requiring that to be specified using standard css doesn’t feel very
> “Royale-like” to me.
> States should likely be included as well to allow HTML elements to be
> modified by states.
> I don’t know why Transitions are included in Group in the first place, so
> I can’t comment on that.
>
> IMXMLDocument: Is that needed only for making it a base for an MXML file?
> Should HTML Element components have the ability to be used as a base for
> MXML? I don’t know the answers to this.
>
> Harbs
>
> > On May 10, 2018, at 2:19 AM, Alex Harui <aharui@adobe.com.INVALID>
> wrote:
> >
> > On the other hand, I don't agree with Yishay's and Harb's concerns about
> the NodeElementBase having to subclass Group in order to get MXML
> children.  The ability to specify children in MXML can be added to any
> class.  What else does NodeElementBase.as use from Group/GroupBase?
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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