What I ran into with the drop in themes is that they sometimes change the
size and shape of the components. I had a project where I dropped in FlatUI
and the elements were all cut off because the width and height were
explicitly set. It wasn't hard to fix after the fact but some things
weren't size
I think as well that Material Design should be the base and Bootstrap would
be good as well, but for me in second place.
For SWF, I think FlexJS is more about HTML, so I will put all my efforts in
good-looking HTML and let SWF version to be wireframe looking with the
recipients to make the work, bu
For any included svg, it should not be linked files (to minimize HTTP
requests). It should either be Base64 in CSS, or injected into the HTML as
markup. It might be interesting to put together an SVG injector class which
would basically embed the raw SVG code into the JS and inject it into marku
After looking over the Material stuff and seeing what the FlexJS Basic
component set is capable of, I think a grayscale theme would be best. It
would be neutral to allow browser-specific colors in controls and focus
while still providing a decent look to the components.
I'll let everyone know when
Peter, I think the same, a good looking white-grey default theme would be
perfect as default.
Then people could customize or change theme.
Thanks
2016-06-15 16:06 GMT+02:00 Peter Ent :
> After looking over the Material stuff and seeing what the FlexJS Basic
> component set is capable of, I think
Sounds like there is consensus to implement Material. Again, though, I
would like to see the Basic components be as basic as possible: a for Button, a for Label, etc. AIUI, there is no way to get
control over every pixel. On my Mac, with the OS theme I've selected, the
browser is going to show
On 6/15/16, 12:11 AM, "jude" wrote:
>What I ran into with the drop in themes is that they sometimes change the
>size and shape of the components. I had a project where I dropped in
>FlatUI
>and the elements were all cut off because the width and height were
>explicitly set. It wasn't hard to fi
Hey guys!
I have a question on Apache Flex. The problem is next. Simple
spark.componentes.TextInput didnt understand utf letters. I mean that i can
enter only numbers and english letters from softkeyboard. but from other
languages i cant, for example russian letters. there are no restrictions.
lett
On 6/15/16, 11:03 AM, "Anton Bondarenko" wrote:
>Hey guys!
>I have a question on Apache Flex. The problem is next. Simple
>spark.componentes.TextInput didnt understand utf letters. I mean that i
>can
>enter only numbers and english letters from softkeyboard. but from other
>languages i cant, fo
1. Russian letters are showed in soft keyboard.
2. if im using input.text = "{%russian text%}" than all is fine.
3. when i want to enter text from softkeyboard letters are animated by
click but no text adding to input. if i change soft keyboard locale to
english letters are adding to input correct.
forgot to add than on PC works fine. thats problem on android device and i
didnt test on ios device
2016-06-15 23:36 GMT+04:00 Anton Bondarenko :
> 1. Russian letters are showed in soft keyboard.
> 2. if im using input.text = "{%russian text%}" than all is fine.
> 3. when i want to enter text fro
I couldn't find any mention of this problem on the internet so I don't
think it is a known issue. If you want to debug into it, try putting
keyDown, keyUp, and textInput event listeners and see what happens.
-Alex
On 6/15/16, 12:46 PM, "Anton Bondarenko" wrote:
>forgot to add than on PC works
i watched all i use and found that in textinputskin im using
richeditabletext
2016-06-16 0:15 GMT+04:00 Alex Harui :
> I couldn't find any mention of this problem on the internet so I don't
> think it is a known issue. If you want to debug into it, try putting
> keyDown, keyUp, and textInput eve
RichEditableText is a lot of code, but if you want to keep debugging, try
following whether it is getting the keyDown event or not and what happens
to it after it gets it.
-Alex
On 6/15/16, 1:21 PM, "Anton Bondarenko" wrote:
>i watched all i use and found that in textinputskin im using
>richedi
For some languages you may need to set the IME mode. But that seems to be
only for specific languages. I haven't used IME mode before but it looks
like you may need to set those properties. Harbs may know more about this.
http://flex.apache.org/asdoc/spark/components/supportClasses/SkinnableTextBa
before this new skin i used mobile skin for android and ios, which used
stagetextinputskin. But using hem i had a problem with softkeyboard. i
couldnt use number keyboard for example. its just ignored setting. Also in
some cases i couldnt prevent softkeyboardectivating event. thats why i
dicided t
IME is only necessary for CJK languages. Cyrillic languages should work with
regular input.
On Jun 16, 2016, at 12:03 AM, jude wrote:
> For some languages you may need to set the IME mode. But that seems to be
> only for specific languages. I haven't used IME mode before but it looks
> like you
Key_down and key_up events works for English letters but with Russian
handler doesn't receive this events. It's very interesting. Yes, IME works
only for CJK, there are 3 languages for it as I know.
For stage textinputskin a little correction: softkeyboardtype is working,
but I can't prevent softke
18 matches
Mail list logo
