Re: Adobe has announced the end-of-life of the Flash Player

[flex capacitor]

Microsoft, Google and Firefox have all explicitly disabled FP in the
browser and then faced backlash from users and then they reenabled it.
Remember Microsoft's exclusion list? We read tech blogs and have heard the
news but the average user isn't paying attention or they'll be distracted
around 2020 (by elections).

My opinion is businesses won't move over unless they have to and many of
them don't want to spend the money to. And some companies don't have the
money to.

What if we fork a version of Firefox that continues to support plugins. Get
announcements out to the major tech blogs. Clear up the misconceptions at
the same time. Unity would be down for that and they have major investors.
They were thrown under the bus too.

I had written a paragraph about Googles web team here but to keep it short
they are bias and are trying to make decisions for everyone. Firefox is
following their lead so they somehow don't lose users. When the browsers
makers decide (for everyone) to disable plugins there will be a huge
audience looking for a browser that continues to support them.

At the same time maybe we can put some part of Flex into it like client
side MXML rendering or compiling. I think Alex said the compiler could be
stripped down to 29MB. Almost everyone uses IE to download Chrome or
Firefox. Download size is not a big an issue as it used to be.

HTML, CSS, JS need an upgrade. HTML can be upgraded to MXML (Flex or
FlexJS), CSS in Flex has always been fine for me but it could be upgraded
to SCSS or post CSS (I'm sure there are others). JS is being upgraded to
ES5, 6 slowly but even ES6 still feels less than ES4. That might generate
interest from developers. My 2 cents.


On Mon, Aug 14, 2017 at 9:10 AM, Jeffry Houser 
wrote:

>  For legacy applications or archival purposes, you'll probably want to
> keep an installer for the Flash Player and/or older browsers.  So they can
> be reset up on an old machine, or in a VM. Browsers, for the most part,
> have already shut down their plugin APIs.
>
>
>
> On 8/14/2017 8:26 AM, Clint M wrote:
>
>> I remember reading that browsers won't be supporting after that.
>>
>> On Mon, Aug 14, 2017 at 6:19 AM, Deepak MS 
>> wrote:
>>
>> Let's say Adobe releases final version of flash player version 35 for
>>> instance, by end of 2019, without further maintenance or development of
>>> the
>>> plugin. Will this version continue to stay forever, whether or not users
>>> want to use it or is it that flash player will be blocked by browsers
>>> themselves? It isn't clear in the article. Or did I miss it?
>>>
>>>
>>>
>>> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
>>> nicholaskwiatkow...@gmail.com> wrote:
>>>
>>> Looks like we have a date :

 https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html

 -Nick


> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.dot-com-it.com
> http://www.jeffryhouser.com
> 203-379-0773
>
>

Re: TLF, problem with the delay of updates

[flex capacitor]

It is not clear what you are asking but if you have images in your text
flow they do not display right away. There are various status events that
you can listen for to see when an image has loaded. After that you can call
updateAllControllers and it will move the text to the new line.

The RichEditableText component will listen for inline images and update the
control when the image loads, the RichText does not guarantee it will
update the control (in this case RichText will not guarantee it will show
the image).

You can add event listeners on the TextFlow to listen for the StatusChange
event and update the text flow when any new image loads.

Note: If you set the width and height of the image in TLF markup then the
text flow knows how to lay out it's contents before the image loads and
there will be no resizing.

On Fri, Feb 17, 2017 at 4:07 AM, goratz  wrote:

> Hi Harbs I only want to reply you to see my previous message.
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/TLF-problem-with-the-delay-of-updates-
> tp59313p59591.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: flexjs and flashdevelop

[flex capacitor]

Good job!

On Mon, Feb 13, 2017 at 10:21 PM, lizhi  wrote:

> https://github.com/matrix3d/spriteflexjs/wiki/flashdevelop
>
>
>
> -
> spriteflexjs.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/flexjs-and-flashdevelop-tp59364.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: MXML Azzurro

[flex capacitor]

The default MXML is rendering and the cursor shows the location at 00:00 so
I'm guessing it's there but behind the SWF. I might need to set the wmode.

At some point the swf in the browser started layering HTML content over the
swf plugin content without changing the wmode. I don't know how this is
possible but it's working in those browsers. I know gpu and direct were
added at some point. I'm currently not setting it to anything. IE uses
ActiveX so maybe it still needs to be set to opaque or transparent.

On Mon, Feb 13, 2017 at 4:20 PM, flex capacitor <flexcapaci...@gmail.com>
wrote:

> Hi Olaf, I'll check it out. I'll have to find a Windows 7 IE 11 VM. In the
> mean time can you check if there any errors in the browser console?
>
> On Mon, Feb 13, 2017 at 7:31 AM, OK <p...@olafkrueger.net> wrote:
>
>> Cool, thanks for working on this!
>>
>> It seems to me that the mxml editor at the bottom is not working under
>> Windows 7 with IE11 [1].
>> Firefox and Chrome works for me...
>>
>> Olaf
>>
>> [1]https://snag.gy/4f6CTA.jpg
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-flex-development
>> .247.n4.nabble.com/MXML-Azzurro-tp59262p59316.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>
>
>

Re: MXML Azzurro

[flex capacitor]

Hi Olaf, I'll check it out. I'll have to find a Windows 7 IE 11 VM. In the
mean time can you check if there any errors in the browser console?

On Mon, Feb 13, 2017 at 7:31 AM, OK  wrote:

> Cool, thanks for working on this!
>
> It seems to me that the mxml editor at the bottom is not working under
> Windows 7 with IE11 [1].
> Firefox and Chrome works for me...
>
> Olaf
>
> [1]https://snag.gy/4f6CTA.jpg
>
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/MXML-Azzurro-tp59262p59316.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: MXML Azzurro

[flex capacitor]

For drawing to a FlexJS *swf* it would be much simpler than a partial or
all JS method. The way it works now is it loads an embedded application.swf
via loader.loadBytes(). The application.swf is an empty compiled Spark
Application. Once that's loaded the MXMLDocumentImporter class parses the
MXML and using a class map creates the elements and adds them to the
Application instance. Each time the editor is updated all the elements are
removed and then added again.

I didn't go the agent route for a few reasons. The LocalConnection would
sometimes hang and at first I couldn't figure it out. I tracked it down to
if previous connections were not closed correctly. So if someone reloaded
the browser not all of the connections would be closed. I got around this
by creating new connections each time. The second reason is I already had a
lot of work in the existing method using a parser and loading elements onto
an empty application swf. The reason for loading a separate swf was so that
the design view application could have it's own system manager, style
manager, sandbox and so on. It currently inherits the styles from the
container application but it in the future it could be sandboxed so styles,
classes and so on are not inherited. For my purposes at the time it made
sense.

For a FlexJS Importer class it could use local connections. The code from
the MXMLLiveEditAgent that you made a while back sends the changes through
the local connection. But it doesn't rebuild the swf from scratch or maybe
it does? Here is the MXMLLiveEditPlugin class
<https://gist.github.com/monkeypunch3/3044426aaaed2e66d4a4399814b68959> and
the main MXMLLiveAgent class
<https://gist.github.com/monkeypunch3/b2c17b5b729b0f2d6671515e1b45c0b0>.

Here's the current MXMLDocumentImporter class
<https://github.com/monkeypunch3/Radii8/blob/master/Radii8Library/src/com/flexcapacitor/utils/MXMLDocumentImporter.as>
and the decoupled one I started to work on here
<https://github.com/monkeypunch3/MXML-Azzurro/tree/master/MXMLAzzurroLibrary/exports>
(untested). Here is the main online editor application
<https://github.com/monkeypunch3/MXML-Azzurro/blob/master/MXMLAzzurroLibrary/src/MXMLAzzurroMainView.mxml>.
A FlexJS Importer would roughly follow the MXMLDocumentImport class at
least. Here is the project view source
<https://www.radii8.com/mxml/srcview/index.html>.
There are areas that need refactored and performance would probably
increase 10 fold.

On Mon, Feb 13, 2017 at 10:47 AM, Alex Harui <aha...@adobe.com> wrote:

>
>
> On 2/13/17, 5:20 AM, "flex capacitor" <flexcapaci...@gmail.com> wrote:
>
> >Thanks. I'm not sure but it would probably take around a week to a month
> >depending on what route you go and if you want JS output or Flash output.
> >If you wanted to use the existing application you would create a
> >FlexJSImporter and have it write to a div or iframe. It could reuse all
> >the
> >classes but it would require the Flash Player plugin. The second route
> >would be to create it all in FlexJS. That would be more work since you
> >would have to update any code that uses Flash specific APIs and you would
> >have to update the classes for any changes in the FlexJS reflection API
>
> Doesn't this work via an agent in the running application?  Seems like
> we'd only need to supply a FlexJS-knowledgable agent in order to see it
> work for FlexJS SWFs.  Does it use LocalConnection?  If so, then to get it
> to work for JS, we'd either need to rewrite the communications to use
> sockets, or require a special Flash-based agent that talks to the JS Agent.
>
> Of course I could be completely wrong...
> -Alex
>
>

Re: MXML Azzurro

[flex capacitor]

Thanks. I'm not sure but it would probably take around a week to a month
depending on what route you go and if you want JS output or Flash output.
If you wanted to use the existing application you would create a
FlexJSImporter and have it write to a div or iframe. It could reuse all the
classes but it would require the Flash Player plugin. The second route
would be to create it all in FlexJS. That would be more work since you
would have to update any code that uses Flash specific APIs and you would
have to update the classes for any changes in the FlexJS reflection API

On Sun, Feb 12, 2017 at 4:26 PM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:

> So Cool Jude,
>
> I add to Harbs question would it work for FlexJS? That would be
> awesome!! :)
>
> 2017-02-12 22:23 GMT+01:00 Harbs <harbs.li...@gmail.com>:
>
> > Jude,
> >
> > That is way cool!
> >
> > What would be involved in getting it to work with FlexJS MXML?
> >
> > Harbs
> >
> > > On Feb 12, 2017, at 11:14 PM, flex capacitor <flexcapaci...@gmail.com>
> > wrote:
> > >
> > > I just wanted to make the community aware of the project MXML Azzurro
> > > <https://www.radii8.com/mxml/>. It's an online MXML editor,
> interpreter
> > and
> > > render that you can use to create and post MXML snippets.
> > >
> > > Why do this?
> > >
> > >   - So Flex developers can see MXML code rendered live without
> installing
> > >   a compiler
> > >   - So Flex developers can save and share MXML snippets
> > >   - So non-Flex developers can see MXML syntax and rendered results
> > >
> > > Also, HTML markup is far behind MXML and XML in general. Not so much
> the
> > > rendering but the markup. We need to promote something better natively
> > even
> > > if we are cross compiling to it. HTML doesn't have VGroups or HGroups
> > like
> > > Flex or simple styles like horizontalAlign or verticalAlign. They have
> > > display, box-sizing, floats, shadow dom, no content fit and all of
> these
> > > other rules to get basic functionality we get for free. They probably
> > won't
> > > listen but if they were wise they could use MXML (mustella, etc) as a
> > > scaffold for a updated syntax and expected syntax behavior.
> > >
> > > If it's something that would fit on the Apache website it's welcome.
> > >
> > > Note:  It does not support states, declarations, css or AS3 although
> > those
> > > things can be added in time by myself or anyone who has access to
> github.
> > > It has dependencies to other project libraries but with some work it
> can
> > be
> > > decoupled.
> > >
> > > More info here <https://www.radii8.com/blog/?p=1075>. The source is at
> > > github here <https://github.com/monkeypunch3/MXML-Azzurro>.
> >
> >
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05
> http://www.codeoscopic.com
> http://www.avant2.es
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.
>

