Yes, I know.My answer was to clarify Erels' comment.
I don't know what this code is doing however you can change the text color like this:
Two points about it:For these properties, the user enters native colors, like for any other view / node, which means Color as Int in B4A and B4i and Color As Paint for B4J.
lbl.TextColor = xui.COLOR_RED 'or 0xFFFF0000
In mine App, I do not even use the XUI , also because I develop only small personal things with B4J but I generally use VB.Net. For me it is only an academic exercise.I personally dont use XUI. In my opinion each platform should have his own views and it would be wrong to try to have same views for all platforms.
People that are used to ios will not like to see an ios app with android characteristics and the same for android users.
I understand the xui is trying to do that (use native views for each platform) but i think it will reach a point where u will make compromise and loose the os filling and make them too similar.
In mine App, I do not even use the XUI , also because I develop only small personal things with B4J but I generally use VB.Net. For me it is only an academic exercise.
But I like the idea a lot, as I said before I'm fascinated by Delphi that the same code compiles it for Windows Android and iOS, with the possibility to access specific features of the system if you want to compile only for a specific system . Just like Unity does for many platforms.
So I have something uniform I like, but I agree with you that if it is not necessary to go on specific language
In my opinion each platform should have his own views
That "view" does not mean "a standard GUI view", means "point of view".The second point is important. XUI types provide a different "view" or a different wrapper above the same native objects. They do not replace the native types.
What you wrote is wrong. Try to use it and you will see. XUI just provides a different API to the exact same native views.I personally dont use XUI. In my opinion each platform should have his own views and it would be wrong to try to have same views for all platforms.
People that are used to ios will not like to see an ios app with android characteristics and the same for android users.
I understand the xui is trying to do that (use native views for each platform) but i think it will reach a point where u will make compromise and loose the os filling and make them too similar.
I would preffer erel concitrate on adding more native properties to the views instead of using native object to access them.
Cross platform is the main reason to use XUI framework.I still don't get the need of it (except cross platform)
I'm trying to do just that.In my opinion, the way with the XUI framework is wrong.
I expect a B4x platform to do it all with the IDE.
If I have a label in B4a then it should have the same property in B4i as if you were using the XUI framework, just so it makes sense to me.
The more I use the XUI framework, the more I'm convinced that the design behind it is very good. It exposes all the methods common to the three platforms, in a convenient way, and it allows you to easily access the platform specific features.In my opinion, the way with the XUI framework is wrong.
Creating custom XUI views that wrap the native views will not add anything useful. It will just limit the developer and make things more complicated.Custom XUI views that have the same properties on all platforms