Re: [FlexJS] Support in BlazeDS communication

[Alex Harui]

On 11/4/16, 11:12 AM, "PKumar"  wrote:

>Thanks Alex, I am new to FlexJS and your comments are really helping me
>improve my FlexJS understanding.
>Regarding  tag,  is there any option/command available  so
>that
>compiler automatically include the injected file in to output folder.

The compiler doesn't do that today.  I'm not sure it should.  Shouldn't we
be encouraging the usage of external scripts from off the internet instead
of local copies?

There is a separate discussion going on right now about copying local
"other stuff".  It may be that if you happen to want to use a local copy
there is a way to have that local copy copied to the output folder, but
you'd have to get the remote copy yourself.  I'm not sure about having a
compiler download something and place it locally.

>
>I am also planning to compile RemoteObject with FlexJS. I checked the
>AMFChannel implementation and found that  AMFChannel containing the flash
>netConnection & netStatus related code. So i will wrap the flash flash
>dependent code inside COMPILE::SWF block and will wrap amfjs
>implementation
>inside COMPILE::JS block. Please suggest on this also.
>

Sounds great!  It will be interesting to see what other Flash dependencies
you run into.

Good luck,
-Alex

Re: [FlexJS] Support in BlazeDS communication

[PKumar]

Thanks Alex, I am new to FlexJS and your comments are really helping me
improve my FlexJS understanding. 
Regarding  tag,  is there any option/command available  so that
compiler automatically include the injected file in to output folder. 

I am also planning to compile RemoteObject with FlexJS. I checked the
AMFChannel implementation and found that  AMFChannel containing the flash
netConnection & netStatus related code. So i will wrap the flash flash
dependent code inside COMPILE::SWF block and will wrap amfjs implementation
inside COMPILE::JS block. Please suggest on this also.



-
Regards,
Prashant
--
View this message in context: 
http://apache-flex-users.246.n4.nabble.com/FlexJS-Support-in-BlazeDS-communication-tp11562p14048.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Less athen in MXML

[Jay Wood]

On 11/4/2016 9:16 AM, Clint M wrote:



On Fri, Nov 4, 2016 at 9:08 AM, scott matheson  wrote:


hi
How to do write  Less than in MXML  i have a head black, to near the
weekend almost beer time :)







--
Jay Wood
Tech4Learning, Inc.
http://www.tech4learning.com
http://www.pics4learning.com

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

[Alex Harui]

On 11/4/16, 1:56 AM, "OK"  wrote:

>Thank you Justin!
>
>Reading Alex hints I'm not sure what would be the right way:
>Keeping the material lib external or as part of Apache Flex.
>Probably both have benefits and also drawbacks.
>
>What do others think?
>Is anyone interested in a Material Design component set that is shipped
>with
>the SDK?

It is really up to Rui to decide where future development should be and
under what license.  Once that's decided, we can look into our options.

From a "bundling" stand point, it is probably possible for the Installer
to offer download of Rui's code even if it remains under GPL since it
would be an optional component.  So how we present it to our users can be
different from how it is being developed.

-Alex

Re: Less athen in MXML

[Clint M]

On Fri, Nov 4, 2016 at 9:08 AM, scott matheson  wrote:

> hi
>How to do write  Less than in MXML  i have a head black, to near the
> weekend almost beer time :)
>
> 
>
>

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

[Benjamin Povirk]

would be nice to have material set in the SDK

> On 4 Nov 2016, at 09:56, OK  wrote:
>
> Thank you Justin!
>
> Reading Alex hints I'm not sure what would be the right way:
> Keeping the material lib external or as part of Apache Flex.
> Probably both have benefits and also drawbacks.
>
> What do others think?
> Is anyone interested in a Material Design component set that is shipped with
> the SDK?
>
> Thanks,
> Olaf
>
>
>
> --
> View this message in context: 
> http://apache-flex-users.246.n4.nabble.com/Donating-Spark-Material-to-Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14040.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.

SAMO NASLOVNIKU! / ONLY FOR THE INTENDED RECIPIENT! Opozorilo: Ta elektronska 
pošta vsebuje informacije, ki so lahko zaupne narave in so namenjene samo 
naslovniku. Če je bilo zaradi napake v naslovu ali pri prenosu sporočilo 
poslano drugam, prosimo, da o tem obvestite njegovega avtorja. Če sporočilo ni 
bilo namenjeno vam, ne smete uporabljati, razkriti, širiti, kopirati, tiskati 
ali kakorkoli uporabiti informacije v sporočilu. Disclaimer: This e-mail 
contains proprietary information some or all of which may be legally 
privileged. It is for the intended recipient only. If an addressing or 
transmission error has misdirected this e-mail, please notify the author by 
replying to this e-mail. If you are not the intended recipient you must not 
use, disclose, distribute, copy, print, or rely on this e-mail.

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

[OK]

Thank you Justin!

Reading Alex hints I'm not sure what would be the right way:
Keeping the material lib external or as part of Apache Flex.
Probably both have benefits and also drawbacks.

What do others think?
Is anyone interested in a Material Design component set that is shipped with
the SDK?

Thanks,
Olaf



--
View this message in context: 
http://apache-flex-users.246.n4.nabble.com/Donating-Spark-Material-to-Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14040.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.