Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

@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

Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

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:

Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

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

Re: Multidimensional States

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:

Re: Multidimensional States

Hi, > Side thought... will we have an Apache Flex namespace? We already do look at the apache and experimental projects. Justin

RE: Multidimensional States

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

Re: Multidimensional States

> > > > > > > >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

Re: Multidimensional States

. > >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:

Re: Multidimensional States

Hi Cosma, Thanks for presenting this possible approach. -Alex On 6/3/13 12:45 AM, "Cosma Colanicchia" wrote: >Just trying to throw a quick thinking at it, in particular about the MXML >declaration mess - to avoid cartesian multiplication of states, couldn't >we >just normalize them? I mean, gr

RE: Multidimensional States

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,

Re: Multidimensional States

Just trying to throw a quick thinking at it, in particular about the MXML declaration mess - to avoid cartesian multiplication of states, couldn't we just normalize them? I mean, grouping them in mutually exclusive groups, which is the typical scenario:

Re: Multidimensional States

Hi Max, Thanks for detailing it out. In the relatively few minutes I've spent thinking about the problem, I pondered whether the answer is to expand on how s:State is used, or simply allow you to have conditional attributes based on things other than States. IMO, along with this set of States is

Re: Multidimensional States

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'.

Re: Multidimensional States

Hi, I figure you can use some input from the community for this. I personally never use stategroups as i find them a bit confusing. So I tend to structure my components the way that it's not needed and use the normal straightforward states. IMHO states are one of the key features of Flex, stat

Re: Multidimensional States

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, let's discuss. I'm actually finishing

Re: Multidimensional States

When I find myself pondering such a situation, I usually come to the conclusion it's time to split up my component into smaller ones: most of the times it's a signal that there's too much going in one view and I'm breaking "separation of concerns". Of course that's not true for *every* situation, b

Re: Multidimensional States

Usually I solve this by just overriding the getCurrentState method and a having all the posible options in the group. J On Sat, Jun 1, 2013 at 6:41 AM, John Cunliffe wrote: > How is that different from the already existing > stateGroups< > http://help.adobe.com/en_US/flex/using/WS2db454920e96

Re: Multidimensional States

How is that different from the already existing stateGroupsproperty? 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 mu