MXML Azzurro

[flex capacitor]

I just wanted to make the community aware of the project MXML Azzurro
. It's an online MXML editor, interpreter and
render that you can use to create and post MXML snippets.

Why do this?

   - So Flex developers can see MXML code rendered live without installing
   a compiler
   - So Flex developers can save and share MXML snippets
   - So non-Flex developers can see MXML syntax and rendered results

Also, HTML markup is far behind MXML and XML in general. Not so much the
rendering but the markup. We need to promote something better natively even
if we are cross compiling to it. HTML doesn't have VGroups or HGroups like
Flex or simple styles like horizontalAlign or verticalAlign. They have
display, box-sizing, floats, shadow dom, no content fit and all of these
other rules to get basic functionality we get for free. They probably won't
listen but if they were wise they could use MXML (mustella, etc) as a
scaffold for a updated syntax and expected syntax behavior.

If it's something that would fit on the Apache website it's welcome.

Note:  It does not support states, declarations, css or AS3 although those
things can be added in time by myself or anyone who has access to github.
It has dependencies to other project libraries but with some work it can be
decoupled.

More info here . The source is at
github here .

Re: [FlexJS] How to add html content?

[flex capacitor]

I have a few thoughts on that. I need a component like this in the past for
the times I had separate HTML content already created but needed to be
integrated into a Flex JS app. I would suggest a contentBefore,
contentAfter and contentOverride properties maybe as a bead or a full
separate component.

