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
> 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 "
S/flex/using/WS2db454920e96a9e51e63e3d11c0bf63611-7ffa.html
> >property?
>
>
> On Sat, Jun 1, 2013 at 12:28 PM, jude 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
flex/using/WS2db454920e96a9e51e63e3d11c0bf63611-7ffa.html
> > >property?
> >
> >
> > On Sat, Jun 1, 2013 at 12:28 PM, jude wrote:
> >
> > > I've been coming across more and more cases where it would be great to
> > have
> > > support f
On 6/1/13 3:28 AM, "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
Flex, stateGroups we can live
without.
just my 2 cents,
Arnoud
On 02-06-2013, at 08:49, Alex Harui 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
>
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&#x
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'.
>
>
>
>
&
ng to work on the JS side.
>
> Then you just have:
>
>
>
> And CSS like:
>
> .buttonFocusBorder#focusBorder[emphasized] {
> left: -2;
> }
> .buttonFocusBorder#focusBorder {
> left: -1;
> }
>
> .buttonBackground#background[emphasize] {
> col
could help with some meaningful state combinations like orientation and an
app-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,
find ways to make databinding much faster in
>> FlexJS.
>>
>>
>>
>> And one final thought: In FlexJS, we may end up saying that you
>>shouldn't
>> specify these visual aspects in the "skin". Instead, you might want to
>> use mor
.
>
>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:
> >
> >
> >
> >currentState.mouse = "up" // Change just the mouse group
> >state
> >
> >I agree that having too many substates says there's something wrong, but
> >this could help with some mean
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 with
Hi,
> Side thought... will we have an Apache Flex namespace?
We already do look at the apache and experimental projects.
Justin
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:
On 6/5/13 9:00 PM, "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. Other properties
Multiple states using spaces (e.g. currentState="up default") looks nice to
the eyes.
I was thinking about impact on the transitions management - I'm not sure
that the current transition approach (fromState/toState) scales well once
we go this way.
A possible idea could be to support "state deleg
On Thu, Jun 6, 2013 at 1:33 AM, Alex Harui 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
Yeah. I like the state delegates. What if you took it one step further and
added inline states?
On Thu, Jun 6, 2013 at 2:12 AM, Cosma Colanicchia wrote:
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 blocks (they are the
state of the main MXML component, after all) - on the other hand, defining
them i
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 isF
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. The
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 don't
@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 at
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
"lan
On 6/10/13 6:53 PM, "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
>switch from port
28 matches
Mail list logo
