Hi Yishay,
it seems that I've overlooked your repo.
Good idea and very helpful!!!
I'll also check out the states source code... hope
I'll understand the whole picture better.
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
As Alex mentioned upthread there's nothing preventing you from controlling
visibility according to state.
This [1] is an example of how you can use states to control an attribute or
inclusion in DOM.
[1] https://github.com/yishayw/Examples/blob/States/views/MainView.mxml
--
Sent from: http://
Olaf,
Current states mechanism in Royale (FlexJS) do not manipulate visibility.
It's make components disappear from the DOM - I think this is good after
more thinking. That's what distinguish it from simple manipulation of
visibility.
Piotr
2017-10-24 0:41 GMT+02:00 Olaf Krueger :
>
> Regardin
Regarding states I mean a minimal Implementation that just takes care about
the visibility of related components in different UI states.
Maybe my brain is completely resetted after the first 4 weeks on holiday and
I am writing complete nonsense, sorry for this ;-)
Olaf
--
Sent from: http://a
I also think that for now HTML, CSS, JS should be the focus...
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Olaf,
Just one clarification question - If you would like to write states
behavior in pure CSS/JS the same working as in current FlexJS ? Is this
what you mean ?
Piotr
2017-10-24 0:29 GMT+02:00 Olaf Krueger :
> Hmmm.. it always seems to me that you are miles ahead cause you all already
> though
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 l
Hi Peter,
I think you are right. Main need is to get AS3/MXML producing great
HTML/JS/CSS, and SWF right now is in second place.
I think it could be great to demonstrate that we can generate more outputs,
but maybe WebASM, swift (iOS) and Java (Android) could be great outputs as
well. But for this
I've been debating whether or not to send this, but given this discussion,
I think it is appropriate.
It is still unclear to me whether or not we code Royale with the priority
on HTML/JS/CSS platform or SWF. Alex and I have talked about this and
primarily the rule is: make it work for HTML/JS/CSS
display:none is hooked up to the visible property. You can use states to
change the visible property. IncludeIn/ExcludeFrom should operate on the
DOM since there is no "property" that affects that.
We could introduce an "includeInLayout" property that affects
visibility:hidden, but I found that
Hi Olaf,
Yes they are working and in my first simple tests they seems to be working
nicely with MDL module. I would not change their behavior in case of
removing. I would rather improve it using your suggestion.
1) If some element in state "X" wasn't display yet it should not exists in
the DOM -
>States removes element from DOM
I wonder why Royale states removes element from DOM instead of using the CSS
properties
visibility:hidden; (The element is hidden but still take up the same place)
or display:none (The element is hidden and take up no space);
Does somebody know what is the benefit
States seems to be working nicely :) One question I accidentally assign to
currentState wrong state and my content just disappear. What actually
should happen in that case. In my opinion - Should be thrown an exception.
Thanks, Piotr
2017-10-19 22:23 GMT+02:00 Piotr Zarzycki :
> Ahh! It was pro
Ahh! It was problem on my sight. In Application need to be declared
"SimpleStatesImpl"
[1]
[1] https://paste.apache.org/HEDa
Piotr
2017-10-19 22:14 GMT+02:00 Piotr Zarzycki :
> Harbs,
>
> States removes element from DOM, so this is very different than just
> setting visible to false, but agree
Harbs,
States removes element from DOM, so this is very different than just
setting visible to false, but agree with you that the results for the user
is the same.
Thanks for sharing your thoughts!
2017-10-19 22:06 GMT+02:00 Harbs :
> States cause elements to be added and removed.
>
> FWIW, I
States cause elements to be added and removed.
FWIW, I have found little reason to use States in Royale because setting
visible to false causes elements to take up no space. Hence I’ve never really
spent time looking into them.
Harbs
> On Oct 19, 2017, at 11:02 PM, Piotr Zarzycki
> wrote:
>
Hi Guys,
I'm trying to understand how states are working. I have simple code which
should actually work. I'm using latest FlexJS from develop - not Royale
yet. [1] Am I doing something wrong ?
Can someone shed some light how internally States are working ? I would
like to debug things, but not su
17 matches
Mail list logo