Those would be child tag properties that would pass the raw content through
enclosed in CDATA tags or not and the container or bead would have a
sanitize properties that could be set to true or false.

The purpose would be to allow HTML embed content. Say you want to drop a
Google maps widget or rich text editor into your Flex JS app. You don't
want the compiler to parse that code. You would just want app to write the
raw HTML to the document in the container it is declared in. You would be
responsible for the security as the author and how to talk to it.

The before and after properties would allow things like HTML comments or
other uses. In the past you had php code that wraps HTML markup but now it
could be used for some of the other frameworks out there to use markup to
perform other tasks.

How that will work with the Flex JS model new App(); I'm not sure.

On Jan 1, 2017 3:16 AM, "OmPrakash Muppirala"  wrote:

> On Sun, Jan 1, 2017 at 12:15 AM, Alex Harui  wrote:
>
> >
> >
> > On 12/31/16, 11:23 PM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala"  wrote:
> > >
> > >Okay, I see your point now.  To be clear, I did not set out to write
> HTML
> > >code.  The bio in team.json is a html snippet.  So, I am just trying to
> > >display it as a piece of formatted data.  Even in other projects, I do
> > >need
> > >this kind of thing quite often.
> >
> > IMO, this is use case #1: non-interactive HTML content.  We could just
> > have an HTML component with an "html" property.  But it would want to
> wrap
> > the content in a  or 
> >
>
> This is all I wanted.  I implemented this and it seems to work fine.
>
>
> >
> > Case #2: In MXML, someone wants to mix FlexJS elements with random HTML.
> >
> > Case #3: In MXML, someone wants to put in random HTML where one child
> HTML
> > tag has an id and wants to write code that addresses that id.
> >
> > The cheap option is to only support #1 by creating an HTML component with
> > an "html" property.  Everything else needs more thinking, IMO.
> >
>
> 2 and 3 sound like terrible ways to code :-)
>
>
> >
> > >
> > >That brings up a related concern.  We need to sanitize such html content
> > >during runtime [1]
> >
> > IMO, those are just utility functions.  Not everybody needs sanitization,
> > IMO, so PAYG.
> >
>
> Hmm, to play the devil's advocate, security should not be pay-as-you-go.
> This should be opt-in by default.  Someone will have to go the extra mile
> to turn it off.
>
> This is the sort of thing that will go out in the wild and folks will get
> affected by it soon enough.  We will then need to push out an emergency
> release to fix an XSS attack made possible by FlexJS.
>
> Either that or we call the default implementation 'InsecureHTMLText' or
> something like that.
>
>
> >
> > >>
> > >>Not really sure why this is required.  I am looking for usage patterns
> > >>like
> > >>this:
> > >>
> > >>
> > >>{myFancyHTMLText}
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>I guess the HTMLText component has to be a UIBase for this to work,
> > >>right?
> > >>
> > >>Maybe I am not understanding the point you are trying to make.
> > >
> > >The above would likely create an HTML DOM like:
> > >
> > >
> > >  the HTML from myFancyHTMLText
> > >  
> > >
> > >
> > >
> > >Carlos asked earlier about getting rid of the Span since we all know it
> is
> > >legit to have the HTML DOM look like:
> > >
> > >
> > >  The HTML from MyFancyHTMLTExt
> > >  
> > >
> > >
> > >
> > >I doubt if this HTML can be generated.  Are you sure there will be a
> > >linebreak after the text?
> >
> > No.  I just added that to show the "children".
> >
> > >
> > >That looks a TextNode element.  Which is lightweight than innerHTML  But
> > >are we sure we don't want formatting for such text?  If we want to be
> able
> > >to format, we need to use a p or a span element.
> >
> > AIUI, a TextNode is just plain text.  If the above was:
> >
> > 
> >   The HTML from MyFancyHTMLTExt.
> >   
> > 
> >
> > There would be a TextNode for "The", a Bold node for "HTML", another
> > TextNode for "from" etc.
> >
>
> What I meant was that HTML could be achieved by using the
> document.createTextNode() function which creates a TextNode element.  i.e.
> no need for a wrapping element like P or Span.  Sorry for the confusion.
>
>
> >
> >
> > This doesn't feel right to me.  All of us seem tempted to want to define
> a
> > scrap of complex HTML separate from other child controls in a container.
> > If there was an HTML control, it would still add a wrapping 

