I had forgot the other reason for bringing up this up but I remember it
now.
When creating mobile apps I try to support both portrait and landscape
modes. The Flex framework has some support for this built in. When you
switch from portrait to landscape and you have a state named portrait or
On 6/10/13 6:53 PM, flexcapaci...@gmail.com flexcapaci...@gmail.com
wrote:
I had forgot the other reason for bringing up this up but I remember it
now.
When creating mobile apps I try to support both portrait and landscape
modes. The Flex framework has some support for this built in. When you
The PROP_CHANGING/PROP_CHANGED event pair concept is interesting, even if I
still don't get the whole picture of how it will be working.
However, please note that I was writing thinking about possible (and
incremental) improvements the current MXML states management of Flex 4.x,
personally I
@alex The polymer project has an interesting take on the conditionals
you're proposing.
Some examples:
https://github.com/Polymer/mdv/blob/master/examples/how_to/conditional_template.html
https://github.com/Polymer/mdv/blob/master/examples/how_to/conditional_attributes.html
On Fri, Jun 7, 2013
On 6/5/13 9:00 PM, flexcapaci...@gmail.com flexcapaci...@gmail.com
wrote:
Thanks for this input as well.
Alex, what would currentState look like as a organizing property?
It would look like it does now. By organizing property I mean a
property that you assign semantics to to change the UI.
On Thu, Jun 6, 2013 at 1:33 AM, Alex Harui aha...@adobe.com wrote:
I like these:
currentState.mouse = up;
currentState = up-focused-nonDefault;
They look like something that can be done. In this case, maybe separate
with spaces to promote a more CSS type of syntax? This might be
Yeah. I like the state delegates. What if you took it one step further and
added inline states?
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
s:Group id=focusGroup
s:states
s:State name=nonFocused/
s:State name=focused/
Probably just a sintax choice: having them all toghether could be useful to
quickly have an outlook of the states stuff when you open an MXML document,
instead of searching for a number of sparse s:states blocks (they are the
state of the main MXML component, after all) - on the other hand,
Good stuff.
Today, you can sort of do this with fx:Declarations/fx:Component, but it
isn't in-line, just in the same document. Do either of you have a skin or
component that could truly take advantage of that?
And still, you end up writing code to set currentState according to some
other set of
AFAIK:
- currently states also play a role in the skinning contract of a
skinnable component (skinStates)
- states are supported by transitions management
The first one maybe could be dropped, resulting in a relaxed skinning
contract: the button may have bindable model properties such as
To be clear, I'm mainly concerned about how to implement this in FlexJS.
I'm not planning to try to upgrade or retrofit this into the current Flex
SDK, but someone else is certainly welcome to take that on.
My thoughts around effects in general is that, in FlexJS, you have
replaceable models.
This became a long email. TLDR section at the end.
I went back and checked on the inherits property and it turns out it is
basedOn. I don't remember seeing any documentation on this but it appears
to work:
s:states
s:State name=state1/
s:State name=state2/
s:State
...@gmail.com]
Sent: Saturday, June 01, 2013 4:41 AM
To: dev@flex.apache.org
Subject: Re: Multidimensional States
How is that different from the already existing
stateGroups
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e
3d11c0bf63611-7ffa.htmlproperty?
On Sat, Jun 1, 2013 at 12
Side thought... will we have an Apache Flex namespace?
-Mark
-Original Message-
From: Sebastian Mohr [mailto:flex.masul...@gmail.com]
Sent: Tuesday, June 04, 2013 12:45 PM
To: dev@flex.apache.org
Subject: Re: Multidimensional States
+1
Replacing currentState:String
Hi,
Side thought... will we have an Apache Flex namespace?
We already do look at the apache and experimental projects.
Justin
the 'stateGroups' way to the 'multidimensional states' way.
Here's what that Button's States might look like with 'stateGroups'.
s:states
s:State name=up stateGroups=upStates,normal/
s:State name=down stateGroups=downStates,normal/
s:State name=over stateGroups
-specific state.
Bill Turner
Enterprise Software Engineer
First Pacific Corporation
(503) 588-1411 ext. 2303
bi...@firstpac.com
-Original Message-
From: John Cunliffe [mailto:mahn...@gmail.com]
Sent: Saturday, June 01, 2013 4:41 AM
To: dev@flex.apache.org
Subject: Re: Multidimensional States
AM, Maxime Cowez maxime.co...@gmail.com wrote:
I'd like to make this more concrete. Let's take Alex' Button example
and
compare the 'stateGroups' way to the 'multidimensional states' way.
Here's what that Button's States might look like with 'stateGroups'.
s:states
s:State name
Enterprise Software Engineer
First Pacific Corporation
(503) 588-1411 ext. 2303
bi...@firstpac.com
-Original Message-
From: John Cunliffe [mailto:mahn...@gmail.com]
Sent: Saturday, June 01, 2013 4:41 AM
To: dev@flex.apache.org
Subject: Re: Multidimensional States
How is that different from
On 6/1/13 3:28 AM, flexcapaci...@gmail.com flexcapaci...@gmail.com
wrote:
I've been coming across more and more cases where it would be great to
have
support for multidimensional states. What this looks like and how it's
used
I'm not sure. Maybe we can discuss ideas.
Yes, let's discuss. I'm
, stateGroups we can live
without.
just my 2 cents,
Arnoud
On 02-06-2013, at 08:49, Alex Harui aha...@adobe.com wrote:
I've been coming across more and more cases where it would be great to
have
support for multidimensional states. What this looks like and how it's
used
I'm not sure. Maybe we
I'd like to make this more concrete. Let's take Alex' Button example and
compare the 'stateGroups' way to the 'multidimensional states' way.
Here's what that Button's States might look like with 'stateGroups'.
s:states
s:State name=up stateGroups=upStates,normal/
s:State name
and
compare the 'stateGroups' way to the 'multidimensional states' way.
Here's what that Button's States might look like with 'stateGroups'.
s:states
s:State name=up stateGroups=upStates,normal/
s:State name=down stateGroups=downStates,normal/
s:State name=over stateGroups
I've been coming across more and more cases where it would be great to have
support for multidimensional states. What this looks like and how it's used
I'm not sure. Maybe we can discuss ideas.
Alex wrote on the FlexJS wiki page,
*States were used often but had a limitation once the set
to have
support for multidimensional states. What this looks like and how it's used
I'm not sure. Maybe we can discuss ideas.
Alex wrote on the FlexJS wiki page,
*States were used often but had a limitation once the set of states you
wanted started having dimensions. For example, the Flex
/using/WS2db454920e96a9e51e63e3d11c0bf63611-7ffa.html
property?
On Sat, Jun 1, 2013 at 12:28 PM, jude flexcapaci...@gmail.com wrote:
I've been coming across more and more cases where it would be great to
have
support for multidimensional states. What this looks like and how it's
used
I'm
?
On Sat, Jun 1, 2013 at 12:28 PM, jude flexcapaci...@gmail.com wrote:
I've been coming across more and more cases where it would be great to
have
support for multidimensional states. What this looks like and how it's
used
I'm not sure. Maybe we can discuss ideas.
Alex wrote
27 matches
Mail list logo
