Hmmm.. it always seems to me that you are miles ahead cause you all already thought about so much stuff and how to implement it. So sometimes it's still a bit hard for me to follow and I am pretty sure that I always miss some things ;-)
So I would like to ask a maybe basically question: When I'd like to implement something like states using pure CSS and JS my understanding is that I have to write some of JS code to change the related display or visibility CSS attributes of the related elements. This would be a bit cumbersome. In contrast to this the benefit of MXML is that it does this job for me by just declaring some states in combination to define which components are whithin which state, is that right? What I don't understand is your concern regarding performance. If somebody needs this feature and add some beads I would expect that on JS side less code as possible is generated to achive this. Any additional line of JS is expensive maybe, but there is no other way to realise a SPA... am I wrong? Thanks, Olaf -- Sent from: http://apache-royale-development.20373.n8.nabble.com/