Re: Number of operations per function

[flex capacitor]

Thanks. I read those blog posts in the past but had missed that one.

So when a company advertises last years device can do 1 teraflop and this
years device can do 2 teraflops that doesn't mean twice as fast or twice as
many FPS? It's only twice as fast if they are doing the same exact
operation as the first test (like only adds or only multiply operations)?


On Fri, Dec 23, 2016 at 5:40 AM, Vincent <vinc...@after24.net> wrote:

> Hi,
>
> I don't know if it can be useful but Jackson Dunstan wrote several
> articles about loop speed : http://jacksondunstan.com/articles/358
>
> Cheers
>
>
> Le 22/12/2016 à 22:20, flex capacitor a écrit :
>
>> I have a case where I can write a function a few different ways and since
>> Flash Player doesn't provide a microtime only getTimer() I'm trying to
>> find
>> a way to get the number of operations that are occurring in each different
>> method.
>>
>> For example, I have 3 different ways to get the results I want
>>
>> for (var i:int;i<array.length;i++) {}
>> for (var prop in object) {}
>> for each (value in object) {}
>>
>> each gets the result I'm looking for. But what I want to know is if there
>> is a way to know how many operations are being run on the CPU from a
>> specific statement, a specifc block of code or a specific function. I know
>> about the Flash Builder profiler and Scout but I see only sample time
>> which
>> I'm not looking for just operation counts.
>>
>> I might be running this on a microcontroller that has limited CPU. So
>> instead of 1 teraflop I might have 1000 operations.
>>
>> I guess that also begs the question are all operations equal at the CPU
>> level?
>>
>>
>

Number of operations per function

[flex capacitor]

I have a case where I can write a function a few different ways and since
Flash Player doesn't provide a microtime only getTimer() I'm trying to find
a way to get the number of operations that are occurring in each different
method.

For example, I have 3 different ways to get the results I want

for (var i:int;i

Converting JavaScript libraries to AS3

[flex capacitor]

There's a few large libraries out there that are written in JavaScript.
I've been working with them and am disappointed it's not AS3 for obvious
reasons. Since the community has been working on cross compiling AS3 to JS
is there any work on taking a JavaScript library and parsing it into a AS3
class? I'm not talking about creating a swc that you drop in and then you
have code completion in Flash Builder (I think this is externs?). I'm
talking about taking a github library or source and parsing it into AS3
classes.

Even if we may eventually cross compile that AS3 library back to JS I'd
rather import the JS library, and then work with that AS3 version of it.

Also, we as a community are catering to the JS community by converting AS3
down to JS. Can we rather convince developers to write their libraries in
AS3 from now? I mean is that already possible (it's early morning here hope
this makes sense)? I know we are working on frameworks like FlexJS but I'm
talking about addressing the thousands of libraries written in JS. My
thought on that is, along with everything else we're doing and all the
progress we've made over the years, if it's already possible to convert AS3
to JS would making Flash Builder free draw JS developers to use AS3 for
their libraries going forward?

PS Sick and tired of catering to JS from 1995

How to register a list of classes to be able to parse an MXML document that uses namespaces

[flex capacitor]

I'm parsing an MXML document and then creating the elements. This would
allow me to show a live preview of an MXML document at runtime. So far what
I have is based using my own XML document that has a list of components in
where the node name was a one to one match with a qualified class name.





And I have been, for the time being, mostly ignoring the namespace and just
using the Spark component set.

But now it's necessary to support separate namespaces and each namespace
can have it's own user defined prefix. So my goal now is to parse an MXML
document and get the correct class for the XML node.

I'm having difficulty with this. Mainly there are four parts that are
interrelated: the prefix, the namespace, the node name and the definition.

I've found a few things to help though. SimpleXMLEncoder, XMLEncoder,
XMLDecoder, SchemaTypeRegistry, SchemaManager. These are all Flex excluded
classes.

I have something working but it's hacky, and it feels like something is
missing so I don't want to start off on that and it's fragile since it
doesn't handle certain scenarios. Before I post any of the code I've been
working on can someone suggest how they'd do it?

Plus, using the classes above, like SchemaManager and SchemaTypeRegistry
etc, it seems they expect an XSD for the object definitions (like Button).
I couldn't find and XSD for the Adobe or Apache Flex component set. Up
until now I've been able to parse MXML using the information in the
metadata of the classes and that seems to work fine for the most part but
again I wouldn't mind hearing suggestions on that as well.

Also, I'm attempting to parse an MXML document at *runtime*, not compile
time.

PS. Some research has lead me to ~FlexSDK/frameworks/flex-config.xml. That
file lists namespaces and manifests that list the classes in those
namespaces.

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

[flex capacitor]

In Radiate I convert Flex UIComponents to HTML components and had this
problem. I made an option to allow styles to be defined inline or in a
style sheet. If the option was stylesheet then if the component had an id
the styles were declared by id. This included position, size, etc:

#myLabel {
 style: value;
}

If the component didn't have an id too bad. I'd give it an id using Flex
naming utils class and again declare styles there.

But I added an option to let developers override the styles per component
and that might work here.

So you would have a components style declaration by id and then in Radiate
there is a user styles field. Any values in that field would be declared in
the style declaration but they would be placed at the end. Everybody knows
that last declaration wins, even grandma.

#myLabel {
 style: value; /*define by framework */
 style: newValue; /*  defined by user */
}

You could also declare style: inherit and I think that resets the value.
Yes, the style is declared twice. Who cares. But yes to look pretty, I plan
to remove the first declaration or comment it out in a future update.

If Flex JS made some combination of class and class#id it might be an
option so that you can declare your own style declaration afterwards and
restore the defaults. Yes there might be two style declarations but at
least then they wouldn't be defined inline.

On Dec 2, 2016 11:52 AM, "Carlos Rovira" 
wrote:

> Hi Josh,
>
> right. As I get some few components more, I think I could refactor removing
> the dependencies from some HTML comps so we could manage better MDL set. So
> for example, I will took things from Core, like UIBase or ContainerBase
> while removing html things like TextButton, Container and so on...(in the
> end removing HTML.swc dependency at all). In this way I think MDL will be
> more independent.
>
> 2016-12-02 16:55 GMT+01:00 Josh Tynjala :
>
> > Alex's first point about using the same beads, but not subclassing sounds
> > cleaner to me, Carlos. Kind of the same idea from the other day where all
> > components should be possible to recreate from UIBase with the right set
> of
> > beads. You should consider trying that out for MDL.
> >
> > - Josh
> >
> > On Dec 1, 2016 11:09 PM, "Alex Harui"  wrote:
> >
> > > Re-ordering your post so I can address higher-level points first:
> > >
> > >
> > > On 12/1/16, 4:55 PM, "carlos.rov...@gmail.com on behalf of Carlos
> > Rovira"
> > >  wrote:
> > > >
> > > >But Basic set is at the core of
> > > >all. Is at the core of MDL set
> > > >
> > > >
> > >
> > > This statement doesn't have to be true, and makes me think that the old
> > > Flex SDK mentality is persisting.  IMO, the MDL set has no obligation
> to
> > > subclass the Basic set.  The top-level components in the Basic set are
> > > supposed to be compositions of beads.  MDL can just compose the same or
> > > different beads without having to subclass Basic components.
> > >
> > > One of the problems of having a core and inheritance is that you have
> to
> > > get it right, but often there isn't one right answer.
> > >
> > > >I think
> > > >Basic set (as is) will not be used at all since the final visuals are
> > not
> > > >production ready, so you know people will need this level of
> > customization
> > > >or they will never join FleJS for sure. and here you have the first
> > > >example of many
> > > >of the styles in flexjs needs to be removed in order to get the MDL
> > branch
> > > >working ok, and so will happen with others like Bootstrap, and so
> on...
> > > >Only if we create our own FlexJS style design could take into account
> > the
> > > >actual styles, but I think that if MDL or Bootstrap does not need all
> of
> > > >that, we should not need creating our own CSS set in the end (I can't
> > say
> > > >much more here since I'm not a CSS expert to affirm that, but based on
> > > >what
> > > >I see...is clear that it's the reality).
> > > >
> > >
> > > In my mind, there are going to be two kinds of themes: pre-existing
> ones
> > > like MDL and custom ones like the themes that regular Flex SDK
> customers
> > > used to brand their applications.  In the second kind, I don't think it
> > > matters as much as to what default styles are. Folks will simply
> override
> > > the defaults in their themes.
> > >
> > > I was a bit surprised that MDL didn't override everything we set as
> > > defaults for HTML.swc.  That means to me that if someone has certain
> > > styles set elsewhere, even in their browser settings, that could cause
> > > really strange and unexpected results.  But OK, that's the way it is,
> and
> > > so we should think of other ways to have a default look for HTML.swc,
> > > although again, as I said above, the MDL library has no obligation to
> > > inherit from HTML.swc.
> > >
> > > If we really need to support more inheritance, 

Flex as an operating system

[flex capacitor]

Was Flex going to be an operating system at some point? The way it's setup
allows you to load multiple applications into a system manager. Each of
those applications can be moved and sized. Pop ups appear over all of them
and they each have their own invalidation cycle. Was there ever a plan for
FlexOS?

Getting the DefaultProperty metadata

[flex capacitor]

I've been trying to get the DefaultProperty metadata that's set on some
components and I can't find it anywhere. I'm using the following call to
get the describeType XML:

var describedTypeRecord:DescribeTypeCacheRecord =
mx.utils.DescribeTypeCache.describeType(BorderContainer);var
typeDescription:* = describedTypeRecord.typeDescription;


The first node is:



The default property for BorderContainer or SkinnableContainer is
mxmlContentFactory:

I've set the compiler argument here:

-keep-as3-metadata+=DefaultProperty

and still nothing.

Can someone look in the compiler and see if it's being